Token infrastructure
Issuance, vesting, distribution, staking and treasury mechanics implemented properly.
- Engagement
- Fixed-scope build, with your legal counsel engaged in parallel
- Typical timeline
- 6–7 weeks
- Starts with
- Your allocation table and the list of people who will hold signing keys.
The allocation lives in a spreadsheet: team, advisors, treasury, and a round that closed with a side letter somebody remembers differently. The moment those numbers become a contract, every error in the spreadsheet becomes permanent, public and quoted back at you by holders.
A token programme that runs itself and reports cleanly.
What we build
Concrete artefacts, handed over and documented.
The token contract with its supply behaviour agreed in writing first, fixed, mintable or burnable, and exactly who is able to do which
Vesting contracts per allocation, with cliffs and schedules encoded rather than administered by whoever set the calendar reminder
A merkle-based distribution for large recipient lists, so claiming costs the recipient rather than draining your treasury in network fees
A multisig arrangement with named signers, thresholds, and a written rule for what needs how many signatures
A public page where anyone can verify supply, vesting releases and treasury movements against the chain itself
What changes
Vesting releases execute on their own, so the next cliff is not a person’s responsibility
Holders verify claims against the chain instead of trusting a screenshot
Control of the token is a documented arrangement between named people, not one founder’s hardware wallet
How it runs
01Allocation and control
Every recipient, every schedule, and the signer arrangement, reconciled against your cap table until two people sign it off.
02Contracts and vesting
Token and vesting contracts built and tested against the real schedule, including the awkward mid-cliff cases.
03Distribution rehearsal
A full dry run on a test network using the actual recipient list, then handover of the signer procedure.
Chosen per project. Named here so you can see the shape of it.
- Solidity
- OpenZeppelin
- Foundry
- Safe
- Arbitrum
Questions we get asked
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.