Versions Compared

Old Version 39

changes.mady.by.user jimm1

Saved on

compared with

New Version Current

changes.mady.by.user jimm1

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Reference_description_with_linked_URLs____________________________Notes____________________________________________________________


https://wiki.hyperledger.org/display/fabric/Design+DocumentsFabric Design documents from wiki - see github and Jira also
https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104Fabric product roadmap - JIRA
https://wiki.hyperledger.org/display/fabric/PlaybacksFabric playbacks of design docs
https://lists.hyperledger.org/g/fabric/topicsList server messages
https://wiki.hyperledger.org/display/HYP/Calendar+of+Public+MeetingsFabric public meetings calendar
https://chat.hyperledger.org/channel/fabric-maintainersFabric rocket chat channels


https://jira.hyperledger.org/browse/FAB-106?jql=project%20%3D%20FAB%20AND%20issuetype%20%3D%20Epic%20AND%20fixVersion%20in%20(v2.0.0%2C%20v2.1.0)%20ORDER%20BY%20%20keyJira Fabric product query
file:///C:/Users/Jim%20Mason/Google%20Drive/_docs/howto/tech/blockchain/hyperledger/fabric/docs/design/v2.0/Hyperledger%20JIRA%202019-06-21T14_34_03-v2p0-carrot.xlsxdownload of Jira Fabric product query

https://github.com/IBM/hlf-internals


Fabric Internal Architecture - IBM - v1.4x




IBM Blockchain
https://finance.yahoo.com/news/ibm-announces-multicloud-blockchain-215700061.htmlIBM Blockchain uses Kubernetes to create networks joining peer nodes from Azure, AWS and Google
https://bmos299-fabric.readthedocs.io/en/latest/protocol-spec.htmlOLD 3rd party copy of Fabric docs


Fabric Features- More resources


https://slideplayer.com/slide/14489867/

https://drive.google.com/open?id=1D2feED5WxdgxWQLdSPb5t87TFV50OFI4

Private Data Collections - 2018 - slides
https://lists.hyperledger.org/g/fabric/topic/question_about_implicit/31717564?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,31717564Implicit private data collections answer - 2019
https://drive.google.com/open?id=1mxdeUuEymgtmx1dF5Azz5Ph_2F1-7cfMFabric Private Data Concepts
https://drive.google.com/open?id=1g7vK3kgb1qtnP7pgF1oznDavtesodk9pFabric SideDb

External Chaincode execution from build packs vs Docker


Fabric component services
m gRPC and other protocolsgRPC to executes the smart contract deployed through the chaincode as a remote process that interacts with peer via gRPC.












Fabric interfaces


https://github.com/hyperledger/fabric-chaincode-evm

https://raw.githubusercontent.com/hyperledger/fabric-chaincode-evm/master/EndToEnd.png

Hyperledger Fabric EVM chaincode

enables one to use the Hyperledger Fabric permissioned blockchain platform to interact with Ethereum smart contracts written in an EVM compatible language such as Solidity or Vyper.

https://wiki.hyperledger.org/display/HYP/GardenerGardener - oracle support for external data in smart contracts




Deployment and Management
https://drive.google.com/open?id=1so3SSqnNoCvvG76Ip6ESuR8b_ySg1rNrJustitia - manage and deploy by node w multiple admins
https://drive.google.com/open?id=1-LmT_RAUS96uiJYMLNbgWhKkvqizx90YKubernetes lab for Fabric v1.3 - 2018




...

After transaction commit completion notification, validate block hashes the same on peers if desired 


Each peer logs its block commit hash every block at INFO level. The block commit hash is a hash over all valid transactions that are written to state database. So you can compare block commit hashes across peers to ensure no fork. Look for a peer INFO message every block containing 'commitHash', e.g.:

commitHash=[0d01cbc2d186675855d5b52f2bda5050ff7238d2527062d0fd5c0a8220d817fa]



Some users do like to validate query results by querying a 2nd peer to ensure they get the same results, that certainly is a valid pattern for critical applications.



Related upcoming work:

https://jira.hyperledger.org/browse/FAB-106 - A 'checkpoint' feature will allow peers to bootstrap a channel from a known good state without having to process all prior blocks since genesis block. The feature can also be used to compare global state across peers.

https://jira.hyperledger.org/browse/FAB-33 - BFT for ordering service to ensure a sufficient number of ordering service nodes sign off on blocks.



We will socialize RFCs for these proposed work items once they become available.





Thanks,


Dave Enyeart

...

step 5 - any dependent actors are notified of the completion of the purchase which may trigger additional transactions ( eg start an automatic purchase warranty etc )


Fabric v3x Features


see HLF Contributor 2024 meeting notes

https://wiki.hyperledger.org/display/fabric/Contributor+Meetings+2024

Remaining items for production v3.0 release

  • Previously deprecated features that have already been removed in v3 main branch
    • system channel
    • solo ordering (instead, utilize single node Raft)
    • kafka ordering (instead, utilize Raft)
    • configtxgen flag --outputAnchorPeersUpdate  flag (instead, utilize channel config updates)
    • fabric-tools image (instead, utilize client connections into Fabric networks)
  • Need to finish
    • Finish SmartBFT
      • Finish tests
      • Fix frequent test failures in SmartBFT unit tests and integration test
      • Allow the peer delivery client to select between Deliverer or BFTDeliverer - PR #4856
    • Finish v1 chaincode lifecycle removal - keep external APIs but just return an error message - Tatsuya can help Artem
    • Remove ability to specify orderer endpoints in channel configuration at global level 'Orderer.Addresses' as deprecated in v2 (instead, utilize v2 'OrdererEndpoints' in org config) - PR #4800
    • Change peer property blockGossipEnabled default to false - Block dissemination via gossip already deprecated in v2 (recommendation is to configure all peers as org leaders to receive blocks from ordering service).
  • #3663 Fabric v3 epic misc items 
    • #3306 new channel config MaxWriteSize, prevents large writes that potentially exceeds CouchDB max_document_size
    • #3343 ed25519 support
    • #3650 fabric-protos Go bindings based on protocol buffer APIv2 (v1 protobuf is deprecated) - potential deferral
    • #3704 older v3 ideas from Jira - e.g. Remove support for remaining Go plugins (endorsement and validation plugins) - potential deferral




Potential Value Opportunities

...