Skip to content

Refinement of M3 in traffic-based app rewards grant #479

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
isegall-da wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Refinement of M3 in traffic-based app rewards grant #479

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion proposals/2026-02-DA-Traffic-Based-App-Rewards.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,8 @@ Deliverables:
- SV app UI: support for new configuration parameters.
- Wallet app: `RewardCouponV2` and `MintCoupon` lookup for reward minting.
- Dry-run mode deployed and validated on MainNet, confirming deterministic reward computation across SV nodes.
- Minimum two-week delay between deploying Dry-run mode on MainNet and enabling actual traffic-based rewards on DevNet. This means that explorers and app builders will be able to see what results would be generated via traffic-based application rewards, and compare them to existing marker-based rewards. Doing this two weeks before enforcing traffic-based app rewards on DevNet means that this computation will be available four weeks before the new rewards logic gets enforced on MainNet.
- Minimum four-week delay between the time that activity records are made public via the Scan app on MainNet, and the time that traffic-based app rewards start being enforced. This means that explorers and app builders will be able to see what results would be generated via traffic-based application rewards, and compare them to existing marker-based rewards, during this review period, before traffic-based app rewards go fully live.


- Governance vote to switch from featured app markers to traffic-based app rewards.
- Monitoring: metrics and alerting for trigger health and hidden reward coupon counts.
Expand Down
Loading