Abstract
Hyperledger Bevel is an automation framework for rapidly and consistently deploying production-ready DLT platforms.
Develop a connector that provides both synchronous and asynchronous modes of interacting with a running Hyperledger Besu node. The connector would act as an interface between an enterprise application and the Hyperledger Besu node for data ingestions and it could provide event subscription options.
The scope of the project would also include an end-to-end test on a sample networkThe Hyperledger Labs blockchain-carbon-accounting project has progressed significantly, and we're looking to move to production deployment of it. The deployment of a Hyperledger Fabric, however, has been a difficult and time-consuming process in the past. Hyperledger Bevel is an automation framework for rapidly and consistently deploying production-ready DLT platforms. We would like to streamline the deployment processes for both Fabric and Besu networks. Our goal is to allow any organization to join the networks using its own cloud infrastructure.
Mentors
Name | Time zone | Discord ID | Email ID |
---|
Aruna S M | IST | arsulegai#7968 | |
Rahul Batra | IST |
Mentee
Name | Time zone | Discord ID | Email ID |
---|
Mihir Mehta | IST |
Kiran S M | IST |
Communication channel:
Discord + Github
Project repo:
https://github.com/hyperledger/bevel & https://github.com/hyperledger-labs/blockchain-carbon-accountingarsulegai/eth-connector
Deliverables
- Successful deployment of blockchain-carbon-accounting across multiple cloud networks, such as Digital Ocean, AWS, and Azure.
- Detailed tutorials and learning materials which would benefit both blockchain-carbon-accounting developers and the broader Fabric, Besu, and Bevel communities.
- Design and implement the connector for Besu.
- These connectors (hlf and eth connector) can be standardized and brought into single repository for interface consistency
Merged PR's
- TBD
- TBD
- TBD
Final Project Presentation:
- TBD
Milestones
...
Eval 1:
- TBD
Eval 2:
- TBD
Eval 3:
- TBD
Eval 4:
- TBD
- Learning Objectives (6th Oct to 14th Oct 2022)
- How does Besu Works? Expectation - A document that captures the difference between DB-based transaction vs blockchain transaction.
- SpringBoots understanding. Expectation - Develop and execute a HelloWorld SpringBoots application.
- Git. Expectation - Understand the process to commit, code reviews, and raise a PR.
- App Configurations
1. Network abstraction (input of a running Besu network)
2. Key handling/Wallet integration
3. App configuration read
4. Connector abstraction (input of Kafka/ASB etc)
5. Dynamic update of beans
Estimated Time to Complete: 4 weeksGoal: Smart Contract Ops
1. Transaction send
2. Transaction result read/status
3. Transaction simulation
4. Decode transaction payload
CompletedGoal: Operations
1. Smart contract deployment
2. Calculate contract address
Estimated Time to Complete: 2 weeksGoal: Events and APIs
1. Event from specific block
2. URI for reading the block data
3. Event from specific transaction (optionally of smart contract) given a block
Estimated Time to Complete: 4 weeks
Timeline
Dates | Tasks/Plan |
---|
Expectations |
---|
Evaluation |
---|
Tasks/Plan
Status | |
---|---|
June 1 - June 14 | Mentee intro with the |
mentors. Introduction to the concepts of |
HLF Connector Lab project Setup and run a local instance of Besu ( https://besu.hyperledger.org/en/stable/Tutorials/Developer-Quickstart/) | Integration Test Setup for Eth Connector | |||
June 15 - June 28 | Quarter Evaluation (June 29th) | Quarter Evaluation (June 29th) | ||
June 29 - July 12 | ||||
July 13 - July 26 | MidTerm Evaluation (July 15th) | MidTerm Evaluation (July 15th) | ||
July 27 - Aug 9 | Quarter Evaluation (July 31st) | Quarter Evaluation (July 31st) | ||
Aug 10 - Aug 23 |
Final Evaluation (Aug 24th) | Final Evaluation (Aug 24th) |
Methodology
TBD