Skip to content
Velloreth
Financial Technology 9 min read

Blockchain Beyond Crypto: Practical Uses

Most blockchain projects fail because a database would do. A clear-eyed look at the use cases where shared ledgers actually earn their keep — and the ones that never will.

By

Ask a room of engineers what blockchain is good for and you will hear one of two answers: “digital money” or “nothing.” Both are lazy. The truth is narrower and more useful than either. A blockchain is a shared ledger that multiple parties can write to, that nobody can quietly rewrite, and that works even when the parties do not trust each other or any single operator. That specific property is valuable in a specific set of problems — and worthless in most of the problems it has been sold on.

This post is about telling those sets apart.

The one-question test

Before evaluating any blockchain project, ask: is there a single party who could operate a database for everyone involved, and would everyone accept that?

If yes, use a database. A shared Postgres instance with row-level permissions and an append-only audit log will be faster, cheaper, and easier to reason about than any ledger. Most enterprise blockchain pilots that quietly died — and there were hundreds — failed this test. A company putting its own supply chain data on a chain of its own design was theater: one trust domain pretending to be many.

If no — if the parties genuinely cannot trust a single operator — you have the condition where a shared ledger earns its place. Typical symptoms:

  • The counterparty set is small, known, and regulated (banks, insurers, customs authorities, suppliers).
  • Records must be auditable after the fact by parties who were not present for the transaction.
  • Disputes are expensive, and the ability to prove “this record existed at this time and was not altered” has real value.
  • No commercial neutral party exists who everyone would accept as the database operator. (Where a neutral operator exists — a clearing house, a card network — the market already solved it.)

With that test in hand, the use cases sort cleanly.

Where it has actually stuck

Trade documentation and finance

Trade finance is the oldest unglamorous blockchain win. A single international shipment generates a stack of documents — bills of lading, certificates of origin, letters of credit, customs declarations — each physically handled, couriered, and verified by counterparties who do not fully trust each other. Paper fraud in trade is a centuries-old problem: the same bill of lading gets pledged to multiple lenders; certificates get altered between issuers and banks.

Shared-ledger platforms in this space put the document lifecycle on a record that the issuing party, the bank, and customs can each verify independently. The document still originates from the same source, but it cannot be silently duplicated or edited downstream. Several major trade platforms built on this model have processed meaningful volume for commodity traders and banks — quietly, because trade finance has no consumer audience and does not advertise.

The value here is not decentralization in the ideological sense. It is: multiple regulated institutions, no single trusted operator over the full document set, and legal weight attached to the integrity of the record. That is the textbook condition.

Provenance and certification

Physical goods that carry claims — organic certification, conflict-free minerals, luxury authenticity, pharmaceutical chain of custody — face a consistent problem: the claim’s evidence lives in paper certificates and database entries that individual actors along the chain can edit.

The working pattern is unglamorous: at each handoff point, the party scans or records the item onto the ledger with whatever evidence exists at that moment (batch number, temperature reading, seal ID, certificate reference). Downstream parties can verify the full chain of custody without re-audiiting each supplier, and auditors can spot where the chain breaks.

Two honest caveats:

  1. The garbage-in boundary. The ledger proves what was recorded, not that the physical item matches the record. A counterfeit bottle scanned onto a chain with a valid-looking certificate reference will be faithfully recorded as a counterfeit. Blockchain solves record integrity, not physical-world integrity — you still need sampling, sensors, and human audit.
  2. Adoption is the hard part. The technology is easy; getting five companies in a supply chain to all use the same system, with the same scanning discipline, is a coordination problem. Most supply-chain blockchain projects died of coordination failure, not technical failure.

Where the coordination exists — consortium-backed systems with real anchor customers — provenance chains have run for years in food safety, luxury goods, and pharmaceutical distribution.

Cross-border settlement and stablecoins

Stablecoins — tokens pegged to a fiat currency, backed by reserves — are crypto-adjacent, and the speculation around them is real, but their non-speculative utility has quietly become the largest real-world blockchain deployment outside Bitcoin itself.

The use case is settlement. Traditional cross-border payments move through correspondent banking: multiple intermediaries, multi-day settlement, opaque fees, and cut-off times. A stablecoin transfer settles on-chain in minutes, at any hour, with a single fee. Convert to local currency at either end through an exchange or licensed on/off-ramp, and you have a working remittance rail.

This matters most for corridors where correspondent banking is expensive or unreliable. Remittance-dependent economies — the Philippines, parts of Africa, Nepal and the broader South Asian labor corridor — have seen fintechs and money operators use dollar stablecoins as the middle leg of transfers that previously went through slow banking chains. The local on-ramp and off-ramp remain regulated fiat businesses; the blockchain is the pipe in the middle.

The risks are honest and large: reserve quality varies enormously between issuers, redemption is not guaranteed in a crisis, and regulators are still writing the rules. But unlike most of the 2017-era blockchain pitch deck, this use case has paying users moving real payroll and family support money, not token speculators.

Verifiable credentials and identity

A credential that an issuer signs and you hold in your own wallet — a university degree, a professional license, a KYC verification — has a natural ledger-shaped problem: the issuer must be able to revoke it, the holder must control disclosure, and the verifier must trust the issuer’s signature without querying a private database every time.

Standards in this space (W3C verifiable credentials, various national digital identity pilots) use ledgers for the parts that benefit: a public registry of issuer keys and revocation status, so verification does not depend on the issuer’s server being up or cooperative. Several governments have piloted ledger-backed credential registries for qualifications and professional licensing.

The pattern worth noting: the credential itself does not live on-chain — that would leak private data. Only the issuer’s public key registry and revocation status do. Most “blockchain identity” designs that put personal data on a public chain are either wrong or rebranded centralized databases with extra steps.

Wholesale CBDC and tokenized deposits

Central bank digital currencies come in two flavors and the difference matters.

Retail CBDCs — a digital currency for ordinary citizens — have mostly stalled. The uncomfortable reason: in countries with working instant payment systems (UPI, Pix, FedNow-class rails), a retail CBDC offers little that does not already exist, while raising real concerns about surveillance, bank disintermediation, and privacy. Pilots have produced cautious reports, not launched products in most jurisdictions.

Wholesale CBDCs — settlement between banks and financial institutions — are progressing quietly. Cross-border wholesale settlement pilots between central banks have run for several years, testing interbank settlement on shared ledgers with real institutional participants. The appeal is not consumer payments; it is the plumbing: faster, programmable interbank settlement with atomic delivery-versus-payment.

Tokenized deposits — commercial bank money tokenized for programmable transfer — are the private-sector cousin of this idea, and arguably more likely to see production use, because they keep the bank relationship intact while adding programmable settlement for capital markets and trade.

Where it never belonged

For honesty’s sake, the graveyard list:

Sold asReality
Decentralized identity for consumersMostly centralized registries with tokenized branding; users never wanted the key management
Healthcare record sharingAccess control and standards were the problem; a ledger did not fix either
VotingCryptographic integrity is not the binding constraint; coercion and identity are — both worse on a public ledger
Internal enterprise workflowsOne company, one trust domain: an append-only log in the company database does this without consensus overhead
Most NFT provenanceSolves a problem (digital scarcity) that mostly should not exist; provenance for art that needed none
Land registries (most pilots)The hard part is legal title disputes and political will, not record immutability; several pilots quietly reverted to conventional systems

The land registry case deserves one nuance. A few jurisdictions have run ledger-backed land records beyond pilot stage, and where they work it is because a functioning legal system stands behind the records — the ledger adds tamper-evidence to a system that was already legally enforced. Where land title is contested or corrupt, immutability makes injustice harder to fix, not easier.

The engineering reality

For anyone actually building in this space rather than pitching it, a few things that hold regardless of chain choice:

  • Permissioned is usually correct. Public chains make sense for censorship-resistant money and stablecoin settlement. Consortium or permissioned designs make sense for regulated institutions that need known participants, data confidentiality, and legal recourse. Most enterprise work correctly lands on permissioned chains or hash-anchoring to a public chain for timestamping.
  • Off-chain data is the recurring weak point. Oracle problems, sensor trust, and API reliability break most “trustless” designs. Budget for the data layer accordingly; it is usually harder than the chain.
  • Legal wrapper beats technical wrapper. A smart contract that auto-executes still sits inside a contract law regime. The projects that survive have lawyers and engineers designing together from day one.
  • Consortium governance kills more projects than code. Who pays for the nodes, who sets upgrade policy, who admits new members, who eats the cost when a member refuses to upgrade — these questions decide the project’s fate years before any scaling debate matters.

What to watch

The technology has matured past both the 2017 hype cycle and the subsequent dismissal. What remains is a set of narrow, useful properties — tamper-evident shared records, tokenized settlement, verifiable credentials — applied where those properties are worth real money: trade, remittance settlement, provenance under regulation, and interbank plumbing.

If someone pitches you a blockchain, the two questions that filter signal from noise remain unchanged. Who are the multiple untrusting parties? And what breaks if any single one of them operates the database instead? If the answers are vague, you are looking at a database with a token attached. If the answers are sharp — five banks, a customs authority, and no one who can be the operator — you may be looking at something worth building.

Frequently asked questions

Why not just use a shared database?
If one party can be trusted to operate the database, use a database — it is cheaper, faster, and simpler. Blockchain only adds value when the parties cannot or will not trust any single operator with write access, and need cryptographic proof that history was not rewritten.
Are enterprise blockchains just databases with extra steps?
Permissioned enterprise chains are often closer to a replicated audit log than to Ethereum. That is fine when the audit property is the point — multiple auditors, regulators, or counterparties verifying the same records without exposing full data. It is overkill when the 'multiple parties' are one company's departments.
Do supply chain blockchains actually work?
Parts of them do. Scanning a physical item onto a chain at a checkpoint creates a record that cannot be quietly edited later — useful for certificates, provenance claims, and handoffs between parties. The garbage-in problem remains: the chain proves what was scanned, not that the scanned item was genuine.
Are CBDCs happening?
Wholesale CBDC projects for interbank settlement are active in several jurisdictions. Retail CBDCs have stalled in many countries after privacy pushback and a lack of compelling use cases beyond existing fast-payment systems like UPI. Most central banks that launched pilots have not launched products.