vrfd.eth

vrfd.eth allows users to get their ENS name verified and receive a nice blue checkmark accross the ecosystem.

The way it works is users can open a case, supply as much information as they deem fit to prove they are the rightful owner, and stake ETH.

The case gets reviewed by (ideally) a DAO working group, and if approved the user gets their ETH back and a blue checkmark. If denied for spam, no funds are returned to the user, and if denied as incomplete a partial refund is offered.

From a developer perspective integrating with vrfd.eth is dead easy. Simply check if the users ENS name (ie. vitalik.eth) matches their vrfd.eth subdomain (ie. vitalik.eth.vrfd.eth), and voila, the user is verified.

If you would like find out case-specific information like the date of verification, and the people who approved it you can request those from the smart contract, or from ipfs.If you would like find out case-specific information like the date of verification, and the people who approved it you can request those from the smart contract, or from ipfs.

vrfd.eth uses the ENS subdomain functionality through the use of custom resolvers to allow for seamlessly issueing and controlling subdomains. Users are issued subdomains of vrfd.eth in the form of "luc.computer.vrfd.eth" and "vitalik.eth.vrfd.eth" to validate "luc.computer" and "vitalik.eth" accordingly. The Contract does not do OCR or DNSSEC validation as this is done in the frontend and decided on by the deciding working group.

When a user submits a case they are requested to sign the raw JSON data which is subsequently uploaded using filecoin. (Not fully implemented yet but ideally) the user chooses a currency of their choice to pay for the filecoin deal and then puts the link to the data in the case thats submitted to the contract.

Although the entire end-to-end technical implementation is not complete (due to hackathon pacing), we have put our best effort in the user experience in hopes to clearly illustrate what this aims to be like.