Attestto

• Name: Attestto
• URL: https://attestto.com/
• Tags: solana-ecosystem
• Category: wallet identity-resolution middleware / credential-wallet interoperability / compliance-oriented trust infrastructure
• Summary: Attestto is identity-resolution middleware for policy-gated wallet flows. Its real job is to answer what a wallet address maps to — DID, domain, credential wallet, or compliance signal — before somebody allows payment, approval, or onboarding. The did:sns piece is the only notably crypto-native wrinkle; the rest is mostly trust-routing glue.
• What it does:
  • Publishes a wallet-identity resolver that maps a connected wallet to DIDs, domains, KYC or credential signals, and related trust metadata
  • Ships a browser credential-wallet discovery layer so apps can find and verify W3C-style identity-wallet extensions instead of assuming one wallet stack
  • Maintains did:sns, a DID method that binds Solana Name Service names to DID Documents and adds higher-layer hooks for payment and compliance metadata
  • Packages document verification, compliance checks, and approval/governance tooling around that identity layer
  • Extends the stack into treasury and payment workflows with stablecoin- and multisig-oriented operational hooks
• Key claims:
  • The main platform site presents Attestto as a bundled stack for identity verification, document signing, treasury management, compliance tooling, and credential-wallet flows, including Circle-linked payment hooks. That breadth is exactly why the note should stay blunt about the narrower resolver job underneath.
  • The open site says the stack builds on W3C and IETF standards and publishes open-source identity components instead of stopping at a closed SaaS shell.
  • The wallet-identity-resolver README makes the real pitch plainly: ordinary wallet connectors return an address and signer, while Attestto tries to resolve what that address means in institutional or compliance terms.
  • The id-wallet-adapter materials show a real but narrow job: browser credential-wallet discovery and verification.
  • The did:sns spec is the most crypto-native piece, binding Solana Name Service names to DID Documents and leaving room for payment and compliance metadata above the identifier layer.
  • Across the materials, this does not read like a new base protocol. It reads like trust middleware sitting between wallet control and institution-facing workflows.
• Whitepaper: No canonical standalone Attestto whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the combined platform site, open standards site, and open-source repository network around wallet identity resolution, wallet discovery, and DID specifications; see ../whitepapers/attestto-primary-sources-2026-05-03.md.
• Sources:
  • https://attestto.com/
  • https://attestto.org/
  • https://raw.githubusercontent.com/Attestto-com/identity-resolver/main/README.md
  • https://raw.githubusercontent.com/Attestto-com/id-wallet-adapter/main/README.md
  • https://raw.githubusercontent.com/Attestto-com/did-sns-spec/main/README.md

Internal linkages

• Best upward reads: spruceid for the stronger identity-and-verification middleware stack and did-pkh for the wallet-linked subject-format layer underneath.

Control surface

• Real leverage sits in resolver policy, accepted credential sources, wallet-extension discovery defaults, and whichever compliance mappings downstream apps actually honor.

• So the useful question is not whether Attestto is open. It is who gets to decide what a wallet address means when money, approvals, or onboarding depend on that answer.

• Last reviewed: 2026-06-18 UTC