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

add(storage proof mechanism and external service): Generalize World ID #3

Open
4 tasks
dcbuild3r opened this issue Dec 27, 2022 · 0 comments
Open
4 tasks
Assignees
Labels
enhancement New feature or request

Comments

@dcbuild3r
Copy link
Collaborator

dcbuild3r commented Dec 27, 2022

idea: leverage storage proofs of the WorldIDIdentityManager contract on the Ethereum mainnet and run an external relayer service to update all supported target chain WorldID contracts with new WorldID Merkle tree roots and their corresponding timestamps. This approach is easily generalizable to any target chain that supports the cryptography needed to deploy a Semaphore verifier and a storage-proof verifier. For an EVM-based chain, it is a trivial change as contracts for this are already implemented and would only require a WorldID contract deployment and integration to the state relayer service.

TODO

  • Turn off the state bridge in world-id-contracts
  • Build a relayer service that will relay storage proofs of Ethereum mainnet state to destined target networks
  • Implement Storage proof verifier for EVM networks and deploy <EVM-network>WorldID.sol contracts.
  • Look into other execution environments like Cairo, Fuel VM, Risc V, etc.
@dcbuild3r dcbuild3r self-assigned this Dec 27, 2022
@dcbuild3r dcbuild3r added the enhancement New feature or request label Dec 27, 2022
@dcbuild3r dcbuild3r changed the title add(pull-based mechanism) add(storage proof mechanism and external service): Generalize World ID Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant