Soulbound Tokens · interactive mechanism simulation

Issuers mint credentials that require consent to accept → the SBT contract locks each token permanently to one Soul (wallet) → transfer attempts revert → diverse holdings weight governance votes → issuers can revoke. Non-transferability is a feature and a liability: try the key-loss trigger below.
Issuers university · DAO · exchange SBT contract locked() = true · consent-mint Soul (wallet) 0 SBTs held Buyer / market attempts transfer() reverts — not for sale DAO governance vote weight: 0.0× correlation-discounted Orphaned souls 0 SBTs locked (key lost) recovery: theoretical only
SBTs issued (total)
0
Active SBTs held
0
Transfer attempts blocked
0
Governance vote weight
0.0×
Revoked / lost SBTs
0
Parameters — edit me
1.2/s
85%
5%
0.6/s
1.5×
Controls

Illustrative simulation. Reflects the documented mechanism (consent-based minting, non-transferability with reverting/blocked transfers, issuer revocation, correlation-discounted governance weighting) but issuance timing, consent rates, and vote weights are randomized for visualization — not live onchain data. The "simulate key loss" button illustrates a documented failure mode: because SBTs cannot be moved to a new wallet, a lost key permanently strands them, and standardized community recovery "stayed largely theoretical." Part of The Onchain Experiment Atlas.