Token Bridging
Token bridging is the Bittensor capability that connects TAO across Substrate and EVM account contexts on the same Bittensor blockchain. The official Token Bridging documentation frames it as two related ideas: moving the same TAO between SS58 and H160 account formats, and representing staked TAO as vTAO inside the EVM layer.
In Taopedia terms, token bridging names a connectivity concept, not a wallet type or a subnet role. It belongs alongside the H160 address concept because bridging is what makes TAO usable inside Bittensor’s EVM environment.
Why Token Bridging Exists
TAO is the native token of the Bittensor network and is normally held in Substrate-style SS58 wallets. The Token Bridging documentation explains that Bittensor also has an EVM layer, and participants need a way to use the same TAO inside that layer without changing the asset itself.
For readers, token bridging is best understood as the link between two account contexts for one token. The value does not change when TAO moves between contexts — only the account format and the set of available operations change.
References: Token Bridging, Wallets, Coldkeys and Hotkeys
What Token Bridging Does
Token bridging moves TAO between SS58 and H160 account formats so the same token can participate in both the Substrate side and the EVM side of the Bittensor chain. The Token Bridging documentation describes this as transferring the same token between account formats, where SS58 wallets access Substrate-side operations and H160 wallets access EVM-side operations.
The second part of token bridging is vTAO, the EVM representation of staked TAO. The documentation describes vTAO as representing TAO that has been staked, where the vTAO balance a holder holds stays the same while the underlying staked TAO grows with staking rewards over time.
For readers, token bridging is the concept that keeps TAO usable across both account contexts and across the staked representation that the EVM layer uses.
References: Token Bridging
Relationship to H160 Address
Token bridging and the H160 address are related because H160 is the destination account format for moving TAO into the EVM context. The Token Bridging documentation describes moving TAO into Ethereum-style H160 wallets to use it in the EVM layer, and the H160 address documentation describes the format itself.
For readers, the H160 address names the EVM-side account format, while token bridging names the capability of moving TAO into that format. The two concepts work together — the address is the destination, and the bridge is how TAO reaches it — but they are not the same idea.
References: Token Bridging, H160 Address
Account and Signing Boundary
Token bridging crosses account-format context as well as token context. On the native side, TAO is associated with Substrate-style SS58 wallet addresses. On the EVM side, TAO is used through Ethereum-style H160 addresses. The Token Bridging documentation frames bridging as the path between those account formats, and the H160 conversion documentation explains the relationship between H160 and SS58 address representations.
This does not make the two wallet contexts identical. A Bittensor wallet signs native Subtensor actions through the Bittensor wallet model, while an EVM wallet signs EVM-layer interactions for the H160 account context. Bridging connects TAO across those contexts, but the surrounding wallet software, address format, and signing surface remain important parts of the reader’s interpretation.
The boundary also keeps Bittensor EVM scoped to Bittensor. The token-bridging documentation notes that Bittensor EVM smart contracts execute on the Bittensor blockchain rather than on Ethereum. Moving TAO into H160 context therefore means using the Bittensor EVM side, not sending TAO to a separate Ethereum network.
Likewise, address conversion context does not transfer coldkey authority by itself. H160 and SS58 formats help readers identify which account context is being referenced, while signing authority still comes from the wallet material used for that side of the interaction.
For readers, the useful split is asset, account, and execution location. TAO is the asset being connected, SS58 and H160 are the account formats, and Bittensor remains the chain environment where the native and EVM contexts meet. Confusing those layers can make a bridge example sound like an asset change, a wallet migration, or an Ethereum transfer when the official documentation is describing Bittensor-side bridging.
References: Token Bridging, H160 Address, Bittensor EVM Smart Contracts, Wallets, Coldkeys and Hotkeys
Relationship to Staking
Token bridging and staking are related because vTAO, the EVM representation used in bridging, is a staked form of TAO. The Staking and delegation overview describes staking as committing TAO to support a validator and participate in rewards, and the Token Bridging documentation describes vTAO as representing staked TAO inside the EVM layer.
For readers, staking names the act of committing TAO for rewards, while token bridging names how the resulting staked TAO is represented when it moves into the EVM context. The two concepts connect through vTAO but should not be read as the same operation.
References: Staking and delegation overview, Token Bridging
Relationship to Emission
Token bridging and emission are related because the staked TAO behind vTAO grows with staking rewards over time. The Emissions overview describes how staked TAO earns rewards, and the Token Bridging documentation notes that the underlying TAO represented by vTAO increases with those rewards.
For readers, emission names the reward flow that grows staked TAO, while token bridging names the EVM-side representation that tracks that growth through vTAO. The reward mechanism and the bridge representation are separate concepts that connect through the staked asset.
References: Emissions, Token Bridging
Relationship to Bittensor EVM Smart Contracts
Token bridging is what makes TAO usable inside Bittensor’s EVM smart-contract layer. The Token Bridging documentation notes that Bittensor EVM smart contracts are executed solely on the Bittensor blockchain, not on the Ethereum blockchain.
For readers, this keeps the EVM concept scoped to Bittensor. Token bridging moves TAO into the H160 account context so it can interact with Bittensor’s own EVM contracts. The bridge connects TAO to the EVM layer; it does not send TAO to a separate Ethereum network.
References: Token Bridging, Bittensor EVM Smart Contracts
Reader Boundary
This article defines token bridging and vTAO as concepts. It does not describe bridging steps, wallet setup, exchange rates, tool-specific instructions, or supported chain lists. Readers should use the official Bittensor EVM documentation for operational detail and current parameters.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For token bridging, that sequence changes how readers should interpret evidence about bridge behavior and vTAO conversion outcomes.
In localnet, token bridging mechanics can be tested in an isolated environment. Localnet bridge behavior and conversion outcomes reflect local chain configuration and do not represent production EVM bridge state.
On testnet, token bridging can be observed in a shared, non-production network. Testnet bridge interactions and vTAO conversion outcomes are separate from mainnet production bridge state.
On mainnet, token bridging is a live operation that moves TAO representation between the Subtensor layer and the Bittensor EVM environment. The Token Bridging documentation describes the bridge mechanics that apply on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A token bridging example from one environment should not be read as representing bridge parameters or conversion rates in another environment.
Bridging Moves TAO Between SS58 and H160 Contexts
The Token Bridging documentation describes moving the same TAO between Substrate-style SS58 wallets and Ethereum-style H160 wallets on the Bittensor chain. Token bridging therefore names a cross-format path on one network, not a transfer to a separate blockchain.
Readers should keep SS58 and H160 as account-context labels. Bridging connects native Bittensor wallet operations with EVM wallet operations for the same TAO asset (Bittensor EVM Smart Contracts).
The Bridged Asset Remains TAO
Official bridging material frames token bridging as letting participants use the same TAO inside the EVM layer without changing the asset itself (Token Bridging). Bridging vocabulary should therefore stay on the TAO side of tokenomics, separate from subnet alpha tokens discussed in subnet markets.
A move into H160 context changes how the balance is represented and which wallet software signs, not which network token is being held.