Solana Protocol

On Solana, exposure is expressed through stake accounts delegated to vote accounts and evaluated on epoch boundaries. FortisX aggregates stake-weighted stability and topology signals into datasets and allocation inputs designed for Solana.
Solana Protocol
PoH+PoS
Consensus
Epochs
Cadence
Stake accts
Exposure
Vote accts
Delegation
2020
Mainnet
About Solana staking

Key Concepts for Staking and Delegation

Solana staking is stake-weighted by design, and timing is anchored to epoch boundaries and activation mechanics.

Stake accounts represent exposure and delegate to vote accounts. This link is the foundation for understanding who your stake follows.
Activation and deactivation do not switch instantly. Warmup and cooldown create a transition period that matters for planning.
Performance is read through epoch-level signals and sustained behavior. Short spikes are less informative than stable patterns.

Risk Monitoring

Risk Signals We Track

Solana monitoring emphasizes stake-weighted concentration, activation dynamics, and sustained voting health across epochs. Warmup and cooldown mean that reallocations translate into effective stake gradually, so timing and vote consistency matter alongside correlated operator exposure and version lag.

01

Stake concentration

Large stake skew reduces resilience and amplifies single-entity influence.
02

Activation flow

Warmup/cooldown changes when stake becomes effective after reallocations.
03

Vote health

Persistent missed voting degrades vote credits and consistency over epochs.
04

Cluster exposure

Shared regions, hosting, or tooling can align outages across operators.
05

Version lag

Client version lag raises upgrade risk and coordination cost.
Allocation Policy

Allocation Policy Building Blocks

Solana allocation is expressed through stake accounts delegated to vote accounts, with effective stake changing through warmup and cooldown. Policy must align to epoch boundaries and to the timing of stake becoming active.

Stake-weighted targets are expressed across vote-account groups and operator clusters on Solana. Reviews follow epoch windows, reflecting when delegated stake becomes effective.
Caps limit stake share per vote account and per correlated operator cluster. Limits tighten when stake distribution concentrates or correlation exposure increases.
Floors specify epoch-level voting health thresholds, using delinquency and consistency metrics. Floor levels rise when degradation persists across multiple epochs.
Drift triggers initiate review when epoch-level stability shifts or when warmup and cooldown change the effective stake profile. Actions align to transition points where stake activation affects exposure.
Incident response reduces exposure to affected clusters and raises entry thresholds for new allocations. Changes are staged to reflect warmup and cooldown timing.
Data Coverage

Data Coverage and Integration Points

Solana coverage is derived from on-chain stake delegation and vote activity and normalized into datasets used for allocation policy within Solana.

Coverage is organized around vote accounts and stake delegation state, capturing where delegated stake is assigned and how voting outcomes accumulate.
Timing datasets reflect epoch boundaries and stake warmup and cooldown mechanics, which determine when delegated exposure becomes effective.
Concentration views are expressed as stake-weighted exposure across vote accounts and correlated clusters when shared dependencies can be attributed.
Integrations expose the same datasets through the FortisX API and webhook events for monitoring, idempotent processing, and internal workflows.
FAQ

Solana Protocol FAQ

Epochs are the operational timing unit, and stake activation and deactivation take effect at epoch boundaries.
A vote account represents a validator’s voting identity and is the on-chain object that accumulates voting activity used in performance evaluation.
Because effective stake changes occur at epoch boundaries, allocation adjustments should be aligned to those boundaries to reflect real exposure.
Concentration is described as stake-weighted exposure across vote accounts and correlated operator clusters that may share infrastructure dependencies.
Instability typically appears as degraded voting participation, which reduces observed effectiveness and informs exposure controls and recovery gates.
We use cookies to operate the site, analyze traffic, and remember your preferences. You can change settings at any time.
Learn More