Introduction

Getting started with EBPTO

EBPTO is a distributed, ens-compatible, open and extensible IP registration system. Own your IP, store portfolio, provenance, profile data and more—use it across web3.

Table of Contents
Developers
Sending Ether Using .ip Domains

EBPTO conforms to the ENS standard, which means you can integrate EBPTO into your dapp without changing any code. All you need is a Web3 provider that points to the EBPTO registry instead of the ENS registry. Here is example ethers.js code for creating an EBPTO-enabled provider, looking up an address, and sending 1 ETH to that address: const provider = ethers.getDefaultProvider({ name: "homestead", chainId: 1, ensAddress: '0xDd0Bc20FB93E3033C9282E322f897fC2997F7f92' }); const address =

General
Differences Between .ip and .eth Domains

Here are some key differences between .ip and .eth that you can put to use today. On-chain metadata. In order to give users true self-custody over their IP, the associated metadata must be available in a fully decentralized fashion. We achieve this through our on-chain rendering contract IPTokenRenderer. By contrast, all .eth NFT metadata is mediated by a centralized web2 server (https://metadata.ens.domains/). On-chain name validation. Through our IPRegistrationController, EBPTO prevents