Cowrie Research

attestto-primary-sources-2026-05-03

3 min read

Attestto primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone Attestto whitepaper or litepaper surfaced.
  • The clearest current source of truth is split across Attestto’s commercial platform site, its open standards site, and several first-party GitHub repositories.
  • The materials consistently frame Attestto as identity and trust infrastructure that bridges wallet connectivity, verifiable credentials, compliance hooks, and crypto-native governance/treasury operations.

Primary-source snapshots

1) Main platform site

  • URL: https://attestto.com/
  • Key excerpt:
    • The homepage says Attestto provides identity verification, document signing, governance, treasury, compliance tooling, and a credential wallet inside one integrated platform.
    • It explicitly highlights USDC/EURC wallets, Circle integration, CCTP bridging, settlement batching, multisig vaults, and org-scoped auditability.
    • It also says everything is built on open standards with self-sovereign identity optionality, zero-knowledge proofs, and selective disclosure.

2) Open standards site

  • URL: https://attestto.org/
  • Key excerpt:
    • The site describes Attestto as sovereign identity infrastructure built on W3C and IETF standards, with open-source reference implementations anyone can deploy.
    • It highlights a browser-based document verifier, a sovereign identity wallet app, and live DID resolver surfaces.
    • It also emphasizes technological neutrality, interoperability, privacy, portability, and public-good framing.

3) @attestto/wallet-identity-resolver

  • URL: https://raw.githubusercontent.com/Attestto-com/identity-resolver/main/README.md
  • Key excerpt:
    • The README says the package discovers DIDs, soulbound tokens, attestations, and credentials attached to a wallet address using pluggable providers.
    • It positions itself as the identity layer that comes after WalletConnect, Phantom, or Wagmi, which only return an address and signer.
    • It explicitly frames the resolver as “DNS for compliance” and says the stack is meant to help with FATF Travel Rule, eIDAS 2.0, and institutional identity workflows.

4) @attestto/id-wallet-adapter

  • URL: https://raw.githubusercontent.com/Attestto-com/id-wallet-adapter/main/README.md
  • Key excerpt:
    • The README says it is a discovery and verification layer for credential wallet browser extensions, “like EIP-6963 but for W3C identity wallets.”
    • It focuses on discovery, wallet selection, presentation requests, and verification for verifiable credentials rather than transaction signing.
    • It also explicitly ties the package to regulated use cases such as FATF Travel Rule, eIDAS 2.0, and AML compliance.

5) did:sns specification

  • URL: https://raw.githubusercontent.com/Attestto-com/did-sns-spec/main/README.md
  • Key excerpt:
    • The spec says did:sns maps human-readable Solana Name Service aliases to DID Documents and separates alias from key so identity can survive key rotation.
    • It includes explicit discussion of stablecoin-payment use cases, ISO 20022 party mapping, Travel Rule service hooks, and institutional identity flows layered on top.
    • It also says the method is operator-agnostic and intended as a resolution layer rather than as a closed platform feature.

Working conclusion

Attestto is best cataloged as crypto-adjacent identity, compliance, and governance middleware rather than as a simple KYC product or standalone DID spec. The deciding evidence in this pass was the combination of stablecoin treasury features, onchain multisig governance, wallet-address identity resolution, credential-wallet discovery, and DID-method work that repeatedly positions the project as missing trust infrastructure between crypto wallets and regulated financial or institutional workflows.

Graph View