File size: 6,313 Bytes
edbc049
 
 
 
3e0176f
 
 
 
 
 
 
 
edbc049
 
 
 
 
 
3e0176f
 
edbc049
 
 
 
 
3e0176f
 
 
 
 
edbc049
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3e0176f
 
 
 
 
 
 
 
 
 
 
 
edbc049
3e0176f
edbc049
3e0176f
 
 
 
 
edbc049
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3e0176f
edbc049
 
 
3e0176f
edbc049
3e0176f
 
edbc049
 
3e0176f
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
edbc049
3e0176f
edbc049
3e0176f
edbc049
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
---
license: mit
language:
- en
language_creators:
- expert-generated
annotations_creators:
- expert-generated
multilinguality:
- monolingual
source_datasets:
- original
pretty_name: EVM-QuestBench
task_categories:
- text-generation
tags:
- benchmark
- code-generation
- transaction-code-generation
- execution-grounded-evaluation
- blockchain
- evm
- ethereum
- bsc
- smart-contracts
- defi
- llm
- llm-agents
- agent-evaluation
- acl-2026
size_categories:
- n<1K
arxiv: "2601.06565"
doi: "10.18653/v1/2026.acl-long.1642"
configs:
- config_name: default
  data_files:
  - split: atomic
    path: data/atomic.jsonl
  - split: composite
    path: data/composite.jsonl
---

# 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

```python
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`, and `difficulty`
- `description` and `natural_language_templates`
- `chain`, `network`, `tags`, and `parameter_names`
- JSON-serialized `parameters`, `validation`, `composite_structure`, `interaction_config`, `scoring_strategy`, and `metadata`
- `source_path` and the complete JSON-serialized `raw_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](https://github.com/OpenEdgeHQ/EVM-quest-bench). 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

```bibtex
@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.