Lakshya

Blockchain, Honestly · Chapter 6 of 6

Where it works, where it does not, and how to tell

The public record on enterprise blockchain is unusually clear. Here it is, with a test you can apply in a minute.

7 min read1 diagramAll 6 chapters

This chapter is the point of the book. Everything before it was mechanism; this is judgement, and it is the part that makes you useful in a room where someone is proposing one.

Start with the test

FOUR QUESTIONS — ANY SINGLE “NO” ENDS IT 1. Do multiple parties who distrust each other need to write?One company writing its own records needs a database. This is the question most projects fail.NO → use a database2. Would a trusted operator be unacceptable to them?If everyone would accept a regulator, an exchange or a clearing house holding it — let them.NO → use a database3. Do you need the record to survive that operator?If a court, a regulator or a corrective entry must be able to change it, immutability is a liability.NO → use a database4. Can you live with hundreds of writes a second, not thousands?Chapter 2. If the answer is no, the technology cannot reach your requirement.NO → use a database Four yeses is a genuinely small set — and that is the useful finding, not a dismissal. Cross-border stablecoin settlement passes. Public-good registries with no natural operator pass. Supply-chain tracking, internal reconciliation and most enterprise pilots fail at question 1 — which is what the record below shows.
Question 1 is where almost everything dies. A great many proposals are one organisation wanting better records — which is a database requirement wearing a costume.

What the record actually shows

Enterprise blockchain has now had roughly a decade and a large budget. The results are public, and they are consistent enough to be worth stating plainly.

ASX CHESS — the clearest single case

The Australian Securities Exchange spent seven years replacing its clearing and settlement system with a distributed ledger built on Digital Asset's technology.

It was scrapped in November 2022, at a write-off of roughly A$245–270 million. The replacement programme is now conventional technology, with go-live pushed out to 2029.

The regulator then fined ASX for telling the market the project was ‘on track’ and ‘progressing well’ when internally it was not.

That second part is the transferable lesson. The technology risk and the reporting-integrity risk are different failures, and the second one is the one that gets people sanctioned.

  • TradeLens — Maersk and IBM's shipping platform, shut down in 2023. Its own post-mortem said it could not reach the level of industry collaboration required. Note that this is a failure of question 1, not of engineering: competitors would not co-write.
  • we.trade — a consortium of twelve European banks, ceased trading 2022.
  • Four of five major trade-finance consortiums have closed. This is a pattern, not a run of bad luck.
  • Nasdaq Linq, the 2015 private-market share issuance pilot — widely cited for years afterwards, never scaled into anything.

Set against that, the things that did work: stablecoins, which move very large volumes for cross-border value transfer, and where the honest comparison is against correspondent banking rather than against a database; tokenised money-market funds, where BlackRock's BUIDL and similar products have reached real scale; and JPMorgan's Kinexys (previously Onyx), a permissioned network handling meaningful daily volume in intraday repurchase agreements and cross-border payments.

What those three have in common is instructive. Each moves value between institutions that genuinely do not have a shared trusted operator, on a settlement problem where the existing process is slow because of intermediaries rather than because of compute. They pass all four questions. Most proposals do not.

The Indian picture, since it is unusually well documented

India's central bank digital currency, the digital rupee (e₹), is a live pilot and its numbers are published, which makes it a rare chance to see what adoption looks like without marketing.

  • The wholesale pilot — for settling government securities between banks — collapsed by more than 99% from its early volumes and RBI later paused adding new wholesale use cases.
  • The retail pilot reached about 0.003% of currency in circulation.
  • The widely reported ‘one million transactions a day’ milestone in December 2023 was reached after banks began paying part of employee benefits directly into CBDC wallets. Volume fell roughly 90% once that stopped. The milestone measured the incentive, not the demand.

And now the comparison that makes the point.

In the same country, over the same years: UPI did 228.3 billion transactions in 2025, and the Account Aggregator framework passed 2.61 billion linked accounts — a consent-based financial-data sharing network, which is exactly the kind of multi-party trust problem blockchain is pitched at.

Neither uses a blockchain. Both are ordinary systems with clear governance, open standards and a trusted operator.

India solved the multi-party coordination problem at extraordinary scale by fixing the standards and the governance rather than the data structure. That is the most useful single data point in this book.

So what do you do with all this

Not dismiss it. A technology can be badly oversold and still be the right answer for a narrow set of problems — and being able to say which narrow set, with the record to back it, is a far more valuable position than either enthusiasm or cynicism.

  • If someone proposes one, walk the four questions. Ask who the distrusting writers are, by name. If the answer is departments of the same company, you have your answer without a single technical argument.
  • If you are asked to build one, the security chapter is your checklist: multi-signature with signers on separate hardware, timelocks on privileged actions, aggregated oracles, OpenZeppelin rather than hand-rolled, fuzzing, and an explicit written answer to who can repoint the proxy.
  • If you are considering it as a career direction, re-read the note at the top of chapter 1 — the corpus behind this site mentions it zero times in 4,556 job descriptions. Learn it because the mechanisms are genuinely worth understanding and it makes you the person who can evaluate a proposal. Not because the hiring evidence supports it, because it does not.

For the banking-specific record — the digital rupee's own published figures, what atomic settlement actually removes, and why four of five trade-finance consortiums died — see three chapters in the other book: The digital rupee, and what its own numbers say, Tokenisation, and the one thread that did not collapse, and The consortium graveyard.

The strongest thing this subject teaches is not the cryptography. It is that coordination problems are usually governance problems wearing a technical costume — and that recognising the difference is a rarer skill than implementing either.

Check yourself

What is question 1, and why does it matter most?Do multiple parties who distrust each other need to write? Most proposals are one organisation wanting better records, which is a database requirement.
What happened at ASX?Seven years and about A$245–270 million written off in November 2022; the replacement is conventional technology. The regulator then fined ASX for saying the project was progressing well when it was not.
Why did TradeLens close?Not engineering — it could not reach the industry collaboration required. Competitors would not co-write, which is a question 1 failure.
What do the successes have in common?Stablecoins, tokenised funds and Kinexys all move value between institutions with no shared trusted operator, on problems slowed by intermediaries rather than compute.
What did the e-rupee million-a-day milestone measure?The incentive. Banks paid employee benefits into CBDC wallets; volume fell roughly 90% once that stopped.
What is the most useful Indian data point?UPI and Account Aggregator solved multi-party coordination at enormous scale — 228.3 billion transactions and 2.61 billion linked accounts — without a blockchain, by fixing standards and governance.
What should you say if someone proposes one?Ask who the distrusting writers are, by name. If they are departments of the same company, the answer is settled without any technical argument.
← The stack you would actually usePractice bank →