
KYC is broken.
Every time you sign up for a new financial platform, you hand over the same passport scan, the same proof of address, the same selfie. The platform runs the same checks another platform already ran last week. Your sensitive identity data now lives in yet another corporate database you don't control.
Vercre (Verified Credential) is an open-source Python SDK that implements the full lifecycle for W3C Verifiable Credentials with on-chain KYC/AML attestations.
In plain terms: a compliance provider verifies you once, issues you a cryptographically signed credential, and anchors a hash of it on Ethereum. Any protocol can then verify your compliance status instantly without ever seeing your raw identity data.
How it works:
1. A licensed compliance provider (think Chainalysis, Jumio, Onfido) issues you a credential after running KYC/AML checks
2. The credential is signed as a JWT using Ed25519 or secp256k1 and handed to you, the user
3. Only a SHA-256 hash is anchored on-chain via an AttestationRegistry smart contract
4. When a DeFi protocol or securities platform needs to verify you, they check the JWT signature and the on-chain attestation status
5. If something changes (sanctions match, expired documents), the issuer revokes the on-chain attestation, and every downstream verifier sees it immediately
What makes this different:
1. Privacy by design: Raw identity data never touches the blockchain. Only hashes. Users hold their own credentials.
2. Tiered credential types: From basic country-level KYC to full enhanced due diligence with risk scores, sanctions screening, PEP checks, and accredited investor verification.
3. Three DID methods: did:key (self-certifying), did:ethr (Ethereum wallets), did:web (institutional issuers).
4. Composable and revocable: Issue multiple credential types to the same person. Revoke them independently. An AML flag doesn't invalidate a valid KYC check.
5. 113 tests covering cryptography, DID resolution, credential schemas, smart contract integration, CLI, and full lifecycle flows.
Who this is for:
1. Compliance providers who want to monetize KYC/AML as portable, reusable credentials
2. DeFi protocols that need user verification without building their own compliance stack
3. Tokenized securities platforms that require accredited investor checks at scale
4. Institutional investors tired of repeating the same KYC process across every platform
The CLI makes it tangible: generate keys, issue credentials, verify them, check on-chain status, and revoke - all from the terminal.
This is infrastructure for a world where your identity is yours, compliance is portable, and verification doesn't require trust, just math.
Here is the codebase for your review and assessment (Demo):
github.com/pavondunbar/Ve…
#NeverStopLearning #KYC #AML #DID

English


























