{ "source": "Offlin33er/solidity-audit-instruct", "target": "Offlin33er/solidity-audit-instruct-v3", "n_train": 2224, "n_test": 248, "canonical_distribution": { "Arithmetic Error": 418, "Business Logic Violation": 550, "Reentrancy": 201, "Clean (No Vulnerability)": 800, "Input Validation Error": 215, "Access Control Flaw": 168, "Frontrunning / MEV": 51, "Denial of Service (DoS)": 69 }, "method_counts": { "exact": 831, "tier3": 354, "keyword": 435, "fallback": 52, "clean": 800 }, "fallback_labels": { "incorrect refund handling": 1, "duplicate variable": 1, "incorrect parameter": 1, "collateral token mismatch": 1, "unused enumeration": 2, "array-based flag enumeration": 1, "incentivization": 1, "special case": 1, "inaccurate value used for partial fill quote amount": 1, "incorrect data exposure": 1, "token limit bypass": 1, "smart contract restriction": 1, "rate limiting": 1, "error code": 1, "time-related vulnerability": 3, "incorrect assignment": 1, "arbitrary configuration": 1, "rate limit bypass": 1, "outdated data": 5, "ownable but not pausable": 1, "incorrect time delay constant": 1, "abstraction overload": 1, "plugin failure": 1, "incorrect configuration retrieval": 1, "token-based vulnerability": 1, "format string error": 1, "inconsistent erc20 token implementation": 1, "data encoding ambiguity": 1, "double sha-256 implementation": 1, "double-checked vulnerability": 1, "inconsistent asset handling": 1, "expired protection": 1, "double registration": 1, "unconditional return": 1, "callback not invoked": 1, "address reuse": 1, "erc-1155/721 receiving function missing": 1, "incorrect data fetching": 1, "inconsistent asset return": 1, "snapshot vulnerability": 1, "unconfigured yield mode": 1, "default to rollable": 1, "function name inconsistency": 1, "unrestricted commitment": 1, "inconsistent data conversion": 1 }, "system_prompt": "You are an expert Web3 Smart Contract Auditor. Analyze the provided Solidity code snippet.\nYou MUST classify the primary finding using EXACTLY one of the following canonical categories:\n- Reentrancy\n- Arithmetic Error\n- Access Control Flaw\n- Input Validation Error\n- Frontrunning / MEV\n- Denial of Service (DoS)\n- Business Logic Violation\n- Clean (No Vulnerability)\n\nRules:\n- Use exactly these category names, verbatim, in the '## Finding: ' header.\n- Choose the single most relevant category for the primary issue.\n- If no vulnerability is present, the category is 'Clean (No Vulnerability)'.\nThen provide the functionality, a Description, and a Recommendation." }