samscrack commited on
Commit
54bfe19
·
verified ·
1 Parent(s): 3b47060

docs: add Qwopus 3.6 27B Solidity baseline (46.5%) + clarify pass@1 metric semantics

Browse files
Files changed (1) hide show
  1. README.md +8 -3
README.md CHANGED
@@ -33,9 +33,14 @@ This dataset is intended for use with the [hermes-agent](https://github.com/Nous
33
 
34
  ## Reference baseline
35
 
36
- | Agent | Split | Pass rate | Notes |
37
- | --- | --- | --- | --- |
38
- | Claude Code 2.1.128 (Claude Opus 4.7) | `lite` | **39.0%** (78/200, 1 timeout) | 16-way concurrency, 40 max-turns, default fuzz settings (`fuzz_timeout_s=300`, `fuzz_test_calls=50000`, `fuzz_seed=0xDEADBEEF`). Reference sandbox image extended with Claude Code per the Dockerfile snippet above. Wall-clock ~34 min on a 32-core host. Run via `hermes-agent`'s `solidity_eval` environment with `agent_backend: claude-code`, `terminal_backend: docker`. |
 
 
 
 
 
39
 
40
  A non-trivial fraction of failures on `lite` come from B3 canary false-positives where the deleted function legitimately requires common Solidity primitives (`keccak256`, `encodePacked`, addresses unsorted via `sortTokens`, etc.). The ground-truth canary list is generated by token-overlap with the deleted function body and was not pruned for these false-positives in the v0 build; this is the dominant source of noise on the `lite` baseline. Filter to rows where the canary set excludes those tokens if you want a less-noisy slice.
41
 
 
33
 
34
  ## Reference baseline
35
 
36
+ All scores are **pass@1** under SolBench's `echidna()` rule: per task, a single agentic attempt is scored as 1.0 only if Diffusc compiles the candidate AND Echidna's differential-fuzz finds no behavioral divergence vs. the ground-truth body (or the harness vacuously passes), AND the B3 canary check + stub-residue guard both pass. Slither runs but is recorded as a side metric only — this is **not** Vul@k. No resampling (`group_size=1`).
37
+
38
+ | Agent / model | Split | pass@1 | Wall-clock | Notes |
39
+ | --- | --- | --- | --- | --- |
40
+ | **Qwopus 3.6 27B Solidity (stage4-rft)** | `lite` | **46.5%** (93/200) | ~27 min | Local serve via vLLM TP=2 FP8 (qwen3_xml tool parser) on 2× Blackwell GPUs. Hermes agent loop (in-process tool dispatch). Same fuzz settings + sandbox image as below. |
41
+ | Claude Code 2.1.128 (Claude Opus 4.7) | `lite` | 39.0% (78/200, 1 timeout) | ~34 min | Anthropic API via Claude Code CLI inside the sandbox. CLI agent backend. |
42
+
43
+ **Identical conditions across both rows:** lite split (200 tasks), 16-way concurrency, `max_agent_turns=40`, `max_token_length=32000`, `agent_temperature=0.6`, `fuzz_timeout_s=300`, `fuzz_test_calls=50000`, `fuzz_seed=0xDEADBEEF`, reference sandbox image (`samscrack/solidity-eval-sandbox:dev` extended with the symlink fix below — Claude Code row also adds the Claude Code CLI to the image), `terminal_backend=docker` on the same 32-core host. Run via `hermes-agent`'s `solidity_eval` environment.
44
 
45
  A non-trivial fraction of failures on `lite` come from B3 canary false-positives where the deleted function legitimately requires common Solidity primitives (`keccak256`, `encodePacked`, addresses unsorted via `sortTokens`, etc.). The ground-truth canary list is generated by token-overlap with the deleted function body and was not pruned for these false-positives in the v0 build; this is the dominant source of noise on the `lite` baseline. Filter to rows where the canary set excludes those tokens if you want a less-noisy slice.
46