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: bits/BIT-0006-Dissolution.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,32 +19,32 @@ While the "lolocaust" has been an effective way of dealing with unwanted/dangero
19
19
## Specification
20
20
21
21
- Addition of new governance capabilities to allow for senate members to create and vote on proposals that, should the proposal pass by a super-majority, will automatically dissolve a dTAO-subnet.
22
-
- Dissolution process would also need to include the forced fire-sale of outstanding dtao tokens back to TAO utalising the existing pool liquidity.
22
+
- Dissolution process would also need to include the forced fire-sale of outstanding dtao tokens back to TAO utilising the existing pool liquidity.
23
23
-- It is vital that the dtao fire-sale all done at the same price, completed in a manner that equalises the price impact among all eligible participants.
24
24
-- The applicable dTAO tokens in the subnet owner's wallet should be excluded from this fire-sale process ('burnt')
25
25
- To prevent bad actors from 'rugging' the subnet during the governance window, certain activities on the subnet should be frozen once the governance proposal is submitted
26
-
-- These include the LP (preventing buying/selling), token issueance (miner/vali/subnet owner rewards), and miner/vali registrations).
26
+
-- These include the LP (preventing buying/selling), token issuance (miner/vali/subnet owner rewards), and miner/vali registrations).
27
27
- To avoid abuse (unwarranted dissolution proposals), the governance proposer should be required to lock an amount of tao equal to the registration cost of the subnet.
28
-
- Due to the lack of a "No with Veto" mechanic, voting results would need to accommoate three outcomes (Yes/Split Vote/No
28
+
- Due to the lack of a "No with Veto" mechanic, voting results would need to accommodate three outcomes (Yes/Split Vote/No
29
29
-- Yes (66% Super Majority in support): Subnet is dissolved, locked tokens returned to proposer
30
30
-- Split Vote (34% - 65% in support): Subnet is not dissolved, locked tokens returned to proposer
31
31
-- No (33% or less in support): Subnet is not dissolved, locked tokens are recycled
32
32
33
33
## Rationale
34
34
35
-
Subnets being used to distribute malicious or illicit material (malware, CSAM, etc) pose an exestensial risk to the entire network. It is vital that the network have a manner in which to remove these threats. Additionally, should certain subnets become abandoned, it may be necessary to remove these abandoned subnets to reduce unneccessary chain bloat/overhead.
35
+
Subnets being used to distribute malicious or illicit material (malware, CSAM, etc) pose an existential risk to the entire network. It is vital that the network have a manner in which to remove these threats. Additionally, should certain subnets become abandoned, it may be necessary to remove these abandoned subnets to reduce unnecessary chain bloat/overhead.
36
36
37
37
## Backwards Compatibility
38
38
39
-
It is unknown whether the introduction of additional capabilities to the governance module (including integrating with locking tokens when submitting a dissolution proposal) may have backwards compatiblity issues with the existing governance framework.
39
+
It is unknown whether the introduction of additional capabilities to the governance module (including integrating with locking tokens when submitting a dissolution proposal) may have backwards compatibility issues with the existing governance framework.
40
40
41
41
## Reference Implementation (Optional)
42
42
43
-
The Cosmos SDK provides a wellknown example of governance proposals requiring a deposit, which is then burnt in the event of a "No with Veto" outcome
43
+
The Cosmos SDK provides a well-known example of governance proposals requiring a deposit, which is then burnt in the event of a "No with Veto" outcome
44
44
45
45
## Security Considerations
46
46
47
-
The existance of a dissolution procedure is not a panacea against abuse. Senate members may have vested interests (or lack of interest in voting) that may prevent the successful dissolution of a subnet where it may be otherwise needed. However, this is always a risk in any decentralised ecosystem and relies on network participants showing wisdom in selecting which validator to delegate to.
47
+
The existence of a dissolution procedure is not a panacea against abuse. Senate members may have vested interests (or lack of interest in voting) that may prevent the successful dissolution of a subnet where it may be otherwise needed. However, this is always a risk in any decentralised ecosystem and relies on network participants showing wisdom in selecting which validator to delegate to.
0 commit comments