From 6c6d5c7647591196249526894c99ee0412c2d2e5 Mon Sep 17 00:00:00 2001 From: youyyytrok Date: Mon, 11 Nov 2024 14:11:43 +0100 Subject: [PATCH] typo correction --- docs/pages/syncing-other-l1.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/syncing-other-l1.mdx b/docs/pages/syncing-other-l1.mdx index c566a53..806e027 100644 --- a/docs/pages/syncing-other-l1.mdx +++ b/docs/pages/syncing-other-l1.mdx @@ -4,7 +4,7 @@ title: Syncing to Other L1s # Syncing to Other L1s -Non-Ethereum L1 chains, like Gnosis Chain, Polygon, and BNB, are less straighforward to integrate with Keyspace than L2s. There's no way to reference the state root of the L1 KeyStore contract directly on these chains. Instead, we're faced with two options: using an Ethereum block hash oracle to verify the Keyspace state root from Ethereum or re-sequencing the state transitions on the other L1 without any reference to the Ethereum instance. +Non-Ethereum L1 chains, like Gnosis Chain, Polygon, and BNB, are less straightforward to integrate with Keyspace than L2s. There's no way to reference the state root of the L1 KeyStore contract directly on these chains. Instead, we're faced with two options: using an Ethereum block hash oracle to verify the Keyspace state root from Ethereum or re-sequencing the state transitions on the other L1 without any reference to the Ethereum instance. ## Block Hash Oracles