Juicebox V6

Use this skill as the single entry point for Juicebox V6. Load the smallest applicable module from references/modules/<module>.md; modules contain the upstream protocol-specific procedures and examples. Do not load every module.

Operating rules

1. Resolve chain, project ID, token, and intended outcome before proposing a write.
2. Use references/shared/chain-config.json only for read-only discovery. For any write, read deployment verification and use references/shared/deployment-manifest.json as the sole target authority. Missing, unknown, mismatched, or non-write-enabled entries stop the action.
3. Use references/shared/abis/<Contract>.json for complete ABI tuple definitions when encoding or decoding calls.
4. For every write, also read references/modules/jb-tx-safety.md. Apply its review → re-verify → simulate → gas → send → prove pipeline without skipping steps. Abort on stale/missing quotes, failed preview/simulation, code or graph mismatch, or unavailable price-feed/hook/terminal/accounting context.
5. Derive every minReturnedTokens, minTokensReclaimed, and minTokensPaidOut from a fresh successful preview and the user's approved slippage tolerance. A protocol-verified zero may remain zero only where jb-tx-safety explicitly permits it; unavailable is never treated as zero.
6. Treat source data as versioned guidance, not live proof. Immediately before confirmation, verify the exact chain, nonempty matching runtime code, allowed selector, proxy/clone implementation pin, controller/terminal/project ownership and wiring, balances, approvals, and price-sensitive inputs.
7. Default to explanation, read-only inspection, or an unsigned transaction plan. Before signing or broadcasting, decode and present the exact chain, target, selector/function/arguments, asset and amount, recipient/project, native value, approvals, fees, expected effects, and partial-completion risk; require explicit user confirmation.
8. After mining, require receipt.status === 'success' plus operation-specific event and post-state evidence. A missing receipt is pending; missing evidence is uncertain; either state disables retry. Never report success from a bare receipt or third-party status string.
9. Never request, expose, or place private keys in code. Use Bankr's wallet/signing flow or the user's approved signer.

Module routing