Update cip-0077.md#207
Open
ClementineDrouot wants to merge 2 commits into
Open
Conversation
Signed-off-by: ClementineDrouot <clementine.drouot@taurushq.com>
ClementineDrouot
requested review from
hythloda,
isegall-da,
stas-sbi,
tkatrichenko and
waynecollier-da
Contributor
|
@hythloda This one will need to go to the Accountability Committee. |
Contributor
|
Taurus came to accountability on March 10, 2026 and April 28, 2026. Next step is Tokenomics. |
PR: CIP-0077 Adoption Bonus timing / milestone recognition https://github.com/canton-foundation/cips/blob/main/cip-0077/cip-0077.md 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 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 · Some banking clients will need to onboard Canton as a 3rd party. At least one of our large clients needs to go through TPRM (Third-party risk management with Canton) to onboard the Canton Registry App – which is needed to register their tokenised instrument. · New technical recommendation released 4 months after Taurus delivery. Recommended Wallet features to support interacting and trading with Tokenized Assets – released in March 2026 with recommended implementation timeline until May 21st ie. post our own adoption deadline. · CIP-103 implemented by Taurus (CIP-56 insufficient for some client use cases). · Issuance client identified missing important features in Canton Utilities package (clawback & freeze of an asset) creating internal approval workflows and delay. These dependencies materially impacted timelines and are typical of Tier-1 / G-SIB production deployments. In parallel, Taurus has made significant long-term investments into the Canton ecosystem and currently maintains one of the deepest technical integrations (token, nodes, issuance, CIP-56, CIP-103, wallet gateway), facilitating institutional adoption of Canton beyond simple issuance volumes. Proposed adjustment We propose: · extending the Adoption Bonus deadline to December 31st 2026; · increasing the TVL threshold under Category 2 from $1M to $4M per client to further support meaningful Canton adoption; · maintaining the current bonus weight structure (+0.5 weight per live deployment under Category 1 or Category 2, max total of 2). In addition, to better align incentives with long-term ecosystem participation and retention rather than short-term issuance activity only, we propose linking the retained bonus weight to sustained TVL and ecosystem engagement. Under this approach: · Bonus weight would be granted upon successful production deployment / issuance on Canton (min. TVL of $4M on Canton) and granted for a 12-month period following issuance; · If, following this 12-month period, the corresponding client fully redeems / burns the issued assets, the associated bonus weight would be removed, except in cases where such offboarding is primarily driven by Canton-related compliance, security, or ecosystem complexity considerations outside Taurus’ control. We believe this approach better aligns incentives with the long-term growth, retention, and operational maturity of the Canton ecosystem. Signed-off-by: ClementineDrouot <clementine.drouot@taurushq.com>
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
3 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.
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: