Blockchain: The New Architecture of Trust, A New Geography of Power

On 31 October 2026, a nine-page whitepaper appeared on an old cryptography mailing list. The author was named 'Satoshi Nakamoto'. Nobody knew who he was — where he lived, whether he was alive, whether he was one person or many. The title was plain: 'Bitcoin: A Peer-to-Peer Electronic Cash System'. Inside those nine pages lay the skeleton of a technology the world would later learn to call blockchain. Curiously, the whitepaper never once bothered to explain the word 'blockchain' separately. The mechanism was so intrinsic that its author felt no need even to name it. Years spent in stadium camera booths taught me one thing — the real story is never on the scoreboard, it is in the rules that make the scoreboard possible. Blockchain is the same. Everyone watches the price of Bitcoin; I want to watch the rule that makes the price possible.

What is blockchain, in plain terms? It is a digital ledger kept not by one computer but by thousands at once, where an entry, once written, is practically impossible to erase. A ledger is a book of accounts. The difference is simply this — this book has no single owner, no bank, no central authority to declare 'this is right, that is wrong'. Each page is a 'block'. At the start of each page sits a unique imprint of the previous page — like a fingerprint. So if someone tries to alter a figure on page ten, the imprint on page eleven will not match, and the entire chain of imprints running through every later page collapses. That chain is what we call blockchain — a chain of blocks.

This imprint has a technical name: a 'hash'. A hash is a mathematical machine that takes any text and turns it into a code of fixed length. The same text always yields the same code; change a single character and the code changes entirely — you cannot even tell by how much. This one-wayness is the spine of blockchain's immutability. Take an example from sport: if a ball's trajectory is taped, every frame depends on the frame before it. Remove one frame and the continuity of the rest wobbles. In blockchain, the hash plays exactly that role — every block cradles the hash of the block before it.

But a hash alone is not enough. Who decides which page is valid? Here enters the question of 'consensus'. In Bitcoin's early era, the answer was 'proof of work' — to earn the right to add a block, a computer must solve a difficult puzzle. The puzzle is hard enough that finding even one correct guess consumes enormous electricity. Whoever solves it first writes the block and takes the reward. Why make the competition so hard? Because to cheat, you would have to out-compute the entire network — practically impossible. Consensus does not mean force; it means arithmetic. The more verifiable work you can show, the more power the network gives you — and power here is not inherited, it is earned through proven labour.

One great weakness of this model is energy consumption. In 2026, Bitcoin's annual electricity use was discussed as exceeding that of many mid-sized nations. The response came in 'proof of stake' — where power is set not by computing strength but by how much value you have 'staked' as collateral. Ethereum walked this path in 2026. To me it feels like a change in the rules of a game. Before, the loudest runner became captain. Now the captain is whoever has staked the most — and betrayal means losing that stake. The punishment is not external but built in.

Now the real question — why is blockchain called a 'trust machine'? Normally, to send money we trust a bank. The bank says your balance is this much. We do not question it; we simply accept. In blockchain, that seat of trust is occupied by rules. No one will tell you your balance — anyone can verify it themselves. This is the so-called 'trustless' system: where no individual needs to be trusted, because the system is itself verifiable. If I try to enter a stadium without a ticket, a guard stops me — that is reliance on a person. If a turnstile reads the barcode and opens automatically, that is reliance on a rule. Blockchain is that turnstile.

In 2026, through Vitalik Buterin, Ethereum arrived, and blockchain stopped being merely a 'ledger of money' to become a 'programming platform'. Here came the 'smart contract' — an agreement written as code that executes itself the moment conditions are met. Imagine an insurance contract: if a flight is delayed more than three hours, compensation automatically moves to the passenger's account. No form to fill, no phone to answer, no 'let us see'. The real revolution of the smart contract is not in the technology but in the doorway — a door that leads directly to code instead of the office of a middleman. But caution is required: if the code is flawed, the damage is also automatic. In 2026, a project called 'The DAO' had exactly such a flaw exploited, and tens of millions of dollars were drained.

Blockchain is not one single kind. In a 'public' blockchain anyone may join, as with Bitcoin or Ethereum. In a 'private' blockchain only authorised institutions may enter — for instance a bank consortium's own network. A 'consortium' sits in between — run jointly by several organisations. In cricket terms: a public blockchain is street cricket, where anyone can come to bat. A private blockchain is a franchise league, with fixed teams and fixed rules. Both have their place — the question is which one your task needs.

Now look at applications. First, finance. In decentralised finance, or DeFi, lending, interest and exchange all run on smart contracts, without banks. Second, supply chain. If every step from coffee bean to your cup is written on a blockchain, no one can swap goods midway. Third, healthcare — a patient's records in one place, yet no single party able to alter them unilaterally. Fourth, land records. In countries like Bangladesh or India, disputes over land deeds are perennial. If a deed lives in a ledger no one can secretly alter, the very nature of litigation would change. Fifth, voting — where no one can alter the roll after a vote, yet the voter's identity stays private.

Here I want to make a counter-intuitive claim. The technology born in the name of decentralisation may, in practice, find its biggest users to be states and large corporations. Because public blockchains are slow and limited in privacy, while a bank or government needs transparency in its internal accounts, and privacy too. So private and consortium blockchains are quietly growing today — in hospitals, banks, ports, even central banks. The outside observer sees only the swings of cryptocurrency and concludes blockchain is dead. Yet the real architectural work proceeds silently, inside offices.

Now the challenges, because I am not in the habit of closing my eyes out of affection. The first barrier is the 'scalability trilemma' — in simple terms, a blockchain cannot hold three qualities at once: security, decentralisation and speed. Bitcoin is secure and decentralised but slow — only a few transactions per second, where Visa handles thousands. To gain speed you must concede either security or decentralisation. The second barrier is energy and environment. The third is security — the so-called 'fifty-one percent attack', where controlling more than half the network's computing power lets one break the rules. In smaller blockchains this risk is real. The fourth is quantum computing — if future quantum machines become powerful enough to break today's encryption, the whole foundation comes into question. Researchers are already working on 'post-quantum' algorithms.

The most practical barrier is regulation. India has long wavered — taxing cryptocurrencies on one hand, threatening outright bans on the other. In Bangladesh, cryptocurrency use is effectively prohibited. But a subtle distinction must be understood: blockchain technology and cryptocurrency are not the same thing. A state can ban crypto, but the idea inside blockchain — a verifiable, immutable ledger — cannot be banned. Many countries now accept this and adopt the technology separately.

The biggest example of this adoption is the central bank digital currency, or CBDC. China, India, Sweden — many nations are testing their own digital money. There is a curious paradox here. A CBDC is really a centralised version of blockchain — that is, a technology famous for being centreless is being brought under the state's central control. Some will be disappointed; some will call it a pragmatic decision. To me, the technology here is a political laboratory — a lab in which both the centre and the periphery test their own strength.

Another current is Web3 — where user data belongs to the user, not to big platforms. Alongside it, tokenisation — breaking land, artwork, even future income into small fractions to be traded. This opens the door of capital to the small investor too. But with it comes risk: who truly owns this asset, and who merely holds a digital claim — that question remains unresolved.

In stadiums over long years I learned one thing: great change begins in small, overlooked moments — when nobody is even watching. The blockchain whitepaper was first such an overlooked post. So when someone says today 'blockchain was a bubble, it is over', I smile. When cricket's T20 arrived, the old guard said this is not the game. Yet that very format transformed the economics of the whole sport. Blockchain is the same — perhaps today's name, perhaps another name tomorrow, but the idea inside will remain: a ledger in which power and trust are both distributed, belonging to no one alone.

The final question, then, is not of technology but of us. Are we ready for a world where blame cannot be shifted onto a middleman, because the middleman is gone — the blame falls straight on the code, and code is written by people? Or will we seek the same excuse we have sought in every age — who is responsible? Not me? Blockchain does not erase responsibility. It merely shows that responsibility was never lost anywhere; we simply kept our eyes turned away. And that, perhaps, is this technology's greatest and quietest revolution.