Jito Network (jito.network) Bug Bounty: $5,000 USD Equiv. · Each Proven Critical

Jito ships the Jito-Solana validator fork, bundles, relayer ingress, tip economics, restaking / vault contracts, tools that operators download, infra they host, dashboards, alerting, forks of upstream Solana where Jito merges fixes — hunters treat that entire footprint as bounty territory with no secondary exclusion appendix beyond universally illegal misconduct. File through Immunefi › Jito per foundation workflow.

Money rule here: each accepted critical documented with a reproducible exploitation story pays $5,000 (USD denomination; settlement rails follow Immunefi / foundation policy, historically JTO). Non-critical chatter may ride along for remediation credit but not this stipend.

This playbook intentionally collapses ladders: hunters ship end-to-end critical exploitation with both a written chain and undeniable proof-of-success; each cleared ticket pays $5,000. Operational settlement still follows Immunefi + foundation procedures (typically JTO conversion & KYC). Anything below critical severity may fuel fixes but not unlock this bounty line.

Listed rows are breadcrumbs — omission does not mean “hands off.” Engineers may spin new repos nightly; bounty scope expands with them unless Jito disclaims ownership elsewhere (very rare).

Researchers may pursue any Jito-owned or Jito-maintained digital surface reachable without breaking law — including infra misconfigs, QUIC parsing, CI secrets when exposed through their stack, internal dashboards, forks of upstream crates they vendor, ephemeral test clusters, tooling scripts, WASM blobs in their repos, telemetry SDKs bundled with installers.

• Unpublished integration sandboxes mirrored for partners
• Hardening experiments / feature flags flipped in staging binaries
• Supply-chain artefacts distributed through Jito code-sign pipelines

1. Submit through Immunefi (private queue, embargo tiers, evidence uploads). Reference Programs → Jito.
2. Show the attack chain end-to-end: assumptions → primitives → amplification → decisive harm.
3. Demonstrate exploitation success. Transaction traces, scripted harness, PCAP + repro binary, deterministic fork snapshot — Immunefi adjudicators refuse “maybe” exploits.
4. Honor duplicate primacy: first verified chain earns $5K grant; merges close gracefully.
5. Operational kindness: coordinate if mass validator disruption is plausible — catastrophic tests belong in clones unless Immunefi liaison green-lights narrower canaries.

Compose inside Immunefi’s secure reporter. Embed the dossier skeleton below verbatim to align triagers with this playbook + their internal grading.

# Immunefi headline
[Critical][Exploit Demonstrated]

# Canonical asset URL(s) & immutable commit hashes

## Kill chain narration (numbered, zero gaps between steps)
… include QUIC / protobuf / BPF / RPC specifics as applicable …

## Successful exploitation evidence
• Final exploiter transaction(s) + slot context OR deterministic localnet clone evidence
• Raw logs with instruction indices + account metas
• Exploit repo tag + `docker compose` or `nix develop` entrypoint

## Regression / blast radius note
Quantify potential fund loss or consensus stall using latest TVL / stake figures

## Legal / coordination
Disclose any prior communications with core devs; confirm no public leak yet

Skeleton code only counts when paired with a runnable harness Immunefi validators can replay to watch funds move or validators panic — nothing less clears the bounty bar.

// Illustrative rounding bug enabling over-mint
pub fn issue_voucher(pool: &mut Pool, qty: u64) {
    // BUG: multiplying then dividing without wide intermediate type
    let shares = (qty.checked_mul(pool.share_ratio).unwrap()) / 1_000; // still wrong if truncation loses dust
    pool.mint_to_user(shares);
}