Token contract development
ERC-3643 permissioned tokens, or another standard where the instrument calls for it, written in Solidity against explicit invariants.
Solution · Asset tokenization
RWA tokenization development for issuers and platforms.
When you need your own tokenization stack rather than a shared platform, we design and build it: permissioned token contracts, identity and eligibility registries, investor and issuer interfaces, and the integrations that connect them to your KYC providers, custodians and back office.
The problem
Most tokenization projects underestimate everything around the token. The contract is a few hundred lines; the eligibility model, issuer controls, investor onboarding, reconciliation with off-chain records and the audit that has to happen before launch are where schedules and budgets go. Generic token templates skip most of it, and the gaps surface late, when contracts are hardest to change.
How we approach it
We start from the instrument and the rules it has to obey, and only then choose contracts and chains. Eligibility, transfer restrictions and issuer powers are specified as invariants and tested before deployment. Off-chain components, usually the larger attack surface, are threat-modelled with the same rigour, and the codebase is prepared for an independent external audit rather than presented as a substitute for one.
Capabilities
What we build.
Identity and eligibility modules
On-chain identity registries, claim issuers and transfer rules for investor category, jurisdiction and holding limits.
Investor and issuer interfaces
Onboarding, holdings and transfer flows for investors, and administration consoles for issuers and their agents.
Integrations
KYC/AML providers, custody and the back-office systems that hold the off-chain record of ownership.
Cross-chain settlement
Settlement designs that keep the eligibility check authoritative on every network the instrument reaches.
Audit readiness
Test suites, threat models and documentation prepared for an independent smart contract audit, with remediation support.
Process
How delivery runs.
01 DiscoverInstrument, rules, jurisdictions
02 ArchitectContracts, chains, trust model
03 BuildContracts, interfaces, integrations
04 TestInvariants and threat model
05 AuditIndependent review support
06 LaunchDeployment and monitoring
Who it is for
Built for.
Asset managers
Building an issuance stack they control end to end.
Fintechs and digital asset platforms
Adding tokenized real-world assets to an existing product.
Real estate and private credit sponsors
Structuring investor access around enforceable transfer rules.
Banks and financial institutions
Running tokenization pilots on an architecture that can be reviewed line by line.
Related
Built on this work.
Product: Tokenized private markets
Built on the ERC-3643 permissioned token standard: on-chain eligibility, KYC/AML provider integration, issuer controls and an auditable lifecycle for private-market assets.
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.
Blockchain
Protocol, contract and integration work for cases where shared state has to be provable - with the gas, finality and upgrade constraints designed in from the start.
Web3 & dApps
Application-layer Web3: wallets, dApps, DeFi interfaces and DAO tooling, designed so the hardest parts of on-chain interaction stay understandable.
Software Engineering
Web, mobile, SaaS and enterprise systems built on durable foundations - clear domain models, typed boundaries and tested paths.
FAQ
Questions we get asked.
Use a platform when the instrument is standard and time to market matters most. Build when your structure, jurisdictions or integrations are specific enough that a shared platform would force workarounds. We give a written recommendation either way.
EVM-compatible networks, including Layer 2 rollups. The choice follows finality needs, transaction cost, ecosystem and the requirements of the instrument, and we compare the options in writing before building.
No. We prepare contracts for an independent external audit and support remediation, but the audit itself should be performed by a separate firm.
No. We are a technology company. Licences, offering documents and regulatory approvals remain with the issuer and its legal advisers.
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.