Standards: where each fits
| ERC-3643 T-REX, ONCHAINID | ERC-1404 simple restricted | KAIO protocol-engine | |
|---|---|---|---|
| Compliance lives | In the token (modular engine). | In a sibling contract; token only returns reason codes. | In a separate on-chain protocol engine; token is a vanilla ERC-20. |
| Identity primitive | ONCHAINID with claim topics & trusted issuers. | None mandated. Issuer rolls their own. | Externalised — engine reads any KYC oracle. |
| DeFi composability | partial — can revert in arbitrary lp pools. | partial — same revert risk; reason-code helps UX. | high — ERC-20 surface is unchanged. |
| Modify rules without redeploy | yes — swap modules. | yes — upgrade external logic. | yes — engine is independent. |
| Jurisdictional gating | Native via claim modules. | Custom; encode in restriction codes. | Native; engine plug-in. |
| Holder cap / max-investors | Module. | Custom. | Module. |
| Best fit | Regulated security tokens (Reg D / Reg S issuances). | Lightweight restricted tokens (employee equity, club tokens). | Permissioned RWA that needs to plug into existing AMMs / lending. |
| In this repo | contracts/ERC3643Token.solBasicCompliance.sol + IdentityRegistry.sol |
roadmap — adapter wanted, see issues. | roadmap — adapter wanted. |
Transfer-restriction simulator
Configure a token policy on the left; pick a transfer; see which checks fire and why.
Token policy
Transfer attempt
—
Reference Solidity hook (current standard)
Where this fits in the kcolbchain stack
RWA tokens issued via this toolkit plug into:
- meridian — RWA market-making agent. Quotes are gated per counterparty against the same compliance engine used here.
- stablecoin-toolkit — settles cash-leg in regulated stablecoins with the same identity primitives.
- audit-checklist — drop-in Foundry templates that exercise these compliance modules at audit time.
- switchboard — agent wallets that hold ONCHAINID claims and can transact tokenised RWA via x402 / MPP / AP2 rails.