In the same way as we have Etherscan for solidity "Publish Your Source Code"we need to have Etherscan, "Publish Your Circom Code", or even "Publish Your Stark", "Cairo Precode", or whatever the original source language is. And then it would compile and it would actually verify that the on-chain verification key matches. These are things that totally can be done. And I hope someone does them in the hackathon tomorrow.

Vitalik Buterin March 26, 2024 Source

• support more than just latest circom version
• add support for noir verifiers too
• ddos protection! / account system
• api for programmatic verification / command in circomkit fo ci
• allow for contract name changes?
• form for submitting a proof to be verified
• auto-include circomlib files in selector
• fork/create new circuit

$ git clone https://github.com/numtel/circuitscan
$ cd circuitscan
$ yarn

# Default env var settings are fine for using remote deployed server
$ cp .env.example .env

# In another terminal, start frontend dev server
$ yarn dev

# Configure Etherscan, Postgres, Signer
# and change VITE_API_URL to `/api`
# and change VITE_API_URL_CIRCOM to `/build-circom`
# to use the local running docker container through vite proxy
$ vim .env

# Init database (modify command with your connection settings)
$ psql < migrations/000-init.sql

# Build server lambda docker image
$ yarn build:server

# Run server lambda in docker container
$ yarn dev:server

MIT