Chapter 03
Verification
Proving an account with a code in the bio, and what gets bound on chain.
Every platform uses the same proof, a short code in the bio, and ends in the same onchain binding.
Bio code (every platform)
01
Start
Open Claim, pick the platform, enter the handle, and connect the wallet that should receive fees.
02
Get the code
The identity service issues a short code (
oley-xxxxxx, valid for 24 hours) bound to that person and wallet.03
Paste it
Put the code anywhere in your bio (channel description on YouTube, about on Twitch) and press Verify.
04
Verified
The service reads your public profile, confirms the code and captures the platform's stable account id.
05
Bind
It signs the attestation and you send
attestfrom the wallet. You can delete the code from your bio right away.
Where the code goes
| Platform | Bio code | Stable id used for binding |
|---|---|---|
| X | profile description | numeric user id |
| YouTube | channel description | channel id |
| TikTok | profile bio | open_id |
| Snapchat | public profile bio | username |
| Twitch | channel description | user id |
| Farcaster | profile bio | fid |
What gets bound
The attestation is signed under the EIP-712 domain of the escrow contract:
Attestation(bytes32 personKey, bytes32 platformUserId, address wallet, uint256 deadline, uint256 nonce)
personKey = keccak256(platform, handle), the key the coin is launched against.platformUserIdis a hash of the platform's stable account id. After binding, the coin follows the account, not the handle: renames are harmless, and a new owner of an old handle inherits nothing.noncemust equal the escrow's current bind nonce for the person, so an attestation can be used only once.
Rebinding
New wallet? Verify again from it. The escrow allows a rebind whenever the platformUserId matches the one already bound. Bound persons are never swept.