docs: extend CW20 whitelist policy to rebase/elastic-supply tokens (#448) #985
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!985
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "qa/448-token-whitelist-rebase-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?
The fee-on-transfer prohibition (#377) was documented, but rebase / elastic-
supply / reflection tokens — whose balance changes after receipt with no
transfer — were not named, and there was no explicit audit-evidence requirement
(SEC-I01 H05). Both mechanics desync the pair reserves and limit-order escrow
the same way, since accounting credits declared amounts, not balance deltas.
covering both fee-on-transfer and rebase/elastic-supply, and require source
review + recorded audit evidence before AddWhitelistedCodeId (not checksum
match alone).
the table, add a source-review step (no balance mutation outside an explicit
transfer) and an attach-audit-evidence step to pre-whitelist verification.
Docs-only; the optional balance-delta runtime assertion stays tracked on #448 as
a separate code change.
assigned to @Brouie
Security review
Commit reviewed:
1a8ab01706a9dd2966a1f837407cc496710dfdfcScope: Docs-only MR — extends CW20 whitelist operational policy in
docs/runbooks/cw20-whitelist-policy.mdanddocs/security-model.mdto cover rebase / elastic-supply / reflection tokens alongside fee-on-transfer, and adds pre-whitelist source-review + audit-evidence requirements (GitLab #448, SEC-I01 H05). No smart-contract, indexer, or frontend code changes.Outcome:
FINDINGS: 0medium+Security review: no medium+ findings on this diff.
Summary: Reviewed the full MR diff and traced attacker-controlled inputs to sinks. Changes are documentation and governance-process guidance only; runtime controls are unchanged (
AddWhitelistedCodeIdremains governance-only; pairRESERVES/PENDING_ESCROWstill credit declared CW20 amounts, not balance deltas — invariant P2). The added rebase/elastic-supply prohibition accurately reflects the same reserve-desync class already demonstrated for fee-on-transfer inadversarial_token::fee_on_transfer_creates_reserve_imbalance. New steps (source review, attach audit evidence, do not whitelist on checksum alone) strengthen ops controls rather than introducing injection, authz bypass, secret leakage, or other exploitable paths.Inline threads: None (no medium+ findings to anchor).
mentioned in issue #448
mentioned in commit
658aeae727