AntFleet

Disagreement · f3aba81f-anthropic-4

Chain fallback marker is set in log but not propagated into state or notification context

solo Opus
repo 6f7fc663·PR #23·reviewed 1 week ago

Opus finding

Chain fallback marker is set in log but not propagated into state or notification context

lowapi-contractmedium
  • skills/price-threshold-alert/SKILL.md:110-115
If the configured chain has no pool, the skill prices the token off some *other* chain's pool. ATH and target evaluations then operate on a price from a different market, which can corrupt the ATH baseline. The doc only mentions a log marker; it does not exclude this fallback price from ATH/target evaluation or warn the operator that the canonical chain is unavailable.

Recommendation

When falling back to a non-configured chain, either skip ATH/target writes for that run, or notify with a `PRICE_ALERT_CHAIN_FALLBACK` status. At minimum, persist the fallback flag in state so subsequent runs do not treat the cross-chain price as authoritative.

Other reviewer

The other reviewer flagged nothing in this file/line range.

Why this didn't post

This finding didn't meet AntFleet's unanimous agreement threshold. Both frontier models review every PR independently; only findings they both flag with the same severity and category are posted to the PR. This one fell through.

read the methodology →