Blockchain

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.

First question: do you actually need it?

In most cases the answer is no, and it is worth hearing that from whoever builds these things. A well-made database with an append-only change log and verified backups solves ninety-five per cent of traceability problems at a fraction of the cost, without tying you to a moving ecosystem.

It is genuinely needed when the ledger must be verifiable by parties who don't trust each other and none of them can be the custodian: consortia, supply chains with several actors, instruments representing transferable value. If the parties trust you, you don't need it.

When the answer is no we say so, and propose the cheaper route. It is the only way the opposite answer, when it comes, is worth anything.

The cost nobody quotes for

It isn't writing the contracts: it is verifying them. On a serious project, testing, analysis and formal proof weigh as much as the writing, sometimes more. Which is why low quotes in this field are a signal, not a bargain.

Then there is the external audit, which belongs in the budget from the start: no serious organisation puts value-handling contracts into production without independent review. And there is maintenance, because a chain changes too: protocol upgrades, node versions, dependencies to revisit.

What stays off the chain

Almost everything. On the chain go the few things that must be verifiable by everyone and modifiable by nobody: proof that an event happened, the transfer of a right, the balance of an instrument. Everything else — customer records, documents, personal data — stays outside, in normal systems.

It is a practical obligation before a matter of taste: personal data written to a public chain cannot be deleted, which collides with the right to erasure. The correct approach is to keep the data outside and put at most a fingerprint on the chain, allowing verification without disclosure.