mirror
/
go-ethereum
mirror of https://github.com/ethereum/go-ethereum
2
0
Fork 1
Code Issues Releases Wiki Activity
Official Go implementation of the Ethereum protocol
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
10779 Commits
47 Branches
243 Tags
1010 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 78644f0377
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '78644f0377'
${ noResults }
go-ethereum/contracts/ens
History
Elad 67fc0377e1
contracts/ens: revert bmt to keccak256 (#19323) 		6 years ago
..
contract contracts, swarm: implement EIP-1577 (#19285) 6 years ago
fallback_contract contracts, swarm: implement EIP-1577 (#19285) 6 years ago
README.md contracts, swarm: implement EIP-1577 (#19285) 6 years ago
cid.go contracts/ens: revert bmt to keccak256 (#19323) 6 years ago
cid_test.go contracts/ens: revert bmt to keccak256 (#19323) 6 years ago
ens.go contracts, swarm: implement EIP-1577 (#19285) 6 years ago
ens_test.go contracts, swarm: implement EIP-1577 (#19285) 6 years ago

README.md

Swarm ENS interface

Usage

Full documentation for the Ethereum Name Service can be found as EIP 137. This package offers a simple binding that streamlines the registration of arbitrary UTF8 domain names to swarm content hashes.

Development

The SOL file in contract subdirectory implements the ENS root registry, a simple first-in, first-served registrar for the root namespace, and a simple resolver contract; they're used in tests, and can be used to deploy these contracts for your own purposes.

The solidity source code can be found at github.com/arachnid/ens/.

The go bindings for ENS contracts are generated using abigen via the go generator:

go generate ./contracts/ens

Fallback contract support

In order to better support content resolution on different service providers (such as Swarm and IPFS), EIP-1577 was introduced and with it changes that allow applications to know where content hashes are stored (i.e. if the requested hash resides on Swarm or IPFS).

The code under contracts/ens/contract reflects the new Public Resolver changes and the code under fallback_contract allows us to support the old contract resolution in cases where the ENS name owner did not update her Resolver contract, until the migration period ends (date arbitrarily set to June 1st, 2019).