CIP-0085: Add Talos as Weight 6.5 SV

CIP-0085

Abstract

This CIP preserves Coin Metrics’ existing Weight 1.0 Super Validator under CIP-0046 and adds an escrowed, outcome-linked maximum earnable Weight of +6.5 for Talos. The incremental weight mints only upon Accountability Subcommittee verification of adoption milestones across:

• Canton Coin (CC) trading/custody readiness via Talos
• pX integration to Canton
• Measured production usage through defined trading and settlement volumes

Motivation

The proposal ties incremental SV rewards to real usage and service quality — readiness, live flows, and operational performance — consistent with community precedent. The objective is to broaden CC access through Talos integrations, demonstrate private institutional settlement on Canton (pX), and reward verifiable adoption with outcome-based tranches.

Rewards are broken down into two key initiatives:

• Establish Talos platform-wide support for CC across trading (exchange and OTC) and custody integrations. Integrate CC in the Security Master and adapters so order lifecycles, RFQ flows, deposits/withdrawals, and address whitelists work out of the box. Commit to activating CC at any connected venue or custodian within ≤5 business days of their enablement, so clients can use existing workflows without changes.

• pX is Talos’ stand-alone agency trading desk geared to expedite client onboarding into the crypto ecosystem. It faces upstream exchanges/market makers and downstream institutions, managing credit and post-trade workflows across venues and custodians. pX computes obligations off-chain and would route bilateral settlements through Canton, providing private, confirmed settlement with counterparties—bringing real institutional settlement volume onto Canton and showcasing the network’s privacy and auditability.

Specification

Deliverable	Acceptance Criteria	Deadline	Weight Earned
CC Support and Readiness across Talos	Platform Ready for CC<br> • CC Market Data captures set up, metrics calculation configured <br> • CC added to Security Master; routing/risk parameters configured. <br> • Exchange and OTC adapters CC-capable (order lifecycle & RFQ schemas). <br> • Custody modules CC-capable (addresses/whitelists, deposit/withdraw callbacks). <br><br>Prove it works in UAT / Sandbox<br>* UAT demos: one exchange trade flow, one OTC RFQ flow, one custodian transfer <br> • Add support for CC by default in clients’ sandbox environments	+90 Days from CIP Approval	+1
CC Support Acceleration Bonus	+0 Bonus if delivered +90 Days from SV CIP Approval<br><br>+1 Bonus if delivered +45 Days from SV CIP Approval <br><br>Linear sliding scale between +45 and +90 days <br><br>Example: If delivered in +54 days, Talos is awarded +0.8 SV Weight	+90 Days from CIP Approval	Max +1
CC Support Exchange Activation	Once CC is available to trade at a Talos-supported venue…<br><br> • Enable CC at any Talos connected venue or custodian within ≤5 business days of that counterparty’s enablement <br> • Publish a press release and/or marketing page announcing Talos support for CC (trading and custody workflows) <br>* If any partner lists CC, meet the ≤5-day activation timeframe and record one production flow	≤5 Business Days from Talos-enabled Venue adding CC	+0.5
CC Support Adoption Bonus	• +0.5 for each $25M in CC traded through Talos during the window (aggregate across exchange and OTC) <br> • Evidence: Aggregated Talos trade records for CC (timestamped totals and methodology) submitted to the Tokenomics Working Group (TWG) for verification	+180 Days from first Venue Going Live	+0.5 per $25M of CC traded through Talos <br>Max +1
pX Settlement Support and Readiness	pX Platform Ready for Canton Support<br><br> • pX can create, send, receive, and mark complete settlements over Canton with a counterparty. <br> • Minimal fields: asset (Canton Coin and other supported Canton assets like USDC on Canton), quantity, counterparty, settlement date, reference. <br> • Supports both simple transfers and delivery-with-payment where the counterparty setup allows. <br> • Internal UAT demo: end-to-end flow using a Talos-controlled test counterparty. <br><br>Acceptance Criteria <br> • ≥1 external counterparty completes ≥20 production settlements over Canton (any mix of CC and other supported Canton assets; same-day or value-dated). <br> • Publish basic ops stats for those 20: time from send to confirmation and success/failure counts.	+180 Days from CIP Approval	+1
pX Settlement Acceleration Bonus	+0 Bonus if delivered +180 Days from SV CIP Approval <br><br>+1.0 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, Talos is awarded +0.5 SV Weight	+180 Days from CIP Approval	Max +1.0
pX Settlement Adoption Bonus	• +0.5 for each $1.5B in notional settled on Canton via Talos during the window (any supported Canton asset, incl. CC and USDC on Canton) <br> • Evidence: Aggregated settlement records (instruction counts, timestamps, asset, notional) and reconciliation methodology submitted to the TWG for verification	+180 Days from pX Go Live	+0.5 per $1.5B of notional settled on Canton via Talos <br><br>Max +1

SV Reward Mechanics:

• An extraBeneficiary PartyID associated with the ‘escrowed’ Super Validator will be setup by the Foundation, or another SV node operator approved to provide SV rewards escrow services, with an SV Weight at the maximum earnable weight.

  • The Applicant is responsible for coordinating the process of setting up the escrowed weights with the GSF and the operator of the SV node.
  • The Applicant is responsible for all costs associated with the operation of the escrow SV
  • The escrow SV will NOT mint rewards on a block by block basis
  • All escrow SV rewards will go to the Unclaimed Rewards pool

• ⅔ of the Super Validator Operators will update their configurations to allow the escrowing SV node to host the full weight to be earned by the given Super Validator

• Applicant is required to present proof of successful completed milestones to the Tokenomics Working Group

  • Applicant is required to present a calculation for number of Canton Coin it should earn for meeting the requirements of the milestone

• If the Tokenomics Working Group agrees the milestone has been met and agrees with the calculation, an announcement will be sent via the Tokenomics-Announce mailing List

  • The GSF will update the extraBeneficiary to an active PartyID controlled by that Super Validator.
  • ⅔ of Super Validator Operators will then assign a portion of the Unclaimed Rewards to be minted by the Applicant’s Validator, based on the calculation approved by the Tokenomics working group.

• If any milestones and associated rewards are not achieved by the deadline

  • Applicant will be notified they have not met a deliverable by the GSF
  • Remaining SV Weight assigned to the extraBeneficiary SV will be removed from the GSF node configuration, and the total SV weight of the GSF SV node will be reduced by the same amount by a vote of the Super Validators.
  • 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.

Copyright

• This CIP is licensed under CC0-1.0: Creative Commons CC0 1.0 Universal.

Changelog

• 2025-09-08: Initial draft of the proposal.
• 2025-10-07: Edits from Chris Zuehlke
• 2025-10-09: CIP Approved.