I’m building a ZK-powered infrastructure layer that lets DAOs verify grants and payments trustlessly on-chain.
It uses browser-based proof generation and zkSync smart contracts for fully scalable verification of internal transactions (like “the sum of every contribution equals total amount spent,” etc.).
I’ve just shipped a live demo and I thought Gitcoin may be interested in testing / giving feedback on this project.
Given the volume of grants (amount of grants + number of grantees) how would you envision something like this be scaled for many transactions and tracking over time?
Also, can you provide some details on what the value add for us (or similar DAOs) in tracking grants in this way?
Thanks for your reply. Using this system, one could verify outgoing payments in an organization (meaning the total amount that got issued is valid for example, without revealing the individual contributions to preserve privacy), because it got verified on-chain, meaning it is completely trustless. All the issuer has to do is interact with the proofing mechanism.
I don’t know the situation well enough at Gitcoin, but I can image that in many organizations there is still a part in the grant issuing that is not completely trustless, meaning one must still “trust” the admin for correctly setting up the payment.
For the scaling part, because the system is built on the zkSync L2 chain, which is built to be scalable (or at least a lot more scalable than just the Ethereum L1 chain), so I don’t think this will be a problem. The proofing doesn’t actually make the payments, it just guarantees that all went well to provide full transparency. One idea could be to build the ZK-proof verification inside the grant issuing itself, such that the proofing happens automatically.
The proofs will then be stored on the blockchain and can just be fetched by making a read-only call.
I hope this clears things up!