After a user injects their information on chain, they can request judgement from a registrar. Users declare a maximum fee that they are willing to pay for judgement, and registrars whose fee is below that amount can provide a judgement.
When a registrar provides judgement, they can select up to six levels of confidence in their attestation:
Unknown: The default value, no judgement made yet.
Reasonable: The data appears reasonable, but no in-depth checks (e.g. formal KYC process) were performed.
Known Good: The registrar has certified that the information is correct.
Out of Date: The information used to be good, but is now out of date.
Low Quality: The information is low quality or imprecise, but can be fixed with an update.
Erroneous: The information is erroneous and may indicate malicious intent.
A seventh state, "fee paid", is for when a user has requested judgement and it is in progress. Information that is in this state or "erroneous" is "sticky" and cannot be modified; it can only be removed by complete removal of the identity.
Registrars gain trust by performing proper due diligence and would presumably be replaced for issuing faulty judgements.
To be judged after submitting your identity information, go to the "Extrinsics UI" and select the
identity pallet, then
requestJudgement. For the
reg_index put the index of the registrar you want to be judged by, and for the
max_fee put the maximum you're willing to pay for these confirmations.
If you don't know which registrar to pick, first check the available registrars by going to "Chain State UI" and selecting
identity.registrars() to get the full list.
The image above reveals two registrars:
Registrar 0, FcxNWVy5RESDsErjwyZmPCW6Z8Y3fbfLzmou34YZTrbcraL charges 25 KSM per judgement
Registrar 1, Fom9M5W6Kck1hNAiE2mDcZ67auUCiNTzLBUdQy4QnxHSxdn charges 5 KSM per judgement
To find out how to contact the registrar after the application for judgement or to learn who they are, we can check their identity by adding them to our Address Book. Their identity will be automatically loaded.
Gavin Wood is registrar #0.
Chevdor is registrar #1. We pick that one.
This will make your identity go from unjudged:
At this point, direct contact with the registrar is required - the contact info is in their identity as shown above. Each registrar will have their own set of procedures to verify your identity and values, and only once you've satisfied their requirements will the process continue.
Once the registrar has confirmed the identity, a green checkmark should appear next to your account name with the appropriate confidence level:
Note that changing even a single field's value after you've been verified will un-verify your account and you will need to start the judgement process anew. However, you can still change fields while the judgement is going on - it's up to the registrar to keep an eye on the changes.
Clearing: Users can clear their identity information and have their deposit returned. Clearing an identity also clears all sub accounts and returns their deposits.
Clearing is done through the Extrinsics UI.
Users can also link accounts by setting "sub accounts", each with its own identity, under a primary account. The system reserves a bond of 2 EDG for each sub account. An example of how you might use this would be a validation company running multiple validators. A single entity, "My Staking Company", could register multiple sub accounts that represent the Stash accounts of each of their validators.
To register a sub-account on an existing account, you must currently use the Extrinsics UI. There, select the identity pallet, then
setSubs as the function to use. Click "Add Item" for every child account you want to add to the parent sender account. The value to put into the Data field of each parent is the optional name of the sub-account. If omitted, the sub-account will inherit the parent's name and be displayed as
parent/parent instead of
Note that a deposit is required for every sub-account.
Registrars can set a fee for their services and limit their attestation to certain fields. For example, a registrar could charge 1 EDG to verify one's legal name, email, and GPG key. When a user requests judgement, they will pay this fee to the registrar who provides the judgement on those claims. Users set a maximum fee they are willing to pay and only registrars below this amount would provide judgement.
To become a registrar, submit a pre-image and proposal into Democracy, then wait for people to vote on it. For best results, write a post about your identity and intentions beforehand, and once the proposal is in the queue ask people to second it so that it gets ahead in the referendum queue.
Here's how to submit a proposal to become a registrar:
Go to the Democracy tab, select "Submit preimage", and input the information for this motion - notably which account you're nominating to be a registrar in the
Copy the preimage hash. In the above image, that's
0x90a1b2f648fc4eaff4f236b9af9ead77c89ecac953225c5fafb069d27b7131b7. Submit the preimage by signing a transaction.
Next, select "Submit Proposal" and enter the previously copied preimage hash. The
locked balance field needs to be at least [TO ADD]. You can find out the minimum by querying the chain state under Chain State -> Constants -> democracy -> minimumDeposit.
At this point, EDG holders can second the motion. With enough seconds, the motion will become a referendum which is then voted on. If it passes, users will be able to request judgement from this registrar.
This tutorial is found on the Polkadot wiki and references Kusama (KSM) and DOT for the examples. An updated version will be displayed when Edgeware is supported.
ENS (Ethereum Name Service) is a system of smart contracts on the Ethereum blockchain which allows users to claim domain names like
bruno.eth. Supporting wallets can then allow senders to input ENS domains instead of long and unwieldy addresses. This prevents phishing, fraud, typos, and adds a layer of usability on top of the regular wallet user experience.
Note: You will need an ENS name and an Ethereum account with some ether in it to follow along with this guide. To register an ENS name, visit the ENS App or any number of subdomain registrars like Nameth. Note that if you're using an older ENS name, you should make sure you're using the new resolver. Visiting the ENS App will warn you about this if not. You will also need some way to use your Ethereum address - following this guide on a personal computer is recommended. Wallets like Frame and Metamask are safe and will make interacting with the Ethereum blockchain through your browser very easy.
Despite living on the Ethereum blockchain, the ENS system has multi-chain support. In this guide you'll go through the process of adding a KSM and DOT address to ENS. We cover both KSM and DOT to show two different approaches.
Note: DOT can currently only be added using the Resolver method. KSM can be added through both methods described below.
This guide is also available in video format on Youtube.
The ENS App allows an ENS domain owner to inspect all records bound to the domain, and to add new ones.
In the example above, the domain
bruno.eth has an Ethereum and a Bitcoin address attached. Let's attach a KSM account. First, click the
[+] icon in the Records tab.
Then, pick "Other Addresses", "KSM", and input the Kusama address:
After clicking Save, your Ethereum wallet will ask you to confirm a transaction. Once processed, the record will show up on the domain's page:
The same process applies to adding your DOT address.
Once the transaction is confirmed, your address will be bound to your ENS domain.
There is no wallet support for ENS names for either KSM or DOT at this time, but the crypto accounting and portfolio application Rotki does support KSM ENS resolution.