Key Points
- blockchain at a minimum is DLT - decentralized ledger technology
- an immutable ledger provides a trusted ledger of transactions for all participants in the network
- like any technology, blockchain can add real value when applied correctly to the right use cases
- public blockchains
- Bitcoin and Ethereum are the 2 most popular public blockchains
- Ethereum offers smart contracts to provide common business logic controls on transactions
- Ethereum could also be implemented as a private blockchain when needed
- public blockchains allow anyone to participate
- public blockchains normally provide a degree of anonymity for participants but everyone can see all transactions
- public blockchains with a high number of commit nodes typically have poor performance
- permissioned blockchains
- permissioned blockchains are normally private and require participants to enroll through member services
- permissioned blockchains require read and write permissions to access the blockchain
- permissioned blockchains normally have identified participants
- participants are added through membership services
- transactions may be private between specific participants but macro demand is often public
References
| Reference_description_with_linked_URLs______________________________ | Notes_______________________________________________________ |
|---|---|
| https://www.slideshare.net/DevdattaAjgaonkar/introduction-to-blockchain-194331423 | Blockchain, Bitcoin, Crypto, Smart Contract concepts slideshare |
| https://www.slideshare.net/Synerzip/blockchain-application-development-101 | Blockchain App Development Concepts 101 - slideshare - sweetbridge |
| https://wiki.hyperledger.org/display/fabric/Design+Documents | Fabric design documents wiki |
| https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=11700#Filter -Results/12515 | Fabric release planning dashboard |
| https://www.smallbusinessadvocate.com/small-business-article/blockchain-is-here-are-you-ready-3330 | Blockchain concepts and assessment Jim Blasingame (smallbusinessadvocate.com/). He has just released a three-part series on blockchain that is excellent, and each is a quick read. #1 Blockchain is here - are you ready, #2 Blockchain isn't the end of trust, it is the future of trust, and #3 Your Blockchain close encounter of the first kind. Here is the first article, and I will let you find the next two on his site. Great work, Jim... https://lnkd.in/eJ8qGBE |
| Training materials on Fabric | |
| https://medium.com/coinmonks/build-a-blockchain-poc-application-using- hyperledger-fabric-6bbe633c2204 | Build a Blockchain PoC Application using Hyperledger Fabric |
| Cyrpto Notes | |
| https://blockgeeks.com/guides/security-tokens-explained/ | Security Tokens - regulated assets, peg to fiat ? |
| https://blockstack.org/ | Blockstack - Development stack for Dapps - compare to Truffle uses mining, tokens, etc |
| http://incomelion.com/how-bitcoin-transactions-work/?ref=quuu&utm_content=buffer6b6d6&utm_medium=social&utm_source=linkedin.com&utm_campaign=buffer | How Bitcoin works - High level concepts |
| https://docs.blockstack.org/browser/hello-blockstack.html | Blockstack tutorials |
| https://blockstack.github.io/blockstack.js/ | Blockstack js services - useful interface model |
| Other Hyperledger Notes | |
| https://www.forbes.com/sites/quora/2019/05/29/what-do-people-misunderstand -about-blockchain-technology/#447341245e39 | Jerry Cuomo on common blockchain misconceptions |
| Other Blockchain Concepts | |
| https://medium.com/coinmonks/public-vs-private-blockchain-in-a-nutshell-c9fe284fa39f | public vs private blockchains revisited |
Key Concepts
Cloud Services Models
cloud-xaas-models-compared-cf.PNG
Structured Platforms
- Abstract the operational processes of application deployment away from developers and app teams.
- Can be deployed across private and public clouds
- Capabilities like service brokers, monitoring, scaling, etc. are integrated natively.
- Examples: Cloud Foundry Application runtime, red Hat openShift, Apprenda, etc.
UnStructured Platforms
- Provide control and autonomy for app teams and developers over app deployment workflow.
- Can be deployed across private and public clouds.
- Capabilities like service brokers, monitoring, scaling, etc. must be developed or delivered by additional services.
- Examples:Cloud Foundry Container runtime, kubernetes, Mesosphere, Docker, Tectonic, etc.
Kubernetes Fabric Deployment workshop
https://github.com/aidtechnology/hgf-k8s-workshop/tree/master/prod_example
Covers manual setup of a blockchain network, kafka, kubernetes, CA administration etc
Public vs Private Blockchains Revisited - 2019 article
https://medium.com/coinmonks/public-vs-private-blockchain-in-a-nutshell-c9fe284fa39f
Brian Behlendorf - 2018
- public or private defines who can read the blockchain
- permissionless or permissioned defines who can write to the blockchain
The open versus closed brings in to consideration who’s able to read that data.
And so, we can talk about solutions which are public and open, public and closed, private and open, private and closed.
replace open / closed with permissionless / permissioned in the chart below ...
Pubilc blockchains can be permissioned ( eg Ethereum ) but lack the tools Hyperledger, Corda provide
Public blockchains normally provide anonymity. Private blockchains require identified participants.
Private blockchains need identity management
Most of the time, private blockchains tend to come with identity management tools or a modular architecture, where you can plug in your own identity management solution. This can be anything from a Membership Service Provider to an OAuth solution using Google, Facebook, LinkedIn, etc.
Motivations in public blockchain
We rely on economics and game theory incentives to ensure that everybody in the system behaves honestly and according to the rules.
We set up situations through group consensus, through which honest participants are economically rewarded, where dishonest ones only incur work or cost, with no possibility of ever recouping that cost.
Motivations in private blockchain
we know who an individual is, what organisation they’re associated with and what their role is, we also assume that they’re going to behave fairly, because if not, we know exactly who’s misbehaving and they know that they’re gonna suffer the consequences for that.
False assumption on who can see transactions in private blockchain
Transactions are not publicly viewable (transparent) in the blockchain, and only selected nodes can access the ledger.
Examples include: R3 Corda, which can transact between nodes, and the rest of the blockchain does not participate
Fabric allows control over what transactions and related demand are visible to others on a blockchain
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.
Potential Value Opportunities
Potential Challenges
Candidate Solutions
Step-by-step guide for Example
sample code block