RWA tokenization development
Your own tokenization stack: ERC-3643 contracts, identity registries, investor portals and integrations, built by our blockchain practice.
Case study
RWA tokenization and cross-chain settlement
ERC-3643 permissioned token contracts and cross-chain settlement for real-world asset tokenization, built in Solidity and Hardhat for Luxembourg-focused products.
Challenge
Tokenizing a real-world asset for a regulated market is not the same problem as launching an open token. Transfers must respect identity and eligibility rules at the contract level, the issuer needs recovery and enforcement powers a standard token does not provide, and settlement has to work across more than one chain without weakening either constraint.
Solution
Permissioned token contracts built on the ERC-3643 standard, where eligibility is checked on transfer rather than assumed at issuance, paired with a cross-chain settlement design so one instrument can settle on more than one network. Hardhat underpins the test and deployment workflow, because contracts carrying regulated value are reviewed before deployment, not after.
Why a permissioned standard
ERC-20 assumes transfers are permissionless. That assumption is incompatible with instruments whose holders must be verified and whose transfers may be restricted by jurisdiction, lock-up or investor class. ERC-3643 keeps the token interface familiar while moving eligibility into an on-chain identity check that every transfer must pass.
Enforcement the issuer actually needs
Regulated instruments carry obligations open tokens do not model: forced transfer under court order, recovery of a holder’s position after key loss, freezing on a compliance event. These have to exist in the contract from the start - they cannot be added to an immutable deployment afterwards.
Settlement across chains
Cross-chain settlement is where compliance guarantees are most often lost, because a token that is permissioned on one network and unwrapped on another carries no constraints at all. The settlement design keeps the eligibility check authoritative wherever the instrument moves.
Status
This work is in active development rather than deployed. It appears here because the architecture is settled; commercial detail follows once the product is live.
Detail
How it was delivered.
Context, architecture, technology and outcome for this engagement.
Tokenizing a real-world asset for a regulated market is not the same problem as launching an open token. Transfers must respect identity and eligibility rules at the contract level, the issuer needs recovery and enforcement powers a standard token does not provide, and settlement has to work across more than one chain without weakening either constraint.
Permissioned token contracts built on the ERC-3643 standard, where eligibility is checked on transfer rather than assumed at issuance, paired with a cross-chain settlement design so one instrument can settle on more than one network. Hardhat underpins the test and deployment workflow, because contracts carrying regulated value are reviewed before deployment, not after.
Solidity, ERC-3643, Hardhat, cross-chain settlement
In active development for Luxembourg-focused financial products.
Where it leads
Built on this work.
Ready to scope it properly?
Bring the problem, the constraints and the deadline. We will come back with an architecture and an honest view of effort.