How to Handle Long Backchain

We at R3 believe that near the future businesses will adopt blockchain-based systems for their transactions. Performance is the most important feature of any enterprise software application, and Corda 4.7 introduced a new reissuance functionality that improves performance.

What is the problem?

The need for backchain validation in a blockchain is causing performance setback. Let’s explain, transactions in Corda reference input states which are created by the prior transactions. This flow architecture creates a transaction backchain over time. As the backchain grows, the backchain validation becomes a performance overhead.

What is the solution?

Corda 4.7 introduced a new reissuance functionality that solves this problem. It is achieved by locking the reissued state using Corda’s encumbrance feature. The reissued state can only be unlocked once the original state has been exited.

The above diagram represents the series of steps involved in reissuing a state in Corda. To make things simple for developers, Corda provides the reissuance CorDapp which implements most of the functionality. All developers need to do is call the appropriate flow.

For a sample CorDapp that implements a simple reissuance case click here.

If you need more information on how it works visit the blog post.

Visit your Developer platform, and if you have any questions or concerns, please reach us at: devrel@r3.com