Sismo primary sources

Reviewed: 2026-05-10 UTC

Core protocol framing

Data Vault and anonymous identity model

Data Groups and upstream eligibility design

Attestation and badge issuance layer

Supporting repos for trust-surface analysis

Main takeaways from this pass

  • Sismo’s analytically important split is between private account aggregation, trusted ownership translation, reusable eligibility-group construction, and governed attestation issuance.
  • The vaultId design is a strong comparison point against public identity registries because it gives apps anonymous uniqueness without requiring one globally public subject record.
  • The Commitment Mapper is not incidental infrastructure; it is a named trusted service in the official docs and therefore a central control surface.
  • Sismo Hub shows that group design and data-provider selection sit upstream of badge minting and proof verification, so eligibility politics live before the ZK proof layer, not only inside it.
  • The contracts make clear that badges are only the presentation layer: authorized attesters and registry governance remain the choke points underneath.