Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 2 min read

Why freight needs a permissioned blockchain, explained across a table

I'm Pratyush Shivam, CTO of Konfidio in Berlin, where I lead the technology behind TrustedTrucks. The photo is from a business event in Delhi in September 2026, where I was for TrustedTrucks. Across a table like that one

I'm Pratyush Shivam, CTO of Konfidio in Berlin, where I lead the technology behind TrustedTrucks. The photo is from a business event in Delhi in September 2026, where I was for TrustedTrucks. Across a table like that one, the question I hear most is simple: why a permissioned blockchain, and not a public one?

Here is the answer I give, in engineering terms.

Freight is a network of known companies

A shipment involves a shipper, a forwarder, a carrier and a consignee. They sign contracts with each other. They know each other's names, addresses and tax numbers. Nobody on the job is anonymous, and nobody wants to be.

A permissioned network matches that reality. Participants are onboarded as known companies with known identities, and every approval is tied to the account that made it. "Who approved this version?" has an answer with a company name in it.

The chain holds fingerprints, not documents

Commercial documents carry prices, routes and customer names. Putting them on any shared ledger, permissioned or not, would be a mistake.

So the chain holds fingerprints. A document's hash is anchored; the document itself stays in the platform, visible only to the companies on that shipment. Anyone with access can check that the file in front of them matches the fingerprint, without the ledger revealing what the file says.

Applications never hold keys

If every user had to manage keys, the product would fail on day one. Dispatchers and drivers are not key custodians.

Signing happens behind a signing service, so applications never hold keys and users never see them. A dispatcher sees "approved". The signature, the fingerprint and the block are there for the day someone disputes it.

Running it is the real work

Designing a network is one challenge. Running it reliably every day is another: onboarding participants, permissioning, monitoring, upgrades. That operational side is most of what a permissioned network actually costs, and it's where the engineering attention goes.

What it doesn't prove

Worth repeating every time: a fingerprint proves a document hasn't changed since it was anchored, and who approved it. It doesn't prove the document was true. People still check the goods. The network makes their decisions verifiable.

The short version

  • Known companies, so known identities.
  • Fingerprints on the chain, documents off it.
  • Keys behind a service, never in the app.
  • Operations are the real cost.

More of my writing, films and projects are at pratyushshivam.com.

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.