Internet Computer Wiki - User contributions [en]

File:NEW 25 08 Compliance Assesment Bianca Martina Rohner signiert.pdf

2025-09-05T14:48:40Z

Tina23:

Date corrected compliance assessment

Bianca-Martina Rohner

2025-09-04T11:11:02Z

Tina23: Inserting compliance assessment

== Self-declaration ==
SHA256 hash: ca3973712c4d7947b0b835368ca0648696d52ff6e7ed69a7c92766c1da51e0ce
[[File:BMR self declaration.pdf|center|thumb|1133x1133px|

]]

== Identity document ==
SHA 256 hash: 2c1fa30253103788b7c6510bb1fc66fd4e11b9e9df163ec936c9a460b377ade2

[[File:BMR identity proof.pdf|center|thumb|1133x1133px]]

== Candidate Node Validation ==

Panama node machines
[[File:Optimization Model Panama.pdf|center|thumb|1132x1132px|Optimization Model Panama]]Compliance Assessment
[[File:25 07 Compliance Assesment Bianca Martina Rohner signiert.pdf|thumb|Compliance assessment]]

File:25 07 Compliance Assesment Bianca Martina Rohner signiert.pdf

2025-09-03T17:45:08Z

Tina23:

Compliance assessment by the auditor.

Bianca-Martina Rohner

2025-09-03T06:37:23Z

Tina23: Uploading my compliance assessment from the auditors as instructed.

Node Provider Onboarding

2024-03-12T11:04:33Z

Tina23: Seems 6.1. is outdated, added the new command

Learn how to be accepted by the NNS as a Node Provider and onboard your nodes to the IC.

Please allocate up to a week to complete this guide, as it may take several days for a proposal to be accepted by the NNS, and you may have to submit multiple NNS proposals.

'''Note that the following steps do not need to be performed on the node machine itself.''' You can complete them on your personal laptop.

If you encounter issues through any of these steps, check the [[Node Provider Troubleshooting]] page. If that does not solve your problem, you are encouraged to ask for assistance in the [[Node Provider Matrix channel]].

For regular operations after onboarding, please refer to [[Node Provider Maintenance Guide]]

❗️❗️❗️DFINITY does ''not'' offer live support for Node Providers attempting to onboard nodes.

'''''<big>Requirements</big>'''''
* [[Node Provider Machine Hardware Guide]]
* [[Node Provider Networking Guide]]
* [https://www.ledger.com/ Hardware wallet]
* [https://shop.nitrokey.com/shop/product/nkhs2-nitrokey-hsm-2-7/ NitroKey HSM] (Optional, legacy—not recommended)
* 11 ICP (10 of which are to be staked for the NNS proposal deposit)
* Basic understanding of [[Neurons 101|neurons]], [https://internetcomputer.org/docs/current/tokenomics/nns/nns-staking-voting-rewards staking], and [[Governance of the Internet Computer|governance]] proposals. For instance, understanding what it means to stake a neuron for 8 years.

== 1. Install the required tools ==
===''' A. Install ic-admin '''===

<code>ic-admin</code> is the tool used to create and submit NNS proposals.

==== MacOS ====
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/7445081734e6d896d090295967d50710975c4f25/openssl-static-binaries/x86_64-darwin/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo 3f75026d2f28f171068e332a42c82a2795c93fbf5ab351baef30b30eb901cdba) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

==== Linux ====
NOTE: The instructions below have been tested with the Ubuntu 20.04 release.
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/7445081734e6d896d090295967d50710975c4f25/openssl-static-binaries/x86_64-linux/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo e29bb9cc462e800b8b960ad49c412e5f5fdbb5ae2ae9fde0c13058422ba32802) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

===''' B. Install dfx '''===

#<code>dfx</code> is used to generate neuron hotkeys, among other things <syntaxhighlight lang="shell">
$ sh -ci "$(curl -fsSL https://smartcontracts.org/install.sh)"

</syntaxhighlight>
#Verify that dfx is up to date. <syntaxhighlight lang="shell">
$ export PATH=$HOME/bin:$PATH
$ dfx upgrade
$ dfx --version
</syntaxhighlight>

==2. Create Node Provider hotkey ==

#Create an identity for the Node Provider '''Hotkey''' <syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node-provider-hotkey

Created identity: "node-provider-hotkey".

$ dfx --identity node-provider-hotkey identity get-principal

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# example node-provider-hotkey: wuyst-x5tpn-g5wri-mp3ps-vjtba-de3xs-w5xgb-crvek-tucbe-o5rqi-mae

</syntaxhighlight>'''You will need the Node Provider hotkey in the next steps.''' Note: you may be prompted to enter a passphrase when creating your identity and accessing your identity principal. Take note of the passphrase you choose.

'''Note:''' The Node Provider hotkey is NOT the Node Provider principal. This is the hotkey that is used for the NNS proposal submissions only.

==3. Create and Manage Neuron via NNS Frontend Dapp and Internet Identity==

#Send at least 11 ICPs to your hardware wallet address.
#Navigate to Neurons tab and create a Neuron by staking at least 10 ICP from your hardware wallet. Staking more ICP works as well, but 10 is the minimum to stake a neuron, and you must have a little more for transaction fees.
#IMPORTANT! Confirm the transaction on your hardware wallet.
#:[[File:-docs-stake_neuron_1.png|1024px|stake neuron]]
#After the Neuron has been created successfully, confirm to "Add NNS Dapp as hotkey" in the dialogue and on your hardware wallet, and close the dialog after the action completes.
#:[[File:-docs-stake_neuron_2.png|1024px|neuron id]]
#Set the dissolve delay to at least 6 months, and confirm the choice in the dialogue and on your hardware wallet. After the action completes, you can close the "Follow Neurons".
#:[[File:dissolve_delay.png|480px|neuron id]]
#You will now see a Neuron listed with its ID. Copy the Neuron ID, since you will need it in the next steps to place the necessary proposals.
#:[[File:Neuron id.png|1024px]]

==4. Add hotkeys==

#Select the Neuron you just created to open Neuron management view and press “Add hotkey” button.
#:[[File:Hotkey 1.png|873x873px]]
# A dialog will pop up where you can enter the hotkey you generated in step 2.1 (output from command <code>dfx --identity node-provider-hotkey identity get-principal</code>). This will allow you to submit NNS proposals using <code>ic-admin</code> and will not be used for anything else. 
#:Press the '''confirm''' button and confirm the transactions on your hardware wallet. 
#:[[File:Hotkey 2.png|899x899px]]
#Get the Ledger Hardware Wallet Principal Id: Navigate back to ICP page and select your Ledger hardware wallet account. You will need to use this Ledger Hardware Wallet principal as the Node Provider principal in order to get the rewards directly into the secure hardware wallet.
#:[[File:Node provider principal 1.png|1024px]]
#:[[File:Node provider principal 2.png|800px]]
#Copy and save this Node Provider principal by clicking on the copy icon after the principal id. You'll need it in the next steps. <syntaxhighlight lang="shell">
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# Input ledger Hardware Wallet principal, from the NNS FrontEnd dapp https://nns.ic0.app/

# example: $ NODE_PROVIDER_PRINCIPAL=fharn-5vyi2-4xb4a-64yyi-3jpmj-pga23-mxy25-d5uim-fqcro-eoefh-tae
</syntaxhighlight>

==5. Choose onboarding path (HSM vs no HSM)==
Onboarding '''without''' a NitroKey HSM is the recommended onboarding path. If you will not be using a NitroKey HSM, continue to the next step.

If the legacy procedure is necessary, follow the [[NitroKey HSM onboarding instructions]] and '''return to step 8.'''

==6. Setup the Node Operator keys ==
#'''''Ensure dfx is at least version 0.14.''''' Node Operator keys created with older versions of dfx '''will fail to join the IC'''. Run:<syntaxhighlight lang="bash">
$ dfxvm update
$ dfx --version
</syntaxhighlight>
#Create a new principal with dfx:<syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node_operator
</syntaxhighlight>
#Confirm <code>node_operator</code> identity was created successfully:<syntaxhighlight lang="shell">
$ dfx identity list
</syntaxhighlight>This list ''should'' contain <code>node_operator</code>.
#Copy new key to a known location:<syntaxhighlight lang="shell">
$ cp ~/.config/dfx/identity/node_operator/identity.pem ./node_operator_private_key.pem
</syntaxhighlight>
#Check the contents of the <code>node_operator_private_key.pem</code> file and double check that it contains the following contents. It is imperative that the first line has <code>-----BEGIN EC PRIVATE KEY-----</code>. If it does not, make sure you use the latest <code>dfx</code> version and that you followed the instructions precisely.<syntaxhighlight lang="shell">
❯ cat ./node_operator_private_key.pem
-----BEGIN EC PRIVATE KEY-----
[3 lines of base64 encoded private key, e.g. n2Nhp68YcQpuS0u96r...]
-----END EC PRIVATE KEY-----
</syntaxhighlight>Note: you must retain access to the <code>node_operator_private_key.pem</code> file for when you onboard nodes in '''[https://wiki.internetcomputer.org/wiki/Node_Provider_Roadmap#Milestone_Five:_Node_Machine_Onboarding roadmap milestone five.]'''

==7. Get the node operator principal==

#Get the principal:<syntaxhighlight lang="shell">
$ NODE_OPERATOR_PRINCIPAL=$(dfx --identity node_operator identity get-principal)
$ echo $NODE_OPERATOR_PRINCIPAL

uqquy-76uhn-2mys5-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
</syntaxhighlight>
'''You will need the node operator principal in the next steps.'''

==8. Register your Node Provider principal to the network==
In the next codeblock:
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend Dapp (step 4.4)
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6)

*'''''IMPORTANT:''''' Please make sure that you also update the <code>--summary</code> and include a link to the forum discussion, your company's web page, and/or to another place that can convince the voting community that you are making a legitimate request. You must also include the file hash for the [[Node Provider Self-declaration|self declaration and proof of identity documents]], or the proposal will be rejected. This way you will avoid the community voting NO to your proposal and you losing your staked ICPs.

#Create the Proposal <syntaxhighlight lang="shell">
$ NODE_PROVIDER_NAME="My Company"
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-or-remove-node-provider add \
--proposer $NEURON_ID \
--proposal-title "Register a node provider '${NODE_PROVIDER_NAME}'" \
--summary "Register a node provider '${NODE_PROVIDER_NAME}', in line with the announcement and discussion at <https://forum.dfinity.org/t/...>. The self-declaration documentation is available at <https://wiki.internetcomputer.org/wiki/...> with SHA256 hash <SHA256>. The proof of identity is available at <https://wiki.internetcomputer.org/wiki/...> with SHA256 hash <SHA256>." \
--node-provider-pid "$NODE_PROVIDER_PRINCIPAL"
</syntaxhighlight>
#Find the proposal on https://dashboard.internetcomputer.org/governance and '''wait until it is executed before proceeding to next step.'''
#In order to expedite the speed of your proposal's approval, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1nKy5hKiF72a4NCHvpgij-Np9pbtR5KOBbF1W6qr-nds/edit?usp=sharing template] for the post.
==9. Register your datacenter to the network (if necessary)==
#Search for your data center on https://dashboard.internetcomputer.org/centers.
#*If you found the datacenter that is hosting your nodes, remember its ID, and skip the following section. Otherwise, proceed with the registration of a new DC record.
#:[[File:dc_id.png|1041x1041px|alt=]]
===Create a data center record for a new DC===
In the next block of code:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6)
*Replace the JSON fields from the <code>–data-centers-to-add</code> argument and their corresponding values in <code>--summary</code>:
**<code>"id"</code> represents the city that your datacenter is in and is formulated as a combination of two letters representing the city and an incrementing number. Search data center IDs on https://dashboard.internetcomputer.org, and find a combination of two letters and a number that’s not yet registered. Examples:
***dl1 (Dallas, no IDs with “dl” prefix)
***zh10 (Zurich, numbers 0-9 are already registered)
**:[[File:dc_id.png|1024px]]
**<code>"region"</code> represents the local region of a datacenter and is formulated as a three-part string divided by commas. The three parts making the string are continent, country code, and region, in the given order. Examples:
***North America,US,Florida
***Europe,DE,Bavaria
***Asia,SG,Singapore
**:[[File:datacenter_region.png|1024px]]
**<code>"owner"</code> The entity that provides your datacenter facilities.
***Search https://dashboard.internetcomputer.org for existing data center providers.
*** If there’s match, make sure you use the same exact some name for your datacenter.
***Otherwise, name the data center owner to your best knowledge.
**:[[File:datacenter_owner.png|1024px]]
**<code>"gps"</code> GPS coordinates.
***Find your datacenter on https://www.google.com/maps/.
***Right click on location, and select the GPS coordinates (first item in the menu) in order to copy them.
**:[[File:maps.png|310x310px|alt=Getting GPS coordinates|Getting GPS coordinates]]

#Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-or-remove-data-centers \
--summary "Register a Flexential datacenter as dl1 in North America,US,Texas" \
--skip-confirmation \
--proposer $NEURON_ID \
--data-centers-to-add '{
"id": "dl1",
"region": "North America,US,Texas",
"owner": "Flexential",
"gps": [
33.00803, -96.66614
]
}'
</syntaxhighlight>'''Remember to replace all the values of both the arguments <code>–data-centers-to-add</code> and <code>--summary</code>'''
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.
#In order to expedite the speed of your proposal's approval, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1Hg0tI9O5__Tp4qKrNKuTADsQT7Z47I6aAFXbiDimG_U/edit?usp=sharing template] for the post.

==10. Create a node operator record==
'''''IMPORTANT''':'' Before submitting the Node Operator record, please go through the description of [[Validation of Candidate Node Machines]] to validate whether additional node machines are needed for decentralization of the IC-network.

* Create a pdf with the outcome of running the optimization model and the steps that allow the community to reproduce the validation check.
* Include the pdf in the wiki page that includes the NP documents (self-declaration and proof-of-identity document)
* Include a link to the pdf as well as the hash of the document in the Node Operator record proosal.

In the next codeblock:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 3.6).
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend Dapp (step 4.4).
*Replace the <code>NODE_OPERATOR_PRINCIPAL</code> value with your node operator principal (step 7.1). '''Important''': if you are adding an additional node operator record because you will deploy nodes in another data center, please make sure to create a new node operator principal first (steps 6 and 7). A node operator principal can only be tied to 1 data center.
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_ALLOWANCE</code> variable value with number of nodes you are providing.
* Replace the <code>DC_ID</code> variable value with id of your datacenter.

# Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_OPERATOR_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_PROVIDER_NAME="My Company"
$ NODE_ALLOWANCE=8
$ DC_ID=dl1

$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-node-operator \
$NODE_PROVIDER_PRINCIPAL \
--summary "Node provider '$NODE_PROVIDER_NAME' is adding $NODE_ALLOWANCE nodes in the $DC_ID data center. The result of the canidate node machine validation and exact configuration run is available at <https://wiki.internetcomputer.org/wiki/...> with SHA256 hash <SHA256>." \
--proposer $NEURON_ID \
--node-operator-principal-id $NODE_OPERATOR_PRINCIPAL \
--node-allowance $NODE_ALLOWANCE \
--dc-id $DC_ID
</syntaxhighlight>
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.

Node Provider Matrix channel

2024-03-01T08:57:05Z

Tina23:

There is an open Matrix room (channel) that is intended to be a forum for potential and existing Node Providers as well as anybody else who would like to follow the node provider discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org

The runs on the open, public, and decentralized Matrix network. Matrix [https://matrix.org/clients/ has many clients] you can use. One of the popular clients is element.io, which is very similar to Slack, and offers a web UI, a [https://element.io/download desktop app], and a mobile app.

We strongly recommend that you add [https://ems-docs.element.io/books/element-cloud-documentation/page/element-settings an email address in the Element Profile settings] and to [https://element.io/help#settings3 enable notifications for missed messages].

If you are a Node Provider, please also add your Node Provider contact details on the Matrix room, to facilitate communication.
{| class="wikitable"
|+
!Node Provider Name
!Node Provider Id
!DC list
!Matrix aliases
|-
|1G
|7k7b7-4pzhf-aivy6-y654t-uqyup-2auiz-ew2cm-4qkl4-nsl4v-bul5k-5qe
|fm1
|
|-
|43rd Big Idea Films
|sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe
|hu1
|John Harris
|-
|87m Neuron, LLC
|eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe
|pl1, dl1, lv1
|
|-
|9Yards Capital
|spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe
|jv1, ch2, ny1
|
|-
|ACCUSET SOLUTIONS
|cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe
|gn1
|sagcryptoicp
|-
|Adam Dymecki
|n32q7-33lmk-m33tr-o5ltb-po6cb-tqqrr-2x6wp-pzhw7-ymizu-o3fyp-sqe
|
|
|-
|A Dog's Boutique, LLC
|uvawj-nnt3i-4ch3a-hruy4-hyfjn-7owvl-wgkli-uq2hd-e6lkq-v4b2o-4ae
|
|
|-
|Allusion
|rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae
|an1, br1, br2
|<nowiki>Paul De Cannière (Allusion), Roald | Aviate Labs, Louise Velayo | Aviate Labs</nowiki>
|-
|Anonstake
|kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae
|
|
|-
|ANYPOINT PTY LTD
|fwnmn-zn7yt-5jaia-fkxlr-dzwyu-keguq-npfxq-mc72w-exeae-n5thj-oae
|
|
|-
|Archery Blockchain SCSp
|7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe
|
|
|-
|Arjay LLC
|l2kri-jarwr-7whc4-pjdpn-n6hlb-45ltr-l6ghm-twttl-pcsvt-rynko-dqe
|
|
|-
|Artem Horodyskyi
|diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe
|bt1, li1, ma1, pa2, rg3, ta2, wy1
|ar-111
|-
|Aspire Properties
|2byzn-q2crt-hgczo-eruff-6p7af-pemor-n2z4z-6d2sd-wvdqa-yqvxb-mqe
|
|
|-
|Bigger Capital
|7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe
|me3, aw1
|Dallas W
|-
|Bitmoon
|mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe
|
|
|-
|Blockchain Development Labs
|7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae
|to1, to2, bc1
|@injectedfusion:matrix.org
|-
|BlockTech Ventures, LLC
|ks7ow-zvs7i-ratdk-azq34-zio2b-gbekj-qjicg-pfhp3-ovhgu-k5qql-dae
|
|
|-
|BLP22, LLC
|sma3p-ivkif-hz7nu-ngmvq-ibnjg-nubke-zf6gh-wbnfc-2dlng-l3die-zqe
|
|
|-
|Bohatyrov Volodymyr
|dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae
|bn1,ba1,ma1,rg3,si1,ta1,wa2
|volobo
|-
|Boolean Bit, LLC
|qdj4d-76lh3-w2q5i-kwjcd-643pq-pk42d-cziag-4hkau-35gib-m7s33-6qe
|
|
|-
|Brener, Inc.
|2wxxr-qwylo-n7dhz-6co6m-iektd-vl7dn-ocvyc-xazaf-hbfxq-66spe-aae
|
|
|-
|Conic Ventures
|i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe
|ns1, ld1
|Sebastian Mengwall
|-
|Coplus Limited
|jz47c-irtey-dr2nb-wienh-emhaz-jo6ua-gsbho-t2z5j-l7kbf-5i7p5-5ae
|
|
|-
|CRM52 Systems, LLC
|7nxxb-6qgm4-fftx3-xkwpj-sjrcm-tzmk5-dvuqk-l4ei4-3hvii-scwnj-tae
|
|
|-
|DFINITY Operations SA
|bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe
|mr1, sh1, zh2
| Katie Peters, sasa-tomic, Sven Fischer, eerokelly, garym-dfn, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O, tthebst
|-
|DFINITY USA Research LLC
|lq5ra-f4ibl-t7wpy-hennc-m4eb7-tnfxe-eorgd-onpsl-wervo-7chjj-6qe
|
| Katie Peters, sasa-tomic, Sven Fischer, eerokelly, garym-dfn, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O, tthebst
|-
|DFINITY USA Research LLC
|r2qgy-abcek-yc2ot-3powq-gayr6-4dibc-jvvfl-ri376-gmfmw-u2v7w-4qe
|bo1
| Katie Peters, sasa-tomic, Sven Fischer, eerokelly, garym-dfn, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O, tthebst
|-
|DRMxTech Enterprises, LLC
|olgti-2hegv-ya7pd-ky2wt-of57j-tzs6q-ydrpy-hdxyy-cjnwx-ox5t4-3qe
|
|
|-
|Exaion
|xo7ih-nswlt-hbq3n-v5ixi-etu7j-sasg6-fjf4p-zx6or-cc7c3-pnh7t-2ae
|
|
|-
|Fidgitville Ventures LLC
|ob633-g55bt-y6pu5-5iby6-jmcvi-oylqs-q6ahw-cvecq-5ckeh-m4wws-nae
|
|
|-
|Finteck LLC
|x3zyd-pkcbf-5n3w2-n7uov-2qrbt-d3kfn-ojdd7-pxog5-vpqnt-6lex5-fqe
|
|
|-
|Fractal Labs AG
|wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae
|
|
|-
|Fritz Huie
|67gkg-gkgzz-g2ubz-3cc6h-jr3zm-twsii-7i325-r3gzr-kp2kh-dwxg6-pqe
|
|
|-
|FUM Capital, LLC
|zgupw-boshs-mg6kz-2ciwm-upk7g-igjpn-75t3p-np6g4-47l7q-nuefa-6qe
|
|
|-
|Geodd Pvt Ltd
|eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe
|cm1
|@malithh
|-
|GeoNodes LLC
|5wedd-dwi2c-ybr2g-benav-qlgc7-vifbt-qz3ml-ymopp-uaide-ilpkb-tae
|
|@geo-nodes
|-
|George Bassadone
|lksfo-j2smg-76m4c-jwasz-e5exl-gptsk-jvtc7-zvm34-ezk4g-p2xjt-dqe
|
|
|-
|Giant Leaf, LLC
|wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae
|
|
|-
|Goat, LLC
|p6fou-ngmgk-rxc6t-7ckzz-hojr2-kk6r3-xnlrk-ewzvu-g6xms-rfafz-zae
|
|
|-
|Goodsir, LLC
|myrs2-bc6j6-mydpr-2jmli-l45mu-35ybt-c34mo-kjpve-zmaao-ajusy-nqe
|
|
|-
|Honeycomb Capital (Pty) Ltd
|nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae
|
|honeycombcapital
|-
|Iancu Aurel
|i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae
|
|
|-
|Icaria Systems Pty Ltd
|ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe
|mn2
| Icarus
|-
|IC Pros
|srga3-cikqa-srnxx-rwejf-672jj-5o6qy-tuzsa-khds3-2ofjw-5gnew-mae
|
|
|-
|Illusions In Art (Pty) Ltd
|optdi-nwa4m-hly3k-6ua4n-sqyxf-yahvb-wps77-ddayn-r7zcz-edla5-7qe
|
|
|-
|InfoObjects
|7ws2n-wqorv-vmo4m-5e222-n42c3-hk43s-ei3kp-4hpbn-xlkzo-jgv7i-tqe
|
|
|-
|Internet Computer Explorer
|i7v7g-cwjtl-gzd2s-nt2ko-4d5su-vh64h-bqu4h-rio26-tbaej-dtj6d-fae
|
|
|-
|Ivanov Oleksandr
|ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae
|pa1,ma1, bt1, rg1, wy1, li1, ta2
|alexnod
|-
|Jeffrey Schnettler
|5zqo2-omblo-i7knq-qyrfu-mjccn-tljyd-qslab-b7ukn-7tshi-pbeke-pae
|
|
|-
|Jimmy Quach
|dzxyh-fo4sw-pxckk-kwqvc-xjten-3yqon-fm62b-2hz4s-raa4g-jzczg-iqe
|
|
|-
|Jonathan Ziskind
|qcs4o-yswwp-7ozhg-m2ago-ytjyl-zlckb-raykw-fi5hl-cflyt-4beyv-zqe
|
|
|-
|Joseph Stella
|f5wg2-kl4aq-cj4ym-nq7ul-i4kxy-t4x3x-yiyc5-3wlu6-opzwd-o5qes-hae
|
|
|-
|Karel Frank
|unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe
|jb1, jb2, sc1
|lerak
|-
|KLAW Media, LLC
|pcwis-xaq3p-xvasz-5cfws-oelni-xs72v-acbwz-umxnq-nb2bc-ziyuu-sqe
|
|
|-
|Kontrapunt (Pty) Ltd
|py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe
|
|
|-
|Krishna Enterprises
|zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae
|pl2
|@krishnaenterprises:matrix.org
|-
|Krishna Sriram
|sajvr-l5iok-rj6c2-r76co-k2mde-d3kir-pnmjs-443f6-lxto4-pu55q-uae
|
|
|-
|Lauren Dymecki Chickvara
|abscc-3lezh-oezci-5i3kz-pkwlc-ozz3r-5wv4n-htujn-rtajh-6cgyv-jae
|
|
|-
|Lukas Helebrandt
|efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe
|bn1
|@lukas:greensteps.cn
|-
|Luke Jacobson
|6dwst-olsa5-tagsr-jylgj-oicju-rf42e-o7job-gedre-fgoxt-7br62-jqe
|
|
|-
|Maksym Ishchenko
|4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae
|bn1,ma2,bt1,rg1, wa1,ba1,ta1
|77676m
|-
|Marc Johnson
|xfvlz-qkgs4-xyeyx-lbke5-aarza-ovi52-wzpxl-3p27l-ov6ki-csxv6-qqe
|pr1

es1

NZ1
|@mj518
|-
|Mariano Stoll
|s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae
|ar1
|marianostoll
|-
|Marvelous Web3
|7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe
|
|
|-
|Mary Ren
|vdzyg-amckj-thvl5-bsn52-2elzd-drgii-ryh4c-izba3-xaehb-sohtd-aae
|
|
|-
|MB Patrankos šūvis
|4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae
|
|
|-
|Mika Properties, LLC
|3siog-htc6j-ed3wz-sguhu-2objz-g5qct-npoma-t3wwt-bd6wy-chwsi-4ae
|
|
|-
|MI Servers
|izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe
|
|
|-
|Mitchel Guerra
|4anlt-yam7x-eodmx-ik7mo-nl3kx-t35fj-52hfy-uv4jj-u2iea-ntg76-pqe
|
|
|-
|Moon Block Ventures
|sdal5-w2c3d-p3buy-zieck-2wyuj-eu5bn-rkfe6-uuspi-o4n2b-gpei7-iae
|
|
|-
|Mostly Wholesome, Inc.
|ou3o7-akyjc-ldwd5-anyjn-l2buz-cwhbg-nehlc-abkde-qtc7w-fozdi-hae
|
|
|-
|Neptune Partners
|4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae
|
|
|-
|NoviSystems, LLC
|hk7eo-22zam-kqmsx-dtfbj-k5i6f-jg65h-micpf-2cztc-t2eqk-efgvx-vqe
|ny2, fm1
|novisystems
|-
|OneSixtyTwo Digital Capital
|6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe
|
|
|-
|Origin Game
|cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe
|
|
|-
|Palnu_Logistics
|pfcmh-uqedc-ijkjz-mdo35-bvprd-2vtlw-ktod5-npgfc-pgbq4-akaen-uqe
|
|
|-
|Paul Legato
|yr4eg-kwk3m-q44vj-ale35-2mtxk-5dyn7-vgppx-z6tcw-kzo4o-ezpm5-fqe
|
|
|-
|Peggy Shafaghi
|72idx-a7c3y-nrcwc-lboj4-mmsas-sfdpm-gq23i-h2yuy-lykcj-vrxn2-jqe
|
|
|-
|Philippe Chapparone
|2c4m6-25hos-qroi3-mk4aj-nog6s-zbzcv-ccpcc-cbv7s-sjy6p-bv3g5-fae
|
|
|-
|Pindar Technology Limited
|r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae
|
|Robert Song, alexa-zhang410, Miles Million
|-
|Power Meta Corporation
|4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae
|
|
|-
|Prayit Jain
|waj5k-wlyvv-jbj4n-vxwjm-dmkyg-uw2nl-ggojp-34kln-wgx3n-d7xih-5qe
|
|
|-
|Privoxy Solutions, LLC
|trxbq-wy5xi-3y27q-bkpaf-mhi2m-puexs-yatgt-nhwiy-dh6jy-rolw5-zqe
|
|privoxy (@privoxy:matrix.org)
|-
|Rachel Dymecki
|chnsu-yaqt5-6osy5-au4zn-li6yu-nufmw-dewrt-utkiu-twd76-ujypw-rae
|
|
|-
|Richard Ma
|egb3e-rzi2e-vpsmm-akysp-l2owk-4dgst-b5hmg-xrkwa-cr3uk-zlzds-mae
|
|
|-
|Richard Suarez
|cmcjw-6c5ve-4zjnt-lipnl-2lp43-oh5wk-ewciz-xyvnv-m2rz5-hkm6a-hqe
|
|
|-
|Ricky Sidhu
|q22bo-3uyqa-jvtpt-gapjk-pseor-esx4a-zyb74-vzea4-o7nx2-tafgq-hae
|
|
|-
|Rishi Sachdev
|6tg64-cdfoh-kl35i-p6qti-sose3-746lr-jk5ex-phuvu-jfu3d-5svwa-7qe
|
|
|-
|Rivram Inc
|ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae
|nm1,mtl1
|@ritvick
|-
|Rodney Zorrilla
|bgprp-b2mnt-ci5in-57vuk-p7qvo-tj2tb-5w5su-qwenk-gbe77-mnuiq-sqe
|
|
|-
|Ronnie Pellizzari
|wwxec-c2gd2-bu5on-ktpwz-z2ph3-vlr4p-m7ztf-6ck7r-nt3r4-fxbdq-mae
|
|
|-
|Russell Ford
|p5jx4-lsrog-ep5o3-5uudg-opdg3-ur45z-xeefi-4ejfz-47t2k-riwfv-dae
|
|
|-
|Scott Hallock
|i6sxi-fks25-viets-mboa7-3i23b-qeocf-e57qj-ar6vy-2mchu-xb5vp-aqe
|
|
|-
|Shelburne Ventures, LLC
|a24zv-2ndbz-hqogc-ev63f-qxnpb-7ramd-usexl-ennaq-4om4k-sod6u-gae
|
|
|-
|Staking Facilities
|niw4y-easue-l3qvz-sozsi-tfkvb-cxcx6-pzslg-5dqld-ooudp-hsuui-xae
|
|
|-
|Starbase
|sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae
|
|
|-
|Starseed Technology, LLC
|ruxoj-jnqql-uau6o-xwrtb-ufde4-geddn-mnhni-wpew4-zhzi5-xjrxi-lqe
|
|
|-
|Sygnum Bank
|6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe
|
|
|-
|Tomahawk.vc
|ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae
|
|
|-
|Virtual Hive Ltd
|wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae
|fr2
|Chris B
|-
|Vladyslav Popov
|3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae
|pa2,ma2,si1,rg1, wy1,li1,ta2
|vladyslav_p
|-
|Wancloud limited
|g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe
|hk1
|<nowiki>hashbamboo | HashQuark, Daniel | HashQuark</nowiki>
|-
|Web3game
|64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe
|
|
|-
|William Zelver
|usau7-upgoh-sg464-6qnso-lud42-nxho6-ith26-a2jhq-q5bgy-ajeou-4ae
|
|
|-
|Wolfhound LLC
|6mifr-stcqy-w5pzr-qpijh-jopft-p6jl3-n2sww-jhmzg-uzknn-hte4m-pae
|
|
|-
|Wolkboer (Pty) Ltd
|mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae
|jb3
|wolkboer
|-
|Zondax AG
|hzqcb-iiagd-4erjo-qn7rq-syqro-zztl6-cpble-atnkd-2c6bg-bxjoa-qae
|
|
|-
|ZTLC PTE LTD
|xsrwt-tl3tk-n3aya-rafh3-ta6xu-eviw5-ae5dg-2f3bf-siaab-wdwdo-dqe
|
|
|}

Bianca-Martina Rohner

2023-12-13T12:40:15Z

Tina23: Deleting Colombia decentralisation file. Outdated and not needed anymore.

File:Optimization Model Panama.pdf

2023-12-11T11:44:07Z

Tina23:

Results of optimisation model SHA256: b64b7aa1574148fec7af2e039f9b0088b0c081a7f50234067ccd67c26c68adb1

File:Optimization Model Colombia.pdf

2023-12-11T11:43:07Z

Tina23:

Results of diversification topology, SHA256: 2ec54c29f46e17c00940888ee705874c802019f0889ada289ff149afcad74063

File:Invoice Israel.docx

2023-12-10T18:58:11Z

Tina23:

Invoice for ordered servers.

Validation of Candidate Node Machines

2023-12-05T10:36:07Z

Tina23: Objective value should decrease when new node machines help decentralisation.

== Background ==
In order to improve the decentralization network, an optimization model has been proposed on the forum (see [https://forum.dfinity.org/t/ic-topology-series-node-diversification-part-i/23402 node diversification part 1] and [https://forum.dfinity.org/t/ic-topology-node-diversification-part-ii/23553 node diversification part 2]) and also approved (see [https://dashboard.internetcomputer.org/proposal/125367 proposal 125367]). Given a certain target topology, the model optimizes between node rewards (onboarding of additional new nodes and rewards for existing nodes) and decentralization, calculating the minimum number of additional node machines required in order to achieve specific decentralization targets.

The basis for the optimization model is a target IC topology for the next 6 to 12 months which may extend into Q1 2025 for contract ending for Gen1 node machines. This target topology has been proposed on the forum in [https://forum.dfinity.org/t/ic-topology-node-diversification-part-ii/23553 node diversification part 2], and approved by the community in [https://dashboard.internetcomputer.org/proposal/125549 proposal 125549] on 12th November 2023. This model sets targets for the number of Gen1 nodes and Gen2 nodes per subnet, and the decentralization coefficients (Nakamato coefficients) per subnet.
[[File:Validation Candidate Nodes - figure 1.png|center|thumb|800x800px|Validation of Candidate Node Machines - figure 1|alt=]]

Running the optimization tool with the current topology will produce a graph like above, the red blocks showing the number of additional required node machines in order to reach the decentralization targets set in the IC Target Topology. The number of additional node machines required to reach the decentralization targets is visible in the <code>ObjectiveValue</code> which in the example graph is 68 additional Gen 2 node machines.

With the optimization model and the IC Target Topology, the goal is to implement a transparent, objective and reproducible approach for node provider onboarding. Running the model with the existing IC topology and the number of new node machines intended to be onboarded, the model allows the proposer:

* to verify whether adding additional nodes actually improves the decentralization, and
* allows the community to verify this improvement and vote on the proposal to add additional nodes.

Below the steps are described to run the optimization model and verify any new proposal. An example is also given for a specific (fictional) proposal.

== Basic starting points ==
There are a few basic starting points that everybody should be aware of when using the optimization tool and the IC Target Topology. First of all, using the model requires some basic knowledge of Python and Github, so please make sure to familiarize yourself with these before starting.

In addition, it is important to note that the IC Target Topology is not fixed. It is voted in by the community as the target to be achieved within a certain timeframe. [https://dashboard.internetcomputer.org/proposal/125549 Proposal 125549] describes the target topology for the next half year/year, estimated on the current growth of the IC network. If expected growth should change, the community can decide to vote on an updated IC Target Topology with either more node machines or less node machines. Note that the Target IC Topology is intended to assess effectiveness of adding additional nodes, and identify potential nodes that are not relevant from a decentralization perspective. It does not assess or propose any changes in node rewards, which is a topic that the community discusses and votes upon separately.

If target IC Topology is reached - meaning the <code>Objective Value</code> in the optimization model has reached the value of zero, no new node machines should be onboarded. Hence, NNS proposals for increasing the Node Allowance or defining a new Node Allowance should be rejected by the community. Once a new IC Target topology is defined or (other) Node Providers have reduced their Node Allowance, the <code>Objective Value</code> might increase again which would allow for new proposals to be submitted and approved.
== Steps to follow to assess node relevance ==
Assessing the relevance of adding new node machines using the optimization tool requires you to follow four basic steps:

# Installing and running the latest version of the optimization tool
# Determining your candidate node configuration
# Updating your candidate nodes in the optimization tooling
# If adding new node machines is relevant, submitting the Node Operator proposal with the necessary background description.

Each of these steps is discussed in detail below.

=== Step 1 - downloading and installing the optimization tool ===
The optimization tool can be found in the following Github repository: https://github.com/dfinity/decentralization/. The repository is open sourced to allow the community to help improve the tooling with additional functionality and visualizations.

To run the model. Please follow the following steps:

* Find the repository on https://github.com/dfinity/decentralization/
* Either follow one of the following two approaches:
** Command Line approach - Follow the instructions as described in the README file, i.e.:
*** Clone the repository to you computer
*** Install [https://python-poetry.org/ Python Poetry]
*** Run the model in the command line as described in the README file
** Jupyter Notebook approach - Frequent Python users might have a preference for using [https://jupyter.org/ Jupyter Notebook]. If you want to use Jupyter notebook, you can follow the following steps:
*** Copy the code from the repository files and delete the import commands and main() sections from the separate python files (<code>data_preparation.py</code>, <code>helper_functions.py</code>, <code>linear_solver.py</code>, <code>visualization.py</code>)
*** Run each file in subsequent cells in Jupyter notebook
*** You can subsequently rerun the model and adjust parameters using the interface of Jupyter notebook.
* Carefully read the forum posts on [https://forum.dfinity.org/t/ic-topology-series-node-diversification-part-i/23402 node diversification part 1] and [https://forum.dfinity.org/t/ic-topology-node-diversification-part-ii/23553 node diversification part 2] to understand the working of the tooling.
* Check the outcome of the model without making any updates to the model, in particular the <code>ObjectiveValue</code> as described above. As per 23 november 2023, the Objective Value should be similar to the graph shown above, with an additional 72 nodes needed to reach the target topology.

=== Step 2 - determine your candidate node configuration ===
The internet computer dashboard shows the worldwide distribution of node machines. Based on this distribution, as a potential new Node Provider you can identify potential locations and data center providers for new node machines.

For the Node Provider economics and understanding the costs and rewards for running a node machine, please look at the detailed NP documentation on the Internet Computer wiki pages, in particular those on [[Node Provider Machine Hardware Guide|hardware configuration]], [[Node Provider Data Center and ISP Guide|data center requirements]], and [[Node Provider Remuneration|node rewards]].

Once you have decided on potential data center locations and a potential number of new node machines that have viable economics, you can follow the following steps to add this candidate configuration to the optimization tool:

* Collect the following information:
** The node provider name (if you are an existing node provider, use your existing Node Provider name)
** The data center name (if you are intending to add node machines to an existing data center, use the existing data center name)
** The data center provider name (if you are intending to use an existing data center provider, use the existing data center provider name)
** The country name (if you are intending to add node machines to an existing country, use the existing country name)
** The number of nodes you intend to onboard

=== Step 3 - update the candidate node configuration in the optimization tooling ===
The optimization tool includes a function that allows candidate nodes to be added to the node configuration, and to run the optimization with including these candidate nodes. With the information collected in step 2, the following steps allow for the optimization tool to be run including the candidate nodes:

* Updated the latest topology in the optimization tooling
** Find the df_candidate_nodes function in the <code>main.py</code> of the ic_topology directory.
** You will see the following example entry: <code>df_candidate_nodes = create_candidate_node_dataframe(node_provider ='Lionel Messi',data_center ='Buenos Aires',data_center_provider ='Perron Corporation',country = 'AR',is_sev = True,no_nodes = 0)</code>
** Replace ‘Lionel Messi’ with the Node Provider name
** Replace ‘Buenos Aires’ with the data center name
** Replace ‘Perron Corporation’ with the data center provider name
** Replace ‘AR’ with the country name
** Replace “0” in no_nodes with the number of nodes intended to be onboarded.
* Run the model and determine the <code>ObjectiveValue</code>:
** If the <code>ObjectiveValue</code> is lower compared to the <code>ObjectiveValue</code> without making changes to the df_candidate_nodes, it means that adding one or more new nodes is increasing the decentralization of the IC. It is important to note that every single node machine should help 1:1 to reduce the <code>ObjectiveValue</code>. For, if the <code>ObjectiveValue</code> without adding any candidate nodes is 68, and 6 candidate nodes are added, the <code>ObjectiveValue</code> should reduce to 68 minus 6 is 62. If the <code>ObjectiveValue</code> is reduced to for example 66, only 2 candidate node machines will support further decentralization of the IC network, and no more than 2 candidate nodes should be added.
** If the ObjectiveValue is the same compared to the <code>ObjectiveValue</code> without making changes to the df_candidate_nodes, it means that adding one or more new nodes does not improve the decentralization of the IC.

=== Step 4 - Submitting a Node Operator Proposal ===
If the conclusion from step 3 is that adding node machines helps decentralization of the IC network, the final step is to prepare to submit a proposal for onboarding these nodes. Following are the steps to take in order to submit this proposal:

* If you are not yet a Node Provider, please follow the steps on the [[Node Provider Onboarding|NP onboarding wiki page]] to submit a Node Provider Proposal. Please make sure to submit the self-declaration form and the identity-document as part of the proposal, as described in the instructions.
* If you are intending to onboard node machines in a new data center, follow the subsequent steps on the same [[Node Provider Onboarding|NP onboarding wiki page]] to submit a Data Center Proposal.
* Follow the steps on the same [[Node Provider Onboarding|NP onboarding wiki page]] to submit a Node Operator Proposal. The Node Operator Proposal should include the following input in the summary text:
** The number of nodes planned to be onboarded
** Node provider name (as per the public dashboard)
** The data center and country where nodes are to be onboarded
** Evidence of running the optimization model and providing reproducible feedback on decrease in <code>ObjectiveValue</code>. This can be done in the following way:
*** Upload a pdf with screenshots of running the optimization model to the wiki, on the page of your specific Node Provider self-declaration documentation.
*** Include the link to this pdf document and the hash of this document in the Node Operator Proposal.
*** Include/describe exactly the used input data and config the optimization model was run with.
*** Clearly state the <code>ObjectiveValue</code> before adding the candidate nodes
*** Clearly state the <code>ObjectiveValue</code> after adding the candidate nodes
* Complete the steps of the [[Node Provider Onboarding|NP onboarding wiki page]].

== Example ==
In the below example, an example is given how to use the optimization model to validate whether candidate nodes improve the decentralization of the IC network. In the optimization model code in the Github library, you will find a function df_candidate_nodes that is defined as follows:
df_candidate_nodes = create_candidate_node_dataframe(node_provider ='Lionel Messi', data_center ='Buenos Aires', data_center_provider ='Perron Corporation', country = 'AR', is_sev = True, no_nodes = 0)
This function uses a hypothetical new Node Provider, called Lionel Messi, that is interested in setting up new node machines in the Buenos Aires data center. Lionel Messi uses the data center entity Perron Corporation as the data center name. Note that all nodes are marked as <code>is_sev = True</code> which means that Gen2 node machines (with SEV SNP enabled) will be set up, and that <code>no_nodes = 0</code> so when running the current optimization tooling zero nodes will be added; the optimization tool will only use the existing IC topology to calculate the number of required Gen2 Nodes, defined as <code>ObjectiveValue</code>.

Now let’s add one node machine to the candidate node list of Lionel Messi. For this, the function is updated as follows:
df_candidate_nodes = create_candidate_node_dataframe(node_provider ='Lionel Messi', data_center ='Buenos Aires', data_center_provider ='Perron Corporation', country = 'AR', is_sev = True, no_nodes = 1)
Re-running the optimization model will generate (amongst others) the following output. As can be seen from the Node Provider topology Matrix, Lionel Messi is added as a node Provider with one node (which is the top orange block in the graph, and the bottom name in the Node Provider legenda on the right).
[[File:Validation of Candidate Node Machines - figure 2.png|alt=Validation of Candidate Node Machines - figure 2|center|thumb|800x800px|Validation of Candidate Node Machines - figure 2]]

The output also shows the data center being added to the Data Center topology. Again, the node is shown on the top (as the block block on second to the top) and the data center name is shown at the bottom of the data center legenda as Perron Corporation.

[[File:Candidate Node Machine Validation - figure 3.png|center|thumb|800x800px|Validation of Candidate Node Machines - figure 3|alt=]]
More importantly, the node allocation per subnet is now showing an updated <code>ObjectiveValue</code> with a value of 67, hence 67 more Gen2 node machines are required to reach the IC target topology. Compared to running the model without Lionel Messi’s candidate node machine, the <code>ObjectiveValue</code> is reduced from 68 (see beginning of this article) to 67, hence adding one extra node machine in Buenos Aires support the decentralization of the IC network.

[[File:Validation of Canidate Node Machines - figure 4.png|center|thumb|800x800px|Validation of Candidate Node Machines - figure 4|alt=]]

It would be interesting to validate whether adding additional node machines in Buenos Aires further support the decentralization of the IC. Let’s increase the number of candidate nodes from 1 to 4 by update the df_candidate_nodes function as follows:
df_candidate_nodes = create_candidate_node_dataframe(node_provider ='Lionel Messi', data_center ='Buenos Aires', data_center_provider ='Perron Corporation', country = 'AR', is_sev = True, no_nodes = 4)
The node allocation per subnet now shows an <code>ObjectiveValue</code> with a value of 64, hence 64 more Gen2 node machines are required to reach the decentralization targets of the IC network. This is reduction from the original 68 required node machines with 4 node machines. Hence, the model shows that adding 4 candidate nodes in Buenos Aires still adds to the decentralization of the IC network.

Further increasing the number of candidate nodes to 6 shows that decentralization of the IC network still improves. By adding 6 candidate nodes through the updated df_candidate_nodes function, the <code>ObjectiveValue</code> reduces to 62 from 68.
[[File:Validation of Candidate node Machines - figure 5.png|center|thumb|800x800px|Validation of Candidate Node Machines - figure 5]]

Similarly, adding 8 candidate node machines still improves decentralization, as the <code>ObjectiveValue</code> reduced to 60.
df_candidate_nodes = create_candidate_node_dataframe(node_provider ='Lionel Messi', data_center ='Buenos Aires', data_center_provider ='Perron Corporation', country = 'AR', is_sev = True, no_nodes = 8)

[[File:Validation of Candidate node Machines - figure 6.png|center|thumb|800x800px|Validation of Candidate Node Machines - figure 6]]

However, if we increase the number of candidate node machines in Buenos Aires from 8 to 9, we notice that the <code>ObjectiveValue</code> does not reduce anymore. Hence, adding 8 node machines in Buenos Aires is the optimal solution for improving the decentralization targets.
df_candidate_nodes = create_candidate_node_dataframe(node_provider ='Lionel Messi', data_center ='Buenos Aires', data_center_provider ='Perron Corporation', country = 'AR', is_sev = True, no_nodes = 9)
[[File:Validation of Candidate Node Machines - figure 7.png|center|thumb|800x800px|Validation of Candidate Node Machines - figure 7]]

This can be explained by the fact that most subnets (marked in blue in the Node Allocation subnet graph) are already optimized in terms of country limit, node provider limit, and data center limit. Only the subnets with blocks marked in red need additional node machines from unique countries, unique data centers and unique node providers. Adding 8 nodes achieves this. An additional ninth node machine cannot be added to any of the existing subnets in order to improve any of the country limits, data center limits and node provider limits.

File:BMR identity proof.pdf

2023-12-05T09:55:18Z

Tina23:

Identity Proof SHA256: 2c1fa30253103788b7c6510bb1fc66fd4e11b9e9df163ec936c9a460b377ade2

File:BMR self declaration.pdf

2023-12-05T09:53:15Z

Tina23:

Self-declaration SHA 256: ca3973712c4d7947b0b835368ca0648696d52ff6e7ed69a7c92766c1da51e0ce