Generate scopes, configure verification requirements, and test your integration with our comprehensive developer tools
Join our active Telegram community for instant support, code examples, and direct access to the Self Protocol team!
Get started by installing the Self mobile app to create your digital identity
Scan to download the app
Don't have a biometric passport? Generate a mock one for testing
Learn How βServer relayer for testnet, your wallet for mainnet
Configure PRIVATE_KEY environment variable
Celo Testnet (Alfajores)
β Compatible with Self Protocol
π‘ Which network should I choose?
Testnet: Free to use, perfect for testing and development
Mainnet: Real transactions, costs real money, for production use
Free testing environment
Production network
π‘ Pro tip: Start with Testnet to learn and experiment, then switch to Mainnet when you're ready to deploy for real users.
Hash the scope seed with your address or DNS to generate the scope value
The scope is the final value you set in your Self Verification contract. It's generated by hashing your scope seed π± with your address or DNS, creating a unique identifier for your verification requirements.
0/20 chars
Not set
Not set
π‘ What happens when you click deploy:
Use Case: Test your verification configs without spending real money or setting up wallets.
Configure what verification requirements users must meet
Try the βLoad Example Configβ button to see a sample setup with no verification requirements:
This creates an open configuration where all users can verify without restrictions.
Expected Config ID:
Set minimum age requirement. Leave at 0 to disable age verification.
Select countries to exclude from verification. Leave empty to allow all countries.
Note: OFAC (Office of Foreign Assets Control) compliance helps prevent transactions with sanctioned individuals and entities.
Configure PRIVATE_KEY in environment variables to enable server-relayed transactions
Read existing verification configurations by their config ID
Reading from: Celo Testnet (Alfajores)