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
Circuitscan explorer of on-chain circuit verifiers
Circuit developers can use the CLI to compile circuits on a cloud machine with a simple command (with up to 512 GB RAM)
dApp users can check the safety of the application and make proofs as needed
This repository contains the frontend, server (compares on-chain Solidity source against Solidity output by the compilation pipeline along with other administrative functions), and CloudFormation templates necessary for hosting Circuitscan on AWS.
For issues related to compiling Circom files, see the circom-pipeline repo
To create new compilation pipelines, see the circuitscan-pipeline-runner repo
For issues related to the documentation, see the docs repo
To run the frontend locally:
Note
Requires Node.js and Yarn
$ 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
Optionally, you can also develop the server locally.
Note
Requires Docker
# Configure S3 settings for local server
$ vim .env
# Build server lambda docker image
$ yarn build:server
# Run server lambda in docker container
$ yarn dev:server
# Update .env to VITE_SERVER_URL=/api to use server running in local Docker
# Server tests are run on your local machine
$ cd server/
$ yarn
$ yarn test
Contributions to Circuitscan are welcome! Please make an issue or PR.
Special thanks to Ethereum Foundation Ecosystem Support Program for supporting phase one of Circuitscan development!
MIT