| Table of Contents |
|---|
Key Points
...
| Reference_description_with_linked_URLs______________________________ | Notes_______________________________________________________ |
|---|---|
| s Enterprise Blockchain Concepts and Value | |
| m Blockchain Consulting | |
| s Blockchain Opportunity Assessment - BOA | |
| m Blockchain Use Cases More | |
| 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 |
| https://www.geeksforgeeks.org/types-of-blockchain/ | Blockchain types: permissioned, permissionless, hybrid, consortium |
| Layer 2 Blockchain side chain models - Blockchain101 | |
| Layer 3 app engineering value adds | |
| Anthony Day Blockchain Layer Models | |
| Blockchain features and value concepts - datacenterk | summary of blockchain capabilities and value add |
| m Ethereum | |
| m Bitcoin overview | |
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 |
| https://www.udemy.com/course/blockchain-for-digital-transformation/learn/lecture/25252334#overview | Baijiu Udemy course Digital Transformation with Blockchain |
| 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
Blockchain technologies - Hash functions and Merkle Trees
hash-functions-blockchain-kier-finlow-bates-2023.pdf link
hash-functions-blockchain-kier-finlow-bates-2023.pdf. file
Cloud Services Models
cloud-xaas-models-compared-cf.PNG
...
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.
Blockchain Layer Models to Improve Scaling, Performance
https://forkast.news/what-is-layer-3-key-to-blockchain-future/
Layer 1s are characterized as the foundational blockchains like Bitcoin and Ethereum that have their own native cryptocurrency used to reward those who work to secure the network itself.
Layer 2s are protocols built on top of L1s designed to increase transaction speed and mitigate scaling difficulties of layer 1s while leveraging the security of the base chain. For example, Arbitrum is an L2 created to improve Ethereum’s speed of processing transactions as well as overall flexibility and scalability, and it has given birth to a broad range of DeFi protocols.
Layer 3s, on the other hand, offer even higher levels of customizability. At this layer, developers can carry out customized designs that L2s cannot easily achieve, especially for lower-cost execution and privacy-preserving functionalities.
- use cases are for custom blockchain solutions, not general purpose blockchain solutions
- L3s enable customized scaling and realize important functionalities — such as privacy — that L2s can’t effortlessly achieve on their own. L3s increase computation speeds and scalability of single applications by not having to share ZK-circuits with other applications on a single chain.
The current L2 serves as a general-purpose scaling, while L3 accomplishes customized scaling.
For example, an L3, which adopts customized circuits depending on the demand of a specific decentralized application, can achieve better performance. Another example is Validium as L3. This design provides higher levels of throughput at a relatively low cost for decentralized apps by avoiding pushing compressed data to the L1 and utilizing validators to secure the digital asset. L3s can be employed as low-cost and high-performance scaling solutions that allow projects to have more choices for potential solutions, depending on their particular use cases.
L3 challenges now
- One of the main challenges is the lack of standardized infrastructure for L3s. Since L3s are built on top of L2s, they require a standard infrastructure to operate efficiently.
- more development in ZK-rollup technology, which is the underlying technology for L3s. ZK-rollups have the potential to significantly improve the efficiency and scalability of L3s
The Graph - billable 3rd Party Blockchain Query and Indexing Service
https://thegraph.com/docs/en/network/overview/
The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs, to retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens (GRT). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
Active Indexers, Curators and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
1) The Graph is a decentralized protocol for indexing and querying blockchain data.
2) Blockchain Explorer such as Etherscan, Blockchain.com , Blockchain Explorer are a type of Centralized Blockchain indexers that index low level data such as transaction, gas and etc.
3) When Dapps want to index higher level data (unique to their application), then can use 'The Graph' protocol and spin up a sub graph easily, making their data accessible while enjoying all the benefits of decentralization.
4) Using GraphQL makes querying the blockchain easy to use like google, you just need to create your own Scheme and define which smart contracts and events to listen to.
if you're passionate about Blockchain, dApps, and the future of web3, I encourage you to reach out.
How to use Blockchains for a specific use case?
Andy Martin
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 that drives solution design, not the technology.
Engineers don't use just one type of data store for a solution. The same concept applies to blockchains. You use what is needed to fit the use case. Improvements are needed for consumption of blockchain service layers to reduce the work needed by most blockchain platforms today. Yes many different teams are working on this effort currently. I tend to lean toward the open source platforms like Hyperledger where that work is often more visible and consumable.
Potential Value Opportunities
...