Skip to content
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.

EIP-1577 - implement resolver contract changes #940

Closed
acud opened this issue Sep 19, 2018 · 3 comments · Fixed by ethereum/go-ethereum#19285
Closed

EIP-1577 - implement resolver contract changes #940

acud opened this issue Sep 19, 2018 · 3 comments · Fixed by ethereum/go-ethereum#19285
Assignees
Milestone

Comments

@acud
Copy link
Member

acud commented Sep 19, 2018

EIP-1062 has evolved into EIP-1577, which incorporates the use of multiaddr schemes into the resolver contract on ENS.

This allows clients to know from which Dstorage provider to request the content addressed hash directly from the resolver.

See:
https://ethereum-magicians.org/t/eip1577-multiaddr-support-for-ens/1969
status-im/status-mobile#6688
https://eips.ethereum.org/EIPS/eip-1577
ethereum/EIPs#1577

New contract: https://github.com/ensdomains/resolvers/blob/master/contracts/PublicResolver.sol

@acud acud added the web3 label Sep 19, 2018
@acud acud changed the title EIP-1062 - implement resolver method signature changes EIP-1577 - implement resolver contract changes Nov 25, 2018
@acud
Copy link
Member Author

acud commented Dec 17, 2018

related to ethereum/swarm-dapps#28

@acud
Copy link
Member Author

acud commented Jan 19, 2019

ref https://www.npmjs.com/package/content-hash for documentation

@cobordism
Copy link

In particular, Swarm needs to support the new resolvers with the multiaddr field.

For example the resolver deployed here: 0xd3ddccdd3b25a8a7423b5bee360a42146eb4baf3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants