Proposal #382
Passed on 18 Dec 2022 with 96.0% of the votes for yes.
Yes
96.0%
97.6% without abstain
Veto
0.0%
of votes cast
Ended
18 Dec 2022
95.95%
of votes cast
1.71%
of votes cast
2.33%
of votes cast
0.00%
of votes cast
By voting YES on this proposal, you will signal that you approve of uploading the Resolver contract of Interchain Name Service (ICNS) to Osmosis chain. By voting NO on this proposal, you will signal that you disapprove of uploading the contract to Osmosis chain in its current form.
ICNS aims to provide a fair, readily adoptable naming protocol for any chain connected with IBC. It is chain-agnostic, supporting all Cosmos SDK-based and IBC-enabled chains that have registered their bech32 prefixes on the [Hidden link]. ****
The ICNS protocol will be implemented by three different contracts: NameNFT, Resolver, and Registrar. As users can claim their ICNS names by verifying their Twitter handles in its bootstrapping phase, these contracts will be in charge of verifying Twitter OAuth, minting NFT for the given user name, and keeping the list of addresses for each bech32 prefix.
All name resolutions will take place on the Osmosis blockchain initially, but it is expected that ICNS will switch to using an outpost model that allows each chain’s name resolution to happen locally by deploying address resolution contracts on other CosmWasm-enabled blockchains.
Please also note that there will be a multisig admin account(s) that is collectively owned by the initial committee of builders including Chainapsis, Cosmostation, Commonwealth, and Skiff, and it will be in charge of managing the three contracts of ICNS and adding/removing operators of Twitter OAuth verification.
This proposal would approve the deployment of Resolver contract, which is in charge of keeping the state of the list of addresses for each bech32 prefix, by maintaining a map of (user name, bech32 prefix) -> Adress(String) within it. Only the owner of ICNS is able to call the Resolver and set his/her address. Integrators and wallets are able to query via Resolver contract to receive the ICNS information using bech32 addresses.
More details can be found here:
Github: [Hidden link]
Official Announcement: [Hidden link]
Long Form Proposal (Commonwealth): [Hidden link]
Sha256 Checksum using cosmwasm/rust-optimizer:0.12.10 for the ICNS Resolver contract is: 5958d75b214a65593f54ec890feb957b2aeda33e42fabbfb66f89ccf244e746a
Commit hash used for compiling binary for contracts is efdae05456b3e400c97711f608ede67a9a75098c