Security

What the code can and can't do

Program ID
Ap6U2RPXFdQTdYNfKsiX8nu7tgh3rXF1ReMe1bn2DZXx
Network
Solana mainnet
Custody
None. You keep the token you hold; the program is a delegate on the payout-token account only, and never on the token you hold.
Fee
2% of the yield, capped at 2% in the code itself, never of the token you hold
Protected floor
Per wallet and per market, set at delegation to the payout tokens already held; changes only with the user's signature
Slippage guard
1% below the reference Raydium pool's price, checked on-chain after the swap; the pool's recorded price history must cover the market's window (15 minutes at launch) and be fresh, or the compound is refused outright
Swap venue
Jupiter, program address pinned in code; the route is checked before the program signs
Upgrade authority
Retained by the deployer wallet. The program can still be replaced with a different one. Removing the authority is permanent and public, and has not happened
Verified build
Not yet. No reproducible build is registered for this program, so explorers list it as unverified. The deployed bytecode is on chain for anyone to dump and hash.
Audits
Adversarial AI reviews by two independent models, several rounds each, summarised on the audits page. No third-party firm audit yet.

Inspect the program on Solscan, check the delegate on your own account, or read the audit summary. Live pair costs and status are on the pairs page.

The guarantees

The risks

How to verify it yourself

  1. Open your ZEC token account on Solscan. The delegate field shows the Vawlt's authority address and the allowance. Revoke it there any time.
  2. Open the program on Solscan and confirm the upgrade authority matches what this page says.
  3. Read the compound instruction in the source: the ZCAT destination is your associated token account, the Jupiter program address is a constant, and the floor on your enrollment is read, never written.