Hyperledger

Further Design Considerations

Now that you’ve got the basics, there are a few things to keep in mind as you begin to plan your project. Launching a project on a new protocol like this can be complicated, so it helps to ask the right questions from the beginning.

General Architecture

Since Hyperledger networks are intended to act as common records between multiple legal entities, it’s imperative that they’re well planned with consideration for the laws of the presiding jurisdictions. Before any code is written, the first step should be to identify an appropriate validator model for all actions that will be tracked by the system. It’s important to ensure that the system is designed so that no single bad actor could compromise the long term records while also minimizing the increase in overhead due to validation activities. A best practice is to plan validation events to match existing paper documentation. Ink signatures should be replaced with digital signatures where possible, and any critical information should be recorded to the Hyperledger network.

Planning Your Project

As your team develops a better understanding of the requirements of your system, the next stage will be to identify a minimum viable solution. Hyperledger nodes can be deployed locally on client devices, or delivered using a hosted cloud solution. Depending on the scale of the network, it may be practical to test the functionality in a small test environment before deploying to a fully hosted solution.

Up Next

Now that you’re up to date on Hyperledger, you’ll want to look at planning your project. You may want to review our Blockchain Security Course to identify potential issues with your planned architecture. Additionally, you might want to consider trying Amazon or Oracle‘s hosted blockchain options.

 

 

We’re here to help. If you have any questions or feedback about this course please email us at info@theblockchaininstitute.org – we’d love to hear from you!