Update cip-0077.md#207
Open
ClementineDrouot wants to merge 1 commit into
Open
Conversation
Signed-off-by: ClementineDrouot <clementine.drouot@taurushq.com>
Contributor
|
@hythloda This one will need to go to the Accountability Committee. |
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.
PR: CIP-0077 Adoption Bonus timing / milestone recognition
This Pull Request (PR) proposes an adjustment to the Adoption Bonus timing/milestone recognition criteria under CIP-0077 to better reflect the realities of Tier-1 financial institution onboarding and Canton ecosystem dependencies.
Background
Taurus has multiple confirmed G-SIB / Tier-1 institutional projects progressing toward issuance/tokenization on Canton. These projects are active, resourced, and in execution phases, but their delivery timelines extend beyond the current May 10th 2026 Adoption Bonus deadline.
The delays are not linked to lack of adoption or execution from Taurus, but to structural institutional and ecosystem dependencies encountered during implementation.
Rationale for our ask
These dependencies materially impacted timelines and are typical of Tier-1 / G-SIB production deployments.
Proposed adjustment
We propose: