Cross-chain Asset Interoperability

This allows users to operate as a clearinghouse for cross-chain assets interoperability across private and public chains.

Partners

• Layerzero: Provides cross-chain messaging and communication infrastructure.

• Space and Time: Manages proof of SQL database, transaction logging, and orchestrates asset swap requests.

• Jiritsu: Validates and verifies asset ownership on private blockchains.

• Trident3: Handles cross-chain asset verification and protocol compliance.

• Yelay: Manages asset locking and security mechanisms.

• Innerworks: Coordinates identity verification processes across chains.

• Privado ID: Provides secure identity verification and compliance solutions.

Example Use Case Citibank (CB) and JP Morgan (JPM) have both minted RWA’s on their private hyperledger based instances. Citi’s is a representation of gold and JP Morgan’s is a representation of silver. Both banks have userbases who own their respective assets. These users have accounts and have been verified, but only within one of the two banks.

Benefits

• Secure cross-chain asset transfers between private banking networks

• Automated identity verification and compliance checkins

• Real-time transaction logging with on-chain proof storage

• Synchronized asset locking across multiple chains

• End-to-end transaction verification and proof mechanisms

Sequence

1

A CB user (user 1) owns $100 worth of RWA gold (Dgold) and wants to buy RWA silver (Dsilver) with it.

2

Identity Recipe A version of the previously outlined Identity Recipe is used to verify the user s identity to ensure ongoing compliance with regulatory requirements. A successful result is batched and put on chain.

3

ID solution sends back an approved/ not approved message. Not approved comes with information detailing what else is needed.

4

User achieves approval this is sent to Space and Time (S&T) and logged in the proof of SQL database.

5

S&T sends a message to CB saying user 1 is approved and requests information about the assets involved.

6

CB sends to S&T a request to swap $100 of Dgold for $100 of Silver.

7

S&T logs the request and messages Jiritsu asking for proof of $100 of Dgold.

8

Jiritsu checks to see if user 1 has $100 of Dgold on the CB private blockchain.

9

Jiritsu sends S&T a yes/no answer to the request for proof, which is logged.

10

If yes, then S&T sends a message to JPM asking to swap $100 of Dgold for $100 of Dsilver which includes the necessary ID info so JPM can query for ID.

11

If JPM has a counterparty with $100 of Dsilver it triggers a request for ID on user 1 from the Identity Solution.

12

The Identity Solution sends user 1 information to JPM.

13

If user 1 ID info is approved, JPM sends User 2 information to the Identity Solution along with an approval record to S&T.

14

The Identity Solution sends back an approved/ not approved message. Not approved comes with information detailing what else is needed.

15

User achieves approved - this is sent to Space and Time (S&T) and logged in the proof of sequel database.

16

S&T sends a message to JPM saying user 2 is approved and requests information about the assets involved.

17

JPM sends to S&T a request to swap $100 of Dsilver for the $100 of Dgold.

18

S&T logs the request and messages Jiritsu asking for proof of $100 Dsilver.

19

Jiritsu checks to see if user 2 has $100 of Dsilver on the JPM private blockchain.

20

Jiritsu send S&T a yes/no answer to the request for proof, which is logged.

21

If yes, S&T sends a message asking both CB and JPM to lock the requisite assets.

22

CB and JPM both send back proof of lock to S&T.

23

S&T records the asset locks along with the Identity of the owners.

24

S&T hashes the records of the transactions and stores them on-chain.