NIST published a good paper describing blockchain, with a flowchart (Figure 6) to help people determine if it's a good fit for their use case: * https://nvlpub

NIST published a good paper describing blockchain, with a flowchart (Figure 6) to help people determine if it's a good fit for their use case: * https://nvlpubs.nist.gov/nistpubs/ir/2018/nist.ir.8202.pdf#page=53 https://nvlpubs.nist.gov/nistpubs/ir/2018/nist.ir.8202.pdf#p... It asks a series of questions, and if you answer "Yes" to all of them then blockchain should be examined: * Do you need a shared, consistent data store? (No: Consider Email / Spreadsheets.) * Does more than one entity need to contribute data? (No: Consider database.) * Data records, once written, are never updated or deleted? (No: Consider database.) * Sensitive identifiers WILL NOT be written to the data store? (No: Considered encrypted database.) * Are the entities with write access having a hard time deciding who should be in control of the data store? (No: Consider managed database.) * Do you want a tamperproof log of all writes to the data store? (No: Consider database.) All Yes: "You may have a useful Blockchain use case."