CIP-0076: Hypernative as a Super Validator with a Weight of 1

CIP-0076

Abstract:

Hypernative as a Super Validator with a Weight of 1

About Applicant:

Hypernative is a leading blockchain security and monitoring platform, delivering real-time on-chain and off-chain threat detection, anomaly detection, and governance risk monitoring. Its products are trusted by protocols, foundations, and institutional actors seeking resilient risk mitigation in decentralized environments.

With a global team of engineers, researchers, and data scientists, Hypernative continuously monitors blockchain networks, identifies risks in real time, and integrates with client systems for proactive defense.

Key strengths Hypernative brings to Canton include:

• Proven track record of real-time threat detection across multiple ecosystems.
• Enterprise-grade monitoring infrastructure for institutional adoption.
• Deep expertise in blockchain forensics, detection modeling, and incident response.
• Trusted partnerships with foundations, auditors, and institutional actors.
• APIs, dashboards, and integration-ready infrastructure to support compliance and governance.

Deliverables for full SV Reward:

Deliverable	Acceptance Criteria	Deadline	Weight Earned
Hypernative provides proactive network monitoring solution	• Any Canton network member can utilize Hypernative services for Canton blockchain event monitoring. <br> • Measured by ability to monitor and detect balance changes and transfers for Canton Coin including activity for incoming/outgoing transfers and ability to provide alerts generated on thresholds/patterns <br> • At least one entity active on the Canton Network subscribed to monitoring alerts from Hypernative for Canton Network activity (Reference Appendix III, Milestone 5)	+180 Days from CIP Approval	1

SV Reward Mechanics:

• An extraBeneficiary PartyID associated with the ‘escrowed’ Super Validator will be setup by the GSF 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 GSF 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 GSF 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-05: Initial draft of the proposal.
• 2025-09-09: CIP Approved.

Appendix I - Motivation

Canton's adoption depends on the security, resilience, and reliability of its ecosystem. Hypernative directly addresses this by committing to:

• Institutional-Grade Security: Real-time detection and monitoring of on-chain and governance risks.

• Cross-Chain Risk Coverage: Identifying threats originating from external chains and bridging into Canton.

• Incident Response Enablement: Alerts, forensic tooling, and actionable reporting to reduce risk.

• Enhanced Trust & Adoption: Embedding monitoring into Canton's fabric to attract institutional users.

• Market Visibility: Publishing research and engagement materials to elevate Canton's industry standing.

---

Appendix II - Why Hypernative

Hypernative is uniquely suited for Canton's SV role:

• Security-first expertise in blockchain threat detection.

• Technical depth in anomaly detection, governance monitoring, and risk analysis.

• Institutional connections with exchanges, protocols, and financial institutions.

• Complementary specialization versus other SVs, filling the security/monitoring gap.

• Innovation history in security products, analytics, and intelligence services.

• Proven ability to deliver enterprise-grade services for bespoke chain and infrastructure deployments

---

Appendix III - Hypernative's Scope of Work

Deliverable	Acceptance Criteria	Deadline	Evidence of Completion
Milestone 1 - Initial Research & Core Indexing	<br> •Research document on Canton architecture & prerequisites completed<br> •Confirmation of necessary access permissions (Splice permissions sufficient)<br> • Indexed dataset of Canton transactions/events operational	Up to 2 months	<br> •Internal research report shared<br> • Logs/screenshots of indexed chain data beyond transaction hashes
Milestone 2 - Validator Setup	<br> • Validator node deployed, operational, and connected<br> •Validator approved through CIP with assigned weight<br> • Logs show validator active in consensus & governance	Up to 2 months	<br> •Governance confirmation validator is live/approved<br> •Logs/screenshots showing validator in consensus
Milestone 3 - Basic Agents: Address Monitoring	<br> • Agents detect balance changes & transfers for Canton Coin<br> • Monitoring active for incoming/outgoing transfers in real time<br> • Alerts generated on thresholds/patterns	2 months after Stage 1	<br> • Config examples of monitoring agents<br> • Logs/screenshots showing detection of transfers & balance changes
Milestone 4 - Security Detection Research	<br> • Research document outlining Canton threat categories<br> • Prototype implementations provided where relevant<br> • Clear methodology for alert definitions	1 month after Stage 3	<br> • Research report shared<br> • Documentation describing address-based alert guidance
Milestone 5 - Service Adoption, Ecosystem Engagement & Market Enablement	<br> • At least one public engagement (e.g., community post)<br> • Published integration summary on official Hypernative channels <br> • At least one entity active on the Canton Network subscribed to monitoring alerts from Hypernative for Canton Network activity	After all prior stages	<br> • Published blogs, briefs, or webinars<br> • External mentions of Hypernative-Canton integration