Hyperledger Transact simplifies distributed ledger development
The latest addition to the Hyperledger family is Hyperledger Transact. The aim of the project is to make developing distributed ledger solutions easier by separating the execution of smart contracts from the distributed ledger implementation. Let’s have a closer look.
The latest project to join the Hyperledger greenhouse aims to simplify the execution of transactions with smart contracts. According to Shawn Amundson on the Hyperledger blog, in creating a platform-agnostic library, they want to make developing distributed ledger solutions easier by separating the execution of smart contracts from the distributed ledger implementation.
It’s a solution that helps to bridge the gap between other projects in the Hyperledger framework while making development easier. Let’s take a closer look.
What is Hyperledger Transact?
Built on experience and insights gained from Hyperledger Sawtooth, among other Hyperledger projects, Transact aims to make integration of smart contracts into distributed ledger development easier. It also represents Hyperledger’s movement towards building components that will work together better, allowing faster responsible adoption of new blockchain technologies by reducing the development effort necessary.
Specifically, Hyperledger Transact handles smart contracts, including scheduling, transaction dispatch, and state management. Custom distributed ledgers, as well as those built on the Hyperledger framework, can make use of Transact’s advanced transaction execution and state management to simplify transaction execution code. Transact uses an approach called “smart contract engines”, which uses virtual machines or interpreters to process smart contracts. It also offers SDKs, simplifying the writing of smart contract business logic in a number of programming languages
Until now smart contract solutions have been tailored to specific distributed ledger implementations. Transact is a more adaptable solution focused purely on transaction execution and state; as a result it doesn’t conflict with other platform-level design elements.
The figure below, as shown on the Hyperledger blog, summarizes how the Transact architecture looks.
Features of Hyperledger Transact
You can check out the official announcement for all the detailed information.