← All expertise

07

Blockchain

Verifiable ledgers and tokens, when they are genuinely needed

Few companies need this, and it should be said: in most cases a well-built database solves the same problem for far less. When you genuinely need a ledger nobody can rewrite, the work changes nature.

Before release
  1. Threat modelActors, trust boundaries and where the funds move
  2. TestsThe properties that must never break, written as rules
  3. Automated analysisKnown mistakes, searched across every contract on every change
  4. Random sequencesThousands of combinations nobody would write by hand
  5. Mathematical verificationThe rule proven for every possible value, not just the tested ones
  6. External auditMandatory before production: the code is worth real money

Code is money, so you prove it

Tests as the base, then automated analysis across every contract, thousands of random sequences against the properties that must never break, and mathematical verification on the critical rules.

These tools find different things: automated analysis recognises known mistakes, random sequences find combinations nobody would have written by hand, mathematical verification proves a rule holds for every possible value and not only the ones you tested.

Upgradeable but not arbitrary

Contracts that must evolve go through a mandatory delay before every change: whoever holds funds has time to see what is about to change and to leave. The ones that must not change stay immutable and without special powers.

Withdrawals carry explicit limits, and whoever is owed something withdraws it rather than receiving it: that way one badly behaved recipient cannot block everyone else.

A chain is infrastructure too

Behind a network there are processes that must stay up: the component ordering transactions, the public node, the one publishing data to the layer below, the explorer and the monitoring. It is systems work as much as contract work.

Portfolio

What we did on this, project by project.

Manora

Layer 2 network with its own gas coin

  • Seven contracts on an OpenZeppelin base: immutable fixed-supply coin, wrapper, reimbursement of publishing costs, distribution with progressive vesting, treasury with delayed withdrawals and a daily cap, five-tier staking with fee discounts from 10% to 70%.
  • A shared upgradeable base with a mandatory 48-hour delay on every change, role control and an emergency stop.
  • 487 automated tests at 99.4% statement coverage; mathematical verification on 27 of 29 properties and 50 of 51 rules, random sequences against the staking invariants, automated analysis with no true positives.
  • Network on Arbitrum Nitro with a custom gas coin and distinct identifiers between development and production for replay protection.
  • Phased release with a manifest and post-release checks, plus a thirteen-document package for external auditors.
  • Solidity
  • OpenZeppelin
  • Hardhat
  • Foundry
  • Docker
  • Arbitrum Nitro

Need this?

Tell us the problem and we'll tell you how we would tackle it — and if it isn't worth doing, we'll tell you that too.

Let's talk