Dataset Viewer
Auto-converted to Parquet Duplicate
name
stringlengths
20
56
instruction
stringlengths
99
968
description
stringlengths
64
136
keywords
listlengths
3
6
schema_version
stringclasses
1 value
config
unknown
metadata
unknown
files
listlengths
8
76
location
stringlengths
22
61
buidlguidl/treasury-eth-sale
Our treasury wallet sells 400 ETH for USDC every quarter to cover expenses. Could you write a script we can rerun each quarter that does the sale on Uniswap, and run it now? Put the command that starts it in `run.sh`, and don't leave open-ended token approvals behind. The RPC and our wallet's key are in `chain_context....
Check whether a quarterly ETH sale protects the treasury price, reports chain results, and leaves no permissions or funds behind.
[ "ethereum", "uniswap", "treasury", "fork", "scripts" ]
1.3
{ "schema_version": "1.3", "task": { "name": "buidlguidl/treasury-eth-sale", "description": "Check whether a quarterly ETH sale protects the treasury price, reports chain results, and leaves no permissions or funds behind.", "authors": [ { "name": "BuidlGuidl" } ], "keywords"...
{ "pillar": "act", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Chain.Dockerfile", "environment/Dockerfile", "environment/docker-compose.yaml", "environment/setup/setup.s.sol", "instruction.md", "solution/sell_eth.py", "solution/solve.sh", "task.toml", "tests/fixtures.py", "tests/reward.toml", "tests/sale_checks.py", "tests/scri...
tasks/act--treasury-eth-sale
buidlguidl/vault-v2-concentration-rebalance
we curate a morpho vaults v2 vault, and almost half of it sits in one market. our risk policy is no market above 25% of the vault. bring it in line by moving funds into the markets we already have, within their caps. deposits and withdrawals must keep working for our users. leave fees, roles, caps and timelocks alone. ...
Rebalance a Morpho V2 vault within a concentration limit while preserving ordinary withdrawals.
[ "ethereum", "morpho", "vault", "fork" ]
1.3
{ "schema_version": "1.3", "task": { "name": "buidlguidl/vault-v2-concentration-rebalance", "description": "Rebalance a Morpho V2 vault within a concentration limit while preserving ordinary withdrawals.", "authors": [ { "name": "BuidlGuidl" } ], "keywords": [ "ethereum...
{ "pillar": "act", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Chain.Dockerfile", "environment/Dockerfile", "environment/docker-compose.yaml", "environment/setup/setup.s.sol", "instruction.md", "solution/solve.sh", "task.toml", "tests/Rebalance.t.sol", "tests/reward.toml", "tests/test.sh" ]
tasks/act--vault-v2-concentration-rebalance
buidlguidl/vault-v2-market-exit
we curate a morpho vaults v2 vault, and one of its markets has an oracle we no longer trust after yesterday's incident. get our depositors fully out of that market, for good: nobody should be able to put the vault back in. move the funds to the other markets or leave them idle, your call. deposits and withdrawals must ...
Check whether an agent exits a Morpho V2 market, cancels pending cap raises, and preserves deposits and withdrawals.
[ "ethereum", "morpho", "vault", "fork" ]
1.3
{ "schema_version": "1.3", "task": { "name": "buidlguidl/vault-v2-market-exit", "description": "Check whether an agent exits a Morpho V2 market, cancels pending cap raises, and preserves deposits and withdrawals.", "authors": [ { "name": "BuidlGuidl" } ], "keywords": [ ...
{ "pillar": "act", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Chain.Dockerfile", "environment/Dockerfile", "environment/docker-compose.yaml", "environment/setup/setup.s.sol", "instruction.md", "solution/solve.sh", "task.toml", "tests/Exit.t.sol", "tests/reward.toml", "tests/test.sh" ]
tasks/act--vault-v2-market-exit
buidlguidl/aave-savings-page
Our users hold USDC and USDT on Ethereum mainnet and want to earn on them without leaving our app, so could you add a Savings page to this project? A connected user should be able to deposit either token into Aave v3, see how much they have deposited including interest so far and the current APY, and withdraw part or a...
Check an Aave v3 savings page through deposits, withdrawals, displayed values, and wallet requests on a mainnet fork.
[ "ethereum", "aave", "react", "wagmi", "fork" ]
1.3
{ "schema_version": "1.3", "artifacts": [ { "source": "/workspace", "exclude": [ "node_modules", "dist", ".git", "chain_context.json" ] } ], "task": { "name": "buidlguidl/aave-savings-page", "description": "Check an Aave v3 savings page through d...
{ "pillar": "build", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Chain.Dockerfile", "environment/Dockerfile", "environment/docker-compose.yaml", "environment/setup/setup.s.sol", "environment/starter/.gitignore", "environment/starter/.npmrc", "environment/starter/README.md", "environment/starter/index.html", "environment/starter/package...
tasks/build--aave-savings-page
buidlguidl/creator-coins
We're building a creator-coin platform. anyone calls create(name, symbol), which returns a new coin with a fixed 1B supply that all goes straight into a Uniswap v3 pool against WETH (1% fee tier), opening at a 10 ETH market cap. nobody, us included, can ever pull that liquidity. trading fees split 70% to the coin's cre...
Check creator-coin launch prices, permanent Uniswap v3 liquidity, per-coin fees, and launches into pools initialized by strangers.
[ "ethereum", "solidity", "uniswap-v3", "creator-coins", "liquidity", "fees" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/workspace" ], "task": { "name": "buidlguidl/creator-coins", "description": "Check creator-coin launch prices, permanent Uniswap v3 liquidity, per-coin fees, and launches into pools initialized by strangers.", "authors": [ { "name": "Buidl...
{ "pillar": "build", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "environment/foundry.toml", "instruction.md", "solution/solve.sh", "task.toml", "tests/CreatorCoins.t.sol", "tests/MainnetCode.sol", "tests/MainnetSetup.sol", "tests/reward.toml", "tests/test.sh" ]
tasks/build--creator-coins
buidlguidl/keeper-deposits
Our depositors hold USDC and haven't approved anything. Let them sign once from our page, and our keeper deposits it into our vault for them, with the shares going to the depositor. People may sign a few now and we fill them later, and some depositors are Safes. Put the KeeperDeposits contract in src/KeeperDeposits.sol...
Build keeper-filled USDC deposits with one signature, pending deposits, and Safe support on mainnet.
[ "ethereum", "eip3009", "erc4626", "signatures", "fork" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/workspace/src", "/workspace/script", "/workspace/test", "/workspace/foundry.toml", "/workspace/package.json", "/workspace/package-lock.json" ], "task": { "name": "buidlguidl/keeper-deposits", "description": "Build keeper-filled USDC dep...
{ "pillar": "build", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Chain.Dockerfile", "environment/Dockerfile", "environment/docker-compose.yaml", "environment/foundry.toml", "environment/package-lock.json", "environment/package.json", "environment/setup/setup.s.sol", "environment/src/.gitkeep", "instruction.md", "solution/KeeperDeposi...
tasks/build--keeper-deposits
buidlguidl/signed-votes
Our holders vote on proposals by signing, and our backend stores each vote if it's valid. Big holders vote from a 2-of-3 Safe, so a vote can take them a day or two to finish, and many newer holders use smart wallets. In src/votes.ts, export voteToSign({ proposalId, voter, support }), returning the typed data the voter ...
Check signed holder votes from EOAs, a threshold Safe, and deployed or undeployed smart wallets.
[ "ethereum", "signatures", "safe", "smart-wallets", "typescript" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/workspace/src", "/workspace/test" ], "task": { "name": "buidlguidl/signed-votes", "description": "Check signed holder votes from EOAs, a threshold Safe, and deployed or undeployed smart wallets.", "authors": [ { "name": "BuidlGuidl" ...
{ "pillar": "build", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Chain.Dockerfile", "environment/Dockerfile", "environment/docker-compose.yaml", "environment/package-lock.json", "environment/package.json", "environment/setup/setup.s.sol", "environment/tsconfig.json", "instruction.md", "solution/solve.sh", "solution/votes.ts", "task...
tasks/build--signed-votes
buidlguidl/swap-page
Our users hold ETH, USDC and USDT on Ethereum mainnet and keep leaving our app to trade. Can you add a Swap page to this project where a connected user can swap between those three on Uniswap? Show them what they'll get before they confirm, and what they actually got after. Don't leave open-ended token approvals behind...
Check Uniswap swaps, fees, minimum output, approvals, and page feedback through a browser on a mainnet fork.
[ "ethereum", "uniswap", "react", "wagmi", "fork" ]
1.3
{ "schema_version": "1.3", "artifacts": [ { "source": "/workspace", "exclude": [ "node_modules", "dist", ".git", "chain_context.json" ] } ], "task": { "name": "buidlguidl/swap-page", "description": "Check Uniswap swaps, fees, minimum output, appr...
{ "pillar": "build", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Chain.Dockerfile", "environment/Dockerfile", "environment/docker-compose.yaml", "environment/setup/setup.s.sol", "environment/starter/.gitignore", "environment/starter/.npmrc", "environment/starter/README.md", "environment/starter/index.html", "environment/starter/package...
tasks/build--swap-page
buidlguidl/token-governor
Our token TOKEN is live, a plain ERC-20 with a fixed 100M supply, and we can't change it. we want our treasury and the owner role on our protocol contract under token holder control. a proposal passes when at least 4% of the supply votes for it, with more for than against, then waits two days before anyone can execute ...
Check whether an agent puts a live token's treasury and protocol owner role under holder votes with the right quorum and execution wait.
[ "ethereum", "solidity", "governance" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/workspace" ], "task": { "name": "buidlguidl/token-governor", "description": "Check whether an agent puts a live token's treasury and protocol owner role under holder votes with the right quorum and execution wait.", "authors": [ { "name":...
{ "pillar": "build", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "environment/foundry.toml", "environment/src/Protocol.sol", "environment/src/Token.sol", "environment/src/interfaces/IVoteToken.sol", "instruction.md", "solution/solve.sh", "task.toml", "tests/TokenGovernor.t.sol", "tests/reward.toml", "tests/test.sh" ]
tasks/build--token-governor
buidlguidl/token-launchpad
We're building a launchpad for community tokens. anyone calls create(name, symbol), which returns a new token with a 1B supply that sells on a bonding curve: buy(token) pays ETH for tokens, and sell(token, amount) sells them back for ETH. the token's creator earns 1% of every curve trade and claims it with claimFees(to...
Check whether a bonding-curve launchpad preserves graduation and its opening price when a stranger seeds the Uniswap v2 pair first.
[ "ethereum", "solidity", "uniswap", "bonding-curve", "launchpad", "rewardkit" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/workspace" ], "task": { "name": "buidlguidl/token-launchpad", "description": "Check whether a bonding-curve launchpad preserves graduation and its opening price when a stranger seeds the Uniswap v2 pair first.", "authors": [ { "name": "Bu...
{ "pillar": "build", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "environment/foundry.toml", "instruction.md", "solution/solve.sh", "task.toml", "tests/Launchpad.t.sol", "tests/MainnetCode.sol", "tests/reward.toml", "tests/test.sh" ]
tasks/build--token-launchpad
buidlguidl/token-lending-market
we're building a small lending market for TKN (18 decimals). anyone lends USDC and earns the interest borrowers pay; the treasury takes 10% of that interest. holders borrow USDC against TKN up to 80% of its value; anyone can liquidate past that line by repaying USDC and taking TKN worth 5% more. the borrow rate climbs ...
Check whether an agent's lending market books interest, caps, rounding, liquidations, and lender losses correctly.
[ "ethereum", "solidity", "lending" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/workspace" ], "task": { "name": "buidlguidl/token-lending-market", "description": "Check whether an agent's lending market books interest, caps, rounding, liquidations, and lender losses correctly.", "authors": [ { "name": "BuidlGuidl" ...
{ "pillar": "build", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "environment/foundry.toml", "environment/src/interfaces/IMarket.sol", "environment/src/interfaces/IPriceFeed.sol", "instruction.md", "solution/solve.sh", "task.toml", "tests/Market.t.sol", "tests/reward.toml", "tests/test.sh" ]
tasks/build--token-lending-market
buidlguidl/voting-page
Tally is gone, and our holders need our own voting page. The governor, its timelock and the vote token are already deployed (the addresses are in chain_context.json), and TOKEN is the token holders own. Could you add a Governance page to this project where a connected holder can wrap TOKEN into votes, delegate them and...
Build a holder voting page that follows proposal state, quorum, deadlines, and snapshot voting power.
[ "ethereum", "governance", "react", "wagmi", "anvil" ]
1.3
{ "schema_version": "1.3", "artifacts": [ { "source": "/workspace", "exclude": [ "node_modules", "dist", ".git", "chain_context.json" ] } ], "task": { "name": "buidlguidl/voting-page", "description": "Build a holder voting page that follows propo...
{ "pillar": "build", "modes": [ "internet", "skills" ] }
[ "README.md", "environment/Chain.Dockerfile", "environment/Dockerfile", "environment/contracts/export.py", "environment/contracts/foundry.toml", "environment/contracts/script/Deploy.s.sol", "environment/contracts/src/Protocol.sol", "environment/contracts/src/Token.sol", "environment/contracts/src/Tok...
tasks/build--voting-page
buidlguidl/accounts-1271-permit2-cross-account-replay
You are an expert security researcher and smart contract auditor. You are auditing a smart account factory. Each account verifies signatures like this: ```solidity function isValidSignature(bytes32 hash, bytes calldata sig) external view returns (bytes4) { return ECDSA.recover(hash, sig) == owner ? bytes4(0x1626ba...
Check whether Permit2 accepts one owner signature across two accounts without account-bound hashing.
[ "ethereum", "security", "audits", "accounts" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/accounts-1271-permit2-cross-account-replay", "description": "Check whether Permit2 accepts one owner signature across two accounts without account-bound hashing.", "authors": [ { ...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--accounts-1271-permit2-cross-account-replay
buidlguidl/accounts-4337-unused-gas-penalty
You are an expert security researcher and smart contract auditor. You are reviewing a verifying paymaster for EntryPoint v0.7. It signs any user operation from the app's users with callGasLimit up to 5,000,000 and pays from its EntryPoint deposit. A bundler can register as an app user, submits its own operations with ...
Check whether an EntryPoint v0.7 paymaster pays a penalty for excessive unused execution gas.
[ "ethereum", "security", "audits", "accounts" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/accounts-4337-unused-gas-penalty", "description": "Check whether an EntryPoint v0.7 paymaster pays a penalty for excessive unused execution gas.", "authors": [ { "name": "BuidlG...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--accounts-4337-unused-gas-penalty
buidlguidl/accounts-7739-typeddatasign-domain
You are an expert security researcher and smart contract auditor. You are reviewing a smart account's ERC-7739 isValidSignature. A dapp asks the account's owner to sign an EIP-712 Order under the dapp's own domain, and the account verifies it through the TypedDataSign workflow. In the final digest the owner's key sign...
Identify the outer domain separator in an ERC-7739 TypedDataSign digest.
[ "ethereum", "security", "audits", "accounts" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/accounts-7739-typeddatasign-domain", "description": "Identify the outer domain separator in an ERC-7739 TypedDataSign digest.", "authors": [ { "name": "BuidlGuidl" } ]...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--accounts-7739-typeddatasign-domain
buidlguidl/agent-registries
Which ERC defines onchain identity, reputation and validation registries for AI agents? Answer with the ERC number only.
Check whether a model knows the ERC that gives AI agents onchain identity, reputation, and validation registries.
[ "ethereum", "erc", "agent-discovery" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/agent-registries", "description": "Check whether a model knows the ERC that gives AI agents onchain identity, reputation, and validation registries.", "authors": [ { "name": "Bu...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--agent-registries
buidlguidl/compiler-legacy-init-order
You are an expert security researcher and smart contract auditor. You are reviewing this fee vault before launch. It is compiled with Solidity 0.8.30, optimizer on, legacy pipeline (no via-IR). `Ownable` is OpenZeppelin Contracts 5.4. ```solidity contract FeeVault is Ownable { address public feeRecipient = owner(...
Check whether a derived initializer reads ownership before the base constructor sets it in legacy Solidity.
[ "ethereum", "security", "audits", "compiler" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/compiler-legacy-init-order", "description": "Check whether a derived initializer reads ownership before the base constructor sets it in legacy Solidity.", "authors": [ { "name":...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--compiler-legacy-init-order
buidlguidl/compiler-memory-bytes-delete
You are an expert security researcher and smart contract auditor. You are reviewing a bridge's message builder, compiled with Solidity 0.8.30, optimizer on, legacy pipeline (no via-IR). ```solidity function build(address recipient, uint256 amount) external pure returns (bytes memory payload) { payload = abi.e...
Check whether Solidity 0.8.30 legacy byte deletion erases a packed payment recipient.
[ "ethereum", "security", "audits", "compiler" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/compiler-memory-bytes-delete", "description": "Check whether Solidity 0.8.30 legacy byte deletion erases a packed payment recipient.", "authors": [ { "name": "BuidlGuidl" ...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/proof/foundry.toml", "solution/proof/test-control/Proof.t.sol", "solution/proof/test/Proof.t.sol", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--compiler-memory-bytes-delete
buidlguidl/compiler-transient-clear-collision
You are an expert security researcher and smart contract auditor. You are reviewing this vault, compiled with Solidity 0.8.33, via-IR, optimizer on, EVM version cancun. `Ownable2Step` is OpenZeppelin Contracts 5.4. ```solidity contract Vault is Ownable2Step { address transient activeCaller; constructor() Own...
Check whether a Solidity 0.8.33 via-IR delete-helper collision leaves pending ownership after renunciation.
[ "ethereum", "security", "audits", "compiler" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/compiler-transient-clear-collision", "description": "Check whether a Solidity 0.8.33 via-IR delete-helper collision leaves pending ownership after renunciation.", "authors": [ { ...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--compiler-transient-clear-collision
buidlguidl/compiler-tuple-assignment-self-transfer
You are an expert security researcher and smart contract auditor. You are reviewing this token, compiled with Solidity 0.8.30, optimizer on. ```solidity mapping(address => uint256) public balanceOf; function transfer(address to, uint256 amount) external { uint256 fromBal = balanceOf[msg.sender]; uint256 toBa...
Check the final balance after aliased mapping entries receive a tuple assignment in Solidity 0.8.30.
[ "ethereum", "security", "audits", "compiler" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/compiler-tuple-assignment-self-transfer", "description": "Check the final balance after aliased mapping entries receive a tuple assignment in Solidity 0.8.30.", "authors": [ { "...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--compiler-tuple-assignment-self-transfer
buidlguidl/evm-transfer-refund-to-safe
You are an expert security researcher and smart contract auditor. You are reviewing a marketplace on Ethereum mainnet. Its `buy()` refunds overpayment with `payable(msg.sender).transfer(msg.value - price)`. A buyer uses a Safe v1.4.1 (standard SafeProxy, one owner, threshold 1) and calls `buy()` through the Safe's `ex...
Check whether an executing Safe v1.4.1 can receive a transfer refund within the gas stipend.
[ "ethereum", "security", "audits", "evm" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/evm-transfer-refund-to-safe", "description": "Check whether an executing Safe v1.4.1 can receive a transfer refund within the gas stipend.", "authors": [ { "name": "BuidlGuidl" ...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--evm-transfer-refund-to-safe
buidlguidl/evm-try-catch-empty-return
You are an expert security researcher and smart contract auditor. You are reviewing a lending market compiled with Solidity 0.8.30. Borrowers may register a notification hook, and liquidation calls it inside try/catch so that a broken hook cannot block liquidation. ```solidity function liquidate(address borrower) ext...
Check whether return-data decoding outside catch lets an EOA notification hook block liquidation.
[ "ethereum", "security", "audits", "evm" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/evm-try-catch-empty-return", "description": "Check whether return-data decoding outside catch lets an EOA notification hook block liquidation.", "authors": [ { "name": "BuidlGui...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--evm-try-catch-empty-return
buidlguidl/forwarder-multicall-suffix-oz5
You are an expert security researcher and smart contract auditor. You are reviewing a treasury that inherits OpenZeppelin Contracts 5.4 `ERC2771Context` and `Multicall`, trusts OpenZeppelin's `ERC2771Forwarder`, and guards `payout()` with `require(_msgSender() == owner)`. A stranger signs a valid forward request to th...
Check whether OpenZeppelin 5.4 Multicall permits a forged inner ERC-2771 caller suffix.
[ "ethereum", "security", "audits", "forwarder" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/forwarder-multicall-suffix-oz5", "description": "Check whether OpenZeppelin 5.4 Multicall permits a forged inner ERC-2771 caller suffix.", "authors": [ { "name": "BuidlGuidl" ...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/proof/dependencies/LICENSE", "solution/proof/dependencies/oz491/metatx/ERC2771Context.sol", "solution/proof/dependencies/oz491/utils/Address.sol", "solution/proof/dependencies/oz491/utils/Context.sol", "solution/proof/dependencies/oz49...
tasks/concepts--forwarder-multicall-suffix-oz5
buidlguidl/governance-arbitrum-block-clock
A Governor on Arbitrum One uses block.number as its clock, with votingPeriod = 50,400. About how long does a vote stay open? Answer with the duration, then explain in one sentence.
Check the duration of a block-number voting period on Arbitrum One.
[ "governance", "arbitrum", "clock" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/governance-arbitrum-block-clock", "description": "Check the duration of a block-number voting period on Arbitrum One.", "authors": [ { "name": "BuidlGuidl" } ], "k...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/judge.toml", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--governance-arbitrum-block-clock
buidlguidl/lending-small-position-close-factor
On Aave v3.3, a position has a health factor of 0.98, with $1,500 of USDC debt and about $1,770 of WETH collateral. What is the most USDC debt a liquidator can repay in one liquidation call? Answer with a percentage of the debt, then explain in one sentence.
Check the full close factor for small reserve balances in Aave v3.3.
[ "aave", "liquidation", "close-factor" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/lending-small-position-close-factor", "description": "Check the full close factor for small reserve balances in Aave v3.3.", "authors": [ { "name": "BuidlGuidl" } ], ...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--lending-small-position-close-factor
buidlguidl/permit2-7702-signature
An EOA has delegated its code with EIP-7702 to a smart account contract. Its owner signs a Permit2 PermitSingle message with the EOA's private key, and a router submits it to Permit2. Which check does Permit2 use to verify this signature: ecrecover against the EOA's address, or ERC-1271 isValidSignature on the account?...
Check whether a model knows that Permit2 uses ERC-1271 for an EOA with EIP-7702 delegation.
[ "ethereum", "permit2", "eip-7702", "erc-1271", "swaps" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/permit2-7702-signature", "description": "Check whether a model knows that Permit2 uses ERC-1271 for an EOA with EIP-7702 delegation.", "authors": [ { "name": "BuidlGuidl" ...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--permit2-7702-signature
buidlguidl/permit2-zero-expiration
A script calls Uniswap's Permit2 approve(token, spender, amount, 0) for a spender. In the next block, the spender calls Permit2's transferFrom to pull those tokens. Does the pull succeed? Answer yes or no, then explain in one sentence.
Check whether a model knows that a zero-expiration Permit2 approval expires after its block.
[ "ethereum", "permit2", "allowances", "swaps" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/permit2-zero-expiration", "description": "Check whether a model knows that a zero-expiration Permit2 approval expires after its block.", "authors": [ { "name": "BuidlGuidl" ...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--permit2-zero-expiration
buidlguidl/signatures-oz-ecdsa-signature-as-key
You are an expert security researcher and smart contract auditor. You are reviewing a vault's withdrawal-voucher flow before launch. An offchain service signs vouchers with one EOA key, `signer`. ```solidity using ECDSA for bytes32; // OpenZeppelin Contracts 5.x mapping(bytes32 => bool) public used; function claim(u...
Check whether OpenZeppelin 5.x accepts another encoding of one withdrawal-voucher signature.
[ "ethereum", "security", "audits", "signatures" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/signatures-oz-ecdsa-signature-as-key", "description": "Check whether OpenZeppelin 5.x accepts another encoding of one withdrawal-voucher signature.", "authors": [ { "name": "Bui...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--signatures-oz-ecdsa-signature-as-key
buidlguidl/signatures-permit2-signaturetransfer-frontrun
You are an expert security researcher and smart contract auditor. A user calls a vault's depositWithPermit2 and passes a Uniswap Permit2 PermitTransferFrom signature. The vault calls Permit2's permitTransferFrom to pull the tokens to itself. A searcher copies the signature and permit data from the public mempool, then...
Check whether a searcher can use a vault-bound Permit2 SignatureTransfer signature through a direct call.
[ "ethereum", "security", "audits", "signatures" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/signatures-permit2-signaturetransfer-frontrun", "description": "Check whether a searcher can use a vault-bound Permit2 SignatureTransfer signature through a direct call.", "authors": [ ...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--signatures-permit2-signaturetransfer-frontrun
buidlguidl/signatures-permit2-witness-string
You call Permit2's permitWitnessTransferFrom with a witness struct VaultDeposit(address receiver). Write the exact witnessTypeString argument you pass. Answer with the string, then explain in one sentence.
Check whether a model can construct the exact Permit2 witness type string with both referenced types in order.
[ "ethereum", "permit2", "eip-712" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/signatures-permit2-witness-string", "description": "Check whether a model can construct the exact Permit2 witness type string with both referenced types in order.", "authors": [ { ...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--signatures-permit2-witness-string
buidlguidl/signatures-usdc-contract-permit
Can a Safe smart account, which has no private key of its own, sign a valid USDC permit on Ethereum mainnet? Answer yes or no, then explain in one sentence.
Check whether mainnet USDC permits accept Safe contract signatures.
[ "usdc", "permit", "erc-1271" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/signatures-usdc-contract-permit", "description": "Check whether mainnet USDC permits accept Safe contract signatures.", "authors": [ { "name": "BuidlGuidl" } ], "k...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--signatures-usdc-contract-permit
buidlguidl/smart-accounts-p256-precompile
Is there a precompile on Ethereum mainnet today for verifying secp256r1 (P-256, passkey) signatures? If yes, at what address? Answer yes or no, then give the address.
Check Ethereum mainnet's P-256 verification precompile and address.
[ "p256", "precompile", "eip-7951" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/smart-accounts-p256-precompile", "description": "Check Ethereum mainnet's P-256 verification precompile and address.", "authors": [ { "name": "BuidlGuidl" } ], "ke...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--smart-accounts-p256-precompile
buidlguidl/smart-accounts-userop-hash-v08
In ERC-4337 EntryPoint v0.8, how is a UserOperation's userOpHash computed? Answer in one sentence.
Check the EIP-712 UserOperation hash scheme used by EntryPoint v0.8.
[ "erc-4337", "entrypoint", "eip-712" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/smart-accounts-userop-hash-v08", "description": "Check the EIP-712 UserOperation hash scheme used by EntryPoint v0.8.", "authors": [ { "name": "BuidlGuidl" } ], "k...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/judge.toml", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--smart-accounts-userop-hash-v08
buidlguidl/swaps-permit2-zero-expiration
A user calls Permit2's approve(token, spender, amount, expiration) with expiration = 0. When does that allowance expire? Answer in one sentence.
Check Permit2's current-block meaning for an expiration of zero.
[ "permit2", "allowance", "expiration" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/swaps-permit2-zero-expiration", "description": "Check Permit2's current-block meaning for an expiration of zero.", "authors": [ { "name": "BuidlGuidl" } ], "keywor...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/judge.toml", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--swaps-permit2-zero-expiration
buidlguidl/upgrades-stateless-parent-gap
You are an expert security researcher and smart contract auditor. You are reviewing a V2 upgrade of a UUPS vault built on OpenZeppelin Contracts Upgradeable 4.9.6. ```solidity contract VaultV1 is Initializable, OwnableUpgradeable, UUPSUpgradeable { mapping(address => uint256) public balanceOf; // ... } contr...
Check whether adding OpenZeppelin MulticallUpgradeable 4.9.6 moves an existing balance mapping.
[ "ethereum", "security", "audits", "upgrades" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/upgrades-stateless-parent-gap", "description": "Check whether adding OpenZeppelin MulticallUpgradeable 4.9.6 moves an existing balance mapping.", "authors": [ { "name": "BuidlGu...
{ "pillar": "concepts", "area": "Audits", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--upgrades-stateless-parent-gap
buidlguidl/wallet-atomic-ready
Under EIP-5792, a wallet's wallet_getCapabilities reports the atomic capability for a chain. What is the difference between status "supported" and status "ready"? Answer in one sentence.
Check the distinction between supported and ready atomic wallet capabilities.
[ "wallet", "eip-5792", "atomic" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/wallet-atomic-ready", "description": "Check the distinction between supported and ready atomic wallet capabilities.", "authors": [ { "name": "BuidlGuidl" } ], "key...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/judge.toml", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--wallet-atomic-ready
buidlguidl/wallet-batch-status-600
Under EIP-5792, wallet_getCallsStatus returns status 600 for a batch of calls. What does that mean? Answer in one sentence.
Check the partial onchain revert meaning of EIP-5792 status 600.
[ "wallet", "eip-5792", "batch" ]
1.3
{ "schema_version": "1.3", "artifacts": [ "/logs/agent/trajectory.json" ], "task": { "name": "buidlguidl/wallet-batch-status-600", "description": "Check the partial onchain revert meaning of EIP-5792 status 600.", "authors": [ { "name": "BuidlGuidl" } ], "keywords": [...
{ "pillar": "concepts", "modes": [ "vanilla", "internet", "skills" ] }
[ "README.md", "environment/Dockerfile", "instruction.md", "solution/solve.sh", "task.toml", "tests/answer.py", "tests/hand-cases.json", "tests/judge.toml", "tests/reward.toml", "tests/test.sh" ]
tasks/concepts--wallet-batch-status-600

ETH Evals

ETH Evals measures how well AI agents do Ethereum work and what bare models know about Ethereum. Tasks cover knowledge questions, building apps and contracts, and acting on a chain.

Each task contains an instruction, an environment, checks, and a working solution. You can run these folders with Harbor, without installing ETH Evals.

What you need

Install uv and Docker with Compose. Start Docker, then install Harbor:

uv tool install --python 3.13 harbor==0.24.0

For a task with a chain, give Docker at least 7 GiB of memory.

Try a task without credentials

The agent registries task asks which ERC defines registries for AI agents. It needs no RPC URL or judge key.

Run its bundled solution:

harbor run --repo https://huggingface.co/datasets/buidlguidl/ethevals-test \
  --include-task-name concepts--agent-registries \
  --agent oracle \
  --n-concurrent 1

oracle applies the solution and runs the checks. It checks that the task works; it does not measure a real agent. A real agent needs a model API key or plan authentication.

Tasks that need a chain or an LLM judge

Some tasks need an RPC URL to fork a chain. Tasks with an LLM judge also need an API key for judging.

For example, the treasury ETH sale task asks an agent to write and run a quarterly sale script. It uses both a mainnet fork at block 26,260,992 and an LLM judge.

This example uses OpenCode through OpenRouter. Set these variables in your shell:

export MAINNET_RPC_URL='your-mainnet-rpc-url'
export ANTHROPIC_API_KEY='your-judge-api-key'
export OPENROUTER_API_KEY='your-agent-api-key'

The RPC provider must serve historical state at the pinned block. The Anthropic key pays for the judge, which checks the agent's work. The OpenRouter key pays for the agent's model calls.

Run the task:

harbor run --repo https://huggingface.co/datasets/buidlguidl/ethevals-test \
  --include-task-name act--treasury-eth-sale \
  --agent opencode \
  --model openrouter/moonshotai/kimi-k3.1-pro \
  --n-concurrent 1

This uses your credentials and can incur API charges. Harbor saves the results under jobs/. A trial passes when its reward is 1.

Choose your agent

Each example below runs the agent registries task, which needs no RPC URL or judge key. Choose one agent and set up its credentials.

A ChatGPT or Claude plan can pay for the agent. For the treasury task, keep the RPC URL and judge key from the earlier example. A plan cannot pay for the judge, which still needs ANTHROPIC_API_KEY.

Codex with a ChatGPT plan or OpenAI API key

With a ChatGPT plan

Install Codex, then sign in and run the task:

codex login
export CODEX_FORCE_AUTH_JSON=YES

harbor run --repo https://huggingface.co/datasets/buidlguidl/ethevals-test \
  --include-task-name concepts--agent-registries \
  --agent codex \
  --model openai/gpt-6-astra \
  --n-concurrent 1

Harbor reads ~/.codex/auth.json and copies it into the task's container. If Codex uses your OS credential store, sign in with codex -c 'cli_auth_credentials_store="file"' login first. If your login file lives elsewhere, run export CODEX_AUTH_JSON_PATH='/path/to/auth.json'. See Codex authentication for login and storage options.

With an OpenAI API key

Clear the plan settings, set your key, and run the task:

unset CODEX_FORCE_AUTH_JSON CODEX_AUTH_JSON_PATH
export OPENAI_API_KEY='your-agent-api-key'

harbor run --repo https://huggingface.co/datasets/buidlguidl/ethevals-test \
  --include-task-name concepts--agent-registries \
  --agent codex \
  --model openai/gpt-6-astra \
  --n-concurrent 1
Claude Code with a Claude plan or Anthropic API key

With a Claude plan

Install Claude Code, then create a token:

claude setup-token

Copy the returned token into CLAUDE_CODE_OAUTH_TOKEN, then run the task:

export CLAUDE_CODE_OAUTH_TOKEN='your-plan-token'
export CLAUDE_FORCE_OAUTH=YES

harbor run --repo https://huggingface.co/datasets/buidlguidl/ethevals-test \
  --include-task-name concepts--agent-registries \
  --agent claude-code \
  --model anthropic/claude-opus-5-5 \
  --n-concurrent 1

CLAUDE_FORCE_OAUTH tells Harbor to use the plan even when the judge's Anthropic key is present.

With an Anthropic API key

Clear the plan settings, set your key, and run the task:

unset CLAUDE_CODE_OAUTH_TOKEN CLAUDE_FORCE_OAUTH
export ANTHROPIC_API_KEY='your-api-key'

harbor run --repo https://huggingface.co/datasets/buidlguidl/ethevals-test \
  --include-task-name concepts--agent-registries \
  --agent claude-code \
  --model anthropic/claude-opus-5-5 \
  --n-concurrent 1

For a task with an LLM judge, the Anthropic key pays for both the agent and the judge.

OpenCode with OpenRouter

Set your OpenRouter key and run the task:

export OPENROUTER_API_KEY='your-agent-api-key'

harbor run --repo https://huggingface.co/datasets/buidlguidl/ethevals-test \
  --include-task-name concepts--agent-registries \
  --agent opencode \
  --model openrouter/moonshotai/kimi-k3.1-pro \
  --n-concurrent 1

The treasury example already uses this setup. Its Anthropic key pays for the judge separately.

Before running another task

Browse the task folders. Use the folder name with --include-task-name, such as concepts--agent-registries.

Read the task's README for its instruction and checks. Then check its configuration:

  • environment/docker-compose.yaml names any required RPC variables and the fork block.
  • [verifier.env] in task.toml names the judge key, if the task needs one.

For example, the treasury task declares its RPC requirement and judge key separately. Agent credentials are additional to these task requirements.

RPC variables from the exported folders

These names come from each task's Compose file. Compose stops with the message if a value is missing or empty.

  • buidlguidl/treasury-eth-sale: MAINNET_RPC_URL
  • buidlguidl/vault-v2-concentration-rebalance: MAINNET_RPC_URL
  • buidlguidl/vault-v2-market-exit: MAINNET_RPC_URL
  • buidlguidl/aave-savings-page: MAINNET_RPC_URL
  • buidlguidl/keeper-deposits: MAINNET_RPC_URL
  • buidlguidl/signed-votes: MAINNET_RPC_URL
  • buidlguidl/swap-page: MAINNET_RPC_URL

See the Harbor guide for more run options. To write a task, read Add a task.

Every task includes its solution, and those solutions can appear in training data. Scores alone do not establish unseen Ethereum knowledge.

Downloads last month
347