Skip to content

Update cip-0077.md #207

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

Open
ClementineDrouot wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update cip-0077.md #207

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4e11777
Update cip-0077.md
ClementineDrouot May 12, 2026
1ab11f9
Update cip-0077.md
ClementineDrouot May 28, 2026
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
7 changes: 6 additions & 1 deletion cip-0077/cip-0077.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@
| ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | -------------------------------------------------------------------------------------- |
| **CUSTODY** <br> Integration w/ Taurus-EXPLORER <br> + Integration w/ Taurus-PROTECT | Custody (including nodes & indexing) support of Canton Network Token Standard | +180 days from CIP approval | 1 |
| **Acceleration Bonus** | For Custody <br> <br> +0 Bonus if delivered +180 Days from SV CIP Approval <br> <br> +2 Bonus if delivered +60 Days from SV CIP Approval <br> <br> Linear sliding scale between +60 and +180 days <br> <br> Example: If delivered in +120 days, Taurus is awarded +1 SV Weight <br> <br> • At least one Taurus customer must be live, having completed a transaction on MainNet | +180 days from CIP approval | 2 |
| **Adoption Bonus** | Category 1 <br> • Per $1.5b of assets transferred <br> <br> Category 2 <br> • For each approved participant (by the Tokenomics Committee), using Taurus to issue an asset >$1M TVL on Canton | +180 days from custody support going live | • 0.5 per live deployment under Category 1 or Category 2 <br> • Max up to 2 in total |
| **Adoption Bonus** | Category 1 <br> • Per $1.5b of assets transferred <br> <br> Category 2 <br> • For each approved participant (by the Tokenomics Committee), using Taurus to issue an asset >$4M TVL on Canton | December 31st, 2026 | • 0.5 per live deployment under Category 1 or Category 2 <br> • Max up to 2 in total • 12 month revision /sustained TVL |

## Milestone Mechanics

Expand All @@ -63,6 +63,11 @@
* The Tokenomics Working Group will make a recommendation to the SVs on what to do with the Unclaimed Rewards
* Applicant is subject to CIP-0045 : SV Operating Requirements
* If, at any time, the Applicant has been rewarded SV Weight > 2.5, they are required to operate their SV within 6 months of crossing that Weight. This SV node will join the network with an SV weight of zero (0) and may add weights as the SV completes the milestones listed in this CIP.

* Notes on the Adoption Bonus: 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.


## Copyright

Expand Down