Unexpected fields do not silently alter transaction semantics
unexpected-fields-rejected
Description
Fields that are not part of the proposal schema (such as an "approved" flag or a limit override) are rejected, so they cannot be mistaken for authorisation.
adversarial-input · required · ../../packages/cli/templates/scenarios/adversarial-input/unexpected-fields-rejected.yaml
Outcomes across stored runs
- Pass 3
- Fail 1
- Error 0
- Skipped 0
Execution history
- run_317318f32026-11-06 20:03 UTCFail
- run_b271aaff2026-11-06 20:03 UTCPass
- run_28b022e22026-11-06 20:03 UTCPass
- run_34e4198a2026-11-06 20:03 UTCPass
| Run | Started | Outcome |
|---|---|---|
| run_317318f3 | 2026-11-06 20:03 UTC | Fail |
| run_b271aaff | 2026-11-06 20:03 UTC | Pass |
| run_28b022e2 | 2026-11-06 20:03 UTC | Pass |
| run_34e4198a | 2026-11-06 20:03 UTC | Pass |
Most recent steps
- #1proposefailedexpected BLOCK, observed ALLOWExpected
{ "decision": "BLOCK", "reason_codes": [ "PROPOSAL_UNKNOWN_FIELD" ], "reason_codes_exact": false, "absent_reason_codes": [] }Observed{ "decision": "ALLOW" }