[Application Development] Curious about atomic cross-chain messaging between OP Stack chains.

[Billy19191]

Did you check the documentation?

• Yes
• No

Documentation Feedback (Optional)

No response

What type of issue are you experiencing?

• Error
• Feature Request
• General Question

Issue Description

Based on the knowledge provided here, cross-chain transactions between OP chains in the Superchain are currently asynchronous, meaning they are not atomic. I’m researching and designing a cross-chain use case within the Superchain, such as lending on OP Chain A and borrowing on OP Chain B.

From my understanding, this means that lending on OP Chain A and borrowing on OP Chain B would not be atomic—the lending transaction could complete while the borrowing transaction might fail or be delayed. Is that correct?

Are there any existing solutions or workarounds to achieve this kind of atomic behavior, or is it currently not supported by the OP Stack?

Steps to Reproduce

Are you using a specific library or SDK?

• OP-SDK
• Viem
• Other
• Not Sure

Are you using the latest version of the library/SDK?

• Yes
• No

Environment Details

No response

Troubleshooting Attempts

No response

What type of support do you need?

• Technical support for issue resolution
• Feature implementation guidance
• General advice or consultation
• Documentation or learning resources

Additional Information

No response

Feedback

No response

[imtipi]

Synchornous cross-chain txs are not part of the initial interop release. Our P0 focus is shipping interop (1-block latency) and then iterating on it accordingly. As such we dont have a timeframe for sync xchain txs yet

from Zain

[hash1go]

Hey!
Transactions spanning separate database systems cannot be atomic by principle. Application deployers must catch failure events on the destination chain and define behaviors in advance to handle them, implementing the system in a way that mimics atomicity.

[hash1go]

To add to that, ensuring atomicity in crosschain transactions requires the source chain to stop updating its state and processing other transactions until it becomes clear whether the crosschain transaction has succeeded or failed on the destination chain.