Subnet 30: Endure Network
Endure Network is Bittensor Subnet 30.
What Endure Network Provides
The project website is endure.network, and the public Endure documentation describes Endure Network as a decentralized risk-intelligence subnet for financial assets, markets, and exposures.
Risk Intelligence Context
Endure’s public documentation frames risk intelligence as a measurable subnet task. Miners submit parameter estimates such as liquidation thresholds, collateral factors, margin requirements, volatility bounds, confidence intervals, or safe exposure sizes. Validators score those submissions after outcomes are observed, so the network rewards assessments that prove accurate rather than assessments that merely sound credible.
That makes Endure different from a static research report or a committee-style risk process. The subnet is meant to turn risk analysis into a continuous competition where independent methods can be tested against realized market behavior. The public site describes this as risk management and efficiency parameters produced by competing analysts, then scored against what actually happened.
The practical output is a risk signal that downstream products can consume. Endure’s documentation describes products using the shared intelligence layer for pricing, monitoring, governance, underwriting, and risk automation. The website also identifies Forge as an early product built on Endure’s risk intelligence, positioning the subnet as infrastructure for applications rather than as a standalone dashboard.
Network Flow Context
The How It Works documentation describes four layers: collection, validation, delivery, and consumption. Miners produce assessments in the collection layer. Validators score and aggregate those assessments in the validation layer. Delivery makes the consensus output available as a signed artifact, and consumers read the signal before acting on it.
For readers, the important point is that Endure separates the people or systems producing risk assessments from the systems that consume the resulting signal. That separation lets many miners compete on risk quality while giving downstream applications a single verifiable output. The validator role is therefore not just generic review; it is the feedback loop that connects miner assessments to realized outcomes and Yuma Consensus weights.
Miner and Validator Roles
Miners submit risk assessments for targets and contexts, such as assets, markets, portfolios, or exposures. Validators evaluate those assessments against outcomes, aggregate the resulting signals, and set weights. Those weights feed into Yuma Consensus, which converts validator assessments into emissions that reward the strongest performers.
On-Chain Identity
Live subnet data for netuid 30 is available on TaoStats. Public project materials are available at endure.network and the Endure documentation.
Relationship to Yuma Consensus
Subnet 30 uses Yuma Consensus to convert the risk-assessment weight vectors that validators submit into the emission shares distributed to miners and validators within the subnet each tempo. The linked documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
In Endure Network’s context, validators score miner risk-parameter submissions after outcomes are observed, aggregate the resulting signals, and translate those accuracy scores into weight vectors for the subnet. The Emission documentation describes how those consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Endure Network (SN30), that sequence changes how readers should interpret risk intelligence examples and network scoring outcomes.
In localnet, Endure-compatible miners and validators can be developed and tested in an isolated environment. Localnet risk intelligence scores and emission outcomes do not represent production subnet performance.
On testnet, Endure-compatible components can be exercised in a shared, non-production network. Testnet risk evaluations and validator scores are separate from mainnet subnet state.
On mainnet, Endure Network (SN30) is the live production subnet where miners provide risk intelligence data and validators evaluate those contributions to determine real Bittensor emissions. The Endure documentation describes the mechanism that applies on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A risk evaluation result or emission outcome from one environment should not be read as representing production subnet performance in another environment.
Reader Boundary
Subnet 30 Endure Network should not be read as generic Bittensor subnet documentation, a trading bot subnet, or proof that one risk call guarantees market outcomes. It names one subnet’s decentralized risk-intelligence layer on netuid 30 (Understanding Subnets, Glossary: Netuid).
Four Layers Separate Collection From Consumption
Endure’s How It Works documentation describes collection, validation, delivery, and consumption as distinct stages in the network flow (How It Works).
Miners produce assessments, validators score them, and downstream products consume the resulting signal rather than each miner’s raw submission.
Delivery Exposes a Signed Consensus Artifact
The same documentation places signed delivery artifacts between validator aggregation and product consumption (How It Works).
That layer is how applications read one verifiable output instead of reconciling many miner reports directly.
Validator Weights Still Flow Through Yuma Consensus
Subnet 30 uses Yuma Consensus to convert validator weight submissions into emission shares each tempo (Yuma Consensus, Emission).