feat(community-tax): autoregister factory pairs + manager tax skip (#633) #1137
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!1137
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-633-autoregister-manager-skip"
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
config.manageras a buy/sell/transfer tax skip without a paidMANAGER_EXEMPTrow (launch guards stay on).CreatePairreply and AutoLP pair bind executeregister_listed_pairon community-tax assets only (cw2-gated on the factory). Official dApp/createfollows up for the tax pin; Manage shows one highest-LP catch-up button.skills/AGENTS_COMMUNITY_TAX_AUTOREGISTER.md, crosslinked from #609 / #610 / #593 / #626 playbooks.Closes #633
Test plan
make verify-issue-633(crates + Vitest + docs, twice)make verify-issue-609make verify-issue-610CreatePairautoregisters without the dApp follow-upmentioned in commit
bb0194082cmentioned in issue #635
mentioned in issue #633
mentioned in issue #634