We’re pioneering SnarkHooks through SnarkPad’s new programme. First up on our Solana devnet roadmap is Second Orbit.
If a round misses its target, each refunded deposit gets one private vote to try again. Enough yes votes open the relaunch to those backers first.
Many more hooks to come.
2
101
Where did my deposit go?
One signature opens a SnarkPad receipt. In local Solana tests, we followed 0.002 test SOL from escrow through a Meteora batch buy to a token claim. When a second round missed its target, its receipt showed the full refund.
No wallet connection needed.
We’re taking SnarkPad’s proof gate to public Solana devnet. After the next independent Groth16 ceremony contribution, we’ll pin the browser’s proving key and deploy the matching verifier.
You’ll be able to prove eligibility in your browser and trace your deposit to the Meteora batch buy.
1
3
166
MIA build report ☄️
While building Meteora Internal Agent, we hit a bug that looked like an RPC permissions issue. A swap had landed on Solana at slot 465,774,667, but asking MIA to explain it returned a 502.
The primary RPC had actually given us the answer. The transaction used Solana’s v1 format, our decoder requested v0, and a 403 from the fallback node masked the original error. We moved wallet history and individual transaction lookups onto the same parser, added v1 support, and preserved the upstream error through failover. Today we replayed that exact signature against the published API and decoded it successfully.
That same attention went into the agent itself. MIA’s workspace and MCP server share 10 read-only tools. Ask which Meteora DLMM pools led on volume and you can open the tool call to see the filters MIA used, the rows Meteora returned, and how long the request took. Paste a Solana transaction and you can inspect its signers and balance changes.
The latest build passed 66 automated tests. One end-to-end check remains for the wallet inspector: an owner signing a delegate revocation and confirming it on mainnet.
3
5
240
We tried to enter SnarkPad’s first round twice with the same credential.
On a local Solana validator, our zk-SNARK cleared a 0.002 test SOL deposit. SnarkPad rejected the second attempt. The round settled in one Meteora buy, and we claimed the tokens.
Public devnet is next.
3
197
We tested two SnarkPad rounds on a local Solana validator.
One accepted a zk-SNARK, settled in a single Meteora buy, and let the backer claim their tokens. The other missed its target and paid a full refund.
Our next step toward devnet is a second, independent ceremony contribution.
Next up is SnarkPad’s first proof-gated round on Solana devnet.
Once the proving ceremony is complete, you’ll be able to commit test SOL and use a zk-SNARK to prove you qualify while keeping your credential private.
If the round meets its target, those commitments fund one Meteora buy.
6
7
374
GM ☕️ Been hearing from builders who want to launch on SnarkPad.
You’d set a funding target and lock in the terms up front. Backers could use a zk-SNARK to prove they qualify, keep their credentials private, and claim a refund if the round misses its target.
What would you launch?
A founder can have fifty people saying “I’d back this” and still have no idea whether to launch. We’re building SnarkPad so those fifty people can commit funds under clear terms and prove they qualify without revealing their private credentials.
That could change which ideas get built. A small community could give something it believes in a start, long before anyone else is paying attention.
19
18
326
Meet SnarkPad, a Solana launchpad. Creators lock the rules. Your wallet proves you qualify with a zk-SNARK.
Official Token Contract Address: H1E8QmJWin7RBq2BV78RLPR8mUyKz2oh2sLEG6CSnarK
Watch a simulated launch reach its first buy on Meteora’s curve.
Zero-knowledge proofs let backers show they meet a launch’s rules while keeping the details behind that proof private. When enough people commit, the launch can go ahead. That’s the new era we want to open up: one where a founder with a small following can still get a bold idea off the ground.
snarkpad.xyz
17
20
591
GM. We spent a couple of days working through a SnarkPad edge case. Two different Groth16 proofs can both verify for the same allocation.
They share a nullifier. Checking and consuming it atomically with the commitment lets only one claim settle on Solana.
Mainnet is nearly ready.
2
3
213
Wiring SnarkPad’s Circom → snarkjs → Solana proof flow.
Every public input needs a reason to exist. Every authorization needs precise boundaries.
But if the witness stays private while wallet activity remains public, how much privacy does “zero knowledge” actually give the user?
1
1
141
GM. Today’s rabbit hole: SnarkPad’s private eligibility circuit.
We’re working through depth-16 Poseidon Merkle membership proofs and domain-separated nullifiers, scoped to a specific launch, policy hash and action.
The next layer is binding recipient, allocation cap and expiry into the authorization path, then coordinating Groth16 verification with accepted-root checks and atomic nullifier consumption.
In practical terms: proving eligibility without revealing the underlying credential, while preventing a proof from being reused or redirected.
A mathematically valid proof still needs to authorize precisely the right action. That boundary deserves attention.
A lot of constraints behind one simple buy button.
Back to the code.
1
1
127






