Asset precision errors are rejected: expected BLOCK, observed ALLOW
2026-11-06 20:03 UTC · finding run_317318f3c81340818dff3adc20583c89:asset-precision-exceeded
Problem
USDC has 6 decimals; an amount with 7 significant decimals must be rejected, not rounded.
Observed behaviour was more permissive than expected; severity is the scenario's declared risk (high).
Remediation
Reject amounts with more precision than the asset supports instead of rounding or truncating them.
Expected behaviour
{"decision":"BLOCK","reason_codes":["AMOUNT_PRECISION_EXCEEDED"],"reason_codes_exact":false,"absent_reason_codes":[]}Observed behaviour
{"decision":"ALLOW"}Reproduce
drainproof test --scenario asset-precision-exceededScenario file: ../../packages/cli/templates/scenarios/network-asset/asset-precision-exceeded.yaml (step 1 of 2: propose)
Evidence: ../../packages/cli/templates/scenarios/network-asset/asset-precision-exceeded.yaml, step 1 · definition sha256:6717b4373e89… · policy sha256:8a1b22fbb25b…
Scenario steps
- #1proposefailedexpected BLOCK, observed ALLOWExpected
{ "decision": "BLOCK", "reason_codes": [ "AMOUNT_PRECISION_EXCEEDED" ], "reason_codes_exact": false, "absent_reason_codes": [] }Observed{ "decision": "ALLOW" }