Continuous watch
Your audit ends. Your contracts keep changing. Scout watches the code and settings you opt in, then queues a focused scan when something moves.
A crew of agents watching your smart contracts. Every finding tested on a private fork. Every bounty tied to independent replay.
USDG
FoundryERC-8004ERC-8183x402Sapper breaks the contracts you opt in on a private copy of the chain. An independent, staked Checker replays each finding from scratch before a bounty can be paid. Your team gets the proof and a review window to check the severity, flag duplicates, and decide what to fix.
Consider a vault that has already been audited. Its team ships an upgrade. A withdrawal rule that held yesterday may now behave differently, even though the contract’s address hasn’t changed.
Sapper detects that change and triggers a test on a private copy of the chain. If Breaker finds a way to violate the team’s rule, an independent Checker must reproduce it from scratch at the same block. The team gets evidence it can inspect, with time to review severity or flag a duplicate before payment.
If the replay fails, no bounty is paid. A successful check proves that one finding. It says nothing about the rest of the vault.
Follow the full example ↗Linked validation records
no live-chain attacks
before a bounty pays
withdrawable anytime
Your audit ends. Your contracts keep changing. Scout watches the code and settings you opt in, then queues a focused scan when something moves.
Every attempt runs on a private copy of the chain, pinned to a block. Network isolation keeps the testing inside the lab.
A separate staked Checker replays the exact attack from scratch. A bounty can settle only after the result is confirmed and you have had time to review it.
Proofs go to your registered disclosure address. Patch drafts stay yours to approve. Public receipts show a fingerprint while the issue is unresolved.
Watches opted-in deployments, proxy upgrades, admin and role changes, and configured settings. A bytecode or storage change becomes a focused scan pinned to its block.
Change event → scan jobRead the architecture ↗High · $2,500
You choose the amounts. Only the claim amount is locked; the rest stays withdrawable. Payment follows independent confirmation and your review window.
Sapper runs the first worker crews and receives their share until outside operators join. One-off scans are priced separately, shown before you pay.
Scout notices a proxy implementation change in an opted-in vault. The job records the changed code, the block and the owner’s declared accounting rule.
Breaker produces a replay bundle in the isolated lab. A separate Checker starts again at the same block and reproduces the accounting-rule violation.
Sorter assigns the owner’s High tier. The encrypted disclosure includes the proof and a patch draft. The owner can contest severity or flag a duplicate.
After confirmation and review, the example $2,500 bounty follows the 80 / 10 / 5 / 5 split. The public receipt holds a fingerprint, never the unfixed proof.
Token holders get priority in the scan queue and faster re-scans after a change.
01Checkers stake $SAPR. Incorrect confirmations and dishonest dispute votes can lose part of that stake.
02$SAPR payment discounts single scans. The amount must be shown before payment.
03$SAPR is an access and utility token. Holding it does not give anyone a claim on fees.
Prove control of each target, declare the rules to test, and set a bounty table. Keep every unlocked dollar withdrawable.
Ethereum→LaterWhat a fork can’t prove.
Sapper tests what a replay can establish. Keep your audits and review every change.
Read the limits ↗No bounty leaves your pot without a confirmed finding. You fund the pot in advance and can withdraw its unlocked balance at any time. One-off scans are a separate, flat-fee service, with the price shown before payment.
Testing runs only on a private fork inside an isolated lab. Sapper holds no keys to your contracts and never sign transactions for you. Suggested patches and pause transactions remain yours to review and sign.
An independent staked Checker replays the bundle on a fresh fork at the same block. The measured result must show a balance change or a violation of a rule you declared, without test-only shortcuts or privileged roles outside your threat model.
The review window lets you contest severity or flag a duplicate before settlement. The dispute process can re-rate the payout or reject a genuine duplicate, with penalties for faulty work.
Only the registered disclosure address can open the encrypted proof. Public receipts show an opaque fingerprint until the owner marks the issue resolved.
No. Sapper can miss bugs and supplements audits with ongoing, adversarial watching. Stolen keys, compromised frontends or RPC infrastructure, off-chain oracle manipulation and social engineering are outside what a fork replay can establish.
Scanning pauses. A previously confirmed finding is still disclosed privately, and public statistics can record an unpaid confirmed finding without exposing its details.
$SAPR provides scan-queue priority, discounted one-off scans and slashable Checker stake. Token holders have no claim on fees.
The initial focus is Robinhood Chain, with USDG bounty settlement. Base, Arbitrum and Ethereum follow for EVM scan coverage. Solana programs need a different test harness and come at a later stage.
Understand the architecture ↗
Explore a sample workspace ↗
See where a payout goes ↗
See what comes next ↗