BSCB: Sentinel Circuit Breaker
Operator & jurisdiction: BASIS is operated by BASIS DIGITAL INFRASTRUCTURE LTD, a Seychelles-incorporated entity (LEI: 254900IX2F2KCWNSSS64).
Currency convention: Dashboard values may be displayed in USDT as an internal accounting and USD-equivalent reference unit. USDT is not a depositable or withdrawable asset on BASIS. Deposits and withdrawals are supported in native tokens only: BTC, ETH, SOL, and PAXG.
The BASIS Sentinel Circuit Breaker (BSCB) is an automated, rule-based safety mechanism that halts or reduces execution activity when predefined risk thresholds are breached. It is the platform’s first line of automated defense against adverse market conditions, venue instability, or system anomalies.
BSCB exists to preserve deterministic execution quality, maintain state consistency, and protect structural alpha capture under stressed conditions.
1. Theoretical Foundation: Circuit Breakers in Financial Markets
Circuit breakers are a well-established control in financial markets. Following the October 19, 1987 market crash, major exchanges adopted market-wide halts to reduce disorderly trading and allow time for information repricing. The underlying rationale is simple: temporary interruption can reduce cascade risk when market behavior departs from normal assumptions.
In digital asset markets, which operate continuously across fragmented venues, this logic is even more relevant. BASIS applies the same principle to automated execution infrastructure, where latency, state integrity, and venue reliability directly affect execution precision.
The BSCB is designed for a high-speed environment supported by BHLE infrastructure:
Sub-50μs internal latency
100K+ OPS processing capacity
Proprietary routing infrastructure
Deterministic execution controls
Math-constrained state machine risk logic
These characteristics allow BSCB to respond quickly while remaining bounded by explicit control rules rather than discretionary intervention.
2. BSCB Trigger Conditions
The BSCB is activated when any monitored condition exceeds its allowed operating range.
Execution Slippage Anomaly
Realized slippage exceeds modeled slippage by a significant margin
> 3x predicted slippage
Venue API Failure
A whitelisted venue becomes unresponsive or returns repeated errors
> 3 consecutive failed API calls
Margin Health
Margin ratio on a derivatives hedge approaches liquidation danger
< 150% of maintenance margin
Pricing Reference Instability
Internal accounting reference or external price feed deviates beyond tolerance
> 1.5% deviation from expected reference band
Reconciliation Failure
Post-execution balance checks detect mismatch between internal ledger and venue balances
Any non-trivial discrepancy
Abnormal Volatility
Short-term realized volatility exceeds predefined risk bounds
> 4x 1-hour rolling average
Routing Degradation
Venue routing quality falls below minimum expected execution standard
Sustained route quality failure
State Integrity Exception
Risk engine detects invalid or unresolved state transition
Any critical state mismatch
Thresholds shown here are illustrative. Internal production thresholds may vary by asset, venue class, liquidity state, and market regime.
3. BSCB Response Protocol
When the BSCB is triggered, the system enters a deterministic response sequence.
Step 1: Halt New Execution
All new order submissions are immediately suspended. No new exposure is opened while the system is in BSCB state.
Step 2: Evaluate Existing Exposure
The system reviews all open positions, hedge dependencies, venue availability, and current margin state to determine whether residual exposure is safe to maintain.
Step 3: Controlled Exposure Reduction
If open positions are deemed elevated-risk, the system initiates a controlled unwind.
This is not a panic liquidation. The objective is orderly exposure reduction with the highest feasible execution precision under current constraints, using bounded routing logic and limit-based methods where possible.
Step 4: Notify Operations
The operations team is notified with the trigger source, affected subsystem, and current state classification. Where applicable, user-facing status communication may also be published.
Contact channels:
Operations: [email protected]
Support: [email protected]
Compliance: [email protected]
Step 5: Enter Hold State
The system remains in BSCB hold state until:
the triggering condition is resolved
state reconciliation passes
route quality returns within allowed bounds
automated or manual review confirms safe resumption
4. BSCB vs. DMM
BSCB is an automated and immediate control response. It is designed to react faster than human intervention.
DMM (Defensive Maintenance Mode) is a more severe operating state used when BSCB containment is insufficient or when a formal root cause review is required before resumption.
Trigger
Automated, rule-based
Manual escalation or severe automated trigger
Severity
Moderate, temporary halt or reduction
High, full operational pause
Recovery
May be automatic if conditions normalize
Requires review and manual approval
Duration
Minutes to hours
Hours to days
Primary Objective
Immediate containment
Full system safety validation
5. Design Philosophy: Fail-Safe, Not Fail-Open
The BSCB follows a fail-safe design principle.
If the monitoring layer fails, loses connectivity, or cannot validate system state, the default action is to halt execution rather than continue under uncertainty. This is a core design choice of BASIS infrastructure.
In uncertain conditions, inaction is safer than unconstrained execution.
This philosophy supports:
capital preservation
deterministic state control
bounded execution behavior
protection of structural alpha capture
reduction of hidden tail-risk accumulation
BSCB is part of BASIS’s broader risk architecture, which emphasizes deterministic execution, explicit math constraints, and state-machine-based control logic over discretionary intervention.
6. Operational Context Within BASIS
BSCB operates independently of wallet flows and user staking mechanics.
For clarity:
Funding Wallet holds native tokens for deposit and withdrawal: BTC, ETH, SOL, PAXG
Staking Wallet holds stTokens for staking and reward accrual: stBTC, stETH, stSOL, stPAXG
Swaps are same-token only at 1:1:
BTC → stBTC
ETH → stETH
SOL → stSOL
PAXG → stPAXG
USDT is an internal accounting and display unit only
BSCB does not alter wallet ownership records or staking balances unless a validated system action explicitly requires it.
7. Governance and Oversight
BSCB is part of the production control framework operated by BASIS DIGITAL INFRASTRUCTURE LTD in Seychelles under LEI 254900IX2F2KCWNSSS64.
The control philosophy is informed by research collaboration with Base58 Labs, presented in public materials as a Research Partner or Research Institute where applicable. The purpose of that framework is not discretionary speculation, but reliable structural alpha capture through disciplined execution systems.
Questions related to operations, legal process, or technical review can be directed to:
Last updated