Smart contract engineering
Contract code is judged twice: once by an auditor, and once by the operations team that has to pause it at two in the morning. Most engagements arrive with the first in mind and none of the second, and the administrative path — pause, upgrade, recover — is retrofitted after the interface is frozen.
We write contracts against both readers, remediate audit findings, and hand over the key ceremony documentation and the runbook alongside the code.
- Practice
- Advisory and delivery
- Industries
- 12, with 4 evidenced
- Platforms
- Token issuance & tokenization
Four workstreams
Contract design
Issuance, transfer, restriction and redemption paths, with the administrative surface designed at the same time as the user surface.
Upgrade governance
A contract that cannot be changed is a liability; one that can be changed by one party is a different liability. Both are governance questions.
Audit and remediation
Preparation for external audit, remediation of findings, and bytecode verification against the reviewed source.
Operational handover
Runbook, key ceremony, rehearsed pause and recovery, and a client team trained to run it.
How an engagement runs
- 2–3 weeks
Specification. The behaviour, the administrative surface, and the invariants the tests will hold.
- 4–8 weeks
Build. Contracts, test suite, deployment scripts, and the operator documentation written alongside.
- 2–4 weeks
External audit and remediation. We schedule the auditor; we do not review our own work.
- 1–2 weeks
Deployment and handover. Key ceremony, verification, and a rehearsed pause.
This capability, by industry
Intersection pages exist where the work can be evidenced. The rest are listed so you can see what is not claimed.
- Financial services page pending
- Capital markets & digital assets page pending
- Gaming & entertainment page pending
- Sports & loyalty page pending
8 further industries — not yet evidenced
Start a conversation
Tell us what you are trying to build and what has to be true for it to be safe. Enquiries reach an engineer, not a queue.