Brevis
Following our earlier coverage of Brevis and the Proving Grounds, the team has introduced a major extension to its ecosystem. What began as a ZK coprocessor powering intelligent applications has now expanded into a global DePIN compute marketplace called ProverNet, where ZK computation is supplied by a network of independent contributors ⚡
This new environment allows applications to request computation on demand without maintaining their own infrastructure, while giving individuals a clear way to monetize their CPUs and GPUs by turning idle hardware into passive income through real proof workloads 💻
With the mainnet beta now live, anyone with CPUs or GPUs can join ProverNet, process real proving tasks and earn $USDC on Base. As full mainnet approaches, the $BREV token will enable staking and native payments, increasing rewards for committed contributors.
For users, this creates a clear opportunity to put existing hardware to work today while positioning themselves for future rewards as the Brevis proving economy continues to grow 💸
Real workloads are already running on ProverNet, with Brevis migrating production tasks such as Ethereum block execution proofs through ETHProofs. Jobs are assigned through a sealed auction system that routes lighter circuits to CPUs and heavier computations to GPUs.
Brevis
Step by step guide Brevis Airdrop
For Individuals With Idle GPUs or CPUs (Provers)
(Run a prover node and earn rewards)
1.1 Install the Prover Software → Use the official Prover Docs to set up the Pico Proving Service on a CPU or GPU machine and bring the prover containers online
1.2 Enable Bidding for Jobs → Set up the bidder service so your node can participate in ProverNet’s sealed auctions for proof workloads.
1.3 Stake to Join the Network → Initialize your prover with the required USDC stake during the beta (switching to $BREV at full mainnet).
1.4 Start Earning → Once running, your node automatically bids on workloads and generates proofs. You earn USDC for every completed job, with $BREV incentives coming at mainnet.
For Developers Submitting Proof Requests (Applications)
(Submit work without running your own proving infrastructure)
2.1 Request a Proof → Follow the Request Proof Docs to install Pico CLI, prepare your inputs and build your ELF.
2.2 Build & Prepare Inputs → Generate your App ID (verification key) and your input payloads (
vk,publicValuesDigest,inputData).2.3 Submit Your Request → Approve USDC for BrevisMarket, then call
requestProof(or batch-submit via CLI). ProverNet automatically routes lighter workloads to CPUs and heavier workloads to GPUs.2. 4 Receive Your Proof → The winning prover processes your request and returns the proof before your chosen deadline.
* Follow @Brevis_zk on 𝕏, and join the community on Discord & Telegram for updates.
🔎 Looking for the next big Airdrop? Our DEX Airdrops 2025 guide has you covered 📖 🪂
Stay tuned with @AirdropAlertcom 🪂🔥 the original and first-ever Airdrop platform globally, consistently offering premier Airdrop opportunities since 2017 with love 💙 and dedication
