Otterspace’s real reusable mechanism is not “soulbound NFTs” in the abstract but the combination of an issuer object (Raft), reusable badge specs, and non-transferable badge instances issued from those specs.
The docs make clear that badge meaning is governed through policy, not just minting. Burns, revocations, and expiration all matter for whether a badge should still count for access or authority.
The EIP-4973 linkage matters because Otterspace is building on a consensual account-bound-token model rather than a simple ERC-721-that-can’t-transfer model. Holder dissociation is part of the conceptual design.
Snapshot integration shows that badges are intended to be computational inputs for governance, not just profile decoration. Once badges become voting weights, spec selection and weighting become the real control surface.
The transferable Raft token is one of the most analytically important details from the docs because it localizes issuer control in a movable governance object even while issued badges remain non-transferable.
Otterspace sits between broad attestation systems and strict role systems: richer and more user-visible than raw attestations, but less explicitly hierarchical and programmable than Hats-style role trees.
Specific source signals worth retaining
Intro / Key Concepts docs: best concise explanation of badges, specs, and Rafts.
Burning / revocation and expiration docs: strongest evidence that Otterspace models credentials as historically persistent but policy-conditioned objects.
Snapshot integration docs: best example of downstream interpretation power, especially around badge weights and governance rights.
Allowlist / EIP-712 mint flow docs: useful for understanding the consent / issuance path in practice.
EIP-4973: important background for why account-bound tokens here are framed around association and dissociation rather than mere transfer disablement.
Why this entry belongs in the corpus
It strengthens the identity / attestation / role-legibility side of the corpus with a badge-first protocol that is more specific than generic attestation registries.
It helps compare how authority gets expressed across EAS, Sign Protocol, Hats Protocol, Hypercerts, and social-graph systems.
The reusable insight is that credential systems often centralize not in token transfer rules but in issuer custody, revocation rights, expiry semantics, and integration-side validity checks.