From b44ad1edcd5848f616fd2e1223c26453fcdea40b Mon Sep 17 00:00:00 2001 From: Zain Bacchus Date: Mon, 2 Dec 2024 09:23:31 -0600 Subject: [PATCH] Small nit Adding context around oracle problem before explaining what interop does --- pages/stack/interop/explainer.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pages/stack/interop/explainer.mdx b/pages/stack/interop/explainer.mdx index 33b88ffea..ee1d37ea4 100644 --- a/pages/stack/interop/explainer.mdx +++ b/pages/stack/interop/explainer.mdx @@ -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? + 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