Minting a token is easy, running the asset is not
A token is only as good as the rules around it. We build issuance, allowlists, transfer restrictions, distributions, and redemption, wired to the holder register and the off-chain books that have to agree with it.
A token is a claim: the records have to honor it
Tokenization sounds like a minting problem and is actually a records problem. Putting a share, a note, a fund unit, or a warehouse receipt onto a chain takes an afternoon. Keeping the on-chain holder list, the transfer agent's books, and the investor's statement in agreement for years is what decides whether the platform is real. That's where most projects come apart.
The standards are mature. ERC-20 covers fungible units, ERC-721 and ERC-1155 cover unique and mixed inventory, and permissioned designs in the ERC-3643 lineage check eligibility inside the transfer, so an ineligible transfer reverts instead of surfacing in a reconciliation later. An L2 such as Base, Arbitrum, Optimism, or Polygon makes a distribution to a long holder list affordable, and rule logic behind an upgradeable proxy with a timelock means a change is possible, visible, and never one key's quiet decision.
Villaex builds tokenization platforms end to end, and the chain is only one layer: issuance and allowlist tooling, an investor portal where smart accounts and sponsored gas keep non-crypto holders moving, distribution runs, a redemption queue, indexers and subgraphs behind reporting, and a scheduled job comparing positions against your books. We don't tell you what you're allowed to issue. Your counsel sets the structure, eligibility, and disclosures, and we encode those rules, in the contract where it can enforce them and in your procedures where it can't.
From input to outcome
What a chain project moves through before it holds value, and what has to be true at each boundary before the next stage can run.
Scope & chain
What the chain is actually for, then the chain, the standards and the custody model.
- In
- The problem
- Out
- An architecture
Contracts & tests
Contracts written against a specification, with invariants, fuzzing and gas profiling.
- In
- An architecture
- Out
- Tested contracts
Review & audit
Internal review and static analysis, then an external audit, with findings fixed and retested.
- In
- Tested contracts
- Out
- Audited contracts
Mainnet & monitoring
Testnet rehearsal, verified deploy, then alerting on balances, privileged calls and indexer lag.
- In
- Audited contracts
- Out
- A system you can operate
Feedback edge
What monitoring catches on chain, and what support hears off it, feeds the next change and the next audit scope.
What we build and deliver
What a token needs after the mint.
Token Standards & Issuance
ERC-20, ERC-721, or ERC-1155 for the asset, with ERC-3643 style permissioning where holders need approval: onboarding, identity registries, and eligibility rules applied before a holder can receive anything.
Transfer Restrictions
A plain token moves to any address the holder names. Lockups, caps, and freeze controls change that.
Distributions & Redemption
Merkle claims and resumable batches, because one loop over every holder runs out of gas and reverts.
Custody & Controls
Multisig on issuer rights, timelocks on the dangerous calls, so minting isn't one laptop away.
Monitoring & Reconciliation
When the chain and the transfer agent's books drift, nobody trusts either. We check daily.
Where it creates value
Tokenization wherever a register has to satisfy someone outside your company.
Fund unit register
Units are issued to approved investors. Lockups and transfer rules are enforced on the transfer itself.
Fractional ownership
Property interests split among holders, with distributions paid from rental income.
Note issuance
Notes are issued with their schedules attached. Redemption runs through the same platform. The holder record stays auditable the whole way through.
Warehouse receipts
Custody-backed claims on stored goods, redeemable against the physical asset.
Invoice claims
A financier can check a claim for double pledging themselves. The check runs against the chain, so it never depends on trusting your portal.
Certificate retirement
Retirement recorded once, in public, and hard to double count.
The return on the work
What a platform built to operate returns.
- Reconciled
- DailyOn-chain positions checked against your books before a difference ages.
- Tested
- In the buildStatic analysis, property tests, and gas profiling are part of the build and included in it.
- Audited
- Before it mintsAn independent firm reviews the contracts before anything reaches mainnet.
- Timelocked
- Privileged callsMint, freeze, and upgrade wait in public before they take effect.
- Verifiable
- By anyoneVerified source on the explorer, so holders can read the rules themselves.
Questions we get before we start
Still unresolved? A 30-minute conversation with an engineer usually settles it faster than another page of copy.
Often not. If there's one issuer, one register, and nobody outside who has to verify it independently, a database is cheaper and far easier to change. Tokenization earns its place when holders transfer among themselves, or when someone has to check the record without trusting you. We'll tell you honestly which situation you're in.
Usually an EVM L2 such as Base, Arbitrum, Optimism, or Polygon: a distribution to a few thousand holders costs real money on Ethereum mainnet and very little on an L2. We weigh finality, bridge risk, custodian and wallet support, and any view your counsel or transfer agent already holds. A permissioned chain makes sense when the holder list itself can't be public.
Two things happen. Static analysis with Slither, property and fork tests in Foundry, and gas profiling are part of the build and included in it. An independent audit is a separate engagement with an outside firm, and we help you scope it, choose one, and fix what comes back. We don't put an asset on mainnet on our own review alone.
You do, and we help you decide how. Issuer rights sit behind a multisig, dangerous functions behind a timelock, and keys live on hardware or with a custodian you choose. We write the recovery procedure and test it before launch, because finding out a key is gone during an incident is too late.
An indexer and subgraph turn transfers into positions, and a scheduled job compares those positions with your off-chain records, flagging differences as they appear rather than at quarter end. Which record is official is your counsel's call, and it's often the transfer agent's book, so we build the chain to reconcile against it rather than quietly replace it.
Holder count, how complex the transfer restrictions are, whether custody is integrated or handled by a custodian you appoint, and how many off-chain systems have to reconcile. Distribution mechanics matter too, since claim-based payouts are cheaper to run than pushing to everyone. We scope in phases, so contracts, portal, and reporting can be priced and sequenced separately.
Adjacent capabilities
Tokenize an asset properly.
Bring us the asset and the rules your counsel has set. We'll build the issuance, the register, and the reconciliation that keeps them honest.