# ZK-based eligibility proofs for private allowlists (Groth16)

**URL:** <https://forum.arbitrum.foundation/t/zk-based-eligibility-proofs-for-private-allowlists-groth16/30407>\
**Category:** Sales Pitch by Service Providers\
**Created:** [January 15, 2026, 6:46am UTC](https://forum.arbitrum.foundation/t/zk-based-eligibility-proofs-for-private-allowlists-groth16/30407 "2026-01-15T06:46:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![SRIVISHNU\_GV](https://avatars.discourse-cdn.com/v4/letter/s/d78d45/32.png) [@SRIVISHNU\_GV](https://forum.arbitrum.foundation/u/SRIVISHNU_GV)\
**Post date:** [January 15, 2026, 6:46am UTC](https://forum.arbitrum.foundation/t/zk-based-eligibility-proofs-for-private-allowlists-groth16/30407/1 "2026-01-15T06:46:23Z")

</div>

RFC: ZK-based eligibility proofs for private allowlists (Groth16)

I’ve built a small, focused ZK eligibility engine that proves wallet properties (age, activity, cooldowns, token presence) without revealing balances, tx history, or addresses.

It’s intentionally narrow:

No identity

No KYC

No “universal proof” claims

The design goal was correctness, explicit assumptions, and verifiability (off-chain + optional on-chain).

I’m exploring whether this primitive is useful for:

incentive programs

governance gating

private allowlists

If there’s interest, I’m happy to run a small pilot for one rule and share results openly
