Bounties for closed Solana programs

Name a program you want opened and what it is worth to you. Breakers rebuild it in Rust, a referee replays real mainnet traffic against both binaries, and the source stays sealed until somebody pays to break the seal.

$UNSEAL CA dropping soon
LIVE
01

Three moves, one seal

Nobody pays for a promise. Bounties are free to sign, rebuilds are judged by a machine, and money only moves when someone wants the key.

01

Post a bounty

Pick any program id on Solana and name your price in USDC. It is a signed message, not a transaction, so nothing leaves your wallet. Bounties stack: the more people want a target opened, the louder it gets.

02

Rebuild it in Rust

Breakers turn bytecode back into a crate, bounty or not. Your browser encrypts the crate before it uploads, and you set the asking price, 25 USDC at the least. The referee does the rest.

03

Break the seal

A passing verdict goes public at once. A buyer pays in USDC, gets the key, and their browser checks the archive against the commitment printed on the verdict before it saves a single byte.

Open the vault
SolanaUSDCRustJupiterPhantomSolflareBackpackLiteSVMpump.fun
02

Where the money goes

0%
to the breaker

Paid out the moment an unlock settles, with a memo on-chain that ties the payout to the verdict.

0days
first dibs

Whoever posted the top bounty on a target gets the first right to buy its rebuild. After that, it is open to anyone.

0%
bought & burned

Of every unlock, swapped into $UNSEAL on Jupiter and sent to the incinerator.

0targets wanted
0USDC on the table
0proofs sealed
0verdicts issued
03

The referee doesn't take your word for it

No uploaded binaries, ever. It compiles your crate itself with a pinned toolchain, offline, with a ten minute cap, then feeds identical mainnet instructions and account snapshots to the original and to your build.

REPLAY0 / 1,000 matched
mainnet
corpus
original.so
rebuild.so
=

Twin sandboxes, same compute budget, same account states. Real instructions first, fuzzed ones after.

referee · verdict

        
  1. AEvery case must match: result, error code, return data, logs and every writable account byte.
  2. BOne difference is a fail, and the report points straight at it.
  3. CA pass needs at least 100 cases where the original program succeeds.
  4. DCompute-unit log lines are stripped. Everything else is compared.
04

The vault

Every rebuild that passed, sealed until someone opens it. Calibration runs are the referee checking itself against programs whose source is already public.

05

Wanted, rebuilt, judged

GOT BYTECODE YOU CAN'T READ?