docs+feat: protocol fee model, workflow migration guide, compliance tier docs, jurisdiction metadata - #508
Merged
misrasamuelisiguzor-oss merged 2 commits intoAug 29, 2026
Conversation
…ier docs, jurisdiction metadata - docs(treasury): document settlement fee-free-by-design decision and rationale (WHEELBACK#449) - docs(settlement-workflow): document redeploy/migration cutover sequence via set_signer/remove_signer (WHEELBACK#450) - docs(compliance): document existing allow_address_with_tier/get_address_tier semantics, which were already implemented but undocumented (WHEELBACK#451) - feat(compliance): add set_jurisdiction/get_jurisdiction metadata entrypoints (WHEELBACK#452) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
@luka-berry Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #449
closes #450
closes #451
closes #452
docs/economic-parameters.md+ARCHITECTURE.mdpointer: documents thatTreasury::execute_settlementis intentionally fee-free by design, with rationale and the conditions under which it should be revisited (plus a non-implemented sketch of a future fee shape, per the issue's scope).docs/upgrade-guide.md: documents the settlement-workflow redeploy/migration cutover sequence (deploy new instance → initialize → register as treasury signer viaset_signer→ verify → redirect traffic →remove_signeron the old instance), ordered specifically to avoid a window with no working compliance-gated settlement entry point. Depended on the settlement-workflow pinned-config work in feat(contracts): settlement-workflow pin config, emit event, add batc… #482, which has already landed onmain.contracts/compliance/src/lib.rsper the issue's own instruction first:allow_address_with_tier/get_address_tier/DataKey::Tieralready exist and are fully implemented, just undocumented. Scoped down to documentation: added a "Compliance tiers" section tocontracts/compliance/README.mdand the missing entrypoint rows/DataKey row to the README andARCHITECTURE.md.DataKey::Jurisdiction(Address),set_jurisdiction(admin-gated,ContractPaused-aware, like the other setters) andget_jurisdiction(returnsOption<Symbol>, defaults toNonefor addresses tracked before this field existed — no migration needed) tocontracts/compliance/src/lib.rs, plus README/ARCHITECTURE.mddocumentation. Pure metadata, does not affectis_allowed.Test plan
cargo test --allcargo clippy -- -D warningscargo fmt --all -- --check