Re: support for atomic commit of transactions across channels #fabric

Brian Behlendorf <bbehlendorf@...>

Thanks for bringing this here for feedback.

One thing I noticed reading more closely is that this isn't just about transactions across channels in the same Fabric network, but even across different Fabric networks.  That's very cool!

Another part of Hyperledger, Hyperledger Quilt, has been working along the same lines, as an implementation of the Interledger Protocol written in Java.  It was originally written by Ripple and NTT Data and is now supported by Coil, and ILP is somewhat designed for a payments use case, so it right now just supports XRP and BTC; but we're working hard now to reboot the project and bring new contributors and thinking in.  If ILP can be made more general purpose than just payments of cryptocurrencies and apply to transactions of all sorts, perhaps it could also be looked at as the bridge between two Fabric networks?  I know that's a bigger lift but then we'd get interop with other ledger networks potentially more easily.  If not, it'd be great to understand what ILP doesn't yet provide to make this possible.


On 3/20/19 11:21 AM, Praveen wrote:
Hello everyone,
    We have a proposal and design for supporting atomic transactions across channels in Fabric. We have created an issue ( along with the details of the design. We would love to present this in a community call and get feedback from everyone. The design involves minimal changes to Fabric code and mostly to the ledger component, and we have in-house expertise to develop and contribute this to Fabric in 3 months. It also works seamlessly with upcoming features such as token transactions.
Thanks and regards,

Brian Behlendorf
Executive Director, Hyperledger
Twitter: @brianbehlendorf

Join { to automatically receive all group messages.