Skip to content

Latest commit

 

History

History
63 lines (40 loc) · 3.19 KB

SV-ENS.md

File metadata and controls

63 lines (40 loc) · 3.19 KB
Raw

SecureVote ENS For Stuff!

We use the .sv ENS tld via our own ENS contracts.

We then break things down by network: kov.sv, eth.sv, (TODO: etc.sv, rop.sv)

Kovan

  • Registry: 0xd6F4f22eeC158c434b17d01f62f5dF33b108Ae93 (stores .kov.sv names and allows admin of them - kovan only)
  • Registrar: 0xac9f51bab2a28525a1d2172ababa2be27423d48a (admins of this registrar can register .kov.sv names!)
  • Resolver: 0xc8c73829348cb15da4b0785a110017464fb8af51 (resolves ENS domains to addresses, text, ABIs, etc)

Mainnet

  • Registry: 0x30ff37d85c14000b6ba4192137fff59a3c22211f (stores .eth.sv, .etc.sv, .rop.sv, kov.sv - and other names.)
  • Registrar: 0x47f4A6B393a352f5e8De2bDe89Fa121e00A4835E
  • Resolver: 0xd784B7429ed0b2D0Ae9624bCFF1DE8D086f13Aa9

0.secvote.eth

The 0.secvote.eth domain on Eth Mainnet has a registrar set up at 0x2d070f5e32b02ee44021428bbab46f4af5ffb4f4. It allows any admins (secvote.eth is the only address so far with permissions) to register some subdomain of 0.secvote.eth. It's intended that this can be used for automated creation of various names.

You can see a test of this at max-test.0.secvote.eth initialized by this tx.

Registering a name:

AutoDeployer

If you have permissions with the auto-deployer send a tx to:

  • Kovan: autodeploy.kov.sv -- 0x55a529C654b67e17844230B625B8A2478d190F67
  • Mainnet: autodeploy.eth.sv -- 0x644226C0513D860395ac6ed3Aec4D8Ba761aBEF9
  • 0.secvote.eth: autodeploy.0.secvote.eth -- 0x5a8894775e14d238209080f66f4b3d886a298ea5

ABI: ./_distEns/SvEnsEverythingPx.abi

ABI Fragment:

[{"constant":false,"inputs":[{"name":"name","type":"string"},{"name":"resolveTo","type":"address"}],"name":"regName","outputs":[{"name":"node","type":"bytes32"}],"payable":false,"stateMutability":"nonpayable","type":"function"},{"constant": false,"inputs": [{"name": "name","type": "string"},{"name": "resolveTo","type": "address"},{"name": "domainOwner","type": "address"}],"name": "regNameWOwner","outputs": [{"name": "node","type": "bytes32"}],"payable": false,"stateMutability": "nonpayable","type": "function"}]

Tx: regName(string name, address toResolveTo) (or use regNameWOwner) - name should just be the subdomain - e.g. autodeploy in autodeploy.eth.sv

Manually

  • Choose network: .eth.sv, .etc.sv, .kov.sv, .rop.sv
  • On the relevant network
    • Call registerName on the Registrar (note: you need to use an account with admin permissions) - set your eth address as the owner
    • Calculate the node (namehash) using node package eth-ens-namehash => namehash.hash('my-name.kov.sv')
    • Call setResolver on the Registry for your chosen name w/ our resolver
    • Call setAddr on the Resolver

ENS General info

See the ENS docs for an intro overview of ENS.

Some Domains

  • kov.sv (Mainnet) - Points to registrar for kov.sv domains on Kovan
  • autodeployer.kov.sv - allows autodeploying names super quick in 1 tx
  • autodeployer.eth.sv - as above
  • index-2018-04-10.kov.sv