I'm Pratyush Shivam, CTO of Konfidio in Berlin, where I lead the technology behind TrustedTrucks. The photo is from Delhi in September 2026, at a business event for TrustedTrucks. I wrote my first production code in 2016, and a lot of my job is still deciding where the hard parts of a system should live.
This post is about one of those decisions: where the keys go when ordinary business users act on a blockchain.
The problem
TrustedTrucks fingerprints shipment documents on a permissioned blockchain, so every company on a shipment can check which version was approved, when, and by whom. Every approval ends up as a signed entry.
Signed by what, though? The people approving are dispatchers, drivers and finance teams. They are not going to manage private keys, seed phrases or wallets, and they shouldn't have to.
The rule: applications never hold keys
Signing happens behind a signing service. The web platform and the Android app never hold keys, and users never see them. The flow looks like this:
- A user signs in to the product as a person with a role at a company.
- They take an action the platform understands, for example "accept this proof of delivery".
- The platform checks that this role, at this company, may take this action on this shipment.
- Only then does the signing service produce the signed entry that anchors the fingerprint and the approval.
Why this split works
- The product stays a product. A dispatcher sees "approved", never a wallet or a hash.
- Authorisation lives in one place. Roles and permissions are checked before anything is signed, the same way for web and mobile.
- Keys are an operations concern, not a UX concern. Rotation, storage and monitoring happen in one service, where they can be done properly.
- Clients can't sign behind the platform's back. A phone that's lost or compromised doesn't carry signing material.
What it doesn't change
The chain still proves only what it can prove: that a document hasn't changed since it was anchored, and which account approved it. Whether the right person was using that account is a question for sign-in and device security, which is exactly why those checks run before the signature, not after.
The takeaway
If your users are not crypto users, don't make them key custodians. Put the keys behind a service, put the permission check in front of it, and let the product talk in the language of the work.
More of my writing, films and projects are at pratyushshivam.com.
Top comments (0)