# Helix Canton Track Status > hstXDC is not Helix's first piece of Canton infrastructure. The Helix Canton track has been in production on the Canton mainnet path since well before the hstXDC architecture was scoped. This section is the verifiable evidence that the team behind hstXDC has shipped Canton-side institutional infrastructure before, has live external relationships across the Canton ecosystem, and is operating against the Canton mainnet rollout timeline today. ### Live infrastructure today | Component | Where to verify | What it does | | ---------------------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Helix SV Compliance Dashboard** | [vault.helixlabs.org/sv-locking](https://vault.helixlabs.org/sv-locking) | Public, ungated CIP-0105 Super Validator compliance observation surface. Tracks SV locking state across the Canton mainnet validator set, surfaces compliance gaps, and provides the operator-facing observation layer that Helix's institutional architecture is built around. | | **Observation-first vault architecture** | Active on the Canton mainnet path under the `helix-v2g` package | The Canton-side production deployment of Helix's "observation before custody" architectural thesis. Same architectural pattern that the hstXDC vault on Canton (see sec4) extends to the cross-chain context. | | **Earnings indexer infrastructure** | Operational, feeding the SV compliance dashboard | Backend service indexing on-chain SV reward state from the Canton mainnet, with checkpoint-based pagination for production reliability. Demonstrates that the team operates production indexer infrastructure against Canton mainnet, not just test deployments. | The dashboard at vault.helixlabs.org/sv-locking is the most direct verifiable artifact. ### Architectural thesis -- "observation before custody" Helix's Canton-side product thesis is that **operator visibility into validator and custody state must precede any custody product**. The CIP-0105 dashboard is the visibility layer; the pCC custody architecture (in design) is the custody product that the visibility layer enables. The hstXDC vault on Canton is the same pattern applied to a cross-chain context: the bridge attestor network produces visibility into XDC-side state, and the Canton-side vault is the custody product that the visibility layer enables. This is the through-line connecting Helix's existing Canton infrastructure to hstXDC. The hstXDC architecture is not a departure from the Helix product thesis -- it is the cross-chain instantiation of it. ### Canton ecosystem relationships | Relationship | Status | | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Canton Foundation** | Active engagement with Foundation DevRel; grant proposal in process | | **IntellectEU** | Mainnet validator partner; institutional Super Validator infrastructure deployment in progress with Helix as the application-side counterpart | | **Splice (Hyperledger Labs)** | Helix maintains a fork of `hyperledger-labs/splice` for upstream contribution targeting CIP-0105 module work. Public contribution pathway via standard pull request flow against the upstream repository. | | **Global Synchronizer Foundation** | Helix operates against the Global Synchronizer Foundation production synchronizer for the Canton mainnet path | | **BitGo Bank & Trust** | BitGo extended qualified custody to CIP-56 token standard assets (cBTC, USDCx) on March 25 2026 -- the same regulated US qualified custodian that custodies XDC mainnet (live since February 1 2026). The Canton-side asset class that hstXDC produces is in the same custody framework as the existing Canton CIP-56 asset family. | ### Mainnet path positioning Helix's Canton track is positioned for **Super Validator status on the Canton mainnet** as part of the institutional rollout sequence. The validator deployment workstream with IntellectEU is the operational path; the SV compliance dashboard is the application that demonstrates Helix's compliance-side product capability before the validator role activates. The hstXDC architecture is forward-compatible with Helix's SV positioning -- the Canton-side vault contracts can be hosted on a synchronizer where Helix is part of the operating set, which simplifies the operator authority model and reduces the number of distinct institutional counterparties in the trust perimeter. ### What this section deliberately does not claim | Topic | Why we are not claiming it | | ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Specific Foundation grant amounts** | Grant proposal is in process; figures and acceptance status are not yet public. We will not pre-announce financial commitments. | | **Helix as a confirmed Super Validator on Canton mainnet today** | Helix is in the validator deployment workstream, not yet operating as an SV on the Canton mainnet validator set. The architecture is positioned for SV status; the role itself is a future milestone, not a current claim. | | **Specific institutional counterparties under DD with the Helix Canton track** | Partner relationships are confidential until both parties agree to public disclosure. The same disclosure pattern as sec9. | | **Specific dollar revenue figures or deal sizes for the pCC custody product** | The pCC custody and repo desk product is in design with named institutional partners under direct conversation. Public revenue claims are inappropriate for an architecture document. | | **Specific endorsements from Canton Foundation or Digital Asset personnel** | Personal endorsements from individuals at partner organizations belong in direct partner conversations, not in public documentation. |