Every few months someone asks me why we didn't build TrustedTrucks on a public blockchain. It's a fair question. Public networks are open, battle-tested and have enormous ecosystems. So why would a logistics platform choose a permissioned network instead?
The short answer: because freight is a business between known companies, and its data is commercially sensitive. The long answer is worth writing down.
Freight data is competitive data
Think about what a single shipment reveals. Who ships what, from where, to whom. Which carrier was chosen, at what rate, on which lane. How often a customer ships, and how much.
For a logistics company, that is not "transaction data". It is the business. A forwarder's customer list and its rates are exactly what a competitor would love to see.
On a public chain, everything written is visible to everyone, forever. You can encrypt payloads and use clever privacy techniques, but you are always working against the grain of a system designed to be transparent to the whole world.
On a permissioned network, visibility is the default you design, not the exception you fight for. Each party sees what its contract and role allow, and nothing more.
The participants are known anyway
Public blockchains solve a hard problem: how do strangers who don't trust each other agree on a shared history without any authority in the middle?
Freight doesn't have that problem in the same way. A shipper knows its forwarder. A forwarder knows its carriers. A consignee knows who is delivering. These are registered companies with contracts, insurance and legal obligations.
What freight lacks is not identity. It is a single version of the truth that all those known companies can rely on. A permissioned network gives exactly that: a shared, tamper-evident record between identified participants, with governance that matches how the industry already works.
Predictable costs matter more than you'd think
A carrier doesn't want to think about network fees that move with market sentiment. Neither does a finance team trying to price a service.
On a permissioned network, the cost of recording a delivery or approving an invoice is an engineering and operations question, not a market one. That predictability is what lets you build a product that a dispatcher, a finance officer and a CFO can all plan around.
Compliance needs a door you can open
European freight runs under real rules: data protection, tax, customs, transport law. Regulators and auditors sometimes need to look at specific records, and companies have the right to know who saw what.
Permissioned networks make that manageable. You can define who operates nodes, who can read which records, and how access is granted and logged. You can answer the question "who has seen this shipment?" without hand-waving.
What we keep from the public world
None of this means rejecting what public blockchains got right. The core ideas carry over completely:
- Tamper evidence. Once something is anchored, nobody can quietly change it afterwards.
- Shared history. Every party works from the same record instead of reconciling five versions.
- Programmable agreements. Smart contracts encode who must approve what, in which order.
- Standard tooling. An Ethereum-compatible network means mature languages, libraries and auditing practices.
We take the parts that create trust between companies and leave out the parts that would expose them.
The real test is boring
The best sign that the architecture is right is that nobody on the platform talks about it. A dispatcher sees "approved". A carrier sees "paid". A finance team sees an invoice backed by evidence.
The blockchain is there, quietly keeping the record honest. That is exactly where it belongs.
I'm the CTO of Konfidio, where we build TrustedTrucks: one shared record for European freight.
