Refinement of M3 in traffic-based app rewards grant#479
Draft
isegall-da wants to merge 1 commit into
Draft
Conversation
As we are preparing the roll-out plan for this feature, we realized that the precise language used in the original milestone dictates some limitations that would delay roll out unnecessarily. Since the data has been made available on Scan on an earlier release than the full implementation, we can still allow the desired 4 week review period and enable the feature one week earlier. This amendment proposes the corresponding change in the milestone text for full transparency and pre-approval by the committee. Signed-off-by: Itai Segall <itai.segall@digitalasset.com>
This comment was marked as resolved.
This comment was marked as resolved.
|
@isegall-da, thank you for your interest in the Canton Development Fund! Your proposal does not include a Champion/Endorser field. Per CIP-0100, all external proposals require a Tech & Ops Committee champion. Next steps:
If you need help finding a champion, reach out to SIGs or any Tech & Ops Committee member. This PR is being closed automatically. You are welcome to reopen it once a champion is confirmed. |
github-project-automation
Bot
moved this from Incoming
to Declined
in Dev Fund Incoming
meiersi-da
approved these changes
Jun 19, 2026
meiersi-da
left a comment
meiersi-da
left a comment
Contributor
There was a problem hiding this comment.
Thx. This matches what's written in CIP-104: https://github.com/canton-foundation/cips/blob/main/cip-0104/cip-0104.md#incremental-roll-out
The minimal delay between Increment 2 (Scan observability) and Increment 4 (MainNet release) landing on MainNet must be at least 30 days.
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
4 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.
Development Fund Proposal Submission
Proposal file:
/proposals/2026-02-DA-Traffic-Based-App-Rewards.md
Summary
As we are preparing the roll-out plan for this feature, we realized that the precise language used in the original milestone dictates some limitations that would delay roll out unnecessarily. Since the data has been made available on Scan on an earlier release than the full implementation, we can still allow the desired 4 week review period and enable the feature one week earlier. This amendment proposes the corresponding change in the AC text of the milestone for full transparency and pre-approval by the committee.
Checklist
/proposals/Notes for Reviewers
None