# Cross-chain Asset Interoperability

**Partners** 

<div align="left"><figure><img src="/files/3OULzSaKChM7XlsKrKTh" alt=""><figcaption></figcaption></figure></div>

* **Layerzero**: Provides cross-chain messaging and communication infrastructure.
* **Space and Time**: Manages proof of SQL database, transaction logging, and orchestrates asset swap requests.&#x20;
* **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.&#x20;
* **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**

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

{% endstep %}

{% step %}
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.

{% endstep %}

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

{% endstep %}

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

{% endstep %}

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

{% endstep %}

{% step %}
CB sends to S\&T a request to swap $100 of Dgold for $100 of Silver.

{% endstep %}

{% step %}
S\&T logs the request and messages Jiritsu asking for proof of $100 of Dgold.

{% endstep %}

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

{% endstep %}

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

{% endstep %}

{% step %}
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.
{% endstep %}

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

{% endstep %}

{% step %}
The Identity Solution sends user 1 information to JPM.

{% endstep %}

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

{% endstep %}

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

{% endstep %}

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

{% endstep %}

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

{% endstep %}

{% step %}
JPM sends to S\&T a request to swap $100 of Dsilver for the $100 of Dgold.

{% endstep %}

{% step %}
S\&T logs the request and messages Jiritsu asking for proof of $100 Dsilver.

{% endstep %}

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

{% endstep %}

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

{% endstep %}

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

{% endstep %}

{% step %}
CB and JPM both send back proof of lock to S\&T.

{% endstep %}

{% step %}
S\&T records the asset locks along with the Identity of the owners.

{% endstep %}

{% step %}
S\&T hashes the records of the transactions and stores them on-chain.

{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.w3.io/cookbook/real-world-assets/cross-chain-asset-interoperability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.