Case · DiggingBeagle record

CONSTRAINTDIAL mutates smart contract tasks to detect copied exploit solutions

A smart-contract security benchmark paper constructs 3,045 tasks from 203 cases and changes exploit-relevant conditions while preserving the underlying vulnerability. It measures copied-answer resistance, not complete elimination of training contamination.

Scope

The procedure requires that mutations preserve semantics correctly; the paper evaluation does not guarantee every produced task is uncontaminated or that real auditors will perform similarly.

Assessment profile

Assessment method
Setting
evaluation
Exploitation
demonstrated
Evidence
Grade B
Remediation
not applicable
AI role
AGAINST AI
Basis and provenance

Enrich update: CLM-ENRICH-20261027-09 cites SRC-2026-CP21-CONSTRAINTDIAL-CONTRACT-BENCH-DRIFT at Abstract, public-answer reuse and online copying metrics. New evidence concerns the bounded reported mechanism, prerequisite or outcome; setting evaluation; exploit status demonstrated; remediation status not_applicable. No independently comparable impact scale, affected production population or universal exploit success measure was established, so the impact band remains null. Original Claims remain individually attributable and any observed incident or simulated result is distinguished in the narrative.

Assessed Oct 27, 2026 using diggingbeagle.assessment/1.

At a glance

Timeline

  1. Oct 23, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-ENRICH-20261027-09CONSTRAINTDIAL reports reducing acceptance of copied online smart-contract answers by 9.3 percentage points in addition to the 10.9-point average reduction in successful reuse of published answers.supported

Basis: reported finding

Link to claim
CLM-CP21-CONSTRAINTDIAL-CONTRACT-BENCH-DRIFT-1The paper describes reconstruction plus execution-verified protocol mutations producing 3,045 detection, exploitation and patching tasks from 203 public smart-contract incidents, and reports a 10.9-point mean decrease in success using public reference answers.supported

Basis: reported finding

Link to claim

Implications

A public exploit trace should not be a complete answer key to a supposedly novel security-assessment task.

Controls and mitigations

  • Retest agents on unseen, execution-verified variations and independently audit the mutation invariants before accepting a new benchmark score as evidence of original security reasoning.

Unknowns and contradictions

  • The procedure requires that mutations preserve semantics correctly; the paper evaluation does not guarantee every produced task is uncontaminated or that real auditors will perform similarly.

Sources and citation

Material revision history

  1. Oct 27, 2026 · Canonical change recorded · new in release · revision 196