Shared CW20 containment, delayed wallet protections and reserved recovery #14
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/cw20-mintable!14
Loading…
Reference in a new issue
No description provided.
Delete branch "bb/cw20-security-contracts-controller-wallet-limits-thr_n4vtxxfcb7"
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?
Shared CosmWasm containment controller plus CW20v0.2.0 wallet policy and reserved recovery. One shared pause is authoritative for every migrated/enrolled token; guarded ordinary economic paths fail closed. Defaults:10% protected opening-balance rolling24h cap; weakening>=old24h delay; opt-in lock unlock>=48h. Exact recovery reserves source funds and requires >=30d, destination acceptance, separate governance authorization/recovery execution/independent dispute. See docs/token-security-v1.md and generated schemas.
Independent controller source approval3333807: #4 (comment) . Independent token source/schema approval2d70d43: #7 (comment) .91 tests pass; strict workspace clippy and reproducible schemas; Rust1.81 build, pinned optimizer, repeat identical hashes and matching cosmwasm-check1.5.11 pass. Exact artifact/inventory/custody receipts: docs/rollout/. Later CI/docs changes do not alter approved token/controller trees. Required Woodpecker checks are real (CI bootstrapPR15 merged), latest exact-head pipeline must pass before merge.
This branch intentionally preserves inherited stale-minter removal prerequisitecc9a3b1/local8a50c36 absent from original Forgejo main2f8438b. Independent token reviewer examined this prerequisite against the actual Forgejo base. Current main CI+research integrated without losing that fix.
No live deployment/migration or fleet coverage is claimed:35 current code10184 instances remain legacy/uncovered. Registered historical governance2-of-3 multisig identity is on-chain verified, but an unlocked authorized quorum/passphrase and independently verified separate-role custody are unavailable. Several governance/minter overlaps need actual separation before migration. Protocol assignments, DEX whitelist/code-pin coordination and live receipts remain open acceptance for issues#4–#7. No automatic closing keywords.
WIP: Shared CW20 containment, delayed wallet protections and reserved recoveryto Shared CW20 containment, delayed wallet protections and reserved recoveryCoordinator final integration review at exact head
8dc22d98855ba6bc297342cd90046515c99dec75, baseb041c17d852cb92035d939eddd617bdec5ab6de2: approved token tree2d70d43and controller tree3333807remain unchanged; later delta is reviewed CI/docs/provenance/build tooling. Independent token review: issue7 comment65389; independent controller review: issue4 comment65368. Coordinator independently ran 14 focused controller tests (all pass), reviewed final script/docs and verified both local optimized artifact hashes plus Cargo.lock/schema hashes against provenance. Required real CI pipeline8 is successful: https://ci.cl8y.com/repos/26/pipeline/8/1 . Worker actual-Wasm smoke evidence is linked at issue7 comment65426 with explicit host/scope limits. Inherited minter-fix prerequisite is included in source scope. This approves SOURCE INTEGRATION only: no live contract deployment/migration, no unlocked governance quorum, no verified separate role custody, no completed DEX pin/assignment transition; coverage remains0/35. Issues4–7 and epic3 remain open; draft artifact candidate is not a production release.