Native Redbelly is a permissioned-access network, so any wallet that writes to it (transacting, deploying, staking, running a node) must first be verified and enabled. A wrapped representation of RBNT on Ethereum or another chain is just a token on that chain, so it never touches Redbelly's native permission layer and needs no Redbelly onboarding. An exchange holding your wrapped RBNT will still run its own KYC, which is separate from Redbelly's.
Newcomer friendly, answer first
KYC and Wallet Activation on Redbelly Network
The clear, newcomer-friendly guide to getting verified and activating your wallet.
2 phasesVerify, then activate
1 issuerAverer handles verification
5 questionsAnswered plainly below
Start here
Quick check: do you need KYC?
Read one line, get your answer.
Rule of thumb
If your action touches the native Redbelly Network, you need KYC. If it only touches a wrapped token living somewhere else, you do not.
Official
| Sending transactions on native Redbelly mainnet | Yes |
| Deploying contracts on Redbelly mainnet or testnet | Yes |
| Staking RBNT on the native network | Yes |
| Running a Redbelly node | Yes |
| Holding wrapped RBNT on another chain | No |
| Trading wrapped RBNT on an exchange or another chain | No* |
*Not required by Redbelly. The exchange holding it will still run its own KYC.
Straight answers
The five questions, answered
The questions newcomers ask most, answered plainly, with the source called out.
One verified identity can enable up to 10 wallets. If your use case needs more than 10 wallets, you will need a separate verified identity to enable the additional ones.
Approval takes less than 30 minutes, and most verifications clear almost immediately. Clear, in-date document photos and a clean liveness scan are the biggest factors in getting approved right away.
Redbelly's Terms and Conditions state that services are not offered, and tax residents or people located there may not access the website, platform, or software tools, in these jurisdictions:
You must also not be located in a country under United States government embargo or designated by the US as terrorist-supporting, and must not appear on any US government list of prohibited or restricted parties.
Beyond this baseline, individual products and issuers on Redbelly can layer their own eligibility rules through Receptor, the network's credential protocol, for example requiring sophisticated-investor status for a specific asset. Check the specific product for its own rules.
If you are not a resident of, or located in, one of these jurisdictions and were blocked in the past, connect your wallet at the access portal and run the eligibility check again. Sources: Terms and Conditions, section 15, and Vine developer docs on eligibility.
Staking is a native-network action, and every native write action requires a verified, enabled account, so there is no staking without verification first. RBNT is the asset used for staking, transactions, and governance. The reason is accountability: Redbelly only lets known, verified participants secure the network, which is what its compliance-first design requires.
Step by step
How to complete KYC and activate your wallet
Two phases: verify your identity, then activate your wallet on-chain. Official
Phase A. Verify your identity
-
1
Open the official access portal
Go to access.redbelly.network. Select mainnet for real activity or testnet for building. Devnet is deprecated, so do not use it.
-
2
Connect your wallet
Redbelly is EVM-compatible, so a standard EVM wallet such as MetaMask works. The address you connect is the one your credential links to, so pick the wallet you actually intend to use.
-
3
Start verification with an accredited issuer
Verification is done by issuers such as Averer, not by Redbelly directly.
-
4
Submit your ID and pass the biometric check
Provide a valid photo ID document and complete a live selfie or liveness scan. Your documents stay inside the verification flow and are not published to the chain.
-
5
Receive your credential
On approval, a verifiable credential is issued to your wallet and lives there rather than in a public database.
Phase B. Activate your wallet
-
6
Enable your account
Back in the access portal, trigger the enable-account action. This self-enables your wallet with write access through Redbelly's access smart contract, and you sign the transaction in your wallet.
-
7
Confirm activation
When the transaction confirms, your wallet is active and you can transact, deploy, or stake within your eligibility.
Developer note. When deploying by script you may need to set the gas limit manually, and some tools such as Remix may show warnings you can ignore.
Be prepared
Documents you need
For the core network access credential, Redbelly requires a valid photo ID document, specifically a passport, verified by a biometric check. Official
Essential ID
Name and date of birth.
Passport
Passport-derived identity.
Driver's Licence
Licence-derived identity.
National ID
National-ID-derived identity.
Proof of Address
Address verification.
AML / CTF
Anti-money-laundering and counter-terrorism-financing screening.
Have ready before you start
- A valid, in-date passport
- A device with a camera, for the liveness step
- Good lighting
- The email or social login you want tied to your verification
- The wallet address you intend to enable
Where verification happens
Averer
Averer is the identity and verification layer most users interact with during Redbelly KYC. It is a Redbelly Network project that grew out of research at the University of Sydney and CSIRO. It issues reusable credentials on a verify-once, use-everywhere model, runs an embedded wallet behind a normal email or social login, covers gas so you do not need to hold tokens, and generates proofs on your device so your documents stay under your control.
Start verification only from the official Redbelly access portal or Averer's official domain, and never share a seed phrase.
- Verify once, use everywhere
- Embedded wallet, normal login
- Gas covered for you
- Proofs generated on your device
At a glance
Claim status summary
Every claim on this page, labeled by source, in one place.
| Native mainnet activity requires KYC | Official |
| Wrapped RBNT elsewhere does not require Redbelly KYC | Official |
| Verification is done by accredited issuers, not Redbelly directly | Official |
| Core access requires a biometric-verified passport | Official |
| Staking requires KYC and an enabled wallet | Official |
| Node operation requires KYC | Official |
| Ten-wallet-per-identity limit | Official |
| Approval takes under 30 minutes, often almost immediately | Official |
| Services withheld in 18 named jurisdictions per the Terms and Conditions; no other regional block | Official |
Built by Cyon
Web3 growth strategist and builder. Say hi or check the code.