Technical Introduction to IBM's Open Blockchain (OBC)
21 likes19,117 views
This document provides an introduction to Open Blockchain (OBC), an open source blockchain platform contributed by IBM. It discusses the need for permissioned blockchain networks, describes what OBC is and its roadmap. It then provides step-by-step instructions for setting up a sample OBC network with multiple validating peers and deploying a sample chaincode application across the peers.
![14
Step4: Deploy application
14
vagrant ssh
cd $GOPATH/src/github.com/openblockchain/obc-peer
export OPENCHAIN_PEER_ADDRESS=172.17.0.2:30303
./obc-peer chaincode deploy -p github.com/openblockchain/obc-
peer/examples/chaincode/go/map -c '{"Function":"init", "Args": []}'](https://image.slidesharecdn.com/technicalintroductiontoibmsopenblockchainobc-160411172520/85/Technical-Introduction-to-IBM-s-Open-Blockchain-OBC-14-320.jpg)
![16
Step4: Deploy chaincode
16
vagrant ssh
cd $GOPATH/src/github.com/openblockchain/obc-peer
export OPENCHAIN_PEER_ADDRESS=172.17.0.2:30303
./obc-peer chaincode deploy -p github.com/openblockchain/obc-
peer/examples/chaincode/go/map -c '{"Function":"init", "Args": []}'](https://image.slidesharecdn.com/technicalintroductiontoibmsopenblockchainobc-160411172520/85/Technical-Introduction-to-IBM-s-Open-Blockchain-OBC-16-320.jpg)
![17
Step4: Execute transaction
17
./obc-peer chaincode invoke -n <container-id> -c '{"Function":"put", "Args": ["key1",
"val1"]}'
/obc-peer chaincode query -n <container-id> -c '{"Function":"get", "Args": ["key1"]}'](https://image.slidesharecdn.com/technicalintroductiontoibmsopenblockchainobc-160411172520/85/Technical-Introduction-to-IBM-s-Open-Blockchain-OBC-17-320.jpg)
Ad
More Related Content
What's hot (20)
Viewers also liked (8)
Ad
Similar to Technical Introduction to IBM's Open Blockchain (OBC) (20)
![[Call for code] IBM 블록체인을 활용하여 투명하게 구호기금 관리하기 - Hyperledger Fabric v1.1 by 맹개발](https://cdn.slidesharecdn.com/ss_thumbnails/callforcodeblockchainglobalcitizenyunhomaeng-180807004902-thumbnail.jpg?width=560&fit=bounds)
Ad
More from Altoros (20)
Recently uploaded (20)
Technical Introduction to IBM's Open Blockchain (OBC)
- 1. Renat Khasanshyn CEO @ Altoros | @renatco Sergey Matykevich Sr. Software Engineer @ Altoros Technical Introduction to Open Blockchain (OBC) an IBM’s contribution to March 23, 2016
- 3. 1. Increasing demand for permissioned networks 2.Some users/use cases require validating or non-validating nodes to be controlled or sometimes just sponsored by select whitelisted organizations 3.Many network operators want transactors on network to obtain an identity from an issuing authority service on the network 4.Need for private networks, as well as public networks 5.Privacy on iPhone…. Privacy on the network? a. Many network operators want to keep identity and patterns of behavior completely private, inaccessible for 3rd parties 6. Performance / Scalability 7. World of many networks... Why Open Blockchain?
- 4. Not one but many…. A world of many networks
- 5. Why not Ethereum? Wrong License is the primary reason.
- 6. What is Open Blockchain?
- 7. What is scope of core Hyperledger vs. non-core?
- 8. OBC Roadmap Enterprise Integration Performance and Scalability Additional Consensus Plugins Additional Languages Portability
- 9. Biggest bottleneck? Identity on the blockchain.
- 10. 10 Step1: Create first validation peer 10 VP 1 VM vagrant ssh docker run --rm -it openchain-peer go build export OPENCHAIN_VM_ENDPOINT=http://172.17.0.1:4243 export OPENCHAIN_PEER_ID=vp1 export OPENCHAIN_PEER_ADDRESSAUTODETECT=true ./obc-peer peer
- 11. 11 Step2: Create second validation peer 11 VP 1 VM VP 2 VM vagrant ssh docker run --rm -it openchain-peer go build export OPENCHAIN_PEER_ID=vp2 export OPENCHAIN_PEER_ADDRESSAUTODETECT=true export OPENCHAIN_PEER_DISCOVERY_ROOTNODE=172.17.0.2:30303 ./obc-peer peer
- 12. 12 How peer discovery works? 12 1.VP2 sends DISC_HELLO message to its root discovery node (VP1) 2.VP1 replies with 3.Nodes start “chatting” a.Periodically sending DISC_GET_PEERS (asks to share active connections) b.Each node should reply with DISC_PEERS (list of connections) 4.After node receives new connections it starts chatting with them
- 13. 13 Step4: Deploy application 13 VP 1 VM VP 3 VM APP VP 2 VM CLI Chaincode
- 14. 14 Step4: Deploy application 14 vagrant ssh cd $GOPATH/src/github.com/openblockchain/obc-peer export OPENCHAIN_PEER_ADDRESS=172.17.0.2:30303 ./obc-peer chaincode deploy -p github.com/openblockchain/obc- peer/examples/chaincode/go/map -c '{"Function":"init", "Args": []}'
- 15. 15 Application is distributed across all peers 15 VP 1 VM APP VP 3 VM APP VP 2 VM APP CLI App source
- 16. 16 Step4: Deploy chaincode 16 vagrant ssh cd $GOPATH/src/github.com/openblockchain/obc-peer export OPENCHAIN_PEER_ADDRESS=172.17.0.2:30303 ./obc-peer chaincode deploy -p github.com/openblockchain/obc- peer/examples/chaincode/go/map -c '{"Function":"init", "Args": []}'
- 17. 17 Step4: Execute transaction 17 ./obc-peer chaincode invoke -n <container-id> -c '{"Function":"put", "Args": ["key1", "val1"]}' /obc-peer chaincode query -n <container-id> -c '{"Function":"get", "Args": ["key1"]}'
- 18. 18 DB structure 18 Blockchain Block1 TX1 TX2 Block2 TX1 TX2 State State Delta Chaincode State 1 State Delta 1
- 26. 26 Consensus: State machine definition 26 A set of States A set of Inputs A set of Outputs A transition function (Input × State → State) An output function (Input × State → Output) A distinguished State called Start.
- 27. 27 Consensus: System properties 27 The algorithm provides both safety and liveness assuming no more than 1/3 replicas are faulty.
- 28. 28 Consensus: Practical Byzantine Fault Tolerance 28
- 29. Renat Khasanshyn CEO @ Altoros | @renatco Sergey Matykevich Sr. Software Engineer @ Altoros Thank you! More on the topic: altoros.com/blog/tag/hyperledger March 23, 2016
Editor's Notes
- #11: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #12: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #13: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #14: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #15: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #16: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #17: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #18: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #19: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #20: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #21: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #22: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #23: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #24: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #25: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #26: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #27: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #28: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.
- #29: goal: single platform for all devices Increase quality and reduce the amount of stabilization reduce planning. PaaS is good fit for Project automatization tests should be small.