Proposal 136735 Review | Lorimer - CO.DELTA △
VOTE: Pending NO (but will re-evaluate tomorrow) NO
TLDR: Proposes to replace an UP (online) node with a DOWN (offline) node. The online node has been offline recently (such as when this proposal was submitted), but currently appears to be fine. Here’s an illustration of its recent failed block on the Node Provider Rewards dashboard.
Note that metrics are not shown for the last day or two, and are not available for nodes that are not assigned to subnets (the proposed replacement node).
At this current point in time, adopting this proposal will mean putting this subnet into a worse configuration than it’s already in. If that’s still the case when I check again tomorrow, I’ll reject.
Very similar to Proposal 136736 Review | Lorimer - CO.DELTA △
Country Discrepancies (1)
BDL, again, is exceptional in this case…
Node | Data Center | Claimed Country | According to ipinfo.io |
---|---|---|---|
inlh6 | Toronto 2 | Canada | United States of America (the) |
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
Smallest Distance | Average Distance | Largest Distance | |
---|---|---|---|
EXISTING | 548.162 km | 8357.742 km | 16348.372 km |
PROPOSED | 548.162 km | 8357.714 km | 17074.658 km (+4.4%) |
Subnet characteristic counts →
Continents | Countries | Data Centers | Owners | Node Providers | Node Operator | |
---|---|---|---|---|---|---|
EXISTING | 5 | 13 | 13 | 13 | 13 | 13 |
PROPOSED | 5 | 13 | 13 | 13 | 13 | 13 |
Largest number of nodes with the same characteristic (e.g. continent, country, data center, etc.) →
Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
---|---|---|---|---|---|---|
EXISTING | 5 | 1 | 1 | 1 | 1 | 1 |
PROPOSED | 5 | 1 | 1 | 1 | 1 | 1 |
See here for acceptable limits → Motion 135700
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)
-
Black dotted line connects to a small black marker that shows where the IP address indicates the node is located (according to
ipinfo.io
). This is only displayed if it conflicts with where IC records indicate the node is located. See Country Discrepancies section above for more info.
As a side note, this proposal leads to slightly worse decentralisation in terms of clustering within Europe , which can be seen visually on the map above. Continent isn’t a formal part of the IC Target Topology, but I’m sure it will be one day.
Node Changes
Action | Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
---|---|---|---|---|---|---|---|---|---|
Remove | ![]() |
||||||||
Add | 33s7q | DOWN | ![]() |
Europe | Isle of Man | Douglas 1 (im1) | Manx Telecom | Blue Ant LLC | 4isre |
Other Nodes
Node | Status | Continent | Country | Data Center | Owner | Node Provider | Node Operator | |
---|---|---|---|---|---|---|---|---|
o2q5i | UP | ![]() |
Oceania | Australia | Melbourne 2 (mn2) | NEXTDC | Icaria Systems Pty Ltd | l5lhp |
inlh6 | UP | ![]() |
North America | Canada | Toronto 2 (to2) | Cyxtera | Blockchain Development Labs | 4lp6i |
5oe2d | UP | ![]() |
Europe | Switzerland | Zurich 4 (zh4) | Nine.Ch | Tomahawk.vc | paxme |
sbjj4 | UP | ![]() |
Asia | Hong Kong | HongKong 1 (hk1) | Unicom | Pindar Technology Limited | vzsx4 |
pfmqh | UP | ![]() |
Asia | Japan | Tokyo (ty1) | Equinix | Starbase | cqjev |
ftgel | UP | ![]() |
Asia | Korea (the Republic of) | Seoul 2 (kr2) | Gasan | Web3game | 5dwhe |
zbzin | UP | ![]() |
Europe | Lithuania | Vilnius 2 (vl2) | Data Inn | George Bassadone | inluf |
pzdyu | UP | ![]() |
Europe | Sweden | Stockholm 1 (sh1) | Digital Realty | DFINITY Stiftung | lgp6d |
kjzcx | UP | ![]() |
Asia | Singapore | Singapore (sg1) | Telin | OneSixtyTwo Digital Capital | d4bin |
6ssdj | UP | ![]() |
Europe | Slovenia | Maribor (mb1) | Posita.si | Fractal Labs AG | 3xiew |
5i7he | UP | ![]() |
North America | United States of America (the) | Atlanta 2 (at2) | Datasite | BLP22, LLC | 5syyj |
qicnz | UP | ![]() |
Africa | South Africa | Gauteng 3 (jb3) | Xneelo | Wolkboer (Pty) Ltd | ymenq |
You may wish to follow the CO.DELTA known neuron if you found this analysis helpful.
CO.DELTA △
We’re a verifiably decentralised collective who review IC deltas (changes applied by NNS proposals). We follow a common code:
- Look: We observe the details and context of NNS proposals
- Test: We test and verify the claims made by those proposals
- Automate: We automate as much as possible by building increasingly sophisticated tools that streamline and strengthen the reviewal process.
Every vote cast by CO.DELTA is the result of consensus among diligent, skilled and experienced team members acting independently. The CO.DELTA neuron follows the vote of D-QUORUM on NNS topics that the CO.DELTA team does not handle directly. You can therefore follow CO.DELTA on all topics and rely on the highest quality of vote.
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.