Document wasm migration rollback limitations (SEC-H05) — #443 #975
No reviewers
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!975
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-443-wasm-migration-rollback-docs"
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?
Summary
Addresses GitLab #443 (SEC-H05): the wasm admin migration runbook had no operator guidance on what can or cannot be reversed after a CosmWasm upgrade.
docs/runbooks/wasm-admin-migration.mdcovering contract reversal via priorcode_id, irrecoverable cases (admin cleared, code purged, keys lost), indexer DB.down.sqlrollback underindexer/migrations/revert/, and partial fleet recovery steps.docs/runbooks/launch-checklist.mdrollback section,docs/testing.md, anddocs/contracts-security-audit.md.make check-wasm-migration-rollback-docs, acceptance scriptmake verify-issue-443, and agent skillskills/AGENTS_WASM_MIGRATION_ROLLBACK.md.Acceptance checklist
wasm-admin-migration.mdrollback section covers contract reversal and irrecoverable casesgrep -q 'Rollback and limitations' docs/runbooks/wasm-admin-migration.md && grep -q 'Irrecoverable cases' docs/runbooks/wasm-admin-migration.mdindexer/migrations/revert/down.sqlgrep -q 'indexer/migrations/revert/' docs/runbooks/wasm-admin-migration.mdlaunch-checklist.mdrollback section cross-links wasm migration limitationsgrep -q 'rollback-and-limitations-sec-h05' docs/runbooks/launch-checklist.mdmake check-wasm-migration-rollback-docsmake verify-issue-443make test-contracts(included in verify-issue-443)Verification checklist (third parties)
Manual review:
docs/runbooks/wasm-admin-migration.md→ Rollback and limitations (SEC-H05) — confirm reversal path, irrecoverable table, indexer down.sql, and partial migration steps read clearly for operators.docs/runbooks/launch-checklist.md→ Rollback / incident — confirm link to the new section.skills/AGENTS_WASM_MIGRATION_ROLLBACK.mdfor agent-oriented summary.No LocalTerra, Postgres, or frontend required for doc checks.
Security review — MR !975
Commit reviewed:
8c71c202ce8bad7148413b2893b87d3d3fc9a403(base0a75911012cf7b616eee2d12337102784392f393)Scope: Documentation and doc-drift tooling for SEC-H05 / #443 — operator rollback/limitations guidance in
docs/runbooks/wasm-admin-migration.md, cross-links in launch checklist / testing / contracts-security-audit, agent skillskills/AGENTS_WASM_MIGRATION_ROLLBACK.md, drift guardscripts/check_wasm_migration_rollback_docs.py, acceptance scriptscripts/qa/verify-issue-443.sh, Makefile targets, and a comment-only link update insmartcontracts/tests/src/migration_tests.rs.Method: Full MR diff reviewed. Prior MR security threads: none. Each candidate class (injection, authn/authz, secret leakage, SSRF/XSS, unsafe deserialization, supply chain) traced for attacker-controlled input reaching a runtime sink — none present in this diff.
Outcome:
FINDINGS: 0medium+Security review: no medium+ findings on this diff.
Inline threads: none (no findings to anchor).
Notes (informational, below reporting threshold):
check_wasm_migration_rollback_docs.pyreads fixed repo paths with hardcoded markers — no external/user input, no shell invocation.verify-issue-443.shdelegates tomake check-wasm-migration-rollback-docsandmake test-contractswith fixed paths; no attacker-controlled parameters.terrad query wasm migrateto priorcode_id, indexer manual.down.sql, partial-fleet pause) documents existing operational controls; it does not weaken on-chain admin gates or expose credentials.added 3 commits
main5058c61b- Merge branch 'main' into issue-443-wasm-migration-rollback-docsCompare with previous version
Resolved merge conflicts with
main(Makefile only).Merged
origin/mainintoissue-443-wasm-migration-rollback-docsand kept both sides' Makefile targets:check-wasm-migration-rollback-docs,verify-issue-443check-test-evidence-gate-docs,verify-issue-444Updated
.PHONY,lint,help, and verify targets accordingly.make check-wasm-migration-rollback-docsandmake verify-issue-443pass locally.mentioned in commit
c0bd454668Security review — MR !975
Commit reviewed:
5058c61b9595a1381fdd408b7a4b60efbd2c7a20(base71ae2d02b1298844583ad2cde927cb1326812aff)Scope: SEC-H05 / #443 — operator rollback/limitations documentation in
docs/runbooks/wasm-admin-migration.md, cross-links inlaunch-checklist.md,docs/testing.md, anddocs/contracts-security-audit.md, agent skillskills/AGENTS_WASM_MIGRATION_ROLLBACK.md, drift guardscripts/check_wasm_migration_rollback_docs.py, acceptance scriptscripts/qa/verify-issue-443.sh, Makefile targets, and a comment-only link update insmartcontracts/tests/src/migration_tests.rs.Method: Full MR diff reviewed (9 files). Prior MR security thread (2026-06-30,
8c71c202) reported zero medium+ findings; re-validated on current head including merge resolution. Traced injection, authn/authz, secret leakage, SSRF/XSS, unsafe deserialization, and supply-chain classes for attacker-controlled input reaching a runtime sink — none present in this diff.Outcome:
FINDINGS: 0medium+Security review: no medium+ findings on this diff.
Inline threads: none (no findings to anchor).
Notes (informational, below reporting threshold):
check_wasm_migration_rollback_docs.pyreads fixed repo paths with hardcoded markers — no external/user input, no shell invocation.verify-issue-443.shdelegates tomake check-wasm-migration-rollback-docsandmake test-contractswith fixed paths; no attacker-controlled parameters.code_idwith intact admin, manual indexer.down.sql, partial-fleet pause) documents existing operational controls; it does not weaken on-chain admin gates or expose credentials.mentioned in issue #443
mentioned in issue #445