feat: surface F6 code-id freeze on dApp + indexer route/solve #585
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic#585
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Gate
P1 before #581 relies on live F6. Out of scope for #584 / !1108 (ops script + runbook) and #582 / !1107 (on-chain pin).
On-chain: pair write paths fail closed on
AssetCodeIdDrift/AssetCodeIdNotWhitelisted/AssetCodeIdGuardUnavailable. Queries (Simulation/HybridSimulation) stay ungated, so a frozen pair can still quote.MR: !1111 (
feat/585-f6-code-id-freeze).Problem
After factory 1.9.0 + pair 1.15.0 are live, a listed CW20 wasm migrate (or whitelist removal) freezes swaps / LP / limit place+fill / cancel / claim. Today:
route/solvecan still offer that pair.Internal audit F389-01 / F389-02. #584 explicitly deferred this.
Acceptance
ContractInfo.code_id≠ pin or is not factory-whitelisted, soroute/solvedoes not treat them as executable./trade,/charts,/pool) show a freeze state when known (indexer field or LCD), and copy that quotes can still appear while execute is blocked.make verify-issue-*for the new issue number.Out of scope
Columbus-5 migrate itself (#584). 8266 listing (#581). Wasm-admin-at-listing policy (C).
marked as related to #582
marked as related to #584
mentioned in issue #582
mentioned in issue #584
mentioned in merge request !1110
mentioned in issue #581
mentioned in merge request !1111
marked the checklist item Indexer: exclude or flag pairs whose live ContractInfo.code_id ≠ pin or is not factory-whitelisted, so route/solve does not treat them as executable. as completed
marked the checklist item dApp: humanize F6 execute errors on Swap / Trade / Pool (not a generic failed tx). as completed
marked the checklist item Pair surfaces
/trade, /charts, /poolshow a freeze state when knownindexer field or LCD, and copy that quotes can still appear while execute is blocked. as completedmarked the checklist item Tests / make verify-issue-* for the new issue number. as completed
marked the checklist item Does not un-gate on-chain exits or add FoT math (H-01). as completed
Implementation is on
feat/585-f6-code-id-freezeand ready for review in !1111.Acceptance criteria are all checked in the description.
make verify-issue-585passed 8/8 (first pass + retest): indexer freeze eval +code_id_frozen/route/solveexclude, 267 frontend tests (Swap/Trade/Pool/Charts/Limits + humanize), docs/skills F585-1–F585-8.This is visibility only. On-chain F6 write-path fail-closed is still #582/#584. Queries stay ungated, so a quote can still appear while execute is blocked. Does not un-gate cancel/claim/withdraw and does not add FoT math. Does not unblock #581 / 8266.
Playbook:
skills/AGENTS_FRONTEND_CODE_ID_FREEZE.md. Invariants:docs/frontend.md§ code-id freeze.mentioned in commit
048c2dd965mentioned in issue #594
mentioned in issue #595
mentioned in issue #597
mentioned in issue #633
mentioned in issue #634
mentioned in issue #660
mentioned in issue #685
mentioned in issue #690
mentioned in issue #717