EVM-QuestBench: An Execution-Grounded Benchmark for Natural-Language Transaction Code Generation
Paper • 2601.06565 • Published • 1
Datasets:
Tasks:
Text Generation
Modalities:
Text
Formats:
json
Languages:
English
Size:
< 1K
ArXiv:
Tags:
benchmark
code-generation
transaction-code-generation
execution-grounded-evaluation
blockchain
evm
License:
id stringlengths 10 33 | split stringclasses 1
value | task_type stringclasses 1
value | version stringclasses 2
values | category stringclasses 3
values | subcategory stringlengths 7 21 | difficulty stringclasses 4
values | title stringlengths 14 55 | description stringlengths 70 2.38k | natural_language_templates listlengths 3 5 | chain stringclasses 2
values | network stringclasses 3
values | tags listlengths 4 10 | parameter_names listlengths 0 11 | parameters stringlengths 2 2.04k | validation stringlengths 2 1.43k | composite_structure stringclasses 1
value | interaction_config stringclasses 1
value | scoring_strategy stringclasses 1
value | metadata stringlengths 2 1.04k | source_path stringlengths 48 74 | raw_definition stringlengths 2.08k 6.68k |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
contract_delegate_call | atomic | atomic | 2.0.0 | advanced_features | delegate_call | hard | DelegateCall - Proxy Pattern | Call a function through a proxy contract that uses delegatecall to execute logic from an implementation contract.
Technical context:
- The proxy contract forwards calls to an implementation contract using delegatecall
- DelegateCall executes the implementation's code in the proxy's context
- Storage changes affect the... | [
"Call the setValue function on the proxy contract at {proxy_address} with value {value}",
"Set the value to {value} using the proxy contract {proxy_address}",
"Execute setValue({value}) through the proxy at {proxy_address}",
"I want to call setValue on proxy {proxy_address} and pass {value}"
] | BSC | mainnet | [
"delegatecall",
"proxy",
"upgradeable",
"advanced",
"storage_context"
] | [
"implementation_address",
"proxy_address",
"value"
] | {"implementation_address": {"description": "Implementation contract address (contains logic)", "generation": {"comment": "Implementation contract for verification", "env_key": "delegate_call_implementation_address", "method": "from_env"}, "role": "contract", "type": "address"}, "proxy_address": {"description": "Proxy c... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Transaction calls PROXY contract (not implementation)", "expected": "{proxy_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct setValue function signature",... | {} | {} | {} | {"contract_requirements": {"contract_type": "DelegateCallProxy + Implementation", "note": "Tests understanding of delegatecall and proxy patterns", "required_functions": ["setValue", "getValue"]}, "educational_value": "Understanding delegatecall is crucial for upgradeable contracts and many DeFi protocols", "estimated_... | advanced_features/delegate_call/contract_delegate_call.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "advanced_features", "description": ["Call a function through a proxy contract that uses delegatecall to execute logic from an implementation contract.", "", "Technical context:", "- The proxy contract forwards calls to an implementation contract using ... |
contract_payable_fallback | atomic | atomic | 2.0.0 | advanced_features | fallback | medium | Payable Fallback - Send BNB to Contract | Send BNB directly to a contract without calling any specific function.
This will trigger the contract's receive() or fallback() function.
Technical context:
- When you send BNB to a contract without calldata, it triggers receive() if it exists
- If receive() doesn't exist, it triggers fallback() if it's payable
- The ... | [
"Send {amount} BNB to the contract at {contract_address}",
"Transfer {amount} BNB to contract {contract_address} without calling any function",
"I want to send {amount} BNB directly to {contract_address}",
"Send {amount} BNB to {contract_address} (no function call)"
] | BSC | mainnet | [
"fallback",
"receive",
"payable",
"direct_transfer",
"advanced"
] | [
"amount",
"contract_address"
] | {"amount": {"description": "Amount of BNB to send", "generation": {"decimals": 4, "max": 0.05, "method": "random", "min": 0.001}, "role": "transfer_amount", "type": "number", "unit": "BNB"}, "contract_address": {"description": "Contract address with payable fallback/receive", "generation": {"comment": "Use dynamically ... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Transaction sent to correct contract", "expected": "{contract_address}", "type": "contract_address", "weight": 0.2}, {"description": "Correct BNB amount sent", "expected": "{amount}"... | {} | {} | {} | {"contract_requirements": {"contract_type": "FallbackReceiver", "note": "Tests understanding of fallback/receive functions", "required_functions": ["receive() or fallback()"]}, "educational_value": "Understanding fallback/receive is important for contract interactions and DeFi protocols", "estimated_gas": 100000, "requ... | advanced_features/fallback/contract_payable_fallback.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "advanced_features", "description": ["Send BNB directly to a contract without calling any specific function.", "This will trigger the contract's receive() or fallback() function.", "", "Technical context:", "- When you send BNB to a contract without cal... |
erc20_flashloan | atomic | atomic | 2.0.0 | advanced_features | flashloan | hard | ERC20 FlashLoan - Execute Flash Loan | Execute a flash loan by calling the FlashLoan contract's executeFlashLoan function.
Technical context:
- Flash loan allows borrowing tokens without collateral in a single transaction
- The loan must be repaid with a fee (0.3%) in the same transaction
- Function signature: executeFlashLoan(address token, uint256 amount... | [
"Execute a flash loan of {amount} {token_symbol} from the flash loan contract at {flashloan_contract_address}. The loan must be repaid with {fee_percentage}% fee in the same transaction.",
"Borrow {amount} {token_symbol} using flash loan from contract {flashloan_contract_address}, use the funds, and repay with fe... | BSC | mainnet | [
"flashloan",
"defi",
"advanced",
"lending",
"borrowing"
] | [
"amount",
"fee_percentage",
"flashloan_contract_address",
"token_address",
"token_decimals",
"token_symbol"
] | {"amount": {"description": "Amount to borrow (in token units)", "generation": {"decimals": 2, "max": 1000, "method": "random", "min": 100}, "role": "transfer_amount", "type": "number"}, "fee_percentage": {"description": "Flash loan fee percentage", "generation": {"method": "fixed", "value": 0.3}, "role": "parameter", "... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Transaction calls correct flash loan contract", "expected": "{flashloan_contract_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct executeFlashLoan functio... | {} | {} | {} | {"complexity": "high", "contract_requirements": {"contract_type": "FlashLoan", "note": "Agent must approve flash loan contract before calling executeFlashLoan", "required_functions": ["executeFlashLoan"]}, "educational_value": "Demonstrates understanding of flash loans, approvals, and atomic transactions", "estimated_g... | advanced_features/flashloan/erc20_flashloan.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "advanced_features", "description": ["Execute a flash loan by calling the FlashLoan contract's executeFlashLoan function.", "", "Technical context:", "- Flash loan allows borrowing tokens without collateral in a single transaction", "- The loan must be ... |
query_current_block_number | atomic | atomic | basic_transactions | blockchain_queries | easy | Query Current Block Number | Query the current block height of the blockchain by calling eth_blockNumber RPC method. This is a fundamental blockchain query that returns the latest block number, useful for tracking blockchain state, calculating block intervals, and determining transaction timing. The block number increases with each new block mined... | [
"Get the current block number of the blockchain",
"Query the latest block height",
"Check what is the current block number",
"Retrieve the most recent block number from the chain"
] | BSC | mainnet | [
"blockchain",
"block",
"eth_blockNumber",
"query",
"rpc"
] | [] | {} | {"rules": [{"condition": "success", "error_message": "Failed to query current block number", "field": "query_execution", "weight": 50}, {"condition": "has_required_fields", "error_message": "Missing required fields in query result", "field": "return_format", "required_fields": ["block_number"], "weight": 25}, {"conditi... | {} | {} | {} | {"estimated_gas": 0, "learning_objectives": ["Understand the eth_blockNumber RPC method", "Learn how to query blockchain state without contracts", "Master block height tracking", "Understand blockchain time progression", "Learn about block-based timing mechanisms"], "notes": ["eth_blockNumber returns the latest block n... | basic_transactions/blockchain_queries/query_current_block_number.json | {"blockchain": "bsc", "category": "basic_transactions", "description": "Query the current block height of the blockchain by calling eth_blockNumber RPC method. This is a fundamental blockchain query that returns the latest block number, useful for tracking blockchain state, calculating block intervals, and determining ... | |
query_gas_price | atomic | atomic | basic_transactions | blockchain_queries | easy | Query Gas Price | Query the current gas price and EIP-1559 fee parameters by calling eth_gasPrice or getFeeData() methods. This returns the current network gas pricing information including maxFeePerGas and maxPriorityFeePerGas for EIP-1559 transactions. Understanding gas prices is crucial for estimating transaction costs and optimizing... | [
"Get the current gas price of the network",
"Query the current EIP-1559 fee parameters",
"Check what is the current maxFeePerGas and maxPriorityFeePerGas",
"Retrieve the current gas pricing information"
] | BSC | mainnet | [
"blockchain",
"gas",
"eth_gasPrice",
"getFeeData",
"EIP-1559",
"query",
"rpc"
] | [] | {} | {"rules": [{"condition": "success", "error_message": "Failed to query gas price", "field": "query_execution", "weight": 40}, {"condition": "has_required_fields", "error_message": "Missing required EIP-1559 fields in query result", "field": "return_format", "required_fields": ["maxFeePerGas", "maxPriorityFeePerGas"], "w... | {} | {} | {} | {"estimated_gas": 0, "learning_objectives": ["Understand the eth_gasPrice and getFeeData RPC methods", "Learn about EIP-1559 gas pricing mechanism", "Master maxFeePerGas and maxPriorityFeePerGas parameters", "Understand how to optimize transaction gas costs", "Learn about base fee and priority fee concepts"], "notes": ... | basic_transactions/blockchain_queries/query_gas_price.json | {"blockchain": "bsc", "category": "basic_transactions", "description": "Query the current gas price and EIP-1559 fee parameters by calling eth_gasPrice or getFeeData() methods. This returns the current network gas pricing information including maxFeePerGas and maxPriorityFeePerGas for EIP-1559 transactions. Understandi... | |
query_transaction_count_nonce | atomic | atomic | basic_transactions | blockchain_queries | easy | Query Transaction Count (Nonce) | Query the transaction count (nonce) for a specific address by calling eth_getTransactionCount. The nonce represents the number of transactions sent from an address and is critical for transaction ordering and replay protection. Understanding the difference between 'pending' and 'latest' states is important: 'pending' i... | [
"Get the transaction count (nonce) for address {{query_address}}",
"Query the nonce for address {{query_address}}",
"Check how many transactions address {{query_address}} has sent",
"Retrieve the current nonce for address {{query_address}}"
] | BSC | mainnet | [
"blockchain",
"nonce",
"transaction_count",
"eth_getTransactionCount",
"query",
"rpc"
] | [
"query_address"
] | {"query_address": {"description": "Address to query transaction count for", "generation": {"env_key": "test_address", "method": "from_env"}, "type": "address"}} | {"rules": [{"condition": "success", "error_message": "Failed to query transaction count", "field": "query_execution", "weight": 40}, {"condition": "has_required_fields", "error_message": "Missing required fields in query result", "field": "return_format", "required_fields": ["nonce"], "weight": 30}, {"condition": "is_v... | {} | {} | {} | {"estimated_gas": 0, "learning_objectives": ["Understand the eth_getTransactionCount RPC method", "Learn about nonce and its role in transaction ordering", "Master the difference between 'pending' and 'latest' states", "Understand replay attack protection", "Learn when to use which nonce state"], "notes": ["Nonce start... | basic_transactions/blockchain_queries/query_transaction_count_nonce.json | {"blockchain": "bsc", "category": "basic_transactions", "description": "Query the transaction count (nonce) for a specific address by calling eth_getTransactionCount. The nonce represents the number of transactions sent from an address and is critical for transaction ordering and replay protection. Understanding the di... | |
contract_call_simple | atomic | atomic | 2.0.0 | basic_transactions | contract_call | medium | Simple Contract Call - Increment Counter | Call a simple contract function without parameters.
Technical context:
- The target contract is a SimpleCounter with an increment() function
- Function signature: increment() (no parameters, no return value)
- This is a state-changing function that increases a counter by 1
- Function selector: 0xd09de08a (keccak256('i... | [
"Call the increment() function on the contract at {contract_address}",
"Increment the counter in the smart contract {contract_address}",
"Execute the increment function on contract {contract_address}",
"I need you to call increment() on the contract at address {contract_address}"
] | BSC | mainnet | [
"contract_call",
"simple",
"increment",
"state_change",
"basic"
] | [
"contract_address"
] | {"contract_address": {"description": "SimpleCounter contract address", "generation": {"comment": "Use dynamically deployed SimpleCounter contract from environment", "env_key": "simple_counter_address", "method": "from_env"}, "role": "contract", "type": "address"}} | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.4}, {"description": "Transaction calls correct contract", "expected": "{contract_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct increment function signature", "expected": "i... | {} | {} | {} | {"contract_requirements": {"contract_type": "SimpleCounter", "note": "A simple counter contract for testing basic contract calls", "required_functions": ["increment", "getCounter"]}, "estimated_gas": 50000, "requires_contract": true, "tags": ["contract_call", "simple", "increment", "state_change", "basic"]} | basic_transactions/contract_call/contract_call_simple.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Call a simple contract function without parameters.", "", "Technical context:", "- The target contract is a SimpleCounter with an increment() function", "- Function signature: increment() (no parameters, no return ... |
contract_call_with_params | atomic | atomic | 2.0.0 | basic_transactions | contract_call | medium | Contract Call with Parameters - Set Message | Call a contract function with parameters (string argument).
Technical context:
- The target contract is a MessageBoard with a setMessage(string) function
- Function signature: setMessage(string message)
- This function accepts a string parameter and stores it
- You must encode both the function selector and the parame... | [
"Call the setMessage function on contract {contract_address} with the message '{message}'",
"Set the message to '{message}' on the contract at {contract_address}",
"Update the message in contract {contract_address} to '{message}'",
"I want to call setMessage on contract {contract_address} and pass the string ... | BSC | mainnet | [
"contract_call",
"parameters",
"string",
"abi_encoding",
"intermediate"
] | [
"contract_address",
"message"
] | {"contract_address": {"description": "MessageBoard contract address", "generation": {"comment": "Use dynamically deployed MessageBoard contract from environment", "env_key": "message_board_address", "method": "from_env"}, "role": "contract", "type": "address"}, "message": {"description": "Message to set in the contract... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.4}, {"description": "Transaction calls correct contract", "expected": "{contract_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct setMessage function signature", "expected": "... | {} | {} | {} | {"contract_requirements": {"contract_type": "MessageBoard", "note": "A simple message board contract that stores and retrieves messages", "required_functions": ["setMessage", "getMessage"]}, "estimated_gas": 80000, "requires_contract": true, "tags": ["contract_call", "parameters", "string", "abi_encoding", "intermediat... | basic_transactions/contract_call/contract_call_with_params.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Call a contract function with parameters (string argument).", "", "Technical context:", "- The target contract is a MessageBoard with a setMessage(string) function", "- Function signature: setMessage(string message... |
contract_call_with_value | atomic | atomic | 2.0.0 | basic_transactions | contract_call | medium | Contract Call with Value - Send BNB to Payable Function | Call a payable contract function with BNB value attached.
Technical context:
- The target contract is a DonationBox with a payable donate() function
- Function signature: donate() payable
- This function accepts BNB and records donations
- You must set the transaction 'value' field to send BNB
- Function selector: 0xe... | [
"Call the donate() function on contract {contract_address} and send {amount} BNB",
"Donate {amount} BNB to the contract at {contract_address}",
"Send {amount} BNB to the donate function of contract {contract_address}",
"I want to call donate() on contract {contract_address} with {amount} BNB attached"
] | BSC | mainnet | [
"contract_call",
"payable",
"value",
"donation",
"bnb",
"intermediate"
] | [
"amount",
"contract_address"
] | {"amount": {"description": "Amount of BNB to donate", "generation": {"decimals": 3, "max": 0.05, "method": "random", "min": 0.001}, "role": "transfer_amount", "type": "number", "unit": "BNB"}, "contract_address": {"description": "DonationBox contract address", "generation": {"comment": "Use dynamically deployed Donatio... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Transaction calls correct contract", "expected": "{contract_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct donate function signature", "expected": "dona... | {} | {} | {} | {"contract_requirements": {"contract_type": "DonationBox", "note": "A simple donation box contract that accepts BNB via payable function", "required_functions": ["donate"]}, "estimated_gas": 100000, "requires_contract": true, "tags": ["contract_call", "payable", "value", "donation", "bnb", "intermediate"]} | basic_transactions/contract_call/contract_call_with_value.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Call a payable contract function with BNB value attached.", "", "Technical context:", "- The target contract is a DonationBox with a payable donate() function", "- Function signature: donate() payable", "- This fun... |
erc20_approve | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | easy | ERC20 Token Approval | Approve a spender (Router or Contract) to spend your ERC20 tokens. This is a prerequisite for many DeFi operations like swapping or adding liquidity.
The approve function sets the allowance that a spender can use on behalf of the token owner.
Key Points:
- Function: approve(address spender, uint256 amount)
- Sets all... | [
"Approve {spender_name} to spend {amount} {token_symbol} tokens from your account.",
"Grant approval to {spender_name} for {amount} {token_symbol} tokens.",
"Set allowance of {amount} {token_symbol} tokens for {spender_name}.",
"Authorize {spender_name} to use up to {amount} {token_symbol} tokens on your beha... | BSC | mainnet | [
"erc20",
"approve",
"allowance",
"defi",
"prerequisite"
] | [
"agent_address",
"amount",
"chain_id",
"spender_address",
"spender_name",
"token_address",
"token_decimals",
"token_symbol"
] | {"agent_address": {"description": "Agent address (token owner)", "dynamic": true, "generation": {"env_key": "test_address", "method": "from_env"}, "role": "address", "type": "address"}, "amount": {"description": "Amount to approve (in token units)", "example": 200.0, "generation": {"decimals": 2, "max": 500.0, "method"... | {} | {} | {} | {} | {} | basic_transactions/erc20_operations/erc20_approve.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "common_mistakes": ["Forgetting to convert amount to wei (multiply by 10^decimals)", "Sending BNB value with approve transaction (not needed)", "Approving the token address instead of the spender address", "Not waiting for transact... |
erc20_approve_and_call_1363 | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | medium | ERC20 Approve with Callback (ERC1363) | Approve an address to spend ERC20 tokens and trigger an `onApprovalReceived` callback on the spender contract if it implements `IERC1363Spender`.
Technical context:
- ERC1363 extends ERC20 with payable token functions
- Function signature: approveAndCall(address spender, uint256 value) or approveAndCall(address spende... | [
"Approve {spender_address} to spend {amount} {token_symbol} tokens with callback",
"Use ERC1363 approveAndCall to authorize {spender_address} to use {amount} {token_symbol}",
"Grant approval to {spender_address} for {amount} {token_symbol} using the ERC1363 token's callback feature",
"Approve {amount} {token_... | BSC | mainnet | [
"erc1363",
"token",
"approve",
"callback",
"allowance",
"spender_notification",
"onchain"
] | [
"amount",
"spender_address",
"token_address",
"token_decimals",
"token_symbol"
] | {"amount": {"description": "Amount of tokens to approve", "generation": {"decimals": 2, "max": 100.0, "method": "random", "min": 1.0}, "role": "approval_amount", "type": "number", "unit": "token"}, "spender_address": {"description": "Address to be approved for spending tokens", "generation": {"method": "random"}, "role... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Allowance correctly set for spender", "expected_allowance": "{amount}", "owner": "{agent_address}", "spender": "{spender_address}", "token": "{token_address}", "tolerance": "0", "typ... | {} | {} | {} | {"erc_standard": "ERC1363", "estimated_gas": 200000, "implementation_status": "development", "known_limitations": ["Most standard ERC20 tokens (USDT, USDC, DAI) do NOT support ERC1363", "Requires token to implement approveAndCall function", "If spender is a contract, it can optionally implement IERC1363Spender interfac... | basic_transactions/erc20_operations/erc20_approve_and_call_1363.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Approve an address to spend ERC20 tokens and trigger an `onApprovalReceived` callback on the spender contract if it implements `IERC1363Spender`.", "", "Technical context:", "- ERC1363 extends ERC20 with payable to... |
erc20_burn | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | medium | ERC20 Token Burn | Burn (destroy) ERC20 tokens by transferring them to the zero address (0x0000...0000), permanently removing them from circulation.
Technical context:
- Most ERC20 tokens don't have a dedicated burn() function
- The standard way to burn tokens is to transfer them to address(0)
- Zero address: 0x0000000000000000000000000... | [
"Burn {amount} {token_symbol} tokens",
"Destroy {amount} {token_symbol} tokens permanently by sending to zero address",
"Remove {amount} {token_symbol} from circulation using the test token",
"Burn {amount} {token_symbol} from the ERC1363 test token"
] | BSC | mainnet | [
"erc20",
"burn",
"destroy",
"deflation",
"intermediate"
] | [
"amount",
"token_address",
"token_decimals",
"token_symbol"
] | {"amount": {"description": "Amount of tokens to burn", "generation": {"decimals": 3, "max": 1.0, "min": 0.001}, "role": "transfer_amount", "type": "number", "unit": "tokens"}, "token_address": {"description": "ERC20 token contract address", "generation": {"comment": "Use dynamically deployed ERC1363 test token (T1363)"... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Transaction calls correct token contract", "expected": "{token_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct transfer function signature (to zero addre... | {} | {} | {} | {"contract_requirements": {"contract_type": "ERC20", "note": "Token must support burn function and agent must have tokens", "required_functions": ["burn", "balanceOf"]}, "estimated_gas": 70000, "requires_contract": true, "requires_token_balance": true, "tags": ["erc20", "burn", "destroy", "deflation", "intermediate"]} | basic_transactions/erc20_operations/erc20_burn.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Burn (destroy) ERC20 tokens by transferring them to the zero address (0x0000...0000), permanently removing them from circulation.", "", "Technical context:", "- Most ERC20 tokens don't have a dedicated burn() funct... |
erc20_decrease_allowance | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | easy-medium | ERC20 Decrease Allowance | Decrease the allowance for a spender (Router or Contract) by a specified amount. This safely reduces an existing allowance without completely revoking it.
The decreaseAllowance function subtracts from the existing allowance and includes underflow protection.
Key Points:
- Function: decreaseAllowance(address spender, ... | [
"Decrease the allowance for {spender_name} by {subtracted_value} {token_symbol} tokens.",
"Reduce {spender_name}'s allowance by {subtracted_value} {token_symbol}.",
"Subtract {subtracted_value} {token_symbol} from the allowance for {spender_name}.",
"Lower the spending limit for {spender_name} by {subtracted_... | BSC | mainnet | [
"erc20",
"allowance",
"decrease",
"safe",
"revoke"
] | [
"agent_address",
"chain_id",
"spender_address",
"spender_name",
"subtracted_value",
"token_address",
"token_decimals",
"token_symbol"
] | {"agent_address": {"description": "Agent address (token owner)", "dynamic": true, "generation": {"env_key": "test_address", "method": "from_env"}, "role": "address", "type": "address"}, "chain_id": {"description": "BSC Mainnet chain ID", "example": 56, "generation": {"method": "fixed", "value": 56}, "role": "parameter"... | {} | {} | {} | {} | {} | basic_transactions/erc20_operations/erc20_decrease_allowance.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "common_mistakes": ["Using approve(spender, 0) instead of decreaseAllowance()", "Not checking current allowance before calling (causing underflow revert)", "Forgetting to convert subtractedValue to wei", "Sending BNB value with the... |
erc20_increase_allowance | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | easy | ERC20 Increase Allowance | Increase the allowance for a spender (Router or Contract) by a specified amount. This is safer than calling approve() directly as it prevents race conditions.
The increaseAllowance function adds to the existing allowance instead of overwriting it.
Key Points:
- Function: increaseAllowance(address spender, uint256 add... | [
"Increase the allowance for {spender_name} by {added_value} {token_symbol} tokens.",
"Add {added_value} {token_symbol} tokens to the allowance for {spender_name}.",
"Top up the allowance for {spender_name} with an additional {added_value} {token_symbol}.",
"Incrementally increase {spender_name}'s spending all... | BSC | mainnet | [
"erc20",
"allowance",
"increase",
"safe",
"approval"
] | [
"added_value",
"agent_address",
"chain_id",
"spender_address",
"spender_name",
"token_address",
"token_decimals",
"token_symbol"
] | {"added_value": {"description": "Amount to add to allowance (in token units)", "example": 100.0, "generation": {"decimals": 2, "max": 200.0, "method": "random", "min": 50.0}, "role": "parameter", "type": "number"}, "agent_address": {"description": "Agent address (token owner)", "dynamic": true, "generation": {"env_key"... | {} | {} | {} | {} | {} | basic_transactions/erc20_operations/erc20_increase_allowance.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "common_mistakes": ["Using approve() instead of increaseAllowance()", "Forgetting to convert addedValue to wei", "Sending BNB value with the transaction (not needed)", "Confusing spender address with token address", "Not understand... |
erc20_permit | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | hard | ERC20 Permit - Gasless Approval (EIP-2612) | Test understanding of EIP-2612 permit concept by setting token allowance. This tests the same end goal as permit (setting allowance) using approve().
Technical context:
- EIP-2612 extends ERC20 with permit() for gasless, signature-based approvals
- The goal is to set allowance for a spender to use tokens on behalf of ... | [
"Approve {value} tokens for spender {spender_address} at token address {token_address}",
"Set allowance of {value} tokens for spender {spender_address} using token contract {token_address}",
"Call approve function to authorize {spender_address} to spend {value} tokens from token {token_address}"
] | BSC | mainnet | [
"eip-2612",
"permit",
"signature",
"eip-712",
"gasless-approval",
"meta-transaction",
"cryptography",
"advanced"
] | [
"deadline",
"owner_address",
"spender_address",
"token_address",
"token_decimals",
"token_symbol",
"value"
] | {"deadline": {"description": "Timestamp deadline for signature validity (use future timestamp)", "generation": {"comment": "Fixed future timestamp (May 18, 2033)", "method": "fixed", "value": 2000000000}, "role": "signature_deadline", "type": "number"}, "owner_address": {"description": "Token owner address (must sign t... | {} | {} | {} | {} | {"difficulty_notes": ["Requires understanding of EIP-712 typed data", "Must construct proper domain separator", "Must query and use correct nonce", "Signature must be from correct private key", "Must handle deadline timestamp"], "erc_standard": "EIP-2612", "estimated_gas": 80000, "implementation_status": "development",... | basic_transactions/erc20_operations/erc20_permit.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Test understanding of EIP-2612 permit concept by setting token allowance. This tests the same end goal as permit (setting allowance) using approve().", "", "Technical context:", "- EIP-2612 extends ERC20 with permi... |
erc20_revoke_approval | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | medium | ERC20 Revoke Approval (Set Allowance to Zero) | Revoke (cancel) a previously granted ERC20 token approval by setting the allowance to zero.
Technical context:
- This is a security best practice to prevent unauthorized token transfers
- Revoking approval is done by calling approve(spender, 0)
- Function signature: approve(address,uint256)
- The amount should be 0 to... | [
"Revoke approval for spender address {spender_address} to spend my {token_symbol} tokens at {token_address}",
"Cancel the authorization for address {spender_address} to use my {token_symbol} token (contract: {token_address})",
"Remove the spending permission for {spender_address} on {token_symbol} token at {tok... | BSC | mainnet | [
"erc20",
"approve",
"revoke",
"security",
"allowance",
"intermediate"
] | [
"spender_address",
"spender_name",
"token_address",
"token_decimals",
"token_symbol"
] | {"spender_address": {"description": "Address to revoke approval from (typically a DeFi contract)", "generation": {"addresses": ["0x10ED43C718714eb63d5aA57B78B54704E256024E", "0x13f4EA83D0bd40E75C8222255bc855a974568Dd4", "0x1b81D678ffb9C0263b24A97847620C99d213eB14"], "comment": "PancakeSwap Router, Venus Protocol, Panca... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Transaction calls correct token contract", "expected": "{token_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct approve function signature", "expected": "... | {} | {} | {} | {"contract_requirements": {"contract_type": "ERC20", "note": "Revoking approval is a security best practice", "required_functions": ["approve", "allowance"]}, "estimated_gas": 60000, "requires_contract": true, "requires_token_balance": false, "tags": ["erc20", "approve", "revoke", "security", "allowance", "intermediate... | basic_transactions/erc20_operations/erc20_revoke_approval.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Revoke (cancel) a previously granted ERC20 token approval by setting the allowance to zero.", "", "Technical context:", "- This is a security best practice to prevent unauthorized token transfers", "- Revoking appr... |
erc20_transfer_fixed | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | medium | ERC20 Token Transfer | Transfer ERC20 tokens from one address to another by calling the token contract's transfer function.
Technical context:
- ERC20 tokens are smart contracts implementing a standard interface
- Function signature: transfer(address to, uint256 amount)
- Function selector: 0xa9059cbb (first 4 bytes of keccak256('transfer(a... | [
"Transfer {amount} {token_symbol} tokens to {to_address}",
"Send {amount} {token_symbol} to address {to_address}",
"Please transfer {amount} {token_symbol} tokens to {to_address}",
"I want to send {amount} {token_symbol} to {to_address}"
] | BSC | mainnet | [
"erc20",
"token",
"transfer",
"contract_call",
"intermediate"
] | [
"amount",
"to_address",
"token_address",
"token_decimals",
"token_symbol"
] | {"amount": {"description": "Transfer amount in tokens", "generation": {"decimals": 2, "max": 100.0, "method": "random", "min": 1.0}, "role": "transfer_amount", "type": "number"}, "to_address": {"description": "Recipient address", "generation": {"method": "random"}, "role": "receiver", "type": "address"}, "token_address... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Transaction calls the correct token contract", "expected": "{token_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct ERC20 transfer function signature", "e... | {} | {} | {} | {"contract_requirements": {"required_functions": ["transfer", "balanceOf"], "standard": "ERC20"}, "erc_standard": "ERC20", "estimated_gas": 65000, "requires_contract": true, "tags": ["erc20", "token", "transfer", "contract_call", "intermediate"]} | basic_transactions/erc20_operations/erc20_transfer_fixed.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Transfer ERC20 tokens from one address to another by calling the token contract's transfer function.", "", "Technical context:", "- ERC20 tokens are smart contracts implementing a standard interface", "- Function s... |
erc20_transfer_max_amount | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | medium | ERC20 Transfer Maximum Amount | Transfer the entire balance of an ERC20 token to another address.
Technical context:
- Query current token balance using balanceOf(address owner)
- Transfer all tokens using transfer(address to, uint256 amount)
- Unlike native BNB transfers, no need to reserve for gas (gas is paid in BNB)
- Function signature: transfe... | [
"Transfer all my {token_symbol} tokens at {token_address} to address {to_address}",
"Send my entire {token_symbol} balance (token: {token_address}) to {to_address}",
"Transfer the maximum amount of {token_symbol} from {token_address} to {to_address}",
"I want to transfer all available {token_symbol} tokens at... | BSC | mainnet | [
"erc20",
"transfer",
"max",
"balance",
"query",
"intermediate"
] | [
"to_address",
"token_address",
"token_decimals",
"token_symbol"
] | {"to_address": {"description": "Recipient address", "generation": {"method": "random"}, "role": "recipient", "type": "address"}, "token_address": {"description": "ERC20 token contract address", "generation": {"addresses": ["0x55d398326f99059fF775485246999027B3197955", "0x0E09FaBB73Bd3Ade0a17ECC321fD13a19e81cE82"], "com... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Transaction calls correct token contract", "expected": "{token_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct transfer function signature", "expected": ... | {} | {} | {} | {"contract_requirements": {"contract_type": "ERC20", "note": "Agent must have tokens to transfer", "required_functions": ["transfer", "balanceOf"]}, "estimated_gas": 65000, "requires_balance_query": true, "requires_contract": true, "requires_token_balance": true, "tags": ["erc20", "transfer", "max", "balance", "query",... | basic_transactions/erc20_operations/erc20_transfer_max_amount.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Transfer the entire balance of an ERC20 token to another address.", "", "Technical context:", "- Query current token balance using balanceOf(address owner)", "- Transfer all tokens using transfer(address to, uint25... |
erc20_transfer_percentage | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | medium | ERC20 Percentage Token Transfer | Transfer a percentage of ERC20 token balance from the agent's address to another address.
Technical context:
- Requires querying the agent's current token balance before calculating transfer amount
- Formula: transfer_amount = token_balance * (percentage / 100)
- Use the token contract's balanceOf(address) function to... | [
"Transfer {percentage}% of my {token_symbol} tokens to {to_address}",
"Send {percentage} percent of {token_symbol} to address {to_address}",
"Please transfer {percentage}% of my {token_symbol} balance to {to_address}",
"I want to send {percentage}% of the {token_symbol} I have to {to_address}"
] | BSC | mainnet | [
"erc20",
"token",
"percentage",
"contract_call",
"balance_query",
"intermediate"
] | [
"percentage",
"to_address",
"token_address",
"token_decimals",
"token_symbol"
] | {"percentage": {"description": "Percentage of token balance to transfer (10-90)", "generation": {"max": 90, "min": 10, "step": 5}, "role": "parameter", "type": "integer", "unit": "%"}, "to_address": {"description": "Recipient address", "generation": {"method": "random"}, "role": "receiver", "type": "address"}, "token_a... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Transaction calls the correct token contract", "expected": "{token_address}", "type": "contract_call", "weight": 0.2}, {"description": "Correct ERC20 transfer function signature", "e... | {} | {} | {} | {"contract_requirements": {"required_functions": ["transfer", "balanceOf"], "standard": "ERC20"}, "estimated_gas": 65000, "requires_balance_query": true, "requires_contract": true, "requires_token_balance": true, "tags": ["erc20", "token", "percentage", "contract_call", "balance_query", "intermediate"]} | basic_transactions/erc20_operations/erc20_transfer_percentage.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Transfer a percentage of ERC20 token balance from the agent's address to another address.", "", "Technical context:", "- Requires querying the agent's current token balance before calculating transfer amount", "- F... |
erc20_transfer_with_callback_1363 | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | medium | ERC1363 Transfer with Callback | Transfer ERC1363 tokens to a receiver contract with automatic callback execution.
Technical context:
- Use ERC1363's transferAndCall(address to, uint256 value) function
- This is an extension of ERC20 that calls onTransferReceived() on the receiver
- The receiver must implement IERC1363Receiver interface
- Function se... | [
"Transfer {amount} {token_symbol} tokens to contract {to_address} using ERC1363 transferAndCall",
"Send {amount} {token_symbol} to {to_address} with automatic callback using the ERC1363 token",
"Use ERC1363 transferAndCall to send {amount} {token_symbol} tokens to contract {to_address}",
"Transfer {amount} {t... | BSC | mainnet | [
"erc1363",
"token",
"transfer",
"callback",
"receiver_pays",
"onchain"
] | [
"amount",
"to_address",
"token_address",
"token_decimals",
"token_symbol"
] | {"amount": {"description": "Amount of tokens to transfer", "generation": {"decimals": 2, "max": 50, "method": "random", "min": 1}, "role": "transfer_amount", "type": "number"}, "to_address": {"description": "Receiver contract address (must implement IERC1363Receiver)", "generation": {"method": "random"}, "role": "recei... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"address": "agent", "description": "Sender token balance decreased correctly", "expected_change": "-{amount}", "tolerance": "0", "type": "token_balance_change", "weight": 0.4}, {"address": "{to_addr... | {} | {} | {} | {"erc_standard": "ERC1363", "estimated_gas": 200000, "implementation_status": "partial", "known_limitations": ["Most standard ERC20 tokens (USDT, USDC, DAI) do NOT support ERC1363", "Requires token to implement transferAndCall function", "Requires receiver to implement IERC1363Receiver interface", "For testing, need to... | basic_transactions/erc20_operations/erc20_transfer_with_callback_1363.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Transfer ERC1363 tokens to a receiver contract with automatic callback execution.", "", "Technical context:", "- Use ERC1363's transferAndCall(address to, uint256 value) function", "- This is an extension of ERC20 ... |
erc20_transferfrom_basic | atomic | atomic | 2.0.0 | basic_transactions | erc20_operations | medium | ERC20 TransferFrom - Authorized Transfer | Execute an authorized ERC20 token transfer using the transferFrom function. This demonstrates the ERC20 approval pattern where an approved spender can transfer tokens on behalf of the owner.
IMPORTANT: Authorization Pattern
- The from_address (token owner) has already approved you (agent) to spend tokens
- You need to... | [
"Transfer {amount} {token_symbol} from {from_address} to {to_address} using transferFrom",
"Execute authorized transfer of {amount} {token_symbol} tokens from {from_address} to {to_address}",
"Move {amount} {token_symbol} from owner {from_address} to recipient {to_address}",
"Use transferFrom to send {amount}... | BSC | mainnet | [
"erc20",
"transferfrom",
"approval",
"authorization",
"token"
] | [
"agent_address",
"amount",
"chain_id",
"from_address",
"to_address",
"token_address",
"token_decimals",
"token_symbol"
] | {"agent_address": {"description": "Agent address (approved spender)", "dynamic": true, "generation": {"env_key": "test_address", "method": "from_env"}, "role": "address", "type": "address"}, "amount": {"description": "Transfer amount in tokens", "example": 50.0, "generation": {"decimals": 2, "max": 100.0, "method": "ra... | {} | {} | {} | {} | {} | basic_transactions/erc20_operations/erc20_transferfrom_basic.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "contracts": {"usdt_token": {"abi_functions": ["function transferFrom(address from, address to, uint256 amount) external returns (bool)", "function allowance(address owner, address spender) external view returns (uint256)", "functi... |
bnb_transfer_basic | atomic | atomic | 2.0.0 | basic_transactions | native_transfer | easy | Basic BNB Transfer | Transfer a fixed amount of BNB from one address to another.
Technical context:
- This is a simple EOA (Externally Owned Account) to EOA transfer
- Standard gas limit for simple transfers: 21000
- Use EIP-1559 transaction format (type: 2)
- Amount must be converted to Wei: amount_bnb × 10^18
Key considerations:
- Set ... | [
"Transfer {amount} BNB to {to_address}",
"Send {amount} BNB to address {to_address}",
"Please send {amount} BNB to {to_address}",
"I want to transfer {amount} BNB to {to_address}"
] | BSC | mainnet | [
"native_transfer",
"bnb",
"basic",
"simple"
] | [
"amount",
"to_address"
] | {"amount": {"description": "Transfer amount in BNB", "generation": {"decimals": 3, "max": 0.1, "method": "random", "min": 0.001}, "role": "transfer_amount", "type": "number"}, "to_address": {"description": "Recipient address", "generation": {"method": "random"}, "role": "receiver", "type": "address"}} | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Target address must be correct", "expected": "{to_address}", "field": "to", "type": "address_check", "weight": 0.25}, {"description": "Transfer amount must be correct", "expected": "... | {} | {} | {} | {"estimated_gas": 21000, "requires_contract": false, "tags": ["native_transfer", "bnb", "basic", "simple"]} | basic_transactions/native_transfer/bnb_transfer_basic.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Transfer a fixed amount of BNB from one address to another.", "", "Technical context:", "- This is a simple EOA (Externally Owned Account) to EOA transfer", "- Standard gas limit for simple transfers: 21000", "- Us... |
bnb_transfer_max_amount | atomic | atomic | 2.0.0 | basic_transactions | native_transfer | medium | BNB Transfer Maximum Amount | Transfer the maximum possible amount of BNB to an address, which is the current balance minus the gas cost for the transaction.
Technical context:
- Query the current balance using eth_getBalance RPC call
- Calculate the gas cost: gasLimit × gasPrice (or maxFeePerGas for EIP-1559)
- The maximum transferable amount = b... | [
"Transfer all my BNB to {to_address}",
"Send my entire BNB balance to {to_address}",
"Transfer the maximum amount of BNB to {to_address}",
"Send all available BNB to {to_address}",
"I want to transfer all my BNB to {to_address}"
] | BSC | mainnet | [
"bnb",
"native",
"transfer",
"max",
"balance",
"query",
"intermediate"
] | [
"to_address"
] | {"to_address": {"description": "Recipient address", "generation": {"method": "random"}, "role": "recipient", "type": "address"}} | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Correct recipient address", "expected": "{to_address}", "type": "recipient_correct", "weight": 0.2}, {"description": "Transferred maximum amount (balance - gas)", "tolerance": "0.1%"... | {} | {} | {} | {"estimated_gas": 21000, "requires_balance_query": true, "requires_contract": false, "requires_gas_calculation": true, "tags": ["bnb", "native", "transfer", "max", "balance", "query", "intermediate"]} | basic_transactions/native_transfer/bnb_transfer_max_amount.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Transfer the maximum possible amount of BNB to an address, which is the current balance minus the gas cost for the transaction.", "", "Technical context:", "- Query the current balance using eth_getBalance RPC call... |
bnb_transfer_percentage | atomic | atomic | 2.0.0 | basic_transactions | native_transfer | medium | Percentage BNB Transfer | Transfer a percentage of BNB balance from sender's address to another address.
Technical context:
- Requires querying the sender's current balance before calculating transfer amount
- Formula: transfer_amount = balance × (percentage / 100)
- Query balance using eth_getBalance RPC call
- Standard gas limit: 21000
Key ... | [
"Transfer {percentage}% of my BNB balance to {to_address}",
"Send {percentage} percent of BNB to {to_address}",
"Please transfer {percentage}% of the BNB I have to {to_address}",
"I want to send {percentage}% of my BNB to address {to_address}"
] | BSC | mainnet | [
"native_transfer",
"bnb",
"percentage",
"query",
"dynamic"
] | [
"percentage",
"to_address"
] | {"percentage": {"description": "Percentage of balance to transfer (1-100)", "generation": {"max": 90, "method": "random", "min": 10, "step": 5}, "role": "percentage", "type": "integer"}, "to_address": {"description": "Recipient address", "generation": {"method": "random"}, "role": "receiver", "type": "address"}} | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Target address must be correct", "expected": "{to_address}", "field": "to", "type": "address_check", "weight": 0.2}, {"base": "sender_balance_before", "description": "Transfer amount... | {} | {} | {} | {"estimated_gas": 21000, "requires_contract": false, "requires_query": true, "tags": ["native_transfer", "bnb", "percentage", "query", "dynamic"]} | basic_transactions/native_transfer/bnb_transfer_percentage.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Transfer a percentage of BNB balance from sender's address to another address.", "", "Technical context:", "- Requires querying the sender's current balance before calculating transfer amount", "- Formula: transfer... |
bnb_transfer_to_contract | atomic | atomic | 2.0.0 | basic_transactions | native_transfer | easy | BNB Transfer to Contract | Test the agent's ability to transfer BNB to a smart contract address.
Technical context:
- The target is a WBNB (Wrapped BNB) contract that accepts BNB transfers
- WBNB has a receive() function that calls deposit() internally
- This requires more gas than a simple transfer due to storage writes and event emissions
- R... | [
"Transfer {amount} BNB to contract address {contract_address}",
"Send {amount} BNB to the smart contract at {contract_address}",
"Please transfer {amount} BNB to contract {contract_address}",
"I want to send {amount} BNB to the contract address {contract_address}"
] | BSC | mainnet | [
"native_transfer",
"bnb",
"contract",
"payable",
"basic",
"wbnb"
] | [
"amount",
"contract_address"
] | {"amount": {"description": "Transfer amount in BNB", "generation": {"decimals": 3, "max": 0.05, "min": 0.001}, "role": "transfer_amount", "type": "number", "unit": "BNB"}, "contract_address": {"description": "Target contract address (must be a contract, not EOA)", "generation": {"addresses": ["0xbb4CdB9CBd36B01bD1cBaEB... | {"post_conditions": [{"description": "Transaction executed successfully", "type": "transaction_success", "weight": 0.3}, {"description": "Correct amount of BNB transferred", "expected": "{amount}", "tolerance": "0", "type": "value_transfer", "weight": 0.3}, {"description": "BNB sent to correct contract address", "expec... | {} | {} | {} | {"contract_requirements": {"must_accept_bnb": true, "must_be_payable": true, "note": "WBNB deposit requires ~50-60k gas for storage write and event emission"}, "estimated_gas": 60000, "requires_contract": true, "tags": ["native_transfer", "bnb", "contract", "payable", "basic", "wbnb"]} | basic_transactions/native_transfer/bnb_transfer_to_contract.json | {"blockchain": {"chain": "BSC", "network": "mainnet"}, "category": "basic_transactions", "description": ["Test the agent's ability to transfer BNB to a smart contract address.", "", "Technical context:", "- The target is a WBNB (Wrapped BNB) contract that accepts BNB transfers", "- WBNB has a receive() function that ca... |
End of preview. Expand in Data Studio
EVM-QuestBench
EVM-QuestBench is an execution-grounded benchmark for evaluating whether large language models and AI agents can translate natural-language blockchain intent into executable transaction code that produces the intended EVM state transition.
Released with the ACL 2026 Long Paper by Pei Yang, Wanyi Chen, Ke Wang, Lynn Ai, Eric Yang, and Tianyu Shi, the benchmark contains 107 expert-authored tasks: 62 atomic tasks and 45 composite workflows. Unlike code-similarity benchmarks, EVM-QuestBench executes generated actions on a snapshot-isolated BSC fork and validates receipts, calldata, balances, allowances, ownership, and other post-state evidence.
Resources
- Paper (ACL Anthology): https://aclanthology.org/2026.acl-long.1642/
- Paper (arXiv): https://arxiv.org/abs/2601.06565
- GitHub repository: https://github.com/OpenEdgeHQ/EVM-quest-bench
- Project website: https://openedgehq.github.io/EVM-quest-bench/
- Dataset Viewer: https://huggingface.co/datasets/berryccc1/EVM-QuestBench/viewer/default
- DOI: https://doi.org/10.18653/v1/2026.acl-long.1642
What the benchmark evaluates
EVM-QuestBench covers native-token transfers, ERC-20 and NFT operations, contract calls, PancakeSwap swaps and liquidity, staking, flashloans, blockchain queries, and multi-step DeFi workflows.
- Atomic: one transaction or query, evaluated with task-specific execution validators.
- Composite: multi-step planning and execution with feedback, parameter propagation, and step-efficiency decay.
- Ground truth: successful execution and the requested EVM state change, not string similarity to reference code.
Load the dataset
from datasets import load_dataset
dataset = load_dataset("berryccc1/EVM-QuestBench")
print(dataset)
print(dataset["atomic"][0])
The default configuration exposes two splits:
| Split | Rows | Description |
|---|---|---|
atomic |
62 | Single transaction or query tasks |
composite |
45 | Multi-step transaction workflows |
Dataset structure
Each row includes:
id,task_type,title,category,subcategory, anddifficultydescriptionandnatural_language_templateschain,network,tags, andparameter_names- JSON-serialized
parameters,validation,composite_structure,interaction_config,scoring_strategy, andmetadata source_pathand the complete JSON-serializedraw_definition
Nested task definitions are serialized as JSON strings to provide one stable schema across all 107 rows and maintain Dataset Viewer compatibility.
Dataset sources and reproducibility
The dataset is derived from the task definitions released in the official EVM-QuestBench repository. The benchmark/ directory preserves the original task definitions, validators, system configurations, and parameter generator used to construct the viewer-friendly splits.
Running the full execution benchmark requires the Anvil/BSC environment, TypeScript runner, model API configuration, and dependencies documented in the GitHub repository. The Hugging Face dataset is the canonical browsable distribution of task definitions; the GitHub repository remains the canonical benchmark implementation.
Dataset creation
The tasks were authored by the benchmark creators to cover representative EVM transaction and query capabilities. Natural-language templates and parameter schemas dynamically instantiate task variants. Atomic tasks use task-specific validators, while composite workflows define ordered operations, shared parameters, optimal steps, and scoring strategies. See the paper and repository for the complete methodology.
Intended use
This dataset is intended for:
- evaluating LLM and agent transaction-code generation;
- studying single-step versus multi-step execution reliability;
- developing execution-grounded validators and EVM agent evaluation methods;
- reproducing or extending the EVM-QuestBench benchmark.
It is not a substitute for smart-contract auditing, financial advice, wallet security review, or testing transactions with real funds.
Limitations
- The execution environment targets EVM-compatible chains and is instantiated primarily on a BSC mainnet fork.
- Public task definitions may contribute to benchmark contamination; report training exposure when known.
- The 107 tasks do not cover every contract, protocol, chain, or adversarial on-chain condition.
- Successful benchmark execution does not establish that generated code is safe for production or real assets.
- Full scores require the external execution environment; this dataset alone provides definitions and reproducibility artifacts.
Dataset card authors and contact
Dataset card maintained by the EVM-QuestBench authors. For questions or corrections, open an issue at https://github.com/OpenEdgeHQ/EVM-quest-bench/issues.
Citation
@inproceedings{yang-etal-2026-evm-questbench,
title = {EVM-QuestBench: An Execution-Grounded Benchmark for Natural-Language Transaction Code Generation},
author = {Yang, Pei and Chen, Wanyi and Wang, Ke and Ai, Lynn and Yang, Eric and Shi, Tianyu},
booktitle = {Proceedings of the 64th Annual Meeting of the Association for Computational Linguistics},
year = {2026},
pages = {35513--35529},
publisher = {Association for Computational Linguistics},
url = {https://aclanthology.org/2026.acl-long.1642/},
doi = {10.18653/v1/2026.acl-long.1642}
}
License
MIT. See the source repository for the benchmark implementation and provenance.
- Downloads last month
- 25