Subnet 7: Allways
Allways is Bittensor Subnet 7 (SN7), operated by Entrius, with source code published in the Allways repository. The protocol enables trustless native asset swaps across independent blockchains without wrapping tokens or relying on custodial bridges. Assets settle directly on their native chains — Bitcoin moves on Bitcoin, TAO moves on Bittensor — and the subnet provides the collateral enforcement and verification layer that makes this permissionless. The protocol launched with BTC ↔ TAO and is designed to extend to any verifiable asset pair.
How the Mechanism Works
The Allways repository describes a protocol coordinating three parties: a user who wants to swap, a miner who fulfills the swap, and validators who independently verify that the fulfillment happened correctly.
Before quoting rates, miners lock collateral into a smart contract. This collateral backs every rate commitment they post and is at risk of being slashed if they fail to honor an order. The contract manages the entire swap lifecycle — from the moment a user submits an order through matching, execution, and final settlement — without any trusted intermediary.
When a user’s order matches a miner’s quoted rate, the miner executes native on-chain transfers on both blockchains: for a BTC ↔ TAO swap, this means sending BTC on the Bitcoin chain and releasing the corresponding TAO on Bittensor, or the reverse. The miner reports completion to the subnet once both legs are on-chain.
Validators do not take the miner’s report at face value. Each validator independently monitors the blockchains involved, reads their on-chain state, and casts a vote on whether the claimed transaction is valid. The aggregate of validator votes determines whether the fulfillment is accepted or rejected. Accepted outcomes release the miner’s collateral; rejected outcomes trigger slashing. This design means the protocol’s security rests on the independence and honesty of the validator set, not on any single trusted party.
Accepted or rejected fulfillment votes shape the validator weights submitted on netuid 7; Yuma Consensus then settles those weights into emission shares each tempo—on-chain swap verification is subnet evaluation input, not the emission payout itself (Allways repository, Yuma Consensus, Emission).
Participating as a Miner
The Allways repository describes miners as market makers and liquidity providers. To participate, a miner registers on netuid 7, deposits collateral into the smart contract, and begins posting exchange rate pairs for the asset pairs they are willing to trade. When a user’s order matches a posted rate, the miner is obligated to execute the corresponding native-chain transfers within the required time window.
The collateral requirement creates direct accountability: a miner cannot accept orders worth more than their posted collateral, and any failure to fulfill a matched order results in a portion of that collateral being slashed. Miners who maintain accurate pricing, reliable infrastructure, and sufficient liquidity earn subnet emissions proportional to their validated trade volume.
Participating as a Validator
Validators on Allways run the independent verification infrastructure described in the Allways repository. For each claimed swap fulfillment, validators directly inspect the blockchains involved — confirming that the correct amounts reached the correct addresses within the required time — and submit a binary vote on the outcome. The smart contract tallies votes to determine whether a miner is rewarded or slashed.
Validators must maintain continuous connectivity to both Bittensor and the external chains they monitor. Validators that vote consistently with the accurate on-chain outcome receive emissions through Yuma Consensus.
On-Chain Identity
Allways is registered at netuid 7 on Bittensor with 256 neurons. The subnet owner coldkey is 5CAc19iETJmWD2rYVX1ht58ghCpyHq86MoBNdx5TzLfinzcx. The GitHub repository is maintained at entrius/allways and the project website is all-ways.io. Live on-chain data is available on TaoStats.
Native Settlement Context
The Allways repository frames SN7 around assets settling on their own native chains rather than being wrapped or routed through a custodial bridge. For a reader, that design choice is the point worth understanding: most cross-chain swaps introduce a wrapped token or a custodian that holds funds in the middle, and those become the thing that can fail or be seized.
Allways instead keeps Bitcoin on Bitcoin and TAO on Bittensor and treats the subnet as a coordination-and-verification layer over those native transfers. That reframes the subnet’s role: it is not custody of the assets being swapped, but enforcement that the native transfers actually happened as quoted. Reading SN7 this way explains why its security discussion centers on verifying on-chain settlement rather than on protecting a bridge balance.
References: Allways repository, all-ways.io
Collateral and Verification Context
The Allways repository describes two reinforcing ideas: miners post slashable collateral behind their quotes, and validators independently verify each claimed settlement before collateral is released. For a reader, these are best understood together as the subnet’s trust model rather than as separate features.
The collateral makes a broken promise costly, and the independent verification decides whether a promise was kept. Because acceptance depends on the aggregate of validator votes reading on-chain state, the security of a swap rests on the independence of the validator set, not on trusting the miner’s own report. That is the conceptual reason Allways can call itself trustless: honesty is enforced by stake at risk plus independent observation, not by a central operator.
References: Allways repository, Subnet 7 on TaoStats
Distinction from Dynamic TAO
Subnet 7 (Allways) is one subnet market inside Bittensor’s broader Dynamic TAO context. Dynamic TAO names the protocol setting where subnet-level alpha and TAO interact across subnet markets; this article covers Allways’ trustless swap and collateral verification market rather than the full tokenomics model (Emission, Understanding Subnets).
For Allways, rewards available per block depend on SN7’s stake weight relative to other subnets. Within that pool, emission flows to miners in proportion to validated trade volume through Yuma Consensus weight aggregation (Introduction to Bittensor, Yuma Consensus).
Miner and Validator Roles
Subnet 7 operates under the standard Bittensor two-role structure. Miners supply the subnet’s capability and validators evaluate those contributions and set weights. Reward distribution follows Yuma Consensus.
Distinction from Yuma Consensus
Allways on netuid 7 is a trustless native-asset swap subnet where miners post collateral-backed exchange rates and validators independently verify on-chain fulfillment before collateral is released or slashed. That swap-verification vocabulary names how Allways measures validated trade volume on netuid 7, not the on-chain step that turns validator weight submissions into emission shares each tempo (Allways repository, Yuma Consensus).
Yuma Consensus is the on-chain mechanism that runs at the epoch boundary on the selected netuid. It reads the weight matrix from eligible validators, applies clipping and bonding, and converts the result into miner incentives and validator dividend shares (Yuma Consensus, Emission).
Earlier sections describe collateral posting, native-chain settlement, and independent validator votes on fulfillment. Those inputs shape the validator weights; they do not settle emissions themselves. Yuma aggregates the weight signals that flow from that swap-verification path rather than executing cross-chain transfers itself (Allways repository, Understanding Subnets).
Swap verification therefore sits upstream of settlement. Yuma still credits emissions from included validator weights on netuid 7 once the tempo closes (Allways repository, Emission).
Readers should treat Allways as the trustless native swap protocol on netuid 7, and Yuma Consensus as the recurring mechanism that allocates rewards from validator weights each tempo.
- Subnet 7 (Allways) — trustless native cross-chain swap subnet with collateral enforcement.
- Yuma Consensus — epoch-boundary settlement from validator weights to emission shares on a task subnet (Yuma Consensus: Validator emissions).
Reader Boundary
Subnet 7 Allways should not be read as generic Bittensor subnet documentation, a custodial bridge or wrapped-token service, or trading and investment advice. It names one subnet’s trustless native cross-chain swap layer — a collateral-and-slashing contract coordinating market-maker miners and independent verifier validators, launched with BTC ↔ TAO — on netuid 7 (Allways repository, Understanding Subnets, Glossary: Netuid).
Assets settle on their native chains rather than as wrapped tokens, so the article describes the protocol’s verification and collateral mechanism, not a guarantee of swap availability, price, or liquidity for any pair (Allways site — all-ways.io).