Thank you, will do, cheers
1 Like
Repository is fully updated.
Update: Reference Compliance Implementation Added
To validate hook composability in practice, we’ve added an ERC-3643-inspired modular compliance framework as a reference application (src/compliance/). It integrates entirely through the _beforeTokenTransfer / _afterTokenTransfer hooks defined in the reference implementation — zero changes to the core interface.
The framework provides four pluggable compliance modules:
-
KYC verification — both-party identity checks against a shared on-chain registry
-
Jurisdiction restrictions — ISO 3166-1 country blocklist (OFAC/sanctions use cases)
-
Holder caps — maximum unique holder enforcement (Reg D Rule 506(b))
-
Time-based lock-ups — global and per-token transfer locks (Reg S/D holding periods)
All modules are external contracts, swappable at runtime via addComplianceModule() / removeComplianceModule() — no proxy upgrade or token redeployment required. A shared IdentityRegistry stores KYC state and is queried by modules during transfer enforcement.
This is intentionally not part of the EIP specification. It is an application-layer extension that demonstrates the hook architecture’s design surface. The core standard remains the three-layer provenance primitive defined in the EIP.
The point is compositional: the same hooks that enable compliance also enable staking, royalty enforcement, or access control — the standard doesn’t prescribe what plugs into them, it ensures the surface exists.
Test suite: 289 tests across 13 suites, 0 failures.
this is gorgeous. thanks for sharing.
1 Like
Hello to all supporters, fixed some bugs related to KYC module and ran more tests. Looking forward for your feedback. Hope some users get digging into it’s potential and brainstorm about the future integration into the blockchain. Cheers