Create a repository of already deployed Verifier.sol so redeployment isn't needed

[zkonduit]

Create a repository of already deployed Verifier.sol so redeployment isn't needed

[ethan-crypto]

One potential solution, if we want to keep everything decentralized and avoid maintaining a database, is to implement a lightweight factory contract using CREATE2. This factory contract would handle the deployment of all verifiers. Before deploying a new one, it could check for the existence of a verifier by hashing the runtime bytecode (potentially the creation code as well if we want to be on the safe side, but definitely not the metadata) of the verifier and cross-referencing it against a mapping (bytes32=>address) that stores the hashes of all the previously deployed verifiers and maps them to their deployment address. This should provide us with a unique identifier to check whether a verifier has been deployed before. Also, this hashing operation with KECCAK256 would only increase the deployment transaction cost by about 0.1 percent, which is not too bad IMO.

For better accessibility and visibility of the deployed verifiers, we should also create a subgraph for the verifier factory. This would allow for easy decentralized querying of verifiers deployed in production.

One issue with this approach though is how we ensure only verifier contracts are deployed through the factory. I'll need to do some research into this problem.