Blockchain Technology

  The outcome is usually decided before the first sprint Enterprise blockchain projects rarely die from a defect in the chain. They die from decisions made in the weeks before anyone writes code: choosing a ledger for a problem that never needed one, scoping a pilot that avoids every hard requirement, or deferring compliance and key custody until the architecture is already fixed. That is good news. Those decisions are cheap to revisit early and expensive to revisit at launch. What follows are the checks worth running before a budget is approved. First, try to disqualify the blockchain A distributed ledger earns its cost in one situation: several parties who do not fully trust each other need to agree on the same record, and none of them should be the one operating it. If that sentence does not describe your problem, the properties you actually want- durability, integrity, and an audit trail are cheaper from a database you already know how to run. Signals that a chain is the wrong ...