Thanks @bogwar — this looks quite interesting.
I’d like to propose two ICRC extensions aimed at enabling identity and compliance layers for Real World Asset (RWA) tokenization:
ICRC-125: Identity Provider
A standard for ledger blocks to reference the legal identity of the transaction submitter (e.g. passport, driver’s license, national ID). This provides a structured way for dApps and services to verify the identity of users interacting with the ledger.
ICRC-126: Compliance Manager
A standard for ledger blocks to reference or enforce legal and compliance rules related to a transaction before it is processed. This enables programmable compliance logic per asset class (e.g. KYC, jurisdiction checks, investment limits) without altering the base ledger.
Use Case
Each RWA token can define its own compliance rules. For example:
- Stock tokens may require all wallets to be KYC-verified.
- Real estate or gold tokens may only be accessible to residents of specific jurisdictions.
Using ICRC-125 for identity verification and ICRC-126 for transaction-level rule enforcement, developers can reflect regulatory constraints on-chain in a standardised and modular way.
This proposal aligns with concepts from:
If this sounds relevant, I’m happy to start working on an initial implementation, publish a follow-up post, and open GitHub PRs for discussion.