Interoperability between Corda and other DLTs
|
etaroid
Are there any teams or projects working on cross chains that enable interoperability between Corda and Quorum, Corda and HLF, and Corda(CENM Private Network) and Corda(CENM Private Network) ?
If there is no such team, no case, and there is a need, we would like to contribute! |
|
|
|
Roger Willis <roger.willis@...>
Hi there,
My team is working on Corda/Corda private zone interop. We’re primarily concerned with running flows across zones but also we are looking into transacting across zones. Work will be available sometime in Q2. We’ll work on Corda/X interop later on in the year.
Cheers
From: <corda-dev@groups.io> on behalf of "amthgfonger.nk via Groups.Io" <amthgfonger.nk@...>
Are there any teams or projects working on cross chains that enable interoperability between Corda and Quorum, Corda and HLF, and Corda(CENM Private Network) and Corda(CENM Private Network) ?
If there is no such team, no case, and there is a need, we would like to contribute! |
|
|
|
Roger,
toggle quoted message
Show quoted text
That's great. We also see a need for third party service providers (accountant/legal/custodian/administrative) or regulators to connect to potentially multiple Corda networks to service/monitor their clients/participants. In certain scenarios the 3rd party providers will have to actively participate (ex: authorize a transaction) in running flows in these Corda networks. Mani|SwapsHub|212-742-1800|mani@...
On 2/17/2020 6:59 AM, Roger Willis via
Groups.Io wrote:
|
|
|
|
Clemens Wan
Feel free to reference some of my early work “Unlocking Corda <> Ethereum Interoperability Pt 1” by Clemens Wan https://link.medium.com/RixM6LMr93 At the moment, I've seen strategies to have oracle-like nodes run multiple clients and normalize the data saving standards, but this is if you have control of your private deployments. Even with hyperledger besu (which is able to run public and private Ethereum Implementations), you will ultimately need a separate messaging and database, so a node/client based bridge is not really that feasible. You'd only added an identity to your node endpoint for the cases you want to receive private transactions in a public network. I had another piece I was writing which pushed the idea of legal anchors via Openlaw underpinning the legal clauses necessary to support conditions where assets actually move from one network to another. It's manifested into the "lao" work. Since accounts came out on corda, I do think it'd be a good exercise to resolve identities for the LEI parent, LEI sub account, business network addresses, and individual accounts such that they match across platforms if there's need to transfer an asset. I've found that most use cases are more related to preventing double encumbrance across chains and interpreting the asset lifecycle events consistently. I shifted my focus to understanding the data created within these private networks in order to accurately know if and when such a transfer between platforms is needed. On Mon, Feb 17, 2020, 6:52 AM <amthgfonger.nk@...> wrote:
|
|
|
|
etaroid
Roger, your team’s project is so great!
Corda/X Interop, what kind of design do you have under what assumptions?
For example, “centralized or multi-sig notary,” “sidechain/relay,” or “hash lock,” as described in the "types of Interoperability" chapter of vitalik’s Chain Interoperability paper( https://www.r3.com/wp-content/uploads/2017/06/chain_interoperability_r3.pdf ). |
|
|
|
Roger Willis <roger.willis@...>
Unsure yet as we haven’t really given it much thought. I suspect the preferred approach will be to start with something very simple, like orchestration for an organisation running nodes across heterogeneous networks, and then graduate to something more complex like hash locks. While all this is quite interesting, it’s academic for now because I’m not aware of any customers needing multiple different “blockchain” platforms as part of their product. In that light, perhaps we are better focusing on interoperability with “legacy” systems e.g. how can one easily make an idempotent call to an external system from Corda because that’s where customers are focused at the moment. Cheers
From: <corda-dev@groups.io> on behalf of "etaroid via Groups.Io" <amthgfonger.nk@...>
Roger, your team’s project is so great!
Corda/X Interop, what kind of design do you have under what assumptions?
For example, “centralized or multi-sig notary,” “sidechain/relay,” or “hash lock,” as described in the "types of Interoperability" chapter of vitalik’s Chain Interoperability paper( https://www.r3.com/wp-content/uploads/2017/06/chain_interoperability_r3.pdf ). |
|
|
|
takagiwa.shun@...
Hi people,
A new project, Cordage has been started! It makes the interoperability possible between Corda and other blockchains without further trusted third party. At first, connecting Ethereum/Quorum.
|
|
|