Open chriseth opened 7 years ago
Found a concept article about ENS https://medium.com/@_maurelian/explaining-the-ethereum-namespace-auction-241bec6ef751#.nbus1nr4f
The yellow paper proposal is here https://github.com/ethereum/EIPs/issues/162
Currently ENS is running on a test net and not available via Mist browser whatsoever
Here are some contract examples https://github.com/ethereum/EIPs/issues/137
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
ENS already has a defined contract for simple first-in-first-served registration https://github.com/ethereum/ens/blob/master/FIFSRegistrar.sol
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.
@yann300 We won't clear the registered names after meetup. Maybe the clearing discussion was related to the last sentence in https://github.com/ethereum/ethendance/issues/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...
So it seems to me that for this registrar contract we need at least:
register
method like in the link above (allowed only for proxy)
This task is about writing a registrar contract following the ENS specification.
This contract should have an owner that can control it