Permissioned security tokens
ERC-3643 (T-REX) tokens where every transfer checks the identity and eligibility of both parties before it executes.
Asset tokenization on blockchain and DLT
We build the smart contract layer for real-world asset (RWA) tokenization, from permissioned security tokens to the identity, compliance and recovery rules around them. Your advisors define the legal structure. We turn their rules into code that enforces them onchain, and we test that it does.
We do not provide legal or regulatory advice. We work alongside your legal advisors, who decide which framework applies and which rules the tokens must enforce.
01 / WHO THIS IS FOR
Who this is for
- Issuers and platforms tokenizing real estate, funds, bonds or other real-world assets
- Teams that need security tokens with transfer restrictions and investor eligibility checks
- Projects moving an existing token to a permissioned model
02 / WHAT WE BUILD
What we build
Onchain identity
Identity registries with signed attestations (EIP-712) from trusted issuers, so eligibility can be verified without storing personal data onchain.
Compliance rules
A modular compliance engine for rules such as investor caps, country restrictions, holding limits or lock-up periods, configured to what your legal team requires.
Operational controls
Custodian-gated wallet recovery and document anchoring (ERC-1643), for the operational actions a regulated asset needs.
Why invariants matter in tokenization
A tokenized asset has its own invariants. The supply must match the underlying asset, every holder must be eligible, and no transfer may bypass the compliance rules. We write them down first and test them with stateful invariant tests, the same way we test DeFi protocols.
03 / HOW AN ENGAGEMENT WORKS
How an engagement works
- 01ScopeA call and a written scope based on the requirements from your legal team.
- 02SpecificationEach legal rule is mapped to an onchain check and an invariant, agreed before any code.
- 03Phased buildEach milestone is delivered with its own unit, fuzz and stateful invariant tests.
- 04Hardening and handoverStatic analysis, coverage review, documentation and NatSpec, plus support for your team during the audit.
04 / WHAT YOU GET
What you get
| DELIVERABLE | FORM |
|---|---|
| Solidity contracts with NatSpec documentation | Repository |
| A Foundry test suite that covers the compliance scenarios, not just the happy path | Repository |
| A specification that maps each rule to the check that enforces it | Document |
| Deployment scripts and an operations guide for administrators and agents | Repository · Document |
06 / FAQ
Questions about tokenization
Which token standard do you use?
ERC-3643 (T-REX), an established standard for permissioned tokens, unless your requirements call for a different approach.
Do you provide legal or regulatory advice?
No. We work on the technical side, alongside your legal advisors, who decide which regulatory framework applies and which rules the tokens must enforce.
Which assets can be tokenized?
On the smart contract side, most assets work in a similar way, whether real estate, funds, bonds or receivables. What changes is the legal structure, and your advisors define it.
Public blockchain or private DLT?
We work with EVM-compatible networks, public or permissioned. Which one fits depends on your requirements, and we can help you weigh the technical trade-offs.