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
@@ -52,28 +47,18 @@ The governance system consists of three main actors working together:
52
47
-**Permissions**:
53
48
- Can vote on proposals submitted by allowed proposers
54
49
55
-
**Open Questions:**
56
-
57
-
- Q3: How to allow a triumvirate member to resign?
58
-
59
50
#### Economic and Building Collectives
60
51
61
52
-**Economic Collective**: Top 16 validators by total stake (including delegated stake) (configurable)
62
53
-**Building Collective**: Top 16 subnet owners by moving average price (with minimum age of 6 months) (configurable)
54
+
-**Total Collective Size**: 32 members (16 Economic + 16 Building)
63
55
-**Recalculation**: Membership refreshed every 6 months (configurable)
64
56
-**Permissions**:
65
57
- Can vote aye/nay on proposals submitted by allowed proposers and approved by Triumvirate
66
-
- More than 2/3 of aye vote for any collective fast tracks the proposal (next block execution) (threshold configurable)
67
-
- More than 1/2 of nay vote for any collective cancels the proposal (threshold configurable)
68
-
- Nays votes accumulate and delay the proposal execution exponentially until cancellation (see Delay Period section)
69
-
- Can replace a Triumvirate member every 6 months via single atomic vote (remove current holder + install replacement candidate, with rotating seat selection)
70
-
- Can mark himself as eligible for nomination to the Triumvirate
71
-
- Can accept a nomination to the Triumvirate
72
-
73
-
**Open Questions:**
74
-
75
-
- Q4: How to handle the nomination process?
76
-
- Q5: How to incentivize the collective members to vote?
58
+
- Votes are aggregated across both collectives (total of 32 possible votes)
59
+
- More than configured threshold of aye votes (based on total collective size of 32) fast tracks the proposal (next block execution) (threshold configurable)
60
+
- More than configured threshold of nay votes (based on total collective size of 32) cancels the proposal (threshold configurable)
61
+
- Delay is calculated using net score (nays - ayes) and applies exponential delay until cancellation (see Delay Period section)
77
62
78
63
### Governance Process Flow
79
64
@@ -102,91 +87,31 @@ The governance system consists of three main actors working together:
102
87
103
88
When a proposal has been approved by the Triumvirate, it is scheduled in 1 hour (configurable) and enters the "Delay Period" where the Economic and Building Collectives can vote to delay, cancel or fast-track the proposal.
104
89
105
-
1. Both collectives can vote aye/nay on the proposal
106
-
2. Delay is an exponential function of the number of nays votes, set to 2^n (configurable).
90
+
1. Both collectives can vote aye/nay on the proposal, with votes aggregated across all 32 collective members
91
+
2. Delay is calculated using **net score** (nays - ayes) and applies an exponential function based on a configurable delay factor.
107
92
108
93
- Initial delay is 1 hour (configurable).
109
-
- After 1 nays vote, the delay is 2^1 \* 1 hour = 2 hours.
110
-
- After 2 nays votes, the delay is 2^2 \* 1 hour = 4 hours.
111
-
- After 3 nays votes, the delay is 2^3 \* 1 hour = 8 hours.
112
-
- After 4 nays votes, the delay is 2^4 \* 1 hour = 16 hours.
113
-
- After 5 nays votes, the delay is 2^5 \* 1 hour = 32 hours.
114
-
- After 6 nays votes, the delay is 2^6 \* 1 hour = 64 hours.
115
-
- After 7 nays votes, the delay is 2^7 \* 1 hour = 128 hours.
116
-
- After 8 nays votes, the delay is 2^8 \* 1 hour = 256 hours.
117
-
- After 9 nays votes, proposal is cancelled (given we have a collective size of 16, hence more than 1/2 of the collective votes nay).
94
+
- Net score = (number of nays) - (number of ayes)
95
+
- If net score > 0: additional delay = initial_delay × (delay_factor ^ net_score)
96
+
- If net score ≤ 0: no additional delay (proposal can be fast-tracked if net score becomes negative)
97
+
-**Example with delay_factor = 2**:
98
+
- Net score of 1 (e.g., 1 nay, 0 ayes): delay = 1 hour × 2^1 = 2 hours
99
+
- Net score of 2 (e.g., 2 nays, 0 ayes): delay = 1 hour × 2^2 = 4 hours
100
+
- Net score of 3 (e.g., 3 nays, 0 ayes): delay = 1 hour × 2^3 = 8 hours
101
+
- Net score of 4 (e.g., 4 nays, 0 ayes): delay = 1 hour × 2^4 = 16 hours
102
+
- Net score of 5 (e.g., 5 nays, 0 ayes): delay = 1 hour × 2^5 = 32 hours
103
+
- Net score of 16 (e.g., 16 nays, 0 ayes): delay = 1 hour × 2^16 = 65,536 hours
104
+
- Net score of 17 (e.g., 17 nays, 0 ayes): proposal is cancelled (threshold configurable, typically ≥ 17 nays out of 32 total members)
118
105
119
106
3. If the delay period expires without cancellation: Proposal executes automatically
120
107
121
-
- The delay is calculated based on the collective with the most nays votes (i.e., if Economic has 3 nays and Building has 1 nay, the delay is based on 3 nays = 8 hours).
122
-
- More than 2/3 of aye vote for any collective fast tracks the proposal (next block execution) (threshold configurable)
123
-
- More than 1/2 of nay vote for any collective cancels the proposal (threshold configurable)
124
-
- Collective members can change their vote during the delay period. If changing a nay vote to aye reduces the delay below the time already elapsed, the proposal executes immediately.
125
-
-**Example**: A proposal has 3 nays votes, creating a 8 hours delay. After 5 hours have elapsed, a collective member changes their nay vote to aye, reducing the delay to 4 hours. Since 5 hours have already passed (more than the new 4 hours delay), the proposal executes immediately.
126
-
127
-
**Open Questions:**
128
-
129
-
- Q6: Should the voting be across both collectives or each collective votes independently? What if a collective decide to go rogue and fast track proposals that the other collective is against or vice versa?
108
+
- The delay is calculated based on the **net score** across both collectives (total of 32 members), not per collective
109
+
- More than configured threshold of aye votes (based on total collective size of 32) fast tracks the proposal (next block execution) (threshold configurable)
110
+
- More than configured threshold of nay votes (based on total collective size of 32) cancels the proposal (threshold configurable, typically ≥ 17 nays)
111
+
- Collective members can change their vote during the delay period. If changing a nay vote to aye (or vice versa) changes the net score such that the delay is reduced below the time already elapsed, the proposal executes immediately.
112
+
-**Example**: A proposal has net score of 3 (3 nays, 0 ayes), creating an 8 hour delay. After 5 hours have elapsed, a collective member changes their nay vote to aye, reducing the net score to 2 (2 nays, 1 aye) and the delay to 4 hours. Since 5 hours have already passed (more than the new 4 hours delay), the proposal executes immediately.
130
113
131
114
#### Execution
132
115
133
116
- Proposals executed automatically after the delay period if not cancelled or when fast-tracked by the collectives.
134
-
- If executing fails, the proposal is not retried and is cleaned up from storage.
135
-
136
-
### Triumvirate Replacement Mechanism
137
-
138
-
Each collective can replace one Triumvirate member every 6 months through a **single atomic vote**: the collective votes to replace the current seat holder with a randomly selected new candidate from the eligible candidates. If the vote succeeds, the replacement happens immediately. The Triumvirate always maintains exactly 3 active members.
139
-
140
-
#### Timing
141
-
142
-
- Each collective can initiate replacement vote every 6 months (configurable)
143
-
- Economic and Building collectives have independent cycles (seat are rotated independently)
144
-
145
-
**Open Questions:**
146
-
147
-
- Q7: How to have an emergency replacement vote?
148
-
- Q8: Can a replaced member be voted back in immediately, or should there be a cooldown period?
- Each collective maintains an independent rotation index that determines which seat they target:
154
-
- Economic Power automatically targets the next seat in rotation:
155
-
- If last removal was Seat 0, next automatically targets Seat 1
156
-
- If last removal was Seat 1, next automatically targets Seat 2
157
-
- If last removal was Seat 2, next automatically targets Seat 0
158
-
- Building Power has independent automatic rotation
159
-
- Rotation ensures no single seat is disproportionately targeted
160
-
- Collective members cannot choose which seat to target: it's determined automatically
161
-
162
-
#### Replacement Process (Single Atomic Vote)
163
-
164
-
The replacement happens in a single vote where the collective votes **both** to remove the current seat holder **and** to install a specific replacement candidate. This is an atomic operation: either both happen or neither happens.
165
-
166
-
**Process:**
167
-
168
-
1.**Eligibility Phase**: Collective members can mark themselves as eligible for nomination to the Triumvirate.
169
-
2.**Voting Phase**: Collective members can vote aye/nay during the voting period to replace the current seat holder.
170
-
- Threshold of more than 1/2 of the collective size (configurable)
0 commit comments