Number: TBA
Title: Add Talos as Weight 7 SV
Author(s): Anton Katz
Discussions-To: TBA
Type: Governance
Status: Draft
Created: 2025-09-05
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 +7.0 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.
Deliverables for full SV Reward:
Deliverable | Acceptance Criteria | Deadline | Weight Earned |
CC Support and Readiness across Talos | Platform Ready for CC * CC added to Security Master; routing/risk parameters configured. * Exchange and OTC adapters CC-capable (order lifecycle & RFQ schemas). * Custody modules CC-capable (addresses/whitelists, deposit/withdraw callbacks). Prove it works in UAT / Sandbox * UAT demos: one exchange trade flow, one OTC RFQ flow, one custodian transfer * 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 +1 Bonus if delivered +45 Days from SV CIP Approval Linear sliding scale between +45 and +90 days 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… * Enable CC at any Talos connected venue or custodian within ≤5 business days of that counterparty’s enablement * Publish a press release and/or marketing page announcing Talos support for CC (trading and custody workflows) * 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) * Evidence: Aggregated Talos trade records for CC (timestamped totals and methodology) submitted to the TWG for verification | + 180 Days from first Venue Going Live | + 0.5 per $25m of CC traded through Talos |
pX Settlement Support and Readiness | pX Platform Ready for Canton Support * pX can create, send, receive, and mark complete settlements over Canton with a counterparty. * Minimal fields: asset (Canton Coin and other supported Canton assets like USDC on Canton), quantity, counterparty, settlement date, reference. * Supports both simple transfers and delivery-with-payment where the counterparty setup allows. * Internal UAT demo: end-to-end flow using a Talos-controlled test counterparty. Acceptance Criteria * ≥1 external counterparty completes ≥20 production settlements over Canton (any mix of CC and other supported Canton assets; same-day or value-dated). * 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 +1.5 Bonus if delivered +60 Days from SV CIP Approval Linear sliding scale between +60 and +180 days Example: If delivered in +120 days, Talos is awarded +0.75 SV Weight | +180 Days from CIP Approval | Max +1.5 |
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) * 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 |