Vote: Adopted Reason:
The proposal removes healthy Active status API Boundary node cjdpl from the AW1 DC in Pennsylvania part of US East region, from NP Bigger Capital that needs to be redeployed as part of the post-48-month transition requirements that can be found here.
Vote: Adopted Reason:
The proposal adds unassigned healthy Awaiting status node gvqb5 from the TO1 DC in Toronto part of US East region, from NP 0X52 that will replace the previously removed API Boundary node cjdpl.
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron’s Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralization of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
Proposal: 135593
Vote: ADOPT
Title: Remove 1 API boundary node(s)
Proposal: 135594
Vote: ADOPT
Title: Add 1 API boundary node(s)
Comments: These proposals were adopted by the CodeGov known neuron at the recommendation of one of our CodeGov team members, @ZackDS, after he reviewed the proposal and posted his review here.
About CodeGov
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron’s Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralization of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
Proposal #136566 turns node jlifv into an API BN to replace tcln7. The node has both an IPv4 address, as well as a correctly configured domain name and can therefore be used as API BN.
These two proposals replace API boundary node tcln7, appearing as “Offline” in the IC dashboard, with node jlifv, which appears in the dashboard as “Awaiting”.
Both nodes are from South Africa, so the geographical distribution of API boundary nodes is essentially unchanged.
The node provider and data centre owner for the replacement node are not already represented in the current API boundary nodes.
Using the ic-admin tool it can be seen that the replacement node has an IPv4 address and a domain name.
About CodeGov
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neurons’ Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralisation of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron’s Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralization of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.
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.
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.
TLDR: Removes 1 offline API Boundary Node which is replaced by a separate open proposal, a review for which will be posted shortly. See combined outcome analysis in the following posts.
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 API boundary nodes (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.
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.
TLDR: This proposal adds a new API boundary node, given the removal of an offline one by proposal 136565. See combined outcome analysis in the following post.
IPv4 + Domain confirmed →
dig +short node2.jb3.wolkboer.co.za A
102.221.177.171
@rbirkner I noted that the node being added is on a different replica version to the other API boundary nodes. Not really an issue, as replica deployments to boundary nodes are staggered anyway (but may be worth upgrading it shortly after this proposal for consistency).
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 API boundary nodes (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.
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.
This review looks at the combined effect of both proposals described above. Though they’re not executed atomically, they both relate to one another in that they take the API boundary nodes to a new topology configuration. →
TLDR: LGTM, the geographics distribution of API boundary nodes is unaffected by these two proposals if they’re both executed successfully.
I note however that there are numerous replica nodes on other continents where there are currently no API boundary nodes. My analysis indicated that there are no suitable nodes nearby for becoming API boundary nodes (hence why they don’t show up on the map below as yellow dots). This means it’s not currently possible to satisfy these criteria →
But I gather that this is a work in progress, and I’m looking forward to seeing this evolve over time towards the desired state.
Decentralisation Stats
API Boundary Node distance stats (distance between any 2 API Boundary Nodes) →
Smallest Distance
Average Distance
Largest Distance
EXISTING
0 km
7919.197 km
16960.232 km
PROPOSED
0 km
7917.628 km
16943.318 km (-0.1%)
API Boundary Node characteristic counts →
Continents
Countries
Data Centers
Owners
Node Providers
Node Operator
EXISTING
4
10
19
15
17
19
PROPOSED
4
10
19
15
17
19
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
8
6
2
3
3
2
PROPOSED
8
6
2
3
3
2
@rbirkner, is there anything similar to the IC Target Topology, but for API boundary nodes as opposed to subnets? e.g. something like Motion 135700
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 API boundary nodes (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.
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.
Reason:
The proposal replaces dead Offline status API Boundary Node tcln7 from Guateng, South Africa with unassigned healthy Awaiting status node jlifv from same location, different DC without any change to decentralization. The new node has ipV4 address set 102.221.177.171 and an associated domain name node2.jb3.wolkboer.co.za.
About CodeGov
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these technical topics. We also have a group of Followees who vote independently on the Governance and the SNS & Neuron’s Fund topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralization of SNS projects such as WaterNeuron, KongSwap, and Alice with a known neuron and credible Followees.
Learn more about CodeGov and its mission at codegov.org.