feat: Implement DAO-Governed Protocol Fee Parameterization - #161
Merged
elizabetheonoja-art merged 2 commits intoApr 23, 2026
Merged
Conversation
|
@BarryArinze 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! 🚀 |
elizabetheonoja-art
merged commit Apr 23, 2026
5104ebc
into
SubStream-Protocol:main
2 of 5 checks passed
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
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.
🧩 Overview
This PR replaces the hardcoded protocol fee with a DAO-governed configurable fee model.
The protocol fee can now be updated through an authorized DAO multi-sig via
update_protocol_fee, enabling governance-driven adjustments over time while preserving merchant protections through hard caps and timelocked fee increases.⚙️ Key Features
protocol_fee_bpsupdate_protocol_fee(new_fee_bps)restricted to DAO multi-sig📢 Events Added
ProtocolFeeUpdateScheduled(old_fee_bps, new_fee_bps, activate_at)ProtocolFeeUpdateExecuted(old_fee_bps, new_fee_bps)🏗️ Implementation Details
Fee Update Logic
If
new_fee_bps <= current_fee_bpsIf
new_fee_bps > current_fee_bpsPull Settlement Logic
For each subscription pull:
Example
For a pull of 100 XLM equivalent:
If updated to 300 bps:
🔐 Security Considerations
🧪 Testing
Added tests for:
✅ Acceptance Criteria Covered
Acceptance 1
DAO can successfully adjust protocol fee model over time.
Acceptance 2
Caps + timelocks protect merchants from extortionate hikes.
Acceptance 3
Settlement math routes funds precisely without leftover dust.
🚀 Impact
🔗 Related Issue
Closes #116
🏷️ Labels
governance, economics, math