Upload ICNS Contracts: Registrar Contract, Part 3

Description\nBy voting YES on this proposal, you will signal that you approve of uploading the Registrar contract of Interchain Name Service (ICNS) to Osmosis chain. \nBy voting NO on this proposal, you will signal that you disapprove of uploading the contract to Osmosis chain in its current form.\n## Details\nICNS 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 SLIP-173 repo.\n\nThe 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. \n\nAll 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. \n\nPlease 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 Registrar Contract, the main entry point for the users in registering and claiming a new record for ICNS. The Registrar contract also keeps a state of message counts for each user name.\n\nOracle verifiers will view the Twitter API for the users’ ID information and then relay it to the Registrar contract. This information would then be verified by different operators of the Registrar contract. When the verification has passed the passing threshold within the Registrar contract, and the Registrar contract would then send a message to the NameNFT contract to mint NFT for the given user name.\n\nMore details can be found here:\n\n1) Github: https://github.com/interchain-name/icns\n\n2) Official Announcement: https://medium.com/@icns/announcing-icns-the-interchain-name-service-e61e0c3e2abb\n\n3) Long Form Proposal (Commonwealth): https://gov.osmosis.zone/discussion/8372-upload-interchain-nameservice-smart-contractsn\n\nSha256 Checksum using cosmwasm/rust-optimizer:0.12.10 for the ICNS Registrar contract is: 8f99546cf4b24c37be87ff93c6aac967cde18d704187b0c9a9d09e2e251368c8\n\nCommit hash used for compiling binary for contracts is efdae05456b3e400c97711f608ede67a9a75098c