Subtensor
15 articles in this topic.
-
Bittensor EVM Smart Contracts
How Bittensor supports Ethereum Virtual Machine-compatible smart contracts on Subtensor.
-
Chain Reads
How chain reads describe looking at public Bittensor chain state without asking Subtensor to record a new action.
-
Extrinsics
Extrinsics are Bittensor chain actions that ask the Subtensor runtime to process a state-changing operation.
-
H160 Address
How H160 addresses identify Ethereum-style wallets in Bittensor EVM, and why they should not be confused with SS58 coldkey or hotkey addresses.
-
Inspecting the Chain with Polkadot.js
How Polkadot.js helps readers inspect Bittensor chain state, metadata, blocks, and events while keeping observations tied to network and block context.
-
Mempool
How the Bittensor mempool holds pending transactions before block inclusion.
-
Polkadot Vault
How Polkadot Vault fits into Bittensor coldkey custody, air-gapped signing, QR transaction transport, Subtensor extrinsic support, and proxy-oriented key operations.
-
Rate Limits
How Bittensor rate limits use block-based cooldowns to pace repeated chain actions.
-
Subnet Stake Burn
How subnet stake burn adds TAO to a subnet reserve while permanently removing alpha from circulation.
-
Subtensor
How Subtensor names Bittensor's blockchain layer and system of record for transactions, rankings, and incentive flow.
-
Subtensor Constants
How Subtensor runtime constants expose named reference values grouped by runtime area.
-
Subtensor Error Codes
How Subtensor error-code families help Bittensor readers interpret failed chain actions.
-
Subtensor Events
How Subtensor runtime events provide named records of Bittensor chain activity.
-
Subtensor Storage
How Subtensor runtime storage entries organize Bittensor chain state by runtime area.
-
Transaction Fees
How Bittensor distinguishes base chain transaction fees from swap fees tied to stake-related actions.