A compliant, on-chain security token for real-world seed reserves

What I owned

• Built the full ERC-3643 (T-REX) token suite — the SVLT token delegates every transfer/mint to a ModularCompliance engine and a triple identity registry, so compliance is enforced by the contract itself, not by a trusted backend.
• Implemented on-chain KYC with ONCHAINID: each investor gets a digital-passport identity contract holding claims signed by a trusted issuer, and IdentityRegistry.isVerified() gates every transfer.
• Wrote the modular compliance layer with a plug-and-play country-allowlist module (ISO country codes) — new rules can be bound without redeploying the token.
• Added a NAV oracle (NAVStore, 8-decimal net asset value per token) and an append-only, IPFS-backed DocumentsRegistry for on-chain document provenance.
• Built an ONCHAINID factory on EIP-1167 minimal-proxy clones with deterministic CREATE2 addresses — cheap identity issuance at scale.
• Designed the V2 'burn-disabled' token: supply is immutable, and redemptions or enforcement run through a treasury forced-transfer pattern instead of ever destroying shares.
• Shipped the whole system to Base mainnet with a 6-phase Hardhat Ignition deployment, then handed every owner/admin role to the client via Ownable2Step + AccessControl — the deployer ends with zero privilege.
• Built the admin dashboard (Next.js 16 · Wagmi · Viem · RainbowKit) — 12 pages to manage identities, compliance, NAV, documents and minting, with a 7-role access model and batched on-chain reads.