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

Registrar contract according to ENS #1

Open
chriseth opened this issue Mar 10, 2017 · 7 comments
Open

Registrar contract according to ENS #1

chriseth opened this issue Mar 10, 2017 · 7 comments
Assignees

Comments

@chriseth
Copy link
Collaborator

chriseth commented Mar 10, 2017

This task is about writing a registrar contract following the ENS specification.

This contract should have an owner that can control it

@winsvega
Copy link

winsvega commented Mar 17, 2017

Found a concept article about ENS
https://medium.com/@_maurelian/explaining-the-ethereum-namespace-auction-241bec6ef751#.nbus1nr4f

The yellow paper proposal is here
ethereum/EIPs#162

Currently ENS is running on a test net and not available via Mist browser whatsoever

Here are some contract examples
ethereum/EIPs#137

@gumb0
Copy link
Member

gumb0 commented Mar 17, 2017

Some obvious links

devcon talk
https://youtu.be/pLDDbCZXvTE

documentation
http://docs.ens.domains/en/latest/index.html

source
https://github.com/ethereum/ens/

official web frontend
http://ens.domains

explorer
https://etherscan.io/ens

@gumb0
Copy link
Member

gumb0 commented Mar 17, 2017

ENS already has a defined contract for simple first-in-first-served registration https://github.com/ethereum/ens/blob/master/FIFSRegistrar.sol

@yann300
Copy link
Contributor

yann300 commented Mar 17, 2017

And by the way, I don't know what is the plan, but could be better to not delete/clear registered domain after the meetup.
Maybe together with that, we can code a Simple Resolver.
That will just resolve to an http link or email for now.

@gumb0
Copy link
Member

gumb0 commented Mar 17, 2017

@yann300 We won't clear the registered names after meetup. Maybe the clearing discussion was related to the last sentence in #3 description ? ("Furthermore, there should be at most one successful register attempt per sender.")

If we want at most one attempt per sender per meetup we need to keep track of who registered on this meetup in the proxy. And this will be cleared with deleting of proxy...

@gumb0
Copy link
Member

gumb0 commented Mar 17, 2017

So it seems to me that for this registrar contract we need at least:

  • simple register method like in the link above (allowed only for proxy)
  • Enabling of the proxy - either create new proxy or register the existing proxy address as active (allowed only for owner (i.e. multisig wallet from Research multisig usage #4)
  • Disabling of the proxy (allowed only for owner)
  • Transfer domain ownership back to the owner? (allowed only for owner)

@gumb0
Copy link
Member

gumb0 commented Mar 24, 2017

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

No branches or pull requests

4 participants