This topic is intended to capture Subnet Management activities over time for the gmq5v subnet, providing a place to ask questions and make observations about the management of this subnet.
At the time of creating this topic the current subnet configuration is as follows:
DFINITY will submit an NNS proposal today to reduce the notarization delay on the subnet, gmq5v, similar to what has happened on other subnets in recent weeks (you can find all details in this forum thread).
Voted to adopt Proposal 133140. This proposal is intended to reduce network latency by reducing the notarization delay from 600ms to 300ms for subnet gmq5v, as has now happened for the majority of application subnets.
Voted to adopt proposal 133140. Similar to recent proposals that have been made targeting application subnets like gmq5v to reduce the notarization delay from 600ms to 300ms according to roadmaps established.
Voted to adopt proposal 134181, as the reasoning is sound and the description matches the payload. This proposal replaces 2 healthy nodes, both of which appear as “Active” on the IC dashboard. The proposed change improves decentralisation with respect to country and brings the target topology parameters to within the requirements.
TLDR: I’m planning to adopt. This is another great proposal! It brings this subnet in line with the formal IC Target Topology, by reducing the max number of nodes per country from 4 to 2 (see ‘Decentralisation Stats’ below for more detail).
Motivation:
replacing node j3wos-4uumz-er7pq-m7fc3-nqm4c-lx64b-h4jp4-gipdn-5osxc-wtbox-sqe to optimize network topology
replacing node fcfcb-mfjxb-72qbc-ekzgu-3kd2y-lbbtn-eu5wu-wi47e-ns4k5-wwgyt-eae to optimize network topology
2 removed US nodes replaced with nodes in South Korea and Singapore.
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
Smallest Distance
Average Distance
Largest Distance
EXISTING
95.554 km
5802.849 km
11093.984 km
PROPOSED
95.554 km
6475.831 km (+11.6%)
15377.131 km (+38.6%)
This proposal slightly increases decentralisation, considered purely in terms of geographic distance (and therefore there’s a slight theoretical increase in localised disaster resilience).
Subnet characteristic counts →
Continents
Countries
Data Centers
Owners
Node Providers
Node Operator
EXISTING
3
9
13
13
13
13
PROPOSED
3
11 (+18.2%)
13
13
13
13
This proposal slightly improves decentralisation in terms of jurisdiction diversity.
Largest number of nodes with the same characteristic (e.g. continent, country, data center, etc.) →
The above subnet information is illustrated below, followed by a node reference table:
Map Description
Red marker represents a removed node (transparent center for overlap visibility)
Green marker represents an added node
Blue marker represents an unchanged node
Highlighted patches represent the country the above nodes sit within (red if the country is removed, green if added, otherwise grey)
Light grey markers with yellow borders are examples of unassigned nodes that would be viable candidates for joining the subnet according to formal decentralisation coefficients (so this proposal can be viewed in the context of alternative solutions that are not being used)
Known Neurons to follow if you're too busy to keep on top of things like this
If you found this analysis helpful and would like to follow the vote of the LORIMER known neuron in the future, consider configuring LORIMER as a followee for the Subnet Management topic.
Another good neuron to follow is Synapse (follows the LORIMER and CodeGov known neurons for Subnet Management, and is a generally well informed known neuron to follow on numerous other topics)
Voted to adopt proposal 134181. The proposal replaces two nodes from subnet gmq5v:
Removed Nodes: j3wos, fcfcb.
Added Nodes: g46et and 6rib4.
The proposal was verified using the DRE tool to verify the metrics stated. All nodes replaced are healthy but this replacements improve the network topology on the country` metric by reducing the number of nodes in the US from 4 to 2.
Voted to adopt proposal 134276. The proposal seeks to remove a cordoned node from the subnet and specifies that the associated data centre is being offboarded “after 48 months”. Decentralisation parameters are improved with respect to country. The necessary context is provided by this forum post and associated discussion. For future proposals of this type I recommend that the background context be included in the proposal text for ease of verification.
Voted to adopt proposal 134276. This proposal is part of a sequence of steps to remove cordoned nodes from subnets as the associated data centeres are being offboarded after 48 months of their respective DC contracts that are still private and were signed up before the Genesis. There is a great and detailed explanation of this changes in this forum post and the forum thread it is in. In the wiki there is a series of Steps for Gen-1 Node onboarding after 48 months that need to be followed in order for the nodes to continue earning rewards which starts by making a forum post in the following thread. As we can verify no one as come forward with nodes from the DCs in this proposals so I don’t see any issues with the removal of this nodes.
A new proposal with id 134486 has been submitted for this subnet.
Click here to open proposal details
Replace nodes in subnet gmq5v
Motivation:
replacing dead node g46et-p24p2-vxbkf-woqqn-edgld-z4iif-5fcd6-a2beb-puqvu-l3wpq-sqe
replacing node jlb2x-vto3e-r2yf4-adrqu-3gult-4fpun-besaz-4nynm-gcmht-nziru-lae to optimize network topology
Calculated potential impact on subnet decentralization if replacing:
1 additional node would result in: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.2575 to 2.3219
Based on the calculated potential impact, replacing 1 additional nodes to improve optimization
Note: the heuristic for node replacement relies not only on the Nakamoto coefficient but also on other factors that iteratively optimize network topology.
Due to this, Nakamoto coefficients may not directly increase in every node replacement proposal.
Code for comparing decentralization of two candidate subnet topologies is at: dre/rs/decentralization/src/nakamoto/mod.rs at 79066127f58c852eaf4adda11610e815a426878c · dfinity/dre · GitHub
This proposal replaces node g46et which appears in the dashboard as “Status: Offline”, along with an additional node in order to improve overall topology. As shown in the proposal, decentralisation parameters are improved with respect to country and remain within the requirements of the target topology.
The proposal replaces dead Offline status node g46et from Seoul2 Korea, and healthy Active status node jlb2x from Geneva Switzerland, in order to optimize network topology. This improves decentralization.
TLDR: I’ve voted to adopt this proposal, as it improves decentralisation metrics (see decentralisation stats below).
However it will very likely need to be followed up with another proposal, given that one of the nodes being added to the subnet is actually DOWN (as pointed out by @ZackDS above). Given that this proposal also removes a DOWN node from the subnet, the number of UP nodes would remain unchanged. Rejecting this proposal would impose an unwarranted cost to the proposing neuron (it doesn’t worsen the subnet).
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
Smallest Distance
Average Distance
Largest Distance
EXISTING
95.554 km
6292.975 km
15377.131 km
PROPOSED
477.324 km (+399.5%)
7545.121 km (+19.9%)
16759.085 km (+9%)
This proposal slightly increases decentralisation, considered purely in terms of geographic distance (and therefore there’s a slight theoretical increase in localised disaster resilience).
Subnet characteristic counts →
Continents
Countries
Data Centers
Owners
Node Providers
Node Operator
EXISTING
3
12
13
13
13
13
PROPOSED
4 (+25%)
13 (+7.7%)
13
13
13
13
This proposal improves decentralisation in terms of jurisdiction diversity.
Largest number of nodes with the same characteristic (e.g. continent, country, data center, etc.) →
The above subnet information is illustrated below, followed by a node reference table:
Map Description
Red marker represents a removed node (transparent center for overlap visibility)
Green marker represents an added node
Blue marker represents an unchanged node
Highlighted patches represent the country the above nodes sit within (red if the country is removed, green if added, otherwise grey)
Light grey markers with yellow borders are examples of unassigned nodes that would be viable candidates for joining the subnet according to formal decentralisation coefficients (so this proposal can be viewed in the context of alternative solutions that are not being used)
You may wish to follow D-QUORUM if you found this analysis helpful.
Known Neurons to follow if you're too busy to keep on top of things like this
If you found this analysis helpful and would like to follow the vote of the LORIMER known neuron in the future, consider configuring LORIMER as a followee for the Subnet Management topic.
Additional good neurons to follow:
D-QUORUM (a highly decentralized neuron that follows neurons that have been elected by the NNS)
Synapse (currently follows the LORIMER and CodeGov known neurons for Subnet Management, and is a generally well informed known neuron to follow on numerous other topics)
CodeGov (actively reviews and votes on Subnet Management proposals, and is well informed on numerous other technical topics)
WaterNeuron (the WaterNeuron DAO frequently discuss proposals like this in order to vote responsibly based on DAO consensus)
Note that this analysis involved data provided by the IC-API, which is not open source. I’m in the process of switching over to more verifiable sources of this sort of information for future proposal reviews. See here for related discussion.
The proposal replaces two node on subnet gmq5v:
Removed nodes: dead node g46et, status Offline and node jlb2x, status Active.
Added nodes: node sjtwn, status Awaiting and node jbgo7, status Awaiting.
Although previous reviewers have verified that the node jbgo7 which is being added is Offline as since returned to a status of Awaiting in the Dashboard.
The active node jlb2x is being removed in order to improve decentralization coefficients in the subnet specifically the country metric reducing the number of nodes in CH from 2 to 1.
