The solution: a KYC that travels
Exchanges found the Crypto Exchange Association (demo) on Verana, open to the banks that serve them: one governed credential, authorized providers, membership with teeth, a reuse fee that pays the original issuer - and counterparty proof for the Travel Rule.
The solution: a KYC that travels
A group of exchanges founds the Crypto Exchange Association (demo) - and keeps membership open to the banks that serve them. One membership, one fee schedule, one set of duties. The checklist is short:
“None of us competes on passport scans. So we stopped pretending it is a moat: we founded an association, wrote the rules once, and made the check itself portable - with the original issuer paid every time it is reused.”
What the Association needs
The Association and every member exchange must be provable online, so a customer can tell a real exchange from a fake one before uploading anything.
A single KYC credential schema, governed on both sides: only accredited members issue it, only accredited members can ask for it.
Joining is a vetted, renewable, paid process - and every fee a member pays or earns builds a public, slashable trust score.
When a member accepts another member's KYC credential, the protocol itself routes a fee to the exchange that paid for the original check.
One verifiable answer to who the counterparty is, published on each member's DID and free to check - instead of a license resubmitted to every travel rule directory.
All of this needs wallets to hold and check the proofs (they exist, open source) and one neutral, public place where membership, permissions and payments anchor - owned by no single exchange. That place is Verana.
Let's build on Verana
Verana is a public infrastructure that generalizes the use of verifiable credentials, and provides out of the box:
Build ecosystems that issue and verify any credential, with your own schemas, governance framework, participants, and business model, or join an existing one.
Identify any service and the organization or person that controls it, and verify it before you connect. Verify first. Then connect.
Discover services and ecosystems by the credentials they hold, ranked by trust, for people, search engines, and AI agents.
Verana is public, decentralized infrastructure. Any ecosystem can self-create. The Association uses the same open infrastructure as everyone else - no gatekeeper, and no member hosting the others' data.
The rulebook: one EGF instead of fifty bilateral contracts
The Association's Ecosystem Governance Framework is a public document, digest-anchored from the trust registry. It defines:
- 1Who may join: licensed exchanges and credit institutions - crypto-native or not - that are already Verifiable Services (ECS-Organization from the Verana ECS Ecosystem, self-issued ECS-Service). One membership class, one fee schedule, one set of duties.
- 2The authorized IDV providers members may use for the original check: IdentiSure (demo), ClearPass (demo), VerifID (demo).
- 3How to be onboarded as an ISSUER member and as a VERIFIER member: licensing evidence, provider contracts, evidence-retention duties, yearly renewal.
- 4The re-binding rule: on every reuse, the accepting exchange verifies the holder is the subject - passport NFC proof of possession plus face match - and runs its own sanctions ping.
- 5The fee schedule: what a reuse costs, who receives it, and that issuing is free.
- 6Evidence duties: the issuer seals the full provider evidence into the holder's wallet alongside the credential, digest-bound. The verifier obtains and maintains the sealed evidence file automatically at presentation - its own complete CDD record from second zero. Contacting the issuer about a reuse is prohibited by design: no phone home.
- 7Slashing causes: issuing outside the provider list, faking evidence, issuing without the sealed evidence bundle.
- 8Travel Rule counterparty proof: every member publishes a CEXA-VerifiedCounterparty credential on its DID carrying legal name, LEI where held, licensing authority and license identifier, VASP category, and a compliance contact endpoint. Renewed at membership renewal, revoked on license loss.
Vendor reusable KYC already exists - which proves the demand. But it is single-vendor and vendor-owned. The Association's credential is cross-provider, member-owned and user-held: the rules belong to the members, the credential belongs to the customer, and no vendor sits in the middle. And because the EGF makes issuers vetted, bonded and auditable, a bank relying on a member-issued check stays inside the classic third-party reliance framework its regulator already accepts.
On the Travel Rule, the Association is deliberately narrow: it carries no transaction data and replaces no messaging protocol. It supplies the one thing every travel rule network rebuilds on its own - a neutral, verifiable answer to who the counterparty is.
The ecosystem the Association builds
Two schemas at founding. CEXA-Kyc: the reusable retail check (KYC level, screening date, provider, expiry, a hashed document number for chip-matching re-binding - and the sealed evidence bundle riding in the holder's wallet, digest-bound). Issuance governed, verification governed, every request a paid, receipted session. CEXA-VerifiedCounterparty: the Travel Rule identity of each member, published on its DID and free to check - issued by the Association, revoked on license loss.
Why it matters: governed verification is what makes the business model enforceable: a wallet only answers requests from members in good standing, with the reuse fee paid.
did:webvh:QmRp...Wrzq:association.cexa.playground.testnet.verana.networkA CEXA-Kyb credential for corporate customers follows the same pattern (higher stakes, higher fees) and ships as the story's second act - and it is where the bank members care most: corporate onboarding is the slowest, costliest check either sector runs.