Smart contract development
Solidity and Rust contracts written for audit, with full test coverage and upgrade paths.
- Engagement
- Fixed-scope build; external audit budgeted separately
- Typical timeline
- 7–8 weeks before external audit
- Starts with
- A written list, in your own words, of what the contract must never be able to do.
Deployed contract code is public, permanent and holding money. A mistake in an ordinary web application is a bad Tuesday; the same mistake here is a withdrawal you cannot reverse and a statement you have to publish.
On-chain logic you would be comfortable publishing.
What we build
Concrete artefacts, handed over and documented.
- 01
Contracts written against a specification you sign off first, including an explicit list of what the system must never allow
- 02
A Foundry test suite with unit tests, fuzzing across random inputs, and invariants, the properties that must hold no matter what order calls arrive in
- 03
Static analysis on every commit, where each finding is either fixed or recorded as accepted with the reasoning attached
- 04
Deployment scripts that are themselves reviewed, because a large share of incidents happen during deployment or configuration rather than in the logic
- 05
An ownership plan naming who holds which key, what a multisig is able to change, and what is deliberately permanent
- 06
An auditor handover pack, specification, tests, coverage, known trade-offs, so an external audit spends its hours on logic instead of orientation
What changes
The system’s guarantees exist as executable tests rather than promises in a document
External audit returns fewer findings, because the obvious ones are already gone
You know before launch which powers you keep and which you can never exercise again
How it runs
- Weeks 1–2
01Specification
What the contract does, what it refuses to do, and who is allowed to change anything, agreed in writing before code exists.
- Weeks 3–6
02Implementation and invariants
Contracts built alongside the tests that try to break them, including sequences no honest user would ever attempt.
- Weeks 7–8
03Testnet and audit preparation
A full rehearsal on a test network, then the handover pack an external auditor needs to start properly.
Chosen per project. Named here so you can see the shape of it.
- Solidity
- Foundry
- OpenZeppelin
- Slither
- Base
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.