...

Good article on basic concepts of public — private and permissionless —  permissioned blockchain features. Nicely shows they address different use cases normally. When I look at use cases, I find Hyperledger Fabric provides the granularity and options to address a very wide set. A good example in the article is transaction data. With Fabric, I can decide on a supply chain what data is private and what is shared with everyone ( usually macro demand ).

A private, permissioned blockchain is more than just a secure database. It provides the provenance and proofs on transactions that increase trust among participants.

How to use Blockchains for a specific use case?

Andy Martin

https://www.linkedin.com/posts/andy-martin-387188a_blockchainthoughtfortheday-tokeneconomythought4theday-activity-6988468305934098432-f06V?utm_source=share&utm_medium=member_desktop

I think there are clear use cases for private blockchains in addition to public ones - not just for ERP integrations. In my experience, engineering success assumes that we have a set of tools ( public, private, permissioned, permissionless blockchains, message services, other protocols, other methods of sharing information etc ) that we just assemble to fit a specific use case. Blockchain is only part of the picture, it's the use case which includes trust engineering.

Potential Value Opportunities

...