You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/btcli/btcli.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -573,7 +573,7 @@ alias: regen_hotkey
573
573
This command regenerates the public part of a hotkey (hotkeypub.txt) for a wallet. Use this command when you need to move machine for subnet mining. Use the public key or SS58 address from your hotkeypub.txt that you have on another machine to regenerate the hotkeypub.txt on this new machine.
574
574
575
575
**Usage**
576
-
The command requires either a public key in hexadecimal format or an `SS58` address from the existing `hotkeypub.txt` from old machine to regenerate the coldkeypub on the new machine.
576
+
The command requires either a public key in hexadecimal format or an `SS58` address from the existing `hotkeypub.txt` from old machine to regenerate the hotkeypub on the new machine.
Copy file name to clipboardExpand all lines: docs/resources/glossary.md
-14Lines changed: 0 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,6 @@ A UID slot that is considered active within a specific subnet, allowing the asso
16
16
17
17
A metric that compares ALPHA tokens held by participants versus ALPHA tokens remaining in the AMM pool. ADR is calculated as the ratio of emissions to injections, measuring how much ALPHA goes to people (emissions) relative to how much is put into the pool (injections). A higher ADR means liquidation happens at a deeper discount to spot price. Under the current protocol, ADR tracks 2^(k - n), where k is the global TAO halving index and n is the subnet's ALPHA halving index.
18
18
19
-
**See also:**[Token Halvings Problem and Solution](../research/synchronized-halving.md), [Token Halvings Problem and Solution: FAQ](../research/halvings-problem.md)
20
-
21
19
### Archive Node
22
20
23
21
A type of public subtensor node that stores the entire blockchain history, allowing for full data access and querying capabilities.
@@ -274,7 +272,6 @@ A portion of the TAO emission received by the subnet miners when they provide va
274
272
275
273
A system that drives the behavior of subnet miners and governs consensus among subnet validators in a Bittensor subnet. Each subnet has one or more incentive mechanisms, which should be designed carefully to promote desired behaviors and penalize undesired ones. When multiple incentive mechanisms are used, each operates independently with separate bond pools for Yuma Consensus calculations, allowing subnet creators to distribute emissions across different types of work or evaluation criteria.
276
274
277
-
278
275
**See also:**[Anatomy of Incentive Mechanism](../learn/anatomy-of-incentive-mechanism.md), [Multiple Incentive Mechanisms Within Subnets](../subnets/understanding-multiple-mech-subnets), [Understanding Subnets](../subnets/understanding-subnets.md)
279
276
280
277
### Issuance
@@ -331,7 +328,6 @@ A data structure that contains comprehensive information about the current state
331
328
332
329
A feature that allows subnets to implement multiple independent evaluation systems within a single subnet. Each mechanism operates with its own bond pool for Yuma Consensus calculations, enabling subnet creators to distribute emissions across different types of work or evaluation criteria. Validators must evaluate miners separately for each mechanism, and miner performance in one mechanism does not affect their rating in another.
333
330
334
-
335
331
**See also:**[Multiple Incentive Mechanisms Within Subnets](../subnets/understanding-multiple-mech-subnets), [Anatomy of Incentive Mechanism](../learn/anatomy-of-incentive-mechanism.md)
336
332
337
333
### Miner Deregistration
@@ -608,7 +604,6 @@ A Bittensor subnet is an incentive-based competition market that produces a spec
608
604
609
605
**See also:**[Understanding Subnets](../subnets/understanding-subnets.md), [Working with Subnets](../subnets/working-with-subnets.md), [Create a Subnet](../subnets/create-a-subnet.md)
610
606
611
-
612
607
### Subnet Miner
613
608
614
609
The task-performing entity within a Bittensor subnet. A subnet miner is a type of node in a Bittensor subnet that is connected only to subnet validators. Subnet miners are isolated from the external world and communicate bidirectionally with subnet validators. A subnet miner is responsible for performing tasks given to them by the subnet validators in that subnet.
@@ -619,10 +614,8 @@ The task-performing entity within a Bittensor subnet. A subnet miner is a type o
619
614
620
615
The individual or entity responsible for defining the specific digital task to be performed by subnet miners, implementing one or more incentive mechanisms, and providing sufficient documentation for participation in the subnet. Subnet creators can configure multiple incentive mechanisms to distribute emissions across different types of work or evaluation criteria.
621
616
622
-
623
617
**See also:**[Create a Subnet](../subnets/create-a-subnet.md), [Subnet Creators btcli Guide](../subnets/subnet-creators-btcli-guide.md), [Multiple Incentive Mechanisms Within Subnets](../subnets/understanding-multiple-mech-subnets)
624
618
625
-
626
619
### Subnet Protocol
627
620
628
621
A unique set of rules defining interactions between subnet validators and miners, including how tasks are queried and responses are provided.
@@ -633,18 +626,14 @@ A unique set of rules defining interactions between subnet validators and miners
633
626
634
627
A component of an incentive mechanism that defines how subnet miners' responses are evaluated, aiming to align subnet miner behavior with the subnet's goals and user preferences. It is a mathematical object that converts miner responses into numerical scores, enabling continuous improvement and competition among miners. When multiple incentive mechanisms are used, each has its own scoring model for independent evaluation.
635
628
636
-
637
629
**See also:**[Anatomy of Incentive Mechanism](../learn/anatomy-of-incentive-mechanism.md), [Multiple Incentive Mechanisms Within Subnets](../subnets/understanding-multiple-mech-subnets), [Understanding Subnets](../subnets/understanding-subnets.md)
638
630
639
-
640
631
### Subnet Task
641
632
642
633
A key component of any incentive mechanism that defines the work the subnet miners will perform. The task should be chosen to maximize subnet miner effectiveness at the intended use case for the subnet. When multiple incentive mechanisms are used within a subnet, each mechanism can define different tasks for miners to perform.
643
634
644
-
645
635
**See also:**[Understanding Subnets](../subnets/understanding-subnets.md), [Anatomy of Incentive Mechanism](../learn/anatomy-of-incentive-mechanism.md), [Multiple Incentive Mechanisms Within Subnets](../subnets/understanding-multiple-mech-subnets)
646
636
647
-
648
637
### Subnet Weights
649
638
650
639
The importance assigned to each subnet determined by relative price among subnets and used to determine the percentage emissions to subnets.
@@ -969,10 +958,8 @@ The directory path where the generated Bittensor wallets are stored locally on t
969
958
970
959
A matrix formed from the ranking weight vectors of all subnet validators in a subnet, used as input for the Yuma Consensus module to calculate emissions to that subnet. When multiple incentive mechanisms are used, each mechanism has its own weight matrix for independent consensus calculations.
971
960
972
-
973
961
**See also:**[Yuma Consensus](../learn/yuma-consensus.md), [Consensus-Based Weights](../concepts/consensus-based-weights.md), [Multiple Incentive Mechanisms Within Subnets](../subnets/understanding-multiple-mech-subnets)
974
962
975
-
976
963
### Weight Vector
977
964
978
965
A vector maintained by each subnet validator, with each element representing the weight assigned to a subnet miner based on its performance. When multiple incentive mechanisms are used, validators maintain separate weight vectors for each mechanism.
@@ -981,7 +968,6 @@ The ranking weight vectors for each subnet are transmitted to the blockchain, wh
981
968
982
969
**See also:**[Consensus-Based Weights](../concepts/consensus-based-weights.md), [Yuma Consensus](../learn/yuma-consensus.md), [Multiple Incentive Mechanisms Within Subnets](../subnets/understanding-multiple-mech-subnets)
0 commit comments