Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Small nit #1156

Merged
merged 1 commit into from
Dec 2, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion pages/stack/interop/explainer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,10 @@ import { InteropCallout } from '@/components/WipCallout'

# Interoperability explainer

The Oracle problem states that a blockchain can only be certain about information generated by that chain. But what about information that happens outside that blockchain, how do you verify what happens somewhere else?

krofax marked this conversation as resolved.
Show resolved Hide resolved
Interoperability is the ability for a blockchain to securely read the state of another blockchain.
Native OP Stack interoperability provides the ability to read messages and transfer assets across the Superchain (without having to go through L1) via low-latency, secure message passing. This results in the following benefits:
Native OP Stack interoperability provides the ability to read messages and transfer assets across chains in the Superchain (without having to go through L1) via low-latency, secure message passing. This results in the following benefits:
* 1-block latency asset movement that is both maximally capital efficient and non-fragmenting
* improved user experience for developers on the Superchain
* secure transfer of ETH and ERC-20s across L2s
Expand Down
Loading