Specification before code
A written description of every state variable, role, function and invariant, so behaviour can be checked against intent rather than against whatever the code happens to do.
Service · Blockchain
Commission us to write, test and prepare for audit the contracts that hold your users’ assets or rules. Solidity is our main language, and the deliverable is code that a reviewer can reason about, not just code that compiles.
Solidity with Foundry or Hardhat
Fuzz and invariant tests included
Audit-ready specification pack
Deliverables
A written description of every state variable, role, function and invariant, so behaviour can be checked against intent rather than against whatever the code happens to do.
Solidity on EVM chains as standard, Vyper where its simplicity helps, and Rust or Move where the target chain requires them, built on audited libraries such as OpenZeppelin where suitable.
Unit tests, fuzz tests across input ranges, invariant tests that run random call sequences, and fork tests against real deployed tokens and protocols.
Gas reports per function, storage layout documentation and, for upgradeable contracts, checks that a new version does not collide with existing storage slots.
Scripted, repeatable deployments, source verification on block explorers, and role handover to multisig wallets as the final step.
Early decisions
Immutable contracts earn more trust but cannot be fixed; transparent or UUPS proxies can be, at the cost of admin risk and storage discipline. We decide per contract, not per project.
Single owner, role-based access, or governance through a timelock and multisig, matched to how much power operators should hold after launch.
Foundry for fast Solidity-native tests and fuzzing, Hardhat where a TypeScript-heavy team will maintain the code, or both where each covers a gap.
Which tokens, oracles and protocols the contracts call, how non-standard tokens such as fee-on-transfer ones are handled, and what happens if a dependency pauses.
A pinned Solidity version with known behaviour, chosen with the target chain’s supported opcodes in mind, and no floating pragmas in deployed code.
Whether a pause, rate limit or circuit breaker exists, who can trigger it and how users can still withdraw while it is active.
Engagement
We write the spec with you, list assets at risk, privileged roles and likely attacks such as reentrancy, price manipulation and signature replay, and agree the invariants that must always hold.
Contracts and tests grow together. Each function arrives with unit tests, and invariants are wired into fuzzing early so regressions show up immediately.
Engineers who did not write the code review it line by line, and tools such as Slither flag patterns worth a second look before anyone external sees it.
We package the spec, tests, known limitations and deployment plan for your chosen auditor, then fix findings and document how each one was resolved.
Fit
Deposits, tokens or rights will sit in the code, so failure means irreversible loss rather than a support ticket.
Your app team is strong but has not shipped production Solidity, and you want that layer engineered properly.
You want code, tests and documentation that let auditors spend their time on logic rather than on understanding intent.
Alternatives
If the contracts implement financial mechanisms such as AMMs, liquidations or oracles, protocol design comes before coding.
Open registerFor minting, metadata and royalties on established token standards, our NFT service covers the whole launch.
Open registerIf network choice and the on-chain boundary are still open, a broader blockchain engagement settles them first.
Open registerAn invariant is a statement that must stay true whatever users do, such as total deposits equalling the sum of balances. Writing them down before coding turns vague intent into something a fuzzer can attack thousands of times per run.
Invariant tests find the bugs unit tests miss: those that appear only after an unusual sequence of calls by different accounts.
Clever assembly and gas tricks make audits slower and mistakes likelier. We use well-reviewed libraries for tokens, access control and signatures, follow checks-effects-interactions, and only optimise where the gas report shows a real cost to users.
A proxy lets you fix a bug, but it also lets whoever controls the admin key change the rules. We put upgrade rights behind a multisig and, where users need warning, a timelock that delays changes long enough for them to exit.
A frozen commit, the specification, a list of privileged roles, known trade-offs, test coverage and deployment parameters. Teams that send only a repository link pay for days of auditor time spent reconstructing intent.
FAQ
No. We review our own code rigorously, but an independent audit should come from a firm with no stake in the implementation. We prepare everything they need and fix what they find.
Yes. We begin by writing the specification the code should have had, adding tests around existing behaviour, and listing risks before changing anything.
It is the one we use most. We also work in Vyper, and in Rust or Move where the target chain needs them, and will tell you if a project falls outside our depth.
Only if it was deployed behind a proxy or with explicit upgrade hooks. Otherwise the fix is a new deployment and a migration of users and state, which is why the upgrade decision is made early.
Related services
Once contracts are stable, users need an interface that explains and signs their transactions safely.
Open registerEnd-to-end tests across the app, indexer and contracts catch integration bugs that contract tests alone miss.
Open registerCI that runs fuzzing on every pull request and gates deployments on passing invariants.
Open registerPrimary sources
Dated official documentation, standards, and research that support the factual claims on this page.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.