Obligation implementation based on the Token SDK?
zhiheng.zheng@...
We have a project currently using Corda-finance provided by Corda out-of-box. R3 just released token SDK, and mentioned that Token SDK was intended to replace Corda-finance. But I can not find the any Obligation implementation in the Token SDK. I can see there is an Obligation implementation in the Corda settler which is compatible with Token SDK, but it seems that implementation is especially for Corda settler and is lack of some functions like netting which Corda-finance's Obligation has already provided.
Anybody know if R3 will port the current Obligation in Corda-finance to Token SDK? |
|
Roger Willis <roger.willis@...>
As you note, there is an obligation state and contract inside the corda-settler, our intention is to pull this obligation state and contract into a separate module and perhaps add some of the netting code we prototyped a couple of years ago for project Ubin. This will allow holders of obligations to perform multi-lateral netting. The finance module will likely be deprecated. Hope to start on this work at some point in the near future. The various library CorDapps which we are working on fit together like so:
If there’s anything you’d like to see that’s not on the list above then let us know, or if there are any features which you would like to see added to the existing libraries then let us know.
Cheers
From: <corda-dev@groups.io> on behalf of "zhiheng.zheng via Groups.Io" <zhiheng.zheng@...>
We have a project currently using Corda-finance provided by Corda out-of-box. R3 just released token SDK, and mentioned that Token SDK was intended to replace Corda-finance. But I can not find the any Obligation implementation in the Token
SDK. I can see there is an Obligation implementation in the Corda settler which is compatible with Token SDK, but it seems that implementation is especially for Corda settler and is lack of some functions like netting which Corda-finance's Obligation has already
provided. |
|
The Corda Commons sounds like it could just be stuff added to the platform directly. It wouldn't require any network-wide upgrade; just a user upgrading the node if the app mandates it via its Min-Platform-Version manifest property. That way there's only one
thing to manage, and the rest of the platform APIs can utilise and integrate with the commons stuff.
|
|