aiken-dex-security-audit

When to use

• Auditing Plutus V3 Aiken contracts for a DEX (validators + minting policies)
• You need a rigorous report: threat model, invariants, findings, and reproducible exploit tx shapes

Non-negotiable rules

• No hallucinations. If something isn't in the repo or inputs, say unknown and list exactly what's missing.
• Assume a hostile attacker can craft arbitrary transactions: multi-input, multi-action, weird datums, weird token bundles.
• Never ask for or handle seed phrases / private keys.
• Prefer evidence over vibes: minimal tx shape + failing test + fix + passing test.

Required inputs (ask for anything missing)

1. Script list + purpose (spend/mint/reward/cert) and which are critical path for swaps/liquidity
2. Datum/redeemer schemas (Aiken types + encoding expectations)
3. Parameters/config: policy IDs, script hashes, upgrade/admin controls, oracle deps (if any)
4. Off-chain tx builder(s) in scope (where swaps/liquidity txs are constructed)
5. Network assumptions (mainnet/preprod) + constraints (tx size, exunits, reference scripts, inline datums)