docs: Align fee tier examples between deployment-guide and architecture #68
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#68
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?
Type
missing-implementation (documentation consistency)
Evidence
docs/deployment-guide.md§5a vsdocs/architecture.mdtier table — numeric/discount driftAcceptance criteria
Epic
#57
marked this issue as related to #57
Single authoritative tier reference is
docs/reference/fee-discount-tiers.md(correctadd_tierJSON withmin_cl8y_balanceandgovernance_only). Architecture now summarizes and links there; deployment guide §5a defers to it. Integration tests usesmartcontracts/tests/src/tier_fixtures.rs(STANDARD_PRODUCTION_TIERS) with updated fee assertions for tier 1/4 and router discount path. @brouie Please confirm tier numbers match intended mainnet economics.@PlasticDigits Verified on current main. Acceptance criteria:
Single source of truth established, no more drift between architecture and deployment guide. Closing.
mentioned in issue #100
mentioned in issue #198
mentioned in issue #641