Revenue Model
Core Revenue Principle
No contribution, no validation, no revenue.
zkPull never charges:
upfront listing fees
subscriptions
contributor-side payments
All revenue is generated after objective, verifiable work is completed.
1. Protocol Fee on Successful Bounty Claims
zkPull charges a 5% protocol fee on every successfully claimed bounty.
Fee Breakdown (Example)
If a bounty reward is 1,000 mUSD:
95% (950 mUSD) → Contributor
5% (50 mUSD) → zkPull Protocol
This fee is:
enforced by smart contracts
collected only after validation succeeds
invisible to contributors until payout
Why 5% makes sense:
Low enough to not discourage contributions
High enough to sustain infrastructure and security costs
Comparable to (or lower than) traditional bounty platforms
2. AVS Operator Reward Allocation
From the 5% protocol fee, rewards are shared with EigenLayer AVS operators.
Operator Allocation
60% of protocol fee → AVS Operators
40% of protocol fee → zkPull Protocol Treasury
Using the same 1,000 mUSD bounty example:
30 mUSD → AVS operators
20 mUSD → zkPull protocol treasury
Why this matters:
Operators are economically incentivized to validate correctly
Decentralized verification is sustainable
Security scales with usage
3. Optional Priority Validation (Future Extension)
For high-value or time-sensitive bounties, zkPull can support optional priority validation.
Proposed fee:
Additional 1–2% optional fee paid by project owners
Guarantees faster AVS processing or higher operator quorum
This feature is:
opt-in
not required for standard usage
designed for enterprise or security-critical projects
Revenue Model Summary Table
Bounty Claim
5%
Project Owner (from bounty)
Only on success
AVS Allocation
60% of fee
Protocol
Validation work
Treasury
40% of fee
Protocol
Sustainability
Priority Validation
+1–2% (optional)
Project Owner
Opt-in
Enterprise Integrations
Custom
Organizations
Optional
Last updated