BIP-108: Onboarding Beets to the Hypernative Security Platform

Summary

This proposal seeks approval for Beets to subscribe to Hypernative, a real-time threat detection and automated mitigation platform used by a wide range of leading DeFi protocols, including Balancer. The annual subscription cost is $24,000, paid up-front from the Beets Treasury.

By onboarding, Beets would immediately inherit the extensive security automations Hypernative and Balancer have developed together over the past year, most notably automated Balancer v3 Vault pausing and targeted pool pausing in response to abnormal rate-provider behaviour. Beets also gains access to any future developments in regards to Balancer safeguards. In addition, the platform allows Beets to configure safety mechanisms tailored to its own products, such as stS, validator-related events, and future products like loopS.

This integration represents a step toward strengthening Beets’ real-time monitoring, detection, and response capabilities. While Hypernative would not have prevented the recent Balancer V2 exploit, that event reinforced the importance of rapid detection and automated mitigation in reducing the blast radius of future incidents.

What is Hypernative?

Hypernative is a security intelligence and incident-response platform focused on early detection of on-chain threats and automated protective actions. It combines real-time blockchain monitoring, curated threat intelligence, machine-learning-driven anomaly detection, and customizable automation modules. Major protocols across the industry rely on Hypernative to identify exploits in progress, catch unexpected oracle or rate-provider movements, respond to validator-level risks, and trigger safe-shutdown procedures when necessary.

Importantly, Hypernative has been working directly with Balancer for more than a year, during which time the two teams co-developed a series of automated security responses for the Balancer v3 Vault. Beets, as a fork of Balancer, can adopt these same protections with minimal engineering overhead.

## Motivation Following the Balancer V2 Composable Stable Pool exploit, and its impact on Beets LPs, contributors evaluated different ways to strengthen the protocol’s security posture. One clear takeaway from the incident was that real-time monitoring and automated mitigation need to be treated as first-class components of protocol operation. The exploit itself could not have been prevented by Hypernative, but the ability to detect irregular behaviour earlier and to automatically pause affected components would have provided a much stronger defensive posture.

Beets today operates the primary LST (stS) on Sonic, manages critical liquidity infrastructure, and is expanding into new products such as loopS. As Beets’ footprint grows, so does its responsibility to deploy stronger protective systems around its contracts, rate providers, validator interactions, and integrations. Hypernative offers a pragmatic path to achieving this, building on top of a security stack that has already been thoroughly exercised through Balancer.

By subscribing, Beets gains immediate access to Balancer’s tested configurations as well as the ability to extend them. In practice, this includes automated pausing of the v3 Vault under specific threat conditions, pausing individual pools if their rate providers suddenly deviate from expected values, and establishing custom detection triggers around stS, validator slashing, or other critical components. Future products can be brought under Hypernative’s umbrella as well, ensuring protection evolves with the protocol.

Security cannot be retrofitted after an incident, and the recent exploit highlighted the need to invest in systems that shorten the time between detection and mitigation. Hypernative helps fill this gap.

Proposal

This BIP proposes that Beets formally subscribe to Hypernative’s security platform at a cost of $24,000 per year, paid from the Treasury. The subscription provides access to all existing Balancer-aligned automations as well as the ability to build protocol-specific monitoring and mitigation workflows.

Once approved, contributors will work with Hypernative to configure relevant modules, beginning with the Balancer v3 Vault protections. Additional stS-level monitoring, validator-related triggers, and protections for future products will be added in over time. All automated actions will be tested prior to activation to ensure safe execution.

## Impact and Risk Considerations Onboarding Hypernative significantly strengthens Beets’ real-time security posture. Automated pausing and anomaly detection reduce the likelihood that a single incident can cause large user losses or damage protocol integrity. The integration introduces a recurring annual cost, and automated actions must be configured carefully to avoid false positives, but both challenges are manageable. Hypernative’s existing Balancer blueprint provides a robust baseline configuration from which to start, and Beets can fine-tune controls gradually as experience accumulates.

The investment is modest relative to the potential damage that timely mitigation can prevent. As Beets continues to play a foundational role in Sonic’s LST, liquidity, and staking infrastructure, reinforcing operational security is essential.

## Execution Upon approval, Treasury funds will be used to pay the $24,000 annual subscription. Contributors will begin onboarding with Hypernative, validate inherited protections, and then configure additional monitoring and mitigation tailored to Beets’ stack. Renewals for subsequent years will be determined through future governance proposals.