Trustless Airdrop

Screenshots

Problem Statement

So, Trustless / Permissionless Airdrop service allows DAOs, chains, DeFi projects, etc. to set up airdrops that are claimable based on the users' activity, which is verified real time.Currently all airdrops happen through whitelisting - the founding teams just make a whitelist of eligible addresses and publish it somewhere on the blockchain. So far this seems to have worked, but of course this isnot a true crypto approach.The true crypto approach would be exactly what Permissionless Airdrop does - verify that you interacted with a certain token, dapp or chain via a zero knowledge proof, submit that proof into the smart contract that manages the airdrop campaign and claim the airdrop immediately.Such an approach adds a lot more transparency to the airdrop claiming process as anyone is able to read the circuit of the proof and understand the exact rules - which are the same for all airdrop claimers.

Solution

Permissionless Airdrop is made on top of brevis.network, which aggregates onchain data and provides verifiable proofs over onchain activity more broadly.The flow for a user would be the following:The user submits a request to claim an airdrop for a certain protocolThe backend fetches relevant user activity for that protocol in the normal wayThe backend then submits that user's activity into a brevis-powered circuit, and within 30 seconds / 1 minute receives a zero knowledge proofThe backend then sends that proof to the brevis's hosted service which makes an additional zk proof to confirm the legitimacy of the provided user activityThe brevis's hosted service submits the resulting proof to the blockchain to a smart contract, which checks the result once again and then issues the airdrop to the user!The entire process takes no longer than 2 minutes and can further optimized!