{
  "id": 21220536,
  "title": "Nobody should have to learn blockchain to use your product",
  "url": "https://urgent.news/2026/11/22/nobody-should-have-to-learn-blockchain-to-use-your-product",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-22T14:17:35.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/pratyushshivam/nobody-should-have-to-learn-blockchain-to-use-your-product-3ph"
  },
  "original_language": "en",
  "account": "Pratyush Shivam, the CTO of Konfidio based in Berlin, has a simple guideline for designing user interfaces over blockchain ledgers: present the status as \"approved\" instead of revealing technical details like wallets or hashes. Developers often design blockchain products with the assumption that users want to learn and engage with the underlying technology. However, this approach creates unnecessary friction for users who simply need to approve deliveries or transactions. In reality, most business users only require three key pieces of information: approval status, the approver's identity, and the time of approval. All other information is merely technical details that can be hidden from the user. Pratyush follows three main principles when building his products: keep keys out of the user's hands, handle signing on the server side after verifying user permissions, and use familiar business terminology like \"approved\" or \"signed\" instead of technical jargon. The cryptographic proof should be easily accessible for auditors or partners who need it, but invisible to the end-users. By focusing on the core functionality of the ledger as a means to make records verifiable between companies, Pratyush believes that users should not even notice its presence. This approach aligns with his published work on the capabilities of permissioned ledgers, which can be found at doi.org/10.5281/zenodo.24438467. Pratyush's insights can also be found on his personal website at pratyushshivam.com.",
  "summary": "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…",
  "key_points": [
    "Present approval status as \"approved\" instead of technical details.",
    "Developers assume users want to engage with blockchain technology.",
    "Focus on core functionality, keep technical details hidden."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}