I'm Pratyush Shivam, CTO of Konfidio in Berlin. One sentence shapes how I design every screen on top of a ledger: a dispatcher should see "approved", never a wallet or a hash.
The mistake
Many blockchain products are built as if their users wanted to learn blockchain. They ask people to install a wallet, guard a seed phrase, wait for confirmations and read long hexadecimal strings. For a developer that can be interesting. For someone approving a delivery at six in the morning, it's friction with no benefit.
What the user actually needs
Strip it back and most people in a business process need three answers: is this approved, who approved it, and when. Everything else is implementation detail.
Three rules I follow
- Keys stay out of users' hands. Signing happens in a properly protected service on the server side, after the platform has checked the person is allowed to act. Users log in the way they always have.
- Business words on the screen. Approved, signed, delivered, corrected. Never a hash, a wallet address or a fee.
- Proof on demand. The cryptographic evidence is one click away for the auditor or partner who needs it, and invisible for everyone else.
Why it matters
A ledger is plumbing. It earns its place by making records verifiable between companies, not by being visible. When people don't notice it, it's working.
This connects to my paper on what permissioned ledgers can and cannot prove, which is open access: doi.org/10.5281/zenodo.24438467.
More of my writing is at pratyushshivam.com.