<aside> 💡 Let’s think together on prioritizing these. Below are three routes or epics for development. the roadmap tasks page reflects these epics.

</aside>

🌱 Initial effort POC

Roadmap tasks

Verification creator

Developer tool that enables users to provide GEO-fencing constraints to generate validation on chain

  1. 🌱 polygons: Generating circom2 poofs for polygon verification
  2. 🌱 contract generator: Check and implement a single contract that receives constraints (alternatively deploying a new contract on every new constraint)
  3. 🌱 Users assets management: create and upload the proof verification key, ptau and wasm files. + infrastructure
  4. 🌱 Command-Line-tool:
    1. constraints input + keys
    2. optional bluetooth implementation
    3. optional foam implementation
    4. generates circuits and, contracts, subgraph

Client tools

Developer tool/suite that generates ZK proofs based on the verification they have created on chain

  1. 🌱 zksnark library for generating proofs based on https://github.com/iden3/snarkjs
    1. 🌱  generate proof module
    2. client lib bluetooth module
    3. client lib FOAM module
    4. FOAM module
  2. 🌱 The Graph: auto ****generating The Graph subgraph for relevant queries. (optional - requires event emitting)

Spoofing solutions

Suites of technologies, hardware, and cryptography to prevent location spoofing, on chain without compromising user privacy

  1. bluetooth p2p (proximity proof: peer-to-peer)
  2. ‣ Cryptography on-chain solutions
  3. FOAM: Connect devices to an Anchor Lite through LoRa (with custom hardware) and create a proof of location relying on zk proofs with high accuracy. This is the first step toward integrating with FOAM *TrustedZones* in the long term.
  4. Helium
  5. soul-bound-tokens

https://github.com/orgs/zkMaps/projects/2

https://github.com/orgs/zkMaps/projects/2/views/2

https://github.com/orgs/AstralProtocol/projects/1