✅For Sybil Providers

For those who want to get approved to our list of checks

Want us to add your verification process inside of our human registry?

Benefits

• Get people sent to you through our aggregator

• Have all the applications that emit our contracts automatically integrate yourself

Have a stamp idea and want the ecosystem to build it, post on github at https://nada.bot/request-stamp OR want to build an idea the ecosystem has had for stamp, check out the idea board at https://nada.bot/requests

Requirements

• Create a contract We prefer you deploy your contract under a named account, preferably as a subaccount like twitter.womrhol3.near so users can trust your entity for maintaining this contract. For example; say you create a contract that binds as twitter account to, you will create a helper function that can be called to view whether an account has successfully binded on both ends. You do not have to create a mapping contract method. For example we are not asking you return the twitter account ID, rather we just are trusting that you just verify if an account has compelted a certain check. For example on twitter.wormhol3.near you would have a method isTwitterVerified(accountId): bool. Currently it is up to the PotLock Sybil team to determine weights based on impact of check and trustworthiness of entity.

• Need a clear external link for users to do the "action" to update their account to the appropriate state to show up as "true" on your check. An example of this https://test.near.org/wendersonpires.testnet/widget/SybilProviderSimulator-Interface?contractId=sybilprovidersimulator-3.nadabot.testnet

This maybe a specific route of an existing application where you use a third party API that interacts with your contract. Make sure you application is integrated with NEAR Wallet Selector.

• Create a helper view method on a contract that takes in a accountid and returns a boolean

• Add the contract name and method

• Create a picture (uploads it to IPFS)

• A clear description of your verification process and what you are verifying

• Estimate gas user needs to verify stamp on your contract (not including what user needs to pay to add stamp to our contract ~0.01N)

How to Submit Check - (On Chain)

First login, click “A Custom Check”, then a form will appear. Submitting of the form requires a transaction

Add A Custom Check

Fill out all details about your form. Make sure you send a link. The best flow for users is to give an application link when after they verify their is redirect back to your check on nada.bot in order to streamline the need for users to also sign a verify transaction to add your stamp to their registry record. Also make sure to clearly describe steps and amount of gas needed.

Example of add a stamp / check

Check out our registry contract to understand how to make your check compatible

📃Our Contract

How It Works in Our System

• Afterward our bot prevention team will review the Check and then add a weight on it. (This weight can be changed)

• Give 2-3 business days to be verified

• You will then be available for other people to verify. After they verify with you they must add a stamp (requires gas) to get their own score up, See proof you are not a bot

• If we discover that bots are verifying with your system or any wrong doing your score can get eliminated or your check will be removed from the approve list.

Examples of Contracts Related to Sybil Providers

• Our Sybil Simulator Contract https://github.com/PotLock/core/tree/main/contracts/sybil_provider_simulator
• NEAR Social Profile Provider - check if someone has a relatively complete NEAR Social Profile https://github.com/PotLock/near-social-sybil-provider
• Integrations Contract used for Connected Contracts, Account Age, Farcaster, and Lens https://github.com/Prometheo/sybil-provider/tree/main/src
• Holoynm - https://github.com/holonym-foundation/v3-near-contract
• NDC I Am Human https://github.com/near-ndc/i-am-human/tree/master/contracts/human_checker (uses fractal face scan for detecting) https://nearblocks.io/address/registry.i-am-human.near (WIP)

  • I-Am-Human registry

    I am human is a registry contract that issues SBT based on Fractal's face verification to issue a SBT according to NEP 393. This was using in the first NDC election to verify humans for a vote. We leverage the registry is_human method to check if someone has a face scan without the need for PotLock's contributor to keep track or having a Fractal api.