Omni-chain WorldID: Support on different L1s and L2s

[dcbuild3r]

Description

WorldID will support Ethereum mainnet, Optimism, and Polygon PoS really soon. However, the landscape of different L2s on Ethereum is greatly expanding and other L1s should also have access to the Ethereum state for integrating WorldID in order to make our protocol credibly neutral and accessible to as many developers as possible (chain-agnostic).

Requirements for bridging to work

• Proving the state inside of world-id-contracts which are deployed on Ethereum mainnet on different networks
• Correct implementation of the Semaphore verifier, or any other future iteration of the verifier for WorldID proofs. The implementation will be different for different execution environments (EVM - Ethereum, Scroll, zkSync, Polygon ZKEVM, Optimism, Arbitrum, ...; Cairo - Starknet, Sway - Fuel; Sealevel - Solana; Noir - Aztec; Substrate - Polkadot; CosmWasm - CosmosSDK/IBC; RiscV - RiscZero; Leo - Aleo; SnarkyJS - Mina and more to come in the future). The development of these implementations can be supported by the Worldcoin Foundation in the form of grants in the future.
• Relaying the proofs from Ethereum to other networks
  • EOAs sending data through calldata to the target network. EOA is controlled by an external relayer service that pushes proofs to the target network WorldID contract.
  • Oracles/Re: e.g. Chainlink, Empiric/Astraly
  • Other: Succinct, Herodotus, Axiom

Solutions

Interesting candidates for proving and verifying L1 state on different networks to be able to do omni-chain WorldID integrations:

• Herodotus (L1<>L2 comms, SNARKified storage proofs)
• Axiom (L1<>L2 comms)
• Succinct (Telepathy L1<>L1 comms)

[Marcecontardo1609]

0x20beaa5f85392b57b008c5785fc71af61115a51d

[Marcecontardo1609]

O