Internet Computer Wiki - User contributions [en]

Node Provider Matrix channel

2025-02-25T10:20:20Z

Sat:

There are Matrix rooms (channels) that are 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.

'''NOTE:''' these rooms should only be consulted for troubleshooting issues '''after consulting all relevant [[Node Provider Troubleshooting]] documentation.'''

There is a [https://matrix.to/#/!YEFYjPAwRoiyVaKfAp:matrix.org?via=matrix.org&via=greensteps.cn&via=rudd-o.com Matrix Space Internet Computer], that includes all relevant rooms and people -- please join that first!

After that, please join the following rooms (can all be found within the [https://matrix.to/#/!YEFYjPAwRoiyVaKfAp:matrix.org?via=matrix.org&via=greensteps.cn&via=rudd-o.com Matrix Space Internet Computer]):

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org (lots of activity)
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org (infrequent messages)
* Incident response: https://app.element.io/#/room/#ic-node-providers-incident-response:matrix.org (communication reserved only for incident response. Please join if you are a node provider, and enable all notifications!)

These rooms run 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.

'''NOTE: 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]. If possible, [https://element.io/help#settings3 enable notifications for missed messages], especially for rooms with lower activity.

If you are a Node Provider, please also add your contact details below, to facilitate communication.
{| class="wikitable"
|+
!Node Provider Name
!Node Provider Id
!DC list
!Can be reached on Matrix via
|-
|1G
|7k7b7-4pzhf-aivy6-y654t-uqyup-2auiz-ew2cm-4qkl4-nsl4v-bul5k-5qe
|fm1
|https://matrix.to/#/#ic-node-provider-7k7b7:matrix.org
|-
|43rd Big Idea Films
|sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe
|hu1
|John Harris, Charles Witte
https://matrix.to/#/#ic-node-provider-sqhxa:matrix.org
|-
|87m Neuron, LLC
|eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe
|pl1, dl1, lv1
|https://matrix.to/#/#ic-node-provider-eipr5:matrix.org
|-
|9Yards Capital
|spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe
|jv1, ch2, ny1
|https://matrix.to/#/#ic-node-provider-spp3m:matrix.org
|-
|ACCUSET SOLUTIONS
|cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe
|gn1
|sagcryptoicp
https://matrix.to/#/#ic-node-provider-cp5ib:matrix.org
|-
|Adam Dymecki
|n32q7-33lmk-m33tr-o5ltb-po6cb-tqqrr-2x6wp-pzhw7-ymizu-o3fyp-sqe
|
|https://matrix.to/#/#ic-node-provider-n32q7:matrix.org
|-
|A Dog's Boutique, LLC
|uvawj-nnt3i-4ch3a-hruy4-hyfjn-7owvl-wgkli-uq2hd-e6lkq-v4b2o-4ae
|
|https://matrix.to/#/#ic-node-provider-uvawj:matrix.org
|-
|AITUBI AG
|znw2p-4cx6u-ocqls-277iu-2lkir-xjy7g-4s3sj-sjy6j-mtlay-rnnra-yqe
|
|
|-
|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>
https://matrix.to/#/#ic-node-provider-rbn2y:matrix.org
|-
|Anonstake
|kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae
|
|https://matrix.to/#/#ic-node-provider-kos24:matrix.org
|-
|ANYPOINT PTY LTD
|fwnmn-zn7yt-5jaia-fkxlr-dzwyu-keguq-npfxq-mc72w-exeae-n5thj-oae
|
|https://matrix.to/#/#ic-node-provider-fwnmn:matrix.org
|-
|Archery Blockchain SCSp
|7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe
|
|https://matrix.to/#/#ic-node-provider-7ryes:matrix.org
|-
|Arjay LLC
|l2kri-jarwr-7whc4-pjdpn-n6hlb-45ltr-l6ghm-twttl-pcsvt-rynko-dqe
|
|https://matrix.to/#/#ic-node-provider-l2kri:matrix.org
|-
|Artem Horodyskyi
|diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe
|bt1, li1, ma1, pa2, rg3, ta2, wy1
|ar-111
https://matrix.to/#/#ic-node-provider-diyay:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-7a4u2:matrix.org
|-
|Bitmoon
|mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe
|
|https://matrix.to/#/#ic-node-provider-mjnyf:matrix.org
|-
|Blockchain Development Labs
|7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae
|to1, to2, bc1
|@injectedfusion:matrix.org
https://matrix.to/#/#ic-node-provider-7at4h:matrix.org
|-
|BlockTech Ventures, LLC
|ks7ow-zvs7i-ratdk-azq34-zio2b-gbekj-qjicg-pfhp3-ovhgu-k5qql-dae
|
|https://matrix.to/#/#ic-node-provider-ks7ow:matrix.org
|-
|BLP22, LLC
|sma3p-ivkif-hz7nu-ngmvq-ibnjg-nubke-zf6gh-wbnfc-2dlng-l3die-zqe
|
|https://matrix.to/#/#ic-node-provider-sma3p:matrix.org
|-
|Bohatyrov Volodymyr
|dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae
|bn1,ba1,ma1,rg3,si1,ta1,wa2
|volobo
https://matrix.to/#/#ic-node-provider-dhywe:matrix.org
|-
|Boolean Bit, LLC
|qdj4d-76lh3-w2q5i-kwjcd-643pq-pk42d-cziag-4hkau-35gib-m7s33-6qe
|
|https://matrix.to/#/#ic-node-provider-qdj4d:matrix.org
|-
|Brener, Inc.
|2wxxr-qwylo-n7dhz-6co6m-iektd-vl7dn-ocvyc-xazaf-hbfxq-66spe-aae
|
|https://matrix.to/#/#ic-node-provider-2wxxr:matrix.org
|-
|Conic Ventures
|i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe
|ns1, ld1
|Sebastian Mengwall
https://matrix.to/#/#ic-node-provider-i3cfo:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-7nxxb:matrix.org
|-
|DFINITY Operations SA
|bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe
|sh1, zh2
|Katie Peters, sasa-tomic, eerokelly, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O<nowiki/>https://matrix.to/#/#ic-node-provider-bvcsg:matrix.org
|-
|DRMxTech Enterprises, LLC
|olgti-2hegv-ya7pd-ky2wt-of57j-tzs6q-ydrpy-hdxyy-cjnwx-ox5t4-3qe
|
|https://matrix.to/#/#ic-node-provider-olgti:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-olgti:matrix.org
|-
|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
|mb1, lj1
|@gorazd_o:matrix.org
https://matrix.to/#/#ic-node-provider-wdjjk:matrix.org
|-
|Fritz Huie
|67gkg-gkgzz-g2ubz-3cc6h-jr3zm-twsii-7i325-r3gzr-kp2kh-dwxg6-pqe
|
|https://matrix.to/#/#ic-node-provider-67gkg:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-eybf4:matrix.org
|-
|GeoNodes LLC
|5wedd-dwi2c-ybr2g-benav-qlgc7-vifbt-qz3ml-ymopp-uaide-ilpkb-tae
|
|@geo-nodes
https://matrix.to/#/#ic-node-provider-6sq7t:matrix.org
|-
|George Bassadone
|lksfo-j2smg-76m4c-jwasz-e5exl-gptsk-jvtc7-zvm34-ezk4g-p2xjt-dqe
|
|https://matrix.to/#/#ic-node-provider-vegae:matrix.org
|-
|Giant Leaf, LLC
|wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae
|
|https://matrix.to/#/#ic-node-provider-wwdbq:matrix.org
|-
|Goat, LLC
|p6fou-ngmgk-rxc6t-7ckzz-hojr2-kk6r3-xnlrk-ewzvu-g6xms-rfafz-zae
|
|https://matrix.to/#/#ic-node-provider-p6fou:matrix.org
|-
|Goodsir, LLC
|myrs2-bc6j6-mydpr-2jmli-l45mu-35ybt-c34mo-kjpve-zmaao-ajusy-nqe
|
|https://matrix.to/#/#ic-node-provider-myrs2:matrix.org
|-
|Honeycomb Capital (Pty) Ltd
|nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae
|
|honeycombcapital
https://matrix.to/#/#ic-node-provider-nmdd6:matrix.org
|-
|Iancu Aurel
|i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae
|
|https://matrix.to/#/#ic-node-provider-i7dto:matrix.org
|-
|Icaria Systems Pty Ltd
|ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe
|mn2
|Icarus
https://matrix.to/#/#ic-node-provider-ihbuj:matrix.org
|-
|Illusions In Art (Pty) Ltd
|optdi-nwa4m-hly3k-6ua4n-sqyxf-yahvb-wps77-ddayn-r7zcz-edla5-7qe
|
|https://matrix.to/#/#ic-node-provider-optdi:matrix.org
|-
|InfoObjects
|7ws2n-wqorv-vmo4m-5e222-n42c3-hk43s-ei3kp-4hpbn-xlkzo-jgv7i-tqe
|
|https://matrix.to/#/#ic-node-provider-7ws2n:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-ivf2y:matrix.org
|-
|Jeffrey Schnettler
|5zqo2-omblo-i7knq-qyrfu-mjccn-tljyd-qslab-b7ukn-7tshi-pbeke-pae
|
|https://matrix.to/#/#ic-node-provider-5zqo2:matrix.org
|-
|Jimmy Quach
|dzxyh-fo4sw-pxckk-kwqvc-xjten-3yqon-fm62b-2hz4s-raa4g-jzczg-iqe
|
|https://matrix.to/#/#ic-node-provider-dzxyh:matrix.org
|-
|Jonathan Ziskind
|qcs4o-yswwp-7ozhg-m2ago-ytjyl-zlckb-raykw-fi5hl-cflyt-4beyv-zqe
|
|https://matrix.to/#/#ic-node-provider-qcs4o:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-unqqg:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-py2kr:matrix.org
|-
|Krishna Enterprises
|zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae
|pl2
|@krishnaenterprises:matrix.org
https://matrix.to/#/#ic-node-provider-zy4m7: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
|
|https://matrix.to/#/#ic-node-provider-abscc:matrix.org
|-
|Lukas Helebrandt
|efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe
|bn1
|@lukas:greensteps.cn
https://matrix.to/#/#ic-node-provider-efem5:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-4r6qy:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-s5nvr:matrix.org
|-
|Marvelous Web3
|7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe
|
|https://matrix.to/#/#ic-node-provider-7uioy:matrix.org
|-
|Mary Ren
|vdzyg-amckj-thvl5-bsn52-2elzd-drgii-ryh4c-izba3-xaehb-sohtd-aae
|
|https://matrix.to/#/#ic-node-provider-vdzyg:matrix.org
|-
|MB Patrankos šūvis
|4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae
|bt1
|@methistos:matrix.org
https://matrix.to/#/#ic-node-provider-4jjya:matrix.org
|-
|Mika Properties, LLC
|3siog-htc6j-ed3wz-sguhu-2objz-g5qct-npoma-t3wwt-bd6wy-chwsi-4ae
|
|https://matrix.to/#/#ic-node-provider-3siog:matrix.org
|-
|MI Servers
|izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe
|
|https://matrix.to/#/#ic-node-provider-izmhk:matrix.org
|-
|Mitchel Guerra
|4anlt-yam7x-eodmx-ik7mo-nl3kx-t35fj-52hfy-uv4jj-u2iea-ntg76-pqe
|
|https://matrix.to/#/#ic-node-provider-4anlt:matrix.org
|-
|Moon Block Ventures
|sdal5-w2c3d-p3buy-zieck-2wyuj-eu5bn-rkfe6-uuspi-o4n2b-gpei7-iae
|
|https://matrix.to/#/#ic-node-provider-sdal5:matrix.org
|-
|Mostly Wholesome, Inc.
|ou3o7-akyjc-ldwd5-anyjn-l2buz-cwhbg-nehlc-abkde-qtc7w-fozdi-hae
|
|https://matrix.to/#/#ic-node-provider-ou3o7:matrix.org
|-
|Neptune Partners
|4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae
|
|https://matrix.to/#/#ic-node-provider-4dibr:matrix.org
|-
|NoviSystems, LLC
|hk7eo-22zam-kqmsx-dtfbj-k5i6f-jg65h-micpf-2cztc-t2eqk-efgvx-vqe
|ny2, fm1
|novisystems
https://matrix.to/#/#ic-node-provider-hk7eo:matrix.org
|-
|OneSixtyTwo Digital Capital
|6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe
|
|https://matrix.to/#/#ic-node-provider-6nbcy:matrix.org
|-
|Origin Game
|cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe
|
|https://matrix.to/#/#ic-node-provider-cgmhq:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-72idx:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-r3yjn:matrix.org
|-
|Power Meta Corporation
|4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae
|
|https://matrix.to/#/#ic-node-provider-4fedi:matrix.org
|-
|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)
https://matrix.to/#/#ic-node-provider-trxbq:matrix.org
|-
|Rachel Dymecki
|chnsu-yaqt5-6osy5-au4zn-li6yu-nufmw-dewrt-utkiu-twd76-ujypw-rae
|
|https://matrix.to/#/#ic-node-provider-chnsu:matrix.org
|-
|Richard Ma
|egb3e-rzi2e-vpsmm-akysp-l2owk-4dgst-b5hmg-xrkwa-cr3uk-zlzds-mae
|
|https://matrix.to/#/#ic-node-provider-egb3e:matrix.org
|-
|Richard Suarez
|cmcjw-6c5ve-4zjnt-lipnl-2lp43-oh5wk-ewciz-xyvnv-m2rz5-hkm6a-hqe
|
|https://matrix.to/#/#ic-node-provider-cmcjw:matrix.org
|-
|Ricky Sidhu
|q22bo-3uyqa-jvtpt-gapjk-pseor-esx4a-zyb74-vzea4-o7nx2-tafgq-hae
|
|https://matrix.to/#/#ic-node-provider-q22bo:matrix.org
|-
|Rishi Sachdev
|6tg64-cdfoh-kl35i-p6qti-sose3-746lr-jk5ex-phuvu-jfu3d-5svwa-7qe
|
|https://matrix.to/#/#ic-node-provider-6tg64:matrix.org
|-
|Rivram Inc
|ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae
|nm1,mtl1
|@ritvick
https://matrix.to/#/#ic-node-provider-ulyfm:matrix.org
|-
|Rodney Zorrilla
|bgprp-b2mnt-ci5in-57vuk-p7qvo-tj2tb-5w5su-qwenk-gbe77-mnuiq-sqe
|
|https://matrix.to/#/#ic-node-provider-bgprp:matrix.org
|-
|Ronnie Pellizzari
|wwxec-c2gd2-bu5on-ktpwz-z2ph3-vlr4p-m7ztf-6ck7r-nt3r4-fxbdq-mae
|
|https://matrix.to/#/#ic-node-provider-wwxec:matrix.org
|-
|Russell Ford
|p5jx4-lsrog-ep5o3-5uudg-opdg3-ur45z-xeefi-4ejfz-47t2k-riwfv-dae
|
|https://matrix.to/#/#ic-node-provider-p5jx4:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-a24zv:matrix.org
|-
|Starbase
|sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae
|
|https://matrix.to/#/#ic-node-provider-sixix:matrix.org
|-
| 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
|
|https://matrix.to/#/#ic-node-provider-6r5lw:matrix.org
|-
|Tomahawk.vc
|ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae
|
|https://matrix.to/#/#ic-node-provider-ucjqj:matrix.org
|-
|Virtual Hive Ltd
|wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae
|fr2
|Chris B
https://matrix.to/#/#ic-node-provider-wdnqm:matrix.org
|-
|Vladyslav Popov
|3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae
|pa2,ma2,si1,rg1, wy1,li1,ta2
|vladyslav_p
https://matrix.to/#/#ic-node-provider-3oqw6:matrix.org
|-
|Wancloud limited
|g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe
|hk1
|<nowiki>hashbamboo | HashQuark, Daniel | HashQuark</nowiki>
https://matrix.to/#/#ic-node-provider-g2ax6:matrix.org
|-
|Web3game
|64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe
|hk4
|web3game
https://matrix.to/#/#ic-node-provider-64xe5:matrix.org
|-
|William Zelver
|usau7-upgoh-sg464-6qnso-lud42-nxho6-ith26-a2jhq-q5bgy-ajeou-4ae
|
|https://matrix.to/#/#ic-node-provider-usau7:matrix.org
|-
|Wolfhound LLC
|6mifr-stcqy-w5pzr-qpijh-jopft-p6jl3-n2sww-jhmzg-uzknn-hte4m-pae
|
|https://matrix.to/#/#ic-node-provider-6mifr:matrix.org
|-
|Wolkboer (Pty) Ltd
|mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae
|jb3
|wolkboer
https://matrix.to/#/#ic-node-provider-mme7u:matrix.org
|-
|Zondax AG
|hzqcb-iiagd-4erjo-qn7rq-syqro-zztl6-cpble-atnkd-2c6bg-bxjoa-qae
|
|https://matrix.to/#/#ic-node-provider-hzqcb:matrix.org
|-
|ZTLC PTE LTD
|xsrwt-tl3tk-n3aya-rafh3-ta6xu-eviw5-ae5dg-2f3bf-siaab-wdwdo-dqe
|
|
|}

Node Deployment config.ini

2025-02-12T16:48:12Z

Sat: /* If you do not set node_reward_type */

= node_reward_type Documentation =

The '''node_reward_type''' parameter in the <code>config.ini</code> file indicates the specific node type for which the node operator expects to receive rewards. This value must correspond to a recognized and community-approved node type defined in the Network Nervous System (NNS).

== What is node_reward_type? ==
* It specifies the node’s reward category.
* The chosen type must be compatible with the configurations listed in the NNS node rewards table.
* Common examples include: <code>type1</code>, <code>type1.1</code>, <code>type3</code>, <code>type3.1</code>, etc.

== How to determine your node_reward_type ==
1. Use the <code>ic-admin</code> CLI tool to inspect your node operator configuration. For example:
<pre>ic-admin --nns-url https://ic0.app get-node-operator <your_node_operator_id></pre>
2. In the output, look for the `rewardable_nodes` field. It might look like:
<pre>rewardable_nodes: {"type1": 28}</pre>
This means <code>type1</code> is a valid and approved node type for your account.

3. If multiple types are listed, select the one that best matches your node’s intended reward category.

Example invocation with <code>ic-admin</code>:
<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>

Alternatively, you can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:

<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.

== Possible values ==
The NNS Registry configuration determines which types are valid. Examples:
* <code>node_reward_type=type1</code>
*<code>node_reward_type=type1.1</code>
*<code>node_reward_type=type3</code>
*<code>node_reward_type=type3.1</code>

The set of valid types may change as the community updates NNS configurations. You may get the entire latest reward table list by running:

ic-admin --nns-urls https://ic0.app get-rewards-table

Or for the particular Node Operator record with:

ic-admin --nns-url https://ic0.app get-node-operator <node-operator-id>

== When should I start setting the node_reward_type? ==
You should start setting the <code>node_reward_type</code> for ALL nodes you redeploy ALREADY NOW. This does not impact rewards yet, and failure to set the <code>node_reward_type</code> will likely result in failing node registrations in the near future.

== If you do not set node_reward_type ==
If <code>node_reward_type</code> is empty, you should not expect to get rewards for the node, after March 2025.

There is no need to redeploy already existing nodes in order to set this value on them. All existing nodes should get the value automatically set.

== Default value ==
If left unset or set to an invalid value, the node registration may fail or may succeed but you may not get rewards for the node.

== How to check ==
Check the node reward type at any time by invoking:

ic-admin --nns-url https://ic0.app get-node <node-id>

Example node record:

Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_record_fvy7i-ux7is-cuvfm-2n2zh-5lpb4-oe2vz-bfnhz-oi5s5-jkzhk-phlj2-gqe
Most recent version is 44039. Value:
Node { xnet: Some("[2800:c20:0:29:6801:29ff:fe18:1f08]:2497"), http: Some("[2800:c20:0:29:6801:29ff:fe18:1f08]:8080"),
node_operator_id: eqv2i-6dtlf-bhbjd-2popw-vvavp-7xzci-6gdd7-qxgox-wdw5w-l3a4w-eae, chip_id: None, hostos_version_id:
Some("2e269c77aa2f6b2353ddad6a4ac3d5ddcac196b1"), public_ipv4_config: None, domain: None, node_reward_type: None }

In this case the <code>node_reward_type</code> for the node is set to None, which means that the node will not get any rewards. The quickest way to resolve this problem is to make changes in the <code>config.ini</code> and redeploy the node.

== Best practices ==
* Ensure <code>node_reward_type</code> in <code>config.ini</code> matches a type listed under <code>rewardable_nodes</code> for your operator ID.
* Check the node reward settings for the node operator and for the node in case of any problems

Node Deployment config.ini

2025-02-12T16:47:20Z

Sat: /* When should I start setting the node_reward_type? */

= node_reward_type Documentation =

The '''node_reward_type''' parameter in the <code>config.ini</code> file indicates the specific node type for which the node operator expects to receive rewards. This value must correspond to a recognized and community-approved node type defined in the Network Nervous System (NNS).

== What is node_reward_type? ==
* It specifies the node’s reward category.
* The chosen type must be compatible with the configurations listed in the NNS node rewards table.
* Common examples include: <code>type1</code>, <code>type1.1</code>, <code>type3</code>, <code>type3.1</code>, etc.

== How to determine your node_reward_type ==
1. Use the <code>ic-admin</code> CLI tool to inspect your node operator configuration. For example:
<pre>ic-admin --nns-url https://ic0.app get-node-operator <your_node_operator_id></pre>
2. In the output, look for the `rewardable_nodes` field. It might look like:
<pre>rewardable_nodes: {"type1": 28}</pre>
This means <code>type1</code> is a valid and approved node type for your account.

3. If multiple types are listed, select the one that best matches your node’s intended reward category.

Example invocation with <code>ic-admin</code>:
<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>

Alternatively, you can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:

<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.

== Possible values ==
The NNS Registry configuration determines which types are valid. Examples:
* <code>node_reward_type=type1</code>
*<code>node_reward_type=type1.1</code>
*<code>node_reward_type=type3</code>
*<code>node_reward_type=type3.1</code>

The set of valid types may change as the community updates NNS configurations. You may get the entire latest reward table list by running:

ic-admin --nns-urls https://ic0.app get-rewards-table

Or for the particular Node Operator record with:

ic-admin --nns-url https://ic0.app get-node-operator <node-operator-id>

== When should I start setting the node_reward_type? ==
You should start setting the <code>node_reward_type</code> for ALL nodes you redeploy ALREADY NOW. This does not impact rewards yet, and failure to set the <code>node_reward_type</code> will likely result in failing node registrations in the near future.

== If you do not set node_reward_type ==
If <code>node_reward_type</code> is empty, you should not expect to get rewards for the node, after March 2025.

There is no need to redeploy already existing nodes, just to set this value.

== Default value ==
If left unset or set to an invalid value, the node registration may fail or may succeed but you may not get rewards for the node.

== How to check ==
Check the node reward type at any time by invoking:

ic-admin --nns-url https://ic0.app get-node <node-id>

Example node record:

Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_record_fvy7i-ux7is-cuvfm-2n2zh-5lpb4-oe2vz-bfnhz-oi5s5-jkzhk-phlj2-gqe
Most recent version is 44039. Value:
Node { xnet: Some("[2800:c20:0:29:6801:29ff:fe18:1f08]:2497"), http: Some("[2800:c20:0:29:6801:29ff:fe18:1f08]:8080"),
node_operator_id: eqv2i-6dtlf-bhbjd-2popw-vvavp-7xzci-6gdd7-qxgox-wdw5w-l3a4w-eae, chip_id: None, hostos_version_id:
Some("2e269c77aa2f6b2353ddad6a4ac3d5ddcac196b1"), public_ipv4_config: None, domain: None, node_reward_type: None }

In this case the <code>node_reward_type</code> for the node is set to None, which means that the node will not get any rewards. The quickest way to resolve this problem is to make changes in the <code>config.ini</code> and redeploy the node.

== Best practices ==
* Ensure <code>node_reward_type</code> in <code>config.ini</code> matches a type listed under <code>rewardable_nodes</code> for your operator ID.
* Check the node reward settings for the node operator and for the node in case of any problems

Node Deployment config.ini

2025-02-12T16:44:58Z

Sat: Clarify when to set node_reward_type

= node_reward_type Documentation =

The '''node_reward_type''' parameter in the <code>config.ini</code> file indicates the specific node type for which the node operator expects to receive rewards. This value must correspond to a recognized and community-approved node type defined in the Network Nervous System (NNS).

== What is node_reward_type? ==
* It specifies the node’s reward category.
* The chosen type must be compatible with the configurations listed in the NNS node rewards table.
* Common examples include: <code>type1</code>, <code>type1.1</code>, <code>type3</code>, <code>type3.1</code>, etc.

== How to determine your node_reward_type ==
1. Use the <code>ic-admin</code> CLI tool to inspect your node operator configuration. For example:
<pre>ic-admin --nns-url https://ic0.app get-node-operator <your_node_operator_id></pre>
2. In the output, look for the `rewardable_nodes` field. It might look like:
<pre>rewardable_nodes: {"type1": 28}</pre>
This means <code>type1</code> is a valid and approved node type for your account.

3. If multiple types are listed, select the one that best matches your node’s intended reward category.

Example invocation with <code>ic-admin</code>:
<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>

Alternatively, you can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:

<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.

== Possible values ==
The NNS Registry configuration determines which types are valid. Examples:
* <code>node_reward_type=type1</code>
*<code>node_reward_type=type1.1</code>
*<code>node_reward_type=type3</code>
*<code>node_reward_type=type3.1</code>

The set of valid types may change as the community updates NNS configurations. You may get the entire latest reward table list by running:

ic-admin --nns-urls https://ic0.app get-rewards-table

Or for the particular Node Operator record with:

ic-admin --nns-url https://ic0.app get-node-operator <node-operator-id>

== When should I start setting the node_reward_type? ==
You should start setting the <code>node_reward_type</code> for ALL your nodes ALREADY NOW. This does not impact rewards yet, and failure to set the <code>node_reward_type</code> will likely result in failing node registrations in the near future.

== If you do not set node_reward_type ==
If <code>node_reward_type</code> is empty, you should not expect to get rewards for the node, after March 2025.

== Default value ==
If left unset or set to an invalid value, the node registration may fail or may succeed but you may not get rewards for the node.

== How to check ==
Check the node reward type at any time by invoking:

ic-admin --nns-url https://ic0.app get-node <node-id>

Example node record:

Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_record_fvy7i-ux7is-cuvfm-2n2zh-5lpb4-oe2vz-bfnhz-oi5s5-jkzhk-phlj2-gqe
Most recent version is 44039. Value:
Node { xnet: Some("[2800:c20:0:29:6801:29ff:fe18:1f08]:2497"), http: Some("[2800:c20:0:29:6801:29ff:fe18:1f08]:8080"),
node_operator_id: eqv2i-6dtlf-bhbjd-2popw-vvavp-7xzci-6gdd7-qxgox-wdw5w-l3a4w-eae, chip_id: None, hostos_version_id:
Some("2e269c77aa2f6b2353ddad6a4ac3d5ddcac196b1"), public_ipv4_config: None, domain: None, node_reward_type: None }

In this case the <code>node_reward_type</code> for the node is set to None, which means that the node will not get any rewards. The quickest way to resolve this problem is to make changes in the <code>config.ini</code> and redeploy the node.

== Best practices ==
* Ensure <code>node_reward_type</code> in <code>config.ini</code> matches a type listed under <code>rewardable_nodes</code> for your operator ID.
* Check the node reward settings for the node operator and for the node in case of any problems

Node Deployment config.ini

2024-12-19T17:37:48Z

Sat:

= node_reward_type Documentation =

The '''node_reward_type''' parameter in the <code>config.ini</code> file indicates the specific node type for which the node operator expects to receive rewards. This value must correspond to a recognized and community-approved node type defined in the Network Nervous System (NNS).

== What is node_reward_type? ==
* It specifies the node’s reward category.
* The chosen type must be compatible with the configurations listed in the NNS node rewards table.
* Common examples include: <code>type1</code>, <code>type1.1</code>, <code>type3</code>, <code>type3.1</code>, etc.

== How to Determine Your node_reward_type ==
1. Use the <code>ic-admin</code> CLI tool to inspect your node operator configuration. For example:
<pre>ic-admin --nns-url https://ic0.app get-node-operator <your_node_operator_id></pre>
2. In the output, look for the `rewardable_nodes` field. It might look like:
<pre>rewardable_nodes: {"type1": 28}</pre>
This means <code>type1</code> is a valid and approved node type for your account.

3. If multiple types are listed, select the one that best matches your node’s intended reward category.

Example invocation with <code>ic-admin</code>:
<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>

Alternatively, you can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:

<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.

== Possible Values ==
The NNS Registry configuration determines which types are valid. Examples:
* <code>node_reward_type=type1</code>
*<code>node_reward_type=type1.1</code>
*<code>node_reward_type=type3</code>
*<code>node_reward_type=type3.1</code>

The set of valid types may change as the community updates NNS configurations. You may get the entire latest reward table list by running:

ic-admin --nns-urls https://ic0.app get-rewards-table

Or for the particular Node Operator record with:

ic-admin --nns-url https://ic0.app get-node-operator <node-operator-id>

== If you do not set node_reward_type ==
If <code>node_reward_type</code> is empty, you should not expect to get rewards for the node, after March 2025.

== Default value ==
If left unset or set to an invalid value, the node registration may fail or may succeed but you may not get rewards for the node.

== How to check ==
Check the node reward type at any time by invoking:

ic-admin --nns-url https://ic0.app get-node <node-id>

Example node record:

Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_record_fvy7i-ux7is-cuvfm-2n2zh-5lpb4-oe2vz-bfnhz-oi5s5-jkzhk-phlj2-gqe
Most recent version is 44039. Value:
Node { xnet: Some("[2800:c20:0:29:6801:29ff:fe18:1f08]:2497"), http: Some("[2800:c20:0:29:6801:29ff:fe18:1f08]:8080"),
node_operator_id: eqv2i-6dtlf-bhbjd-2popw-vvavp-7xzci-6gdd7-qxgox-wdw5w-l3a4w-eae, chip_id: None, hostos_version_id:
Some("2e269c77aa2f6b2353ddad6a4ac3d5ddcac196b1"), public_ipv4_config: None, domain: None, node_reward_type: None }

In this case the <code>node_reward_type</code> for the node is set to None, which means that the node will not get any rewards. The quickest way to resolve this problem is to make changes in the <code>config.ini</code> and redeploy the node.

== Best Practices ==
* Ensure <code>node_reward_type</code> in <code>config.ini</code> matches a type listed under <code>rewardable_nodes</code> for your operator ID.
* Check the node reward settings for the node operator and for the node in case of any problems

Node Deployment config.ini

2024-12-19T17:33:16Z

Sat: /* Possible Values */

= node_reward_type Documentation =

The '''node_reward_type''' parameter in the <code>config.ini</code> file indicates the specific node type for which the node operator expects to receive rewards. This value must correspond to a recognized and community-approved node type defined in the Network Nervous System (NNS).

== What is node_reward_type? ==
* It specifies the node’s reward category.
* The chosen type must be compatible with the configurations listed in the NNS node rewards table.
* Common examples include: <code>type1</code>, <code>type1.1</code>, <code>type3</code>, <code>type3.1</code>, etc.

== How to Determine Your node_reward_type ==
1. Use the <code>ic-admin</code> CLI tool to inspect your node operator configuration. For example:
<pre>ic-admin --nns-url https://ic0.app get-node-operator <your_node_operator_id></pre>
2. In the output, look for the `rewardable_nodes` field. It might look like:
<pre>rewardable_nodes: {"type1": 28}</pre>
This means <code>type1</code> is a valid and approved node type for your account.

3. If multiple types are listed, select the one that best matches your node’s intended reward category.

Example invocation with <code>ic-admin</code>:
<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>

Alternatively, you can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:

<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.

== Possible Values ==
The NNS Registry configuration determines which types are valid. Examples:
* <code>node_reward_type=type1</code>
*<code>node_reward_type=type1.1</code>
*<code>node_reward_type=type3</code>
*<code>node_reward_type=type3.1</code>

The set of valid types may change as the community updates NNS configurations. You may get the entire latest reward table list by running:

ic-admin --nns-urls https://ic0.app get-rewards-table

Or for the particular Node Operator record with:

ic-admin --nns-url https://ic0.app get-node-operator <node-operator-id>

== If you do not set node_reward_type ==
If <code>node_reward_type</code> is empty, you should not expect to get rewards for the node, after March 2025.

== Default value ==
If left unset or set to an invalid value, the node registration may fail or may succeed but you may not get rewards for the node.

== Best Practices ==
* Ensure <code>node_reward_type</code> in <code>config.ini</code> matches a type listed under <code>rewardable_nodes</code> for your operator ID.
* Check the node reward settings for the node operator in case of any problems
* Check the node reward type at any time by invoking:

ic-admin --nns-url https://ic0.app get-node <node-id>

Node Deployment config.ini

2024-12-19T17:32:45Z

Sat: /* What is node_reward_type? */

= node_reward_type Documentation =

The '''node_reward_type''' parameter in the <code>config.ini</code> file indicates the specific node type for which the node operator expects to receive rewards. This value must correspond to a recognized and community-approved node type defined in the Network Nervous System (NNS).

== What is node_reward_type? ==
* It specifies the node’s reward category.
* The chosen type must be compatible with the configurations listed in the NNS node rewards table.
* Common examples include: <code>type1</code>, <code>type1.1</code>, <code>type3</code>, <code>type3.1</code>, etc.

== How to Determine Your node_reward_type ==
1. Use the <code>ic-admin</code> CLI tool to inspect your node operator configuration. For example:
<pre>ic-admin --nns-url https://ic0.app get-node-operator <your_node_operator_id></pre>
2. In the output, look for the `rewardable_nodes` field. It might look like:
<pre>rewardable_nodes: {"type1": 28}</pre>
This means <code>type1</code> is a valid and approved node type for your account.

3. If multiple types are listed, select the one that best matches your node’s intended reward category.

Example invocation with <code>ic-admin</code>:
<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>

Alternatively, you can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:

<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.

== Possible Values ==
The NNS Registry configuration determines which types are valid. Examples:
* <code>node_reward_type=type1</code>
*<code>node_reward_type=t</code><code>ype1.1</code>
*<code>node_reward_type=</code><code>type3</code>
*<code>node_reward_type=</code><code>type3.1</code>

The set of valid types may change as the community updates NNS configurations. You may get the entire latest reward table list by running:

ic-admin --nns-urls https://ic0.app get-rewards-table

Or for the particular Node Operator record with:

ic-admin --nns-url https://ic0.app get-node-operator <node-operator-id>

== If you do not set node_reward_type ==
If <code>node_reward_type</code> is empty, you should not expect to get rewards for the node, after March 2025.

== Default value ==
If left unset or set to an invalid value, the node registration may fail or may succeed but you may not get rewards for the node.

== Best Practices ==
* Ensure <code>node_reward_type</code> in <code>config.ini</code> matches a type listed under <code>rewardable_nodes</code> for your operator ID.
* Check the node reward settings for the node operator in case of any problems
* Check the node reward type at any time by invoking:

ic-admin --nns-url https://ic0.app get-node <node-id>

Node Deployment Guide

2024-12-19T17:31:39Z

Sat: /* B. Edit Config.ini */

This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS).

The physical machine is expected to be racked and stacked according to its respective manual.

To complete these steps, you are expected to be physically present in the data center your machine(s) reside(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel.

If you encounter issues during any of these steps, consult the [[Troubleshooting Node Deployment Errors]] page.

⚠️ DFINITY does '''not''' offer live support for Node Providers attempting to deploy nodes.

==1. Choose onboarding path (HSM vs. no HSM)==
If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], follow the [[NitroKey HSM installation runbook]] to onboard your nodes.

If you chose to onboard '''without''' a Nitrokey HSM, '''continue to the next step.'''

==2. Obtain requirements ==
*A USB (3.0 speed that can hold at least 4GB) to put the image file on.
**Faster USBs will allow the process to go much faster.
*The <code>node_operator_private_key.pem</code> for your data center (Acquired from [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]])
* It is recommended that each server have a label with the BMC's MAC address for ease of identification in future dashboard upgrades.

== 3. Download installation image==
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases].

* '''Note that you should always use a release from the last 6 weeks (newer is better) in order to ensure that your node can correctly correct to the network.'''

== 4. Verify checksum and unarchive file==
===Mac OS X ===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Windows===
#Open PowerShell and type:
#:<syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.zst</syntaxhighlight>

==5. Create Bootable USB Stick ==
===Mac OS X===
# Open the Terminal and type:
#:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight>

=== Linux / Ubuntu===
#Open the Terminal and type
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight>
# All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo umount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/home/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>

===Windows===
#Download and install [https://rufus.ie/en/ Rufus Portable]
#Start Rufus
#Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
#:[[File:05.png|480px|screenshot]]
#You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
#:[[File:06.png|480px|screenshot]]
#:[[File:07.png|480px|screenshot]]
# The "Ready" bar will go from left to right as it completes.

==6. Add configuration==

===A. Open Config.ini in a text editor===

===='''Mac OS X'''====

#Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:mac_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in TextEdit.

===='''Linux'''====

#Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:linux_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in KWrite.

===='''Windows'''====

#Open the Disk Management utility with a right click on the Start menu
#:[[File:09-b.png|300px|screenshot]]#:
#Right click the CONFIG partition
# Select Change drive letter or paths...
#:[[File:10-b.png|780px|screenshot]]
# Select any letter from the drop-down list
#:[[File:11-b.png|480px|screenshot]]
#Click OK.
#You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file
#:[[File:12-b.png|780px|screenshot]]
#Click on Edit to open it.

===B. Edit Config.ini===

Edit the config.ini file to add your network configuration.

Note that '''all Node Providers are requested to deploy two nodes with IPv4 and a domain name for every data center they operate in'''. Node Providers should deploy IPv4 to the '''first two nodes in their first rack'''.
# Set the appropriate value for the node_reward_type.
#:[[File:Pasted Graphic 7.png|780px|screenshot]]
#:You can find the value to set by following [[Node Deployment config.ini]]
# Insert your IPv6 prefix and gateway.
#:[[File:Pasted Graphic 8.png|780px|screenshot]]
#:* The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
#:*For example, a valid prefix could look like this: <code>2a00:fb01:400:200</code>
#:*'''Important:'''
#:**The prefix should not have a trailing ':'
#:**IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. The '::' shorthand should '''not''' be used. Even if some groups are all zeros, they must be explicitly written out.
#[Optional] Insert your IPv4 info and domain name.
#:[[File:Pasted Graphic 9.png|780px|screenshot]]
#:* Configuring your node with IPv4 settings is optional, but if you do configure your node with IPv4 settings, you must also define the domain name for your node.
#:*'''Important:'''
#:**Please note that you '''must use a unique IPv4 address for each node you deploy'''. This means that you cannot use a single IC-OS installation image to deploy multiple nodes (like you are able to do when just configuring IPv6 nodes). '''After each IPv4 node deployment, you must plug your IC-OS Installation USB stick back into your laptop and return to [[Node Deployment Guide#6. Add configuration|step 6]] in the node deployment guide to reconfigure your installation image.'''
#:**You can add, remove, or update your node’s IPv4 address and domain name after completing node deployment using dfx commands. See [[Updating your node's IPv4 and domain name|here]] for details.
#Save the changes.
#:*If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
#:*:[[File:mac_03.png|580px|screenshot]]

===C. Copy Node Operator private key to config partition===

#Copy <code>node_operator_private_key.pem</code> (created in [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]]) to the <code>CONFIG</code> partition. This file should have the name <code>node_operator_private_key.pem</code>, and sit next to <code>config.ini</code>, NOT inside the <code>ssh_authorized_keys</code> folder.

==7. Connect Crash Cart==
#In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
# Plug-in the VGA/Video, keyboard and IC-OS USB stick
#:[[File:08.png|580px|screenshot]]

==8. UEFI Setup and Boot Menu==

Make sure that server date/time is set to UTC (Universal Time Coordinated)

Use the related page below to set up the BIOS/UEFI according to your hardware vendor.

*[[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]]
**[[IC-OS Installation - UEFI Configuration - Gen2 ASUS]]
*[[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]]
***
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.

Resume from this point when you are finished configuring the BIOS.

== 9. IC-OS Installation==
#Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
#:[[File:35-sm.png|580px|screenshot]]
#The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#:[[File:36-sm.png|580px|screenshot]]
#If the installation finished successfully, it will initiate a reboot.
#:[[File:38-sm.png|580px|screenshot]] 
==10. First Boot==
Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#Once you see this message, you may unplug the USB stick and VGA/Video.
#:[[File:Node join message.png|580px|screenshot]]

Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!

'''Note that if you do NOT see a "Join request successful" message, your node may still have successfully onboarded. Continue to the next step to attempt to verify node onboarding.'''

==11. Verify node onboarding==

#Obtain your Node ID
#*Your Node ID should have been outputted in the previous step. If it wasn't, '''please wait at least 10 minutes to see if the node ID is logged to the console.'''
#Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard]
#*The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node.
#*If the status of your node is either “Awaiting Subnet” or “Active in Subnet,” '''congratulations! Your machine successfully joined the Internet Computer!'''
#*If the status of your node is NOT either “Awaiting Subnet” or “Active in Subnet”, or if it is NOT listed under your Node Provider principal, you should consult the [[Troubleshooting Node Deployment Errors]] page.
#*:[[File:Node onboarding verification.png|680px|screenshot]]
#If deploying with IPv4, verify that IPv4 was successfully configured
#*Ten minutes after the initial <code>Join request successful!</code> message, you should see another log indicating a successful IPv4 deployment:
#*:[[File:IPv4 log.jpg|680px|screenshot]]
#*If your log says <code>IPv4: none configured</code>, then your IPv4 deployment failed.

If you are failing to verify your node onboarding, consult the [[Troubleshooting Node Deployment Errors]] page.

Node Deployment Guide (with an HSM)

2024-12-19T17:30:22Z

Sat:

This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS) using the legacy NitroKey HSM instructions. To use the non-HSM onboarding instructions, follow the [[IC-OS Installation Runbook]].

The physical machine is expected to be racked and stacked according to its respective manual.

To complete these steps, you are expected to be physically present in the data center your machine(s) reside(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel.

If you encounter issues during any of these steps, consult the [[Troubleshooting Node Deployment Errors]] page.

⚠️ DFINITY does '''not''' offer live support for Node Providers attempting to deploy nodes.

==1. Choose onboarding path (HSM vs no HSM)==
If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], '''continue to the next step.'''

If you chose to onboard '''without''' a Nitrokey HSM, follow the [[IC-OS Installation Runbook]] to onboard your nodes.

==2. Obtain requirements==
*A USB (3.0 speed that can hold at least 4GB) to put the image file on.
** Faster USBs will allow the process to go much faster.
*The NitroKey HSM for your data center.
*[Optional] A USB hub
** This is helpful at some data centers for simultaneously connecting keyboard, mouse, Nitrokey, etc.
*It is recommended that each server has a label with the BMC's MAC address for ease of identification in future dashboard upgrades.

==3. Download installation image==
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases].
*'''Note that you should always use a release from the last 6 weeks (newer is better) in order to ensure that your node can correctly correct to the network.'''

==4. Verify checksum and unarchive file==
===Mac OS X===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Windows===
#Open PowerShell and type:
#:<syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.zst</syntaxhighlight>

==5. Create Bootable USB Stick==
===Mac OS X===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo umount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/home/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>

===Windows===
#Download and install [https://rufus.ie/en/ Rufus Portable]
#Start Rufus
#Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
#:[[File:05.png|480px|screenshot]]
#You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
#:[[File:06.png|480px|screenshot]]
#:[[File:07.png|480px|screenshot]]
#The "Ready" bar will go from left to right as it completes.

==6. Add configuration ==

===A. Open Config.ini in a text editor===

===='''Mac OS X'''====

#Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:mac_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in TextEdit.

===='''Linux'''====

#Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:linux_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in KWrite.

===='''Windows'''====

#Open the Disk Management utility with a right click on the Start menu.
#:[[File:09-b.png|300px|screenshot]]#:
#Right click the CONFIG partition.
#Select Change drive letter or paths...
#:[[File:10-b.png|780px|screenshot]]
#Select any letter from the drop-down list.
#:[[File:11-b.png|480px|screenshot]]
# Click OK.
# You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file.
#:[[File:12-b.png|780px|screenshot]]
#Click on Edit to open it.

===B. Edit Config.ini===

Edit the config.ini file to add your network configuration.

Note that '''all Node Providers are requested to deploy two nodes with IPv4 and a domain name for every data center they operate in'''. Node Providers should deploy IPv4 to the '''first two nodes in their first rack'''.
# Set the appropriate value for the node_reward_type.
#:[[File:Pasted Graphic 7.png|780px|screenshot]]
#:You can find the value to set by following [[Node Deployment config.ini]]
#:
#Insert your IPv6 prefix and gateway.
#:[[File:Pasted Graphic 8.png|780px|screenshot]]
#:* The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
#:*For example, a valid prefix could look like this: <code>2a00:fb01:400:200</code>
#:*'''Important:'''
#:**The prefix should not have a trailing ':'
#:**IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. The '::' shorthand should '''not''' be used. Even if some groups are all zeros, they must be explicitly written out.
#[Optional] Insert your IPv4 info and domain name.
#:[[File:Pasted Graphic 9.png|780px|screenshot]]
#:*Configuring your node with IPv4 settings is optional, but if you do configure your node with IPv4 settings, you must also define the domain name for your node.
#:*'''Important:'''
#:**Please note that you '''must use a unique IPv4 address for each node you deploy'''. This means that you cannot use a single IC-OS installation image to deploy multiple nodes (like you are able to do when just configuring IPv6 nodes). '''After each IPv4 node deployment, you must plug your IC-OS Installation USB stick back into your laptop and return to [[Node Deployment Guide#6. Add configuration|step 6]] in the node deployment guide to reconfigure your installation image.'''
#:**You can add, remove, or update your node’s IPv4 address and domain name after completing node deployment using dfx commands. See [[Updating your node's IPv4 and domain name|here]] for details.
#Save the changes.
#:*If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
#:*:[[File:mac_03.png|580px|screenshot]]

== 7. Connect Crash Cart==
# In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
#Plug-in the VGA/Video, keyboard and IC-OS USB stick
#:[[File:08.png|580px|screenshot]]

==8. UEFI Setup and Boot Menu ==
Use the related page below to set up the BIOS/UEFI according to your hardware vendor.

*[[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]]
**[[IC-OS Installation - UEFI Configuration - Gen2 ASUS]]
*[[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]]
***
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.

Resume from this point when you are finished configuring the BIOS.

==9. IC-OS Installation==
#Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
#:[[File:35-sm.png|580px|screenshot]]
#The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#:[[File:36-sm.png|580px|screenshot]]
#Once you get asked to insert the HSM, please remove the keyboard and instead insert the HSM USB device.
#:[[File:37-sm.png|580px|screenshot]]
# If the installation finished successfully, it will initiate a reboot. 🚨 '''Please do not unplug the USB stick or HSM USB''' device at this point. 🚨
#:[[File:38-sm.png|580px|screenshot]]

==10. First Boot==
Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
# The first boot of the IC-OS '''still requires the HSM USB device to be plugged in'''. Please wait to take out the device until further instructions. This step can take several minutes.
#Once you see this message, you may unplug the HSM USB device, USB stick and VGA/Video.
#:[[File:Node join message.png|580px|screenshot]]

Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!

'''Note that if you do NOT see a "Join request successful" message, your node may still have successfully onboarded. Continue to the next step to attempt to verify node onboarding.'''

== 11. Verify node onboarding==

#Obtain your Node ID
#*Your Node ID should have been outputted in the previous step. If it wasn't, '''please wait at least 10 minutes to see if the node ID is logged to the console.'''
#Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard]
#*The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node.
#*If the status of your node is either “Awaiting Subnet” or “Active in Subnet,” '''congratulations! Your machine successfully joined the Internet Computer!'''
#*If the status of your node is NOT either “Awaiting Subnet” or “Active in Subnet”, or if it is NOT listed under your Node Provider principal, you should consult the [[Troubleshooting Node Deployment Errors]] page.
#*:[[File:Node onboarding verification.png|680px|screenshot]]
#If deploying with IPv4, verify that IPv4 was successfully configured
#*Ten minutes after the initial <code>Join request successful!</code> message, you should see another log indicating a successful IPv4 deployment:
#*:[[File:IPv4 log.jpg|680px|screenshot]]
#*If your log says <code>IPv4: none configured</code>, then your IPv4 deployment failed.

If you are failing to verify your node onboarding, consult the [[Troubleshooting Node Deployment Errors]] page.

Node Deployment config.ini

2024-12-19T17:28:47Z

Sat: /* How to Determine Your node_reward_type */

= node_reward_type Documentation =

The '''node_reward_type''' parameter in the <code>config.ini</code> file indicates the specific node type for which the node operator expects to receive rewards. This value must correspond to a recognized and community-approved node type defined in the Network Nervous System (NNS).

== What is node_reward_type? ==
* It specifies the node’s reward category.
* The chosen type must be compatible with the configurations listed in the NNS node rewards table.
* Common examples include: <code>type1</code>, <code>type1.1</code>, <code>type3</code>, <code>type3.1</code>, etc.

== How to Determine Your node_reward_type ==
1. Use the <code>ic-admin</code> CLI tool to inspect your node operator configuration. For example:
<pre>ic-admin --nns-url https://ic0.app get-node-operator <your_node_operator_id></pre>
2. In the output, look for the `rewardable_nodes` field. It might look like:
<pre>rewardable_nodes: {"type1": 28}</pre>
This means <code>type1</code> is a valid and approved node type for your account.

3. If multiple types are listed, select the one that best matches your node’s intended reward category.

Example invocation with <code>ic-admin</code>:
<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>

Alternatively, you can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:

<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.

== Possible Values ==
The NNS Registry configuration determines which types are valid. Examples:
* <code>type1</code>
* <code>type1.1</code>
* <code>type3</code>
* <code>type3.1</code>

The set of valid types may change as the community updates NNS configurations. You may get the entire latest reward table list by running:

ic-admin --nns-urls https://ic0.app get-rewards-table

Or for the particular Node Operator record with:

ic-admin --nns-url https://ic0.app get-node-operator <node-operator-id>

== If you do not set node_reward_type ==
If <code>node_reward_type</code> is empty, you should not expect to get rewards for the node, after March 2025.

== Default value ==
If left unset or set to an invalid value, the node registration may fail or may succeed but you may not get rewards for the node.

== Best Practices ==
* Ensure <code>node_reward_type</code> in <code>config.ini</code> matches a type listed under <code>rewardable_nodes</code> for your operator ID.
* Check the node reward settings for the node operator in case of any problems
* Check the node reward type at any time by invoking:

ic-admin --nns-url https://ic0.app get-node <node-id>

Node Deployment config.ini

2024-12-19T17:28:26Z

Sat:

= node_reward_type Documentation =

The '''node_reward_type''' parameter in the <code>config.ini</code> file indicates the specific node type for which the node operator expects to receive rewards. This value must correspond to a recognized and community-approved node type defined in the Network Nervous System (NNS).

== What is node_reward_type? ==
* It specifies the node’s reward category.
* The chosen type must be compatible with the configurations listed in the NNS node rewards table.
* Common examples include: <code>type1</code>, <code>type1.1</code>, <code>type3</code>, <code>type3.1</code>, etc.

== How to Determine Your node_reward_type ==
1. Use the <code>ic-admin</code> CLI tool to inspect your node operator configuration. For example:
<pre>ic-admin --nns-url https://ic0.app get-node-operator <your_node_operator_id></pre>
2. In the output, look for the `rewardable_nodes` field. It might look like:
<pre>rewardable_nodes: {"type1": 28}</pre>
This means <code>type1</code> is a valid and approved node type for your account.
3. If multiple types are listed, select the one that best matches your node’s intended reward category.

Example invocation with <code>ic-admin</code>:
<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>

Alternatively, you can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:

<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.

== Possible Values ==
The NNS Registry configuration determines which types are valid. Examples:
* <code>type1</code>
* <code>type1.1</code>
* <code>type3</code>
* <code>type3.1</code>

The set of valid types may change as the community updates NNS configurations. You may get the entire latest reward table list by running:

ic-admin --nns-urls https://ic0.app get-rewards-table

Or for the particular Node Operator record with:

ic-admin --nns-url https://ic0.app get-node-operator <node-operator-id>

== If you do not set node_reward_type ==
If <code>node_reward_type</code> is empty, you should not expect to get rewards for the node, after March 2025.

== Default value ==
If left unset or set to an invalid value, the node registration may fail or may succeed but you may not get rewards for the node.

== Best Practices ==
* Ensure <code>node_reward_type</code> in <code>config.ini</code> matches a type listed under <code>rewardable_nodes</code> for your operator ID.
* Check the node reward settings for the node operator in case of any problems
* Check the node reward type at any time by invoking:

ic-admin --nns-url https://ic0.app get-node <node-id>

Node Deployment Guide (with an HSM)

2024-12-19T17:25:31Z

Sat: /* B. Edit Config.ini */

This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS) using the legacy NitroKey HSM instructions. To use the non-HSM onboarding instructions, follow the [[IC-OS Installation Runbook]].

The physical machine is expected to be racked and stacked according to its respective manual.

To complete these steps, you are expected to be physically present in the data center your machine(s) reside(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel.

If you encounter issues during any of these steps, consult the [[Troubleshooting Node Deployment Errors]] page.

⚠️ DFINITY does '''not''' offer live support for Node Providers attempting to deploy nodes.

==1. Choose onboarding path (HSM vs no HSM)==
If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], '''continue to the next step.'''

If you chose to onboard '''without''' a Nitrokey HSM, follow the [[IC-OS Installation Runbook]] to onboard your nodes.

==2. Obtain requirements==
*A USB (3.0 speed that can hold at least 4GB) to put the image file on.
** Faster USBs will allow the process to go much faster.
*The NitroKey HSM for your data center.
*[Optional] A USB hub
** This is helpful at some data centers for simultaneously connecting keyboard, mouse, Nitrokey, etc.
*It is recommended that each server has a label with the BMC's MAC address for ease of identification in future dashboard upgrades.

==3. Download installation image==
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases].
*'''Note that you should always use a release from the last 6 weeks (newer is better) in order to ensure that your node can correctly correct to the network.'''

==4. Verify checksum and unarchive file==
===Mac OS X===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Windows===
#Open PowerShell and type:
#:<syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.zst</syntaxhighlight>

==5. Create Bootable USB Stick==
===Mac OS X===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo umount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/home/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>

===Windows===
#Download and install [https://rufus.ie/en/ Rufus Portable]
#Start Rufus
#Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
#:[[File:05.png|480px|screenshot]]
#You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
#:[[File:06.png|480px|screenshot]]
#:[[File:07.png|480px|screenshot]]
#The "Ready" bar will go from left to right as it completes.

==6. Add configuration ==

===A. Open Config.ini in a text editor===

===='''Mac OS X'''====

#Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:mac_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in TextEdit.

===='''Linux'''====

#Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:linux_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in KWrite.

===='''Windows'''====

#Open the Disk Management utility with a right click on the Start menu.
#:[[File:09-b.png|300px|screenshot]]#:
#Right click the CONFIG partition.
#Select Change drive letter or paths...
#:[[File:10-b.png|780px|screenshot]]
#Select any letter from the drop-down list.
#:[[File:11-b.png|480px|screenshot]]
# Click OK.
# You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file.
#:[[File:12-b.png|780px|screenshot]]
#Click on Edit to open it.

===B. Edit Config.ini===

Edit the config.ini file to add your network configuration.

Note that '''all Node Providers are requested to deploy two nodes with IPv4 and a domain name for every data center they operate in'''. Node Providers should deploy IPv4 to the '''first two nodes in their first rack'''.
# Insert your node reward type.
#:[[File:Pasted Graphic 7.png|780px|screenshot]]
#:You can find the value to set by following [[Node Deployment config.ini]]
#:
#Insert your IPv6 prefix and gateway.
#:[[File:Pasted Graphic 8.png|780px|screenshot]]
#:* The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
#:*For example, a valid prefix could look like this: <code>2a00:fb01:400:200</code>
#:*'''Important:'''
#:**The prefix should not have a trailing ':'
#:**IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. The '::' shorthand should '''not''' be used. Even if some groups are all zeros, they must be explicitly written out.
#[Optional] Insert your IPv4 info and domain name.
#:[[File:Pasted Graphic 9.png|780px|screenshot]]
#:*Configuring your node with IPv4 settings is optional, but if you do configure your node with IPv4 settings, you must also define the domain name for your node.
#:*'''Important:'''
#:**Please note that you '''must use a unique IPv4 address for each node you deploy'''. This means that you cannot use a single IC-OS installation image to deploy multiple nodes (like you are able to do when just configuring IPv6 nodes). '''After each IPv4 node deployment, you must plug your IC-OS Installation USB stick back into your laptop and return to [[Node Deployment Guide#6. Add configuration|step 6]] in the node deployment guide to reconfigure your installation image.'''
#:**You can add, remove, or update your node’s IPv4 address and domain name after completing node deployment using dfx commands. See [[Updating your node's IPv4 and domain name|here]] for details.
#Save the changes.
#:*If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
#:*:[[File:mac_03.png|580px|screenshot]]

== 7. Connect Crash Cart==
# In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
#Plug-in the VGA/Video, keyboard and IC-OS USB stick
#:[[File:08.png|580px|screenshot]]

==8. UEFI Setup and Boot Menu ==
Use the related page below to set up the BIOS/UEFI according to your hardware vendor.

*[[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]]
**[[IC-OS Installation - UEFI Configuration - Gen2 ASUS]]
*[[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]]
***
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.

Resume from this point when you are finished configuring the BIOS.

==9. IC-OS Installation==
#Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
#:[[File:35-sm.png|580px|screenshot]]
#The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#:[[File:36-sm.png|580px|screenshot]]
#Once you get asked to insert the HSM, please remove the keyboard and instead insert the HSM USB device.
#:[[File:37-sm.png|580px|screenshot]]
# If the installation finished successfully, it will initiate a reboot. 🚨 '''Please do not unplug the USB stick or HSM USB''' device at this point. 🚨
#:[[File:38-sm.png|580px|screenshot]]

==10. First Boot==
Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
# The first boot of the IC-OS '''still requires the HSM USB device to be plugged in'''. Please wait to take out the device until further instructions. This step can take several minutes.
#Once you see this message, you may unplug the HSM USB device, USB stick and VGA/Video.
#:[[File:Node join message.png|580px|screenshot]]

Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!

'''Note that if you do NOT see a "Join request successful" message, your node may still have successfully onboarded. Continue to the next step to attempt to verify node onboarding.'''

== 11. Verify node onboarding==

#Obtain your Node ID
#*Your Node ID should have been outputted in the previous step. If it wasn't, '''please wait at least 10 minutes to see if the node ID is logged to the console.'''
#Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard]
#*The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node.
#*If the status of your node is either “Awaiting Subnet” or “Active in Subnet,” '''congratulations! Your machine successfully joined the Internet Computer!'''
#*If the status of your node is NOT either “Awaiting Subnet” or “Active in Subnet”, or if it is NOT listed under your Node Provider principal, you should consult the [[Troubleshooting Node Deployment Errors]] page.
#*:[[File:Node onboarding verification.png|680px|screenshot]]
#If deploying with IPv4, verify that IPv4 was successfully configured
#*Ten minutes after the initial <code>Join request successful!</code> message, you should see another log indicating a successful IPv4 deployment:
#*:[[File:IPv4 log.jpg|680px|screenshot]]
#*If your log says <code>IPv4: none configured</code>, then your IPv4 deployment failed.

If you are failing to verify your node onboarding, consult the [[Troubleshooting Node Deployment Errors]] page.

Node Deployment config.ini

2024-12-19T17:23:25Z

Sat: Created page with "= node_reward_type Documentation = The '''node_reward_type''' parameter in the <code>config.ini</code> file indicates the specific node type for which the node operator expec..."

Node Provider Onboarding

2024-12-19T12:08:24Z

Sat: /* A. Install ic-admin */

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|Node Provider Maintenance Guide.]]

== '''<big>Requirements</big>''' ==
* Assure your node(s) meet the [[Node Provider Machine Hardware Guide|Node Provider Machine Hardware requirements.]]
* View the [[Node Provider Networking Guide|Node Provider Networking Guide.]]
* Setup a [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, such as 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. You can install it by running the following in a terminal:

==== MacOS ====
<syntaxhighlight lang="shell">
curl -L "https://github.com/dfinity/ic/releases/latest/download/ic-admin-x86_64-darwin.gz" -o - | gunzip > ic-admin && chmod 0755 ./ic-admin

</syntaxhighlight>

==== Linux ====
NOTE: The instructions below have been tested with the Ubuntu 20.04 release<syntaxhighlight lang="shell">
curl -L "https://github.com/dfinity/ic/releases/latest/download/ic-admin-x86_64-linux.gz" -o - | gunzip > ic-admin && chmod 0755 ./ic-admin
</syntaxhighlight>

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

#<code>dfx</code> is a CLI tool used to generate neuron hotkeys, among other things such as canister deployment and management. <syntaxhighlight lang="shell">
$ sh -ci "$(curl -fsSL https://internetcomputer.org/install.sh)"

</syntaxhighlight>
#Verify that <code>dfx</code> 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 h'''otkey''' <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''': The Node Provider hotkey is NOT the Node Provider principal. This is the hotkey that is used for the NNS proposal submissions only.

'''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.

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

#Send at least 11 ICP tokens to your hardware wallet address.
#Navigate to the Neurons tab and create a Neuron by staking at least 10 ICP from your hardware wallet. Staking more ICP is acceptable, but 10 is the minimum needed for this process, 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 current onboarding path. In particular, node providers onboarding [[Node Provider Machine Hardware Guide|Gen 2 hardware]] must onboard '''without''' a NitroKey HSM. If you will be onboarding '''without''' a NitroKey HSM, continue to the next step.

If the legacy procedure is required for your onboarding (which should only be the case in rare and exceptional situations), follow the [[NitroKey HSM onboarding instructions]] and then '''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>Note: make sure <code>${NODE_PROVIDER_NAME}</code> is presented in single quotes, so the IC dashboard can pick up and display the correct Node Provider name.
#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.

''See guide for [[Troubleshooting Failed NNS proposals]]''

==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.

''See guide for [[Troubleshooting Failed NNS proposals]]''

==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.

''See guide for [[Troubleshooting Failed NNS proposals]]''

Node Provider Onboarding

2024-12-19T12:06:42Z

Sat: /* A. Install ic-admin */

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|Node Provider Maintenance Guide.]]

== '''<big>Requirements</big>''' ==
* Assure your node(s) meet the [[Node Provider Machine Hardware Guide|Node Provider Machine Hardware requirements.]]
* View the [[Node Provider Networking Guide|Node Provider Networking Guide.]]
* Setup a [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, such as 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 ====
# To install <code>ic-admin</code>, run the following in a terminal: <syntaxhighlight lang="shell">
curl -L "https://github.com/dfinity/ic/releases/latest/download/ic-admin-x86_64-darwin.gz" -o - | gunzip > ic-admin && chmod 0755 ./ic-admin

</syntaxhighlight>

==== Linux ====
NOTE: The instructions below have been tested with the Ubuntu 20.04 release.
# To install <code>ic-admin</code>, run the following in a terminal: <syntaxhighlight lang="shell">
curl -L "https://github.com/dfinity/ic/releases/latest/download/ic-admin-x86_64-linux.gz" -o - | gunzip > ic-admin && chmod 0755 ./ic-admin
</syntaxhighlight>

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

#<code>dfx</code> is a CLI tool used to generate neuron hotkeys, among other things such as canister deployment and management. <syntaxhighlight lang="shell">
$ sh -ci "$(curl -fsSL https://internetcomputer.org/install.sh)"

</syntaxhighlight>
#Verify that <code>dfx</code> 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 h'''otkey''' <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''': The Node Provider hotkey is NOT the Node Provider principal. This is the hotkey that is used for the NNS proposal submissions only.

'''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.

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

#Send at least 11 ICP tokens to your hardware wallet address.
#Navigate to the Neurons tab and create a Neuron by staking at least 10 ICP from your hardware wallet. Staking more ICP is acceptable, but 10 is the minimum needed for this process, 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 current onboarding path. In particular, node providers onboarding [[Node Provider Machine Hardware Guide|Gen 2 hardware]] must onboard '''without''' a NitroKey HSM. If you will be onboarding '''without''' a NitroKey HSM, continue to the next step.

If the legacy procedure is required for your onboarding (which should only be the case in rare and exceptional situations), follow the [[NitroKey HSM onboarding instructions]] and then '''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>Note: make sure <code>${NODE_PROVIDER_NAME}</code> is presented in single quotes, so the IC dashboard can pick up and display the correct Node Provider name.
#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.

''See guide for [[Troubleshooting Failed NNS proposals]]''

==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.

''See guide for [[Troubleshooting Failed NNS proposals]]''

==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.

''See guide for [[Troubleshooting Failed NNS proposals]]''

Node Provider Onboarding

2024-12-19T11:58:18Z

Sat: /* A. Install ic-admin */ - add a direct link to the latest

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|Node Provider Maintenance Guide.]]

== '''<big>Requirements</big>''' ==
* Assure your node(s) meet the [[Node Provider Machine Hardware Guide|Node Provider Machine Hardware requirements.]]
* View the [[Node Provider Networking Guide|Node Provider Networking Guide.]]
* Setup a [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, such as 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 ====
# To install <code>ic-admin</code>, view the latest release version in the [https://github.com/dfinity/ic/releases/latest DFINITY/ic repo]. Then, use the following URL <syntaxhighlight lang="shell">
$ curl -L "https://github.com/dfinity/ic/releases/latest/download/ic-admin-x86_64-darwin.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 035abf8925bf54e067d13eee0a6205e883507d6138bcd232ec8069301a9b190a) && 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.
# To install <code>ic-admin</code>, view the latest release version in the [https://github.com/dfinity/ic/releases/latest DFINITY/ic repo]. Then, use the following URL <syntaxhighlight lang="shell">
$ curl -L "https://github.com/dfinity/ic/releases/latest/download/ic-admin-x86_64-linux.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 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

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

#<code>dfx</code> is a CLI tool used to generate neuron hotkeys, among other things such as canister deployment and management. <syntaxhighlight lang="shell">
$ sh -ci "$(curl -fsSL https://internetcomputer.org/install.sh)"

</syntaxhighlight>
#Verify that <code>dfx</code> 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 h'''otkey''' <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''': The Node Provider hotkey is NOT the Node Provider principal. This is the hotkey that is used for the NNS proposal submissions only.

'''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.

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

#Send at least 11 ICP tokens to your hardware wallet address.
#Navigate to the Neurons tab and create a Neuron by staking at least 10 ICP from your hardware wallet. Staking more ICP is acceptable, but 10 is the minimum needed for this process, 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 current onboarding path. In particular, node providers onboarding [[Node Provider Machine Hardware Guide|Gen 2 hardware]] must onboard '''without''' a NitroKey HSM. If you will be onboarding '''without''' a NitroKey HSM, continue to the next step.

If the legacy procedure is required for your onboarding (which should only be the case in rare and exceptional situations), follow the [[NitroKey HSM onboarding instructions]] and then '''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>Note: make sure <code>${NODE_PROVIDER_NAME}</code> is presented in single quotes, so the IC dashboard can pick up and display the correct Node Provider name.
#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.

''See guide for [[Troubleshooting Failed NNS proposals]]''

==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.

''See guide for [[Troubleshooting Failed NNS proposals]]''

==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.

''See guide for [[Troubleshooting Failed NNS proposals]]''

NitroKey HSM onboarding instructions

2024-11-26T14:57:48Z

Sat: /* MacOS */

The NitroKey HSM onboarding path is the '''legacy onboarding path'''. Onboarding '''without''' a NitroKey HSM is the recommended onboarding path. In particular, node providers onboarding [[Node Provider Machine Hardware Guide|Gen 2 hardware]] must onboard '''without''' a NitroKey HSM. To onboard '''without''' a NitroKey HSM, return to the [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding]].

If you wish to use the NitroKey HSM onboarding, follow steps 5-7 before returning to the [[Node Provider Onboarding]] instructions.
==5. Install tools==
It's first necessary to install the necessary tools.
===MacOS===
#Download this OpenSC binary: https://github.com/OpenSC/OpenSC/releases/download/0.22.0/OpenSC-0.22.0.dmg
#Double click the DMG image that you downloaded and then double click the OpenSC PKG file.
#If your system doesn't allow the installation software from an unidentified developer please follow these steps or contact your system administrator:
#*Choose the Apple menu > System Preferences > click Security and Privacy.
#*Click the lock Icon to unlock it, then enter an administrator name and password.
#*Ensure that you're on the tab named “General”.
#*You should see the OpenSC app and you should be able to enable its installation by choosing “Open anyway”.
#Click continue and install until the installation is complete.
#:'''NOTE''': If you’re getting a CKR_DEVICE_ERROR when using your NitroKey and are using '''macOS Sonoma''':
#:<code>Error while trying to read the public key from the HSM. Underlying error: Utility command failed with status exit status: 1: Error while running '`pkcs11-tool --read-object --slot 0 --type pubkey --id 01` input: ': error: PKCS11 function C_OpenSession failed: rv = CKR_DEVICE_ERROR (0x30)</code>
#:Run the following (this will restart your machine) and your nitrokey should start working again:<syntaxhighlight lang="shell">
sudo mkdir -p /usr/local/libexec/SmartCardServices/drivers

sudo cp -a /usr/libexec/SmartCardServices/drivers/ifd-ccid.bundle /usr/local/libexec/SmartCardServices/drivers
sudo reboot
</syntaxhighlight>Source: https://github.com/OpenSC/OpenSC/issues/2887#issuecomment-1810783804
===Linux===
NOTE: The instructions below have been tested with the Ubuntu 20.04 release.

Install pcscd and opensc:
:<syntaxhighlight lang="shell">
$ sudo add-apt-repository universe
$ sudo apt update
$ sudo apt install pcscd opensc
</syntaxhighlight>
== 6. Setup the Node Operator keys==
#Initialize the HSM.<syntaxhighlight lang="shell">
$ sc-hsm-tool --initialize --so-pin 3537363231383830 --pin 358138
</syntaxhighlight>
#Change the HSM so-pin.
#*'''WARNING:''' The new HSM so pin must have 16 hexadecimal digits. This is not very well known, and some HSM users have lost access to a Nitrokey HSM because they tried using regular characters and the command below accepted it.
#*'''Do NOT change the user pin. It must remain as the default for the onboarding scripts to work'''<syntaxhighlight lang="shell">
$ pkcs11-tool --login --login-type so --so-pin 3537363231383830 --change-pin
</syntaxhighlight>
#Create a keypair on the HSM. Enter the default pin 358138 when prompted.<syntaxhighlight lang="shell">
$ pkcs11-tool -k --key-type EC:prime256v1 --login -d 01
</syntaxhighlight>
#*'''Note:''' Key backup may be possible with [https://github.com/OpenSC/OpenSC/wiki/SmartCardHSM#using-key-backup-and-restore these instructions].
==7. Get the node operator principal==
# Configure dfx identity (skip this step if you already configured it for another HSM).
#*'''Note:''' Depending on your installation, the path to the <code>--hsm-pkcs11-lib-path</code> might be different on your platform. You can locate the correct path with the following command:<syntaxhighlight lang="shell">
$ find / -name opensc-pkcs11.so 2> /dev/null
</syntaxhighlight>
#*MacOS<syntaxhighlight lang="shell">
$ dfx identity new node-operator-hsm --hsm-key-id 01 --hsm-pkcs11-lib-path /Library/OpenSC/lib/opensc-pkcs11.so
</syntaxhighlight>
#*Linux<syntaxhighlight lang="shell">
$ dfx identity new node-operator-hsm --hsm-key-id 01 --hsm-pkcs11-lib-path /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
</syntaxhighlight>
#Get the principal.<syntaxhighlight lang="shell">
$ NODE_OPERATOR_PRINCIPAL=$(DFX_HSM_PIN=358138 dfx --identity node-operator-hsm identity get-principal)
$ echo $NODE_OPERATOR_PRINCIPAL

uqquy-76uhn-2mys5-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
</syntaxhighlight>

Note: you must retain access to the HSM for when you onboard nodes in [[Node Provider Roadmap#Milestone%20Five:%20Node%20Machine%20Onboarding|roadmap milestone five.]]

==='''At this point, return to step 8 of the [[Node Provider Onboarding#8. Register your Node Provider principal to the network|Node Provider Onboarding]] instructions'''===

NitroKey HSM onboarding instructions

2024-11-26T14:56:47Z

Sat: /* MacOS */

The NitroKey HSM onboarding path is the '''legacy onboarding path'''. Onboarding '''without''' a NitroKey HSM is the recommended onboarding path. In particular, node providers onboarding [[Node Provider Machine Hardware Guide|Gen 2 hardware]] must onboard '''without''' a NitroKey HSM. To onboard '''without''' a NitroKey HSM, return to the [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding]].

If you wish to use the NitroKey HSM onboarding, follow steps 5-7 before returning to the [[Node Provider Onboarding]] instructions.
==5. Install tools==
It's first necessary to install the necessary tools.
===MacOS===
#Download this OpenSC binary: https://github.com/OpenSC/OpenSC/releases/download/0.22.0/OpenSC-0.22.0.dmg
#Double click the DMG image that you downloaded and then double click the OpenSC PKG file.
#If your system doesn't allow the installation software from an unidentified developer please follow these steps or contact your system administrator:
#*Choose the Apple menu > System Preferences > click Security and Privacy.
#*Click the lock Icon to unlock it, then enter an administrator name and password.
#*Ensure that you're on the tab named “General”.
#*You should see the OpenSC app and you should be able to enable its installation by choosing “Open anyway”.
#Click continue and install until the installation is complete.
#:NOTE: If you’re getting a CKR_DEVICE_ERROR when using your NitroKey and are using macOS Sonoma:
#:<code>Error while trying to read the public key from the HSM. Underlying error: Utility command failed with status exit status: 1: Error while running '`pkcs11-tool --read-object --slot 0 --type pubkey --id 01` input: ': error: PKCS11 function C_OpenSession failed: rv = CKR_DEVICE_ERROR (0x30)</code>
#:Run the following (this will restart your machine) and your nitrokey should start working again:<syntaxhighlight lang="shell">
sudo mkdir -p /usr/local/libexec/SmartCardServices/drivers

sudo cp -a /usr/libexec/SmartCardServices/drivers/ifd-ccid.bundle /usr/local/libexec/SmartCardServices/drivers
sudo reboot
</syntaxhighlight>Source: https://github.com/OpenSC/OpenSC/issues/2887#issuecomment-1810783804
===Linux===
NOTE: The instructions below have been tested with the Ubuntu 20.04 release.

Install pcscd and opensc:
:<syntaxhighlight lang="shell">
$ sudo add-apt-repository universe
$ sudo apt update
$ sudo apt install pcscd opensc
</syntaxhighlight>
== 6. Setup the Node Operator keys==
#Initialize the HSM.<syntaxhighlight lang="shell">
$ sc-hsm-tool --initialize --so-pin 3537363231383830 --pin 358138
</syntaxhighlight>
#Change the HSM so-pin.
#*'''WARNING:''' The new HSM so pin must have 16 hexadecimal digits. This is not very well known, and some HSM users have lost access to a Nitrokey HSM because they tried using regular characters and the command below accepted it.
#*'''Do NOT change the user pin. It must remain as the default for the onboarding scripts to work'''<syntaxhighlight lang="shell">
$ pkcs11-tool --login --login-type so --so-pin 3537363231383830 --change-pin
</syntaxhighlight>
#Create a keypair on the HSM. Enter the default pin 358138 when prompted.<syntaxhighlight lang="shell">
$ pkcs11-tool -k --key-type EC:prime256v1 --login -d 01
</syntaxhighlight>
#*'''Note:''' Key backup may be possible with [https://github.com/OpenSC/OpenSC/wiki/SmartCardHSM#using-key-backup-and-restore these instructions].
==7. Get the node operator principal==
# Configure dfx identity (skip this step if you already configured it for another HSM).
#*'''Note:''' Depending on your installation, the path to the <code>--hsm-pkcs11-lib-path</code> might be different on your platform. You can locate the correct path with the following command:<syntaxhighlight lang="shell">
$ find / -name opensc-pkcs11.so 2> /dev/null
</syntaxhighlight>
#*MacOS<syntaxhighlight lang="shell">
$ dfx identity new node-operator-hsm --hsm-key-id 01 --hsm-pkcs11-lib-path /Library/OpenSC/lib/opensc-pkcs11.so
</syntaxhighlight>
#*Linux<syntaxhighlight lang="shell">
$ dfx identity new node-operator-hsm --hsm-key-id 01 --hsm-pkcs11-lib-path /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
</syntaxhighlight>
#Get the principal.<syntaxhighlight lang="shell">
$ NODE_OPERATOR_PRINCIPAL=$(DFX_HSM_PIN=358138 dfx --identity node-operator-hsm identity get-principal)
$ echo $NODE_OPERATOR_PRINCIPAL

uqquy-76uhn-2mys5-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
</syntaxhighlight>

Note: you must retain access to the HSM for when you onboard nodes in [[Node Provider Roadmap#Milestone%20Five:%20Node%20Machine%20Onboarding|roadmap milestone five.]]

==='''At this point, return to step 8 of the [[Node Provider Onboarding#8. Register your Node Provider principal to the network|Node Provider Onboarding]] instructions'''===

Node Deployment Guide

2024-11-26T13:09:20Z

Sat: /* B. Edit Config.ini */

This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS).

The physical machine is expected to be racked and stacked according to its respective manual.

To complete these steps, you are expected to be physically present in the data center your machine(s) reside(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel.

If you encounter issues during any of these steps, consult the [[Troubleshooting Node Deployment Errors]] page.

⚠️ DFINITY does '''not''' offer live support for Node Providers attempting to deploy nodes.

==1. Choose onboarding path (HSM vs. no HSM)==
If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], follow the [[NitroKey HSM installation runbook]] to onboard your nodes.

If you chose to onboard '''without''' a Nitrokey HSM, '''continue to the next step.'''

==2. Obtain requirements ==
*A USB (3.0 speed that can hold at least 4GB) to put the image file on.
**Faster USBs will allow the process to go much faster.
*The <code>node_operator_private_key.pem</code> for your data center (Acquired from [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]])
* It is recommended that each server have a label with the BMC's MAC address for ease of identification in future dashboard upgrades.

== 3. Download installation image==
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases].

* '''Note that you should always use a release from the last 6 weeks (newer is better) in order to ensure that your node can correctly correct to the network.'''

== 4. Verify checksum and unarchive file==
===Mac OS X ===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Windows===
#Open PowerShell and type:
#:<syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.zst</syntaxhighlight>

==5. Create Bootable USB Stick ==
===Mac OS X===
# Open the Terminal and type:
#:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight>

=== Linux / Ubuntu===
#Open the Terminal and type
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight>
# All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo umount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/home/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>

===Windows===
#Download and install [https://rufus.ie/en/ Rufus Portable]
#Start Rufus
#Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
#:[[File:05.png|480px|screenshot]]
#You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
#:[[File:06.png|480px|screenshot]]
#:[[File:07.png|480px|screenshot]]
# The "Ready" bar will go from left to right as it completes.

==6. Add configuration==

===A. Open Config.ini in a text editor===

===='''Mac OS X'''====

#Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:mac_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in TextEdit.

===='''Linux'''====

#Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:linux_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in KWrite.

===='''Windows'''====

#Open the Disk Management utility with a right click on the Start menu
#:[[File:09-b.png|300px|screenshot]]#:
#Right click the CONFIG partition
# Select Change drive letter or paths...
#:[[File:10-b.png|780px|screenshot]]
# Select any letter from the drop-down list
#:[[File:11-b.png|480px|screenshot]]
#Click OK.
#You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file
#:[[File:12-b.png|780px|screenshot]]
#Click on Edit to open it.

===B. Edit Config.ini===

Edit the config.ini file to add your network configuration.

Note that '''all Node Providers are requested to deploy two nodes with IPv4 and a domain name for every data center they operate in'''. Node Providers should deploy IPv4 to the '''first two nodes in their first rack'''.
# Insert your node reward type.
#:[[File:Pasted Graphic 7.png|780px|screenshot]]
#:You can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:
#:<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.
#:
#:Alternatively, you can get similar information with `ic-admin`. For instance: <syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>
#:
# Insert your IPv6 prefix and gateway.
#:[[File:Pasted Graphic 8.png|780px|screenshot]]
#:* The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
#:*For example, a valid prefix could look like this: <code>2a00:fb01:400:200</code>
#:*'''Important:'''
#:**The prefix should not have a trailing ':'
#:**IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. The '::' shorthand should '''not''' be used. Even if some groups are all zeros, they must be explicitly written out.
#[Optional] Insert your IPv4 info and domain name.
#:[[File:Pasted Graphic 9.png|780px|screenshot]]
#:* Configuring your node with IPv4 settings is optional, but if you do configure your node with IPv4 settings, you must also define the domain name for your node.
#:*'''Important:'''
#:**Please note that you '''must use a unique IPv4 address for each node you deploy'''. This means that you cannot use a single IC-OS installation image to deploy multiple nodes (like you are able to do when just configuring IPv6 nodes). '''After each IPv4 node deployment, you must plug your IC-OS Installation USB stick back into your laptop and return to [[Node Deployment Guide#6. Add configuration|step 6]] in the node deployment guide to reconfigure your installation image.'''
#:**You can add, remove, or update your node’s IPv4 address and domain name after completing node deployment using dfx commands. See [[Updating your node's IPv4 and domain name|here]] for details.
#Save the changes.
#:*If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
#:*:[[File:mac_03.png|580px|screenshot]]

===C. Copy Node Operator private key to config partition===

#Copy <code>node_operator_private_key.pem</code> (created in [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]]) to the <code>CONFIG</code> partition. This file should have the name <code>node_operator_private_key.pem</code>, and sit next to <code>config.ini</code>, NOT inside the <code>ssh_authorized_keys</code> folder.

==7. Connect Crash Cart==
#In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
# Plug-in the VGA/Video, keyboard and IC-OS USB stick
#:[[File:08.png|580px|screenshot]]

==8. UEFI Setup and Boot Menu==

Make sure that server date/time is set to UTC (Universal Time Coordinated)

Use the related page below to set up the BIOS/UEFI according to your hardware vendor.

*[[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]]
**[[IC-OS Installation - UEFI Configuration - Gen2 ASUS]]
*[[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]]
***
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.

Resume from this point when you are finished configuring the BIOS.

== 9. IC-OS Installation==
#Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
#:[[File:35-sm.png|580px|screenshot]]
#The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#:[[File:36-sm.png|580px|screenshot]]
#If the installation finished successfully, it will initiate a reboot.
#:[[File:38-sm.png|580px|screenshot]] 
==10. First Boot==
Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#Once you see this message, you may unplug the USB stick and VGA/Video.
#:[[File:Node join message.png|580px|screenshot]]

Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!

'''Note that if you do NOT see a "Join request successful" message, your node may still have successfully onboarded. Continue to the next step to attempt to verify node onboarding.'''

==11. Verify node onboarding==

#Obtain your Node ID
#*Your Node ID should have been outputted in the previous step. If it wasn't, '''please wait at least 10 minutes to see if the node ID is logged to the console.'''
#Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard]
#*The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node.
#*If the status of your node is either “Awaiting Subnet” or “Active in Subnet,” '''congratulations! Your machine successfully joined the Internet Computer!'''
#*If the status of your node is NOT either “Awaiting Subnet” or “Active in Subnet”, or if it is NOT listed under your Node Provider principal, you should consult the [[Troubleshooting Node Deployment Errors]] page.
#*:[[File:Node onboarding verification.png|680px|screenshot]]
#If deploying with IPv4, verify that IPv4 was successfully configured
#*Ten minutes after the initial <code>Join request successful!</code> message, you should see another log indicating a successful IPv4 deployment:
#*:[[File:IPv4 log.jpg|680px|screenshot]]
#*If your log says <code>IPv4: none configured</code>, then your IPv4 deployment failed.

If you are failing to verify your node onboarding, consult the [[Troubleshooting Node Deployment Errors]] page.

Node Deployment Guide (with an HSM)

2024-11-26T13:08:22Z

Sat: /* B. Edit Config.ini */

This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS) using the legacy NitroKey HSM instructions. To use the non-HSM onboarding instructions, follow the [[IC-OS Installation Runbook]].

The physical machine is expected to be racked and stacked according to its respective manual.

To complete these steps, you are expected to be physically present in the data center your machine(s) reside(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel.

If you encounter issues during any of these steps, consult the [[Troubleshooting Node Deployment Errors]] page.

⚠️ DFINITY does '''not''' offer live support for Node Providers attempting to deploy nodes.

==1. Choose onboarding path (HSM vs no HSM)==
If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], '''continue to the next step.'''

If you chose to onboard '''without''' a Nitrokey HSM, follow the [[IC-OS Installation Runbook]] to onboard your nodes.

==2. Obtain requirements==
*A USB (3.0 speed that can hold at least 4GB) to put the image file on.
** Faster USBs will allow the process to go much faster.
*The NitroKey HSM for your data center.
*[Optional] A USB hub
** This is helpful at some data centers for simultaneously connecting keyboard, mouse, Nitrokey, etc.
*It is recommended that each server has a label with the BMC's MAC address for ease of identification in future dashboard upgrades.

==3. Download installation image==
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases].
*'''Note that you should always use a release from the last 6 weeks (newer is better) in order to ensure that your node can correctly correct to the network.'''

==4. Verify checksum and unarchive file==
===Mac OS X===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Windows===
#Open PowerShell and type:
#:<syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.zst</syntaxhighlight>

==5. Create Bootable USB Stick==
===Mac OS X===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo umount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/home/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>

===Windows===
#Download and install [https://rufus.ie/en/ Rufus Portable]
#Start Rufus
#Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
#:[[File:05.png|480px|screenshot]]
#You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
#:[[File:06.png|480px|screenshot]]
#:[[File:07.png|480px|screenshot]]
#The "Ready" bar will go from left to right as it completes.

==6. Add configuration ==

===A. Open Config.ini in a text editor===

===='''Mac OS X'''====

#Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:mac_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in TextEdit.

===='''Linux'''====

#Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:linux_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in KWrite.

===='''Windows'''====

#Open the Disk Management utility with a right click on the Start menu.
#:[[File:09-b.png|300px|screenshot]]#:
#Right click the CONFIG partition.
#Select Change drive letter or paths...
#:[[File:10-b.png|780px|screenshot]]
#Select any letter from the drop-down list.
#:[[File:11-b.png|480px|screenshot]]
# Click OK.
# You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file.
#:[[File:12-b.png|780px|screenshot]]
#Click on Edit to open it.

===B. Edit Config.ini===

Edit the config.ini file to add your network configuration.

Note that '''all Node Providers are requested to deploy two nodes with IPv4 and a domain name for every data center they operate in'''. Node Providers should deploy IPv4 to the '''first two nodes in their first rack'''.
# Insert your node reward type.
#:[[File:Pasted Graphic 7.png|780px|screenshot]]
#:You can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:
#:<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight> to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.
#:
#:Alternatively, you can get similar information with `ic-admin`. For instance: <syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>
#:
#Insert your IPv6 prefix and gateway.
#:[[File:Pasted Graphic 8.png|780px|screenshot]]
#:* The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
#:*For example, a valid prefix could look like this: <code>2a00:fb01:400:200</code>
#:*'''Important:'''
#:**The prefix should not have a trailing ':'
#:**IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. The '::' shorthand should '''not''' be used. Even if some groups are all zeros, they must be explicitly written out.
#[Optional] Insert your IPv4 info and domain name.
#:[[File:Pasted Graphic 9.png|780px|screenshot]]
#:*Configuring your node with IPv4 settings is optional, but if you do configure your node with IPv4 settings, you must also define the domain name for your node.
#:*'''Important:'''
#:**Please note that you '''must use a unique IPv4 address for each node you deploy'''. This means that you cannot use a single IC-OS installation image to deploy multiple nodes (like you are able to do when just configuring IPv6 nodes). '''After each IPv4 node deployment, you must plug your IC-OS Installation USB stick back into your laptop and return to [[Node Deployment Guide#6. Add configuration|step 6]] in the node deployment guide to reconfigure your installation image.'''
#:**You can add, remove, or update your node’s IPv4 address and domain name after completing node deployment using dfx commands. See [[Updating your node's IPv4 and domain name|here]] for details.
#Save the changes.
#:*If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
#:*:[[File:mac_03.png|580px|screenshot]]

== 7. Connect Crash Cart==
# In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
#Plug-in the VGA/Video, keyboard and IC-OS USB stick
#:[[File:08.png|580px|screenshot]]

==8. UEFI Setup and Boot Menu ==
Use the related page below to set up the BIOS/UEFI according to your hardware vendor.

*[[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]]
**[[IC-OS Installation - UEFI Configuration - Gen2 ASUS]]
*[[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]]
***
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.

Resume from this point when you are finished configuring the BIOS.

==9. IC-OS Installation==
#Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
#:[[File:35-sm.png|580px|screenshot]]
#The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#:[[File:36-sm.png|580px|screenshot]]
#Once you get asked to insert the HSM, please remove the keyboard and instead insert the HSM USB device.
#:[[File:37-sm.png|580px|screenshot]]
# If the installation finished successfully, it will initiate a reboot. 🚨 '''Please do not unplug the USB stick or HSM USB''' device at this point. 🚨
#:[[File:38-sm.png|580px|screenshot]]

==10. First Boot==
Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
# The first boot of the IC-OS '''still requires the HSM USB device to be plugged in'''. Please wait to take out the device until further instructions. This step can take several minutes.
#Once you see this message, you may unplug the HSM USB device, USB stick and VGA/Video.
#:[[File:Node join message.png|580px|screenshot]]

Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!

'''Note that if you do NOT see a "Join request successful" message, your node may still have successfully onboarded. Continue to the next step to attempt to verify node onboarding.'''

== 11. Verify node onboarding==

#Obtain your Node ID
#*Your Node ID should have been outputted in the previous step. If it wasn't, '''please wait at least 10 minutes to see if the node ID is logged to the console.'''
#Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard]
#*The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node.
#*If the status of your node is either “Awaiting Subnet” or “Active in Subnet,” '''congratulations! Your machine successfully joined the Internet Computer!'''
#*If the status of your node is NOT either “Awaiting Subnet” or “Active in Subnet”, or if it is NOT listed under your Node Provider principal, you should consult the [[Troubleshooting Node Deployment Errors]] page.
#*:[[File:Node onboarding verification.png|680px|screenshot]]
#If deploying with IPv4, verify that IPv4 was successfully configured
#*Ten minutes after the initial <code>Join request successful!</code> message, you should see another log indicating a successful IPv4 deployment:
#*:[[File:IPv4 log.jpg|680px|screenshot]]
#*If your log says <code>IPv4: none configured</code>, then your IPv4 deployment failed.

If you are failing to verify your node onboarding, consult the [[Troubleshooting Node Deployment Errors]] page.

Node Deployment Guide

2024-11-26T12:59:21Z

Sat: /* B. Edit Config.ini */

This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS).

The physical machine is expected to be racked and stacked according to its respective manual.

To complete these steps, you are expected to be physically present in the data center your machine(s) reside(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel.

If you encounter issues during any of these steps, consult the [[Troubleshooting Node Deployment Errors]] page.

⚠️ DFINITY does '''not''' offer live support for Node Providers attempting to deploy nodes.

==1. Choose onboarding path (HSM vs. no HSM)==
If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], follow the [[NitroKey HSM installation runbook]] to onboard your nodes.

If you chose to onboard '''without''' a Nitrokey HSM, '''continue to the next step.'''

==2. Obtain requirements ==
*A USB (3.0 speed that can hold at least 4GB) to put the image file on.
**Faster USBs will allow the process to go much faster.
*The <code>node_operator_private_key.pem</code> for your data center (Acquired from [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]])
* It is recommended that each server have a label with the BMC's MAC address for ease of identification in future dashboard upgrades.

== 3. Download installation image==
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases].

* '''Note that you should always use a release from the last 6 weeks (newer is better) in order to ensure that your node can correctly correct to the network.'''

== 4. Verify checksum and unarchive file==
===Mac OS X ===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Windows===
#Open PowerShell and type:
#:<syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.zst</syntaxhighlight>

==5. Create Bootable USB Stick ==
===Mac OS X===
# Open the Terminal and type:
#:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight>

=== Linux / Ubuntu===
#Open the Terminal and type
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight>
# All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo umount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/home/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>

===Windows===
#Download and install [https://rufus.ie/en/ Rufus Portable]
#Start Rufus
#Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
#:[[File:05.png|480px|screenshot]]
#You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
#:[[File:06.png|480px|screenshot]]
#:[[File:07.png|480px|screenshot]]
# The "Ready" bar will go from left to right as it completes.

==6. Add configuration==

===A. Open Config.ini in a text editor===

===='''Mac OS X'''====

#Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:mac_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in TextEdit.

===='''Linux'''====

#Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:linux_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in KWrite.

===='''Windows'''====

#Open the Disk Management utility with a right click on the Start menu
#:[[File:09-b.png|300px|screenshot]]#:
#Right click the CONFIG partition
# Select Change drive letter or paths...
#:[[File:10-b.png|780px|screenshot]]
# Select any letter from the drop-down list
#:[[File:11-b.png|480px|screenshot]]
#Click OK.
#You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file
#:[[File:12-b.png|780px|screenshot]]
#Click on Edit to open it.

===B. Edit Config.ini===

Edit the config.ini file to add your network configuration.

Note that '''all Node Providers are requested to deploy two nodes with IPv4 and a domain name for every data center they operate in'''. Node Providers should deploy IPv4 to the '''first two nodes in their first rack'''.
# Insert your node reward type.
#:[[File:Pasted Graphic 7.png|780px|screenshot]]
You can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance:
<syntaxhighlight lang="bash">
dre registry --filter=dc_id=<dc_id>
</syntaxhighlight>
to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`.

Alternatively, you can get similar information with `ic-admin`. For instance:
<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
</syntaxhighlight>

# Insert your IPv6 prefix and gateway.
#:[[File:Pasted Graphic 8.png|780px|screenshot]]
#:* The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
#:*For example, a valid prefix could look like this: <code>2a00:fb01:400:200</code>
#:*'''Important:'''
#:**The prefix should not have a trailing ':'
#:**IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. The '::' shorthand should '''not''' be used. Even if some groups are all zeros, they must be explicitly written out.
#[Optional] Insert your IPv4 info and domain name.
#:[[File:Pasted Graphic 9.png|780px|screenshot]]
#:* Configuring your node with IPv4 settings is optional, but if you do configure your node with IPv4 settings, you must also define the domain name for your node.
#:*'''Important:'''
#:**Please note that you '''must use a unique IPv4 address for each node you deploy'''. This means that you cannot use a single IC-OS installation image to deploy multiple nodes (like you are able to do when just configuring IPv6 nodes). '''After each IPv4 node deployment, you must plug your IC-OS Installation USB stick back into your laptop and return to [[Node Deployment Guide#6. Add configuration|step 6]] in the node deployment guide to reconfigure your installation image.'''
#:**You can add, remove, or update your node’s IPv4 address and domain name after completing node deployment using dfx commands. See [[Updating your node's IPv4 and domain name|here]] for details.
#Save the changes.
#:*If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
#:*:[[File:mac_03.png|580px|screenshot]]

===C. Copy Node Operator private key to config partition===

#Copy <code>node_operator_private_key.pem</code> (created in [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]]) to the <code>CONFIG</code> partition. This file should have the name <code>node_operator_private_key.pem</code>, and sit next to <code>config.ini</code>, NOT inside the <code>ssh_authorized_keys</code> folder.

==7. Connect Crash Cart==
#In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
# Plug-in the VGA/Video, keyboard and IC-OS USB stick
#:[[File:08.png|580px|screenshot]]

==8. UEFI Setup and Boot Menu==

Make sure that server date/time is set to UTC (Universal Time Coordinated)

Use the related page below to set up the BIOS/UEFI according to your hardware vendor.

*[[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]]
**[[IC-OS Installation - UEFI Configuration - Gen2 ASUS]]
*[[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]]
***
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.

Resume from this point when you are finished configuring the BIOS.

== 9. IC-OS Installation==
#Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
#:[[File:35-sm.png|580px|screenshot]]
#The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#:[[File:36-sm.png|580px|screenshot]]
#If the installation finished successfully, it will initiate a reboot.
#:[[File:38-sm.png|580px|screenshot]] 
==10. First Boot==
Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#Once you see this message, you may unplug the USB stick and VGA/Video.
#:[[File:Node join message.png|580px|screenshot]]

Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!

'''Note that if you do NOT see a "Join request successful" message, your node may still have successfully onboarded. Continue to the next step to attempt to verify node onboarding.'''

==11. Verify node onboarding==

#Obtain your Node ID
#*Your Node ID should have been outputted in the previous step. If it wasn't, '''please wait at least 10 minutes to see if the node ID is logged to the console.'''
#Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard]
#*The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node.
#*If the status of your node is either “Awaiting Subnet” or “Active in Subnet,” '''congratulations! Your machine successfully joined the Internet Computer!'''
#*If the status of your node is NOT either “Awaiting Subnet” or “Active in Subnet”, or if it is NOT listed under your Node Provider principal, you should consult the [[Troubleshooting Node Deployment Errors]] page.
#*:[[File:Node onboarding verification.png|680px|screenshot]]
#If deploying with IPv4, verify that IPv4 was successfully configured
#*Ten minutes after the initial <code>Join request successful!</code> message, you should see another log indicating a successful IPv4 deployment:
#*:[[File:IPv4 log.jpg|680px|screenshot]]
#*If your log says <code>IPv4: none configured</code>, then your IPv4 deployment failed.

If you are failing to verify your node onboarding, consult the [[Troubleshooting Node Deployment Errors]] page.

Node Deployment Guide

2024-11-26T12:57:07Z

Sat: /* B. Edit Config.ini */

This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS).

The physical machine is expected to be racked and stacked according to its respective manual.

To complete these steps, you are expected to be physically present in the data center your machine(s) reside(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel.

If you encounter issues during any of these steps, consult the [[Troubleshooting Node Deployment Errors]] page.

⚠️ DFINITY does '''not''' offer live support for Node Providers attempting to deploy nodes.

==1. Choose onboarding path (HSM vs. no HSM)==
If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], follow the [[NitroKey HSM installation runbook]] to onboard your nodes.

If you chose to onboard '''without''' a Nitrokey HSM, '''continue to the next step.'''

==2. Obtain requirements ==
*A USB (3.0 speed that can hold at least 4GB) to put the image file on.
**Faster USBs will allow the process to go much faster.
*The <code>node_operator_private_key.pem</code> for your data center (Acquired from [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]])
* It is recommended that each server have a label with the BMC's MAC address for ease of identification in future dashboard upgrades.

== 3. Download installation image==
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases].

* '''Note that you should always use a release from the last 6 weeks (newer is better) in order to ensure that your node can correctly correct to the network.'''

== 4. Verify checksum and unarchive file==
===Mac OS X ===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.zst</syntaxhighlight>

===Windows===
#Open PowerShell and type:
#:<syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.zst</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.zst</syntaxhighlight>

==5. Create Bootable USB Stick ==
===Mac OS X===
# Open the Terminal and type:
#:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight>

=== Linux / Ubuntu===
#Open the Terminal and type
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight>
# All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo umount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. Additionally, replace the path to your downloaded IC-OS ''disk.img'' file. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=/home/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M status=progress</syntaxhighlight>

===Windows===
#Download and install [https://rufus.ie/en/ Rufus Portable]
#Start Rufus
#Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
#:[[File:05.png|480px|screenshot]]
#You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
#:[[File:06.png|480px|screenshot]]
#:[[File:07.png|480px|screenshot]]
# The "Ready" bar will go from left to right as it completes.

==6. Add configuration==

===A. Open Config.ini in a text editor===

===='''Mac OS X'''====

#Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:mac_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in TextEdit.

===='''Linux'''====

#Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:linux_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in KWrite.

===='''Windows'''====

#Open the Disk Management utility with a right click on the Start menu
#:[[File:09-b.png|300px|screenshot]]#:
#Right click the CONFIG partition
# Select Change drive letter or paths...
#:[[File:10-b.png|780px|screenshot]]
# Select any letter from the drop-down list
#:[[File:11-b.png|480px|screenshot]]
#Click OK.
#You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file
#:[[File:12-b.png|780px|screenshot]]
#Click on Edit to open it.

===B. Edit Config.ini===

Edit the config.ini file to add your network configuration.

Note that '''all Node Providers are requested to deploy two nodes with IPv4 and a domain name for every data center they operate in'''. Node Providers should deploy IPv4 to the '''first two nodes in their first rack'''.
# Insert your node reward type.
#:[[File:Pasted Graphic 7.png|780px|screenshot]] You can obtain the node_reward_type that is already set in the registry for the particular DC by using the [https://dfinity.github.io/dre/getting-started.html dre tool]. For instance: `dre registry --filter=dc_id=<dc_id>` to get the node operator record associated with the DC. Please replace `<dc_id>` with your DC, e.g. `bu1`. Alternatively, you can get similar information with `ic-admin`. For instance:<syntaxhighlight lang="bash">
❯ ic-admin --nns-url https://ic0.app get-node-operator c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Using NNS URLs: ["https://ic0.app/"]
Fetching the most recent value for key: node_operator_record_c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae
Most recent version is 44799. Value:
NodeOperator { node_operator_principal_id: c5ssg-eh22p-pmsn6-fpjzj-k5nql-mx5mc-7gb4a-4klco-c4f37-ydnfp-bae, node_allowance: 3, node_provider_principal_id: i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae, dc_id: "bu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }

</syntaxhighlight>
# Insert your IPv6 prefix and gateway.
#:[[File:Pasted Graphic 8.png|780px|screenshot]]
#:* The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
#:*For example, a valid prefix could look like this: <code>2a00:fb01:400:200</code>
#:*'''Important:'''
#:**The prefix should not have a trailing ':'
#:**IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. The '::' shorthand should '''not''' be used. Even if some groups are all zeros, they must be explicitly written out.
#[Optional] Insert your IPv4 info and domain name.
#:[[File:Pasted Graphic 9.png|780px|screenshot]]
#:* Configuring your node with IPv4 settings is optional, but if you do configure your node with IPv4 settings, you must also define the domain name for your node.
#:*'''Important:'''
#:**Please note that you '''must use a unique IPv4 address for each node you deploy'''. This means that you cannot use a single IC-OS installation image to deploy multiple nodes (like you are able to do when just configuring IPv6 nodes). '''After each IPv4 node deployment, you must plug your IC-OS Installation USB stick back into your laptop and return to [[Node Deployment Guide#6. Add configuration|step 6]] in the node deployment guide to reconfigure your installation image.'''
#:**You can add, remove, or update your node’s IPv4 address and domain name after completing node deployment using dfx commands. See [[Updating your node's IPv4 and domain name|here]] for details.
#Save the changes.
#:*If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
#:*:[[File:mac_03.png|580px|screenshot]]

===C. Copy Node Operator private key to config partition===

#Copy <code>node_operator_private_key.pem</code> (created in [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]]) to the <code>CONFIG</code> partition. This file should have the name <code>node_operator_private_key.pem</code>, and sit next to <code>config.ini</code>, NOT inside the <code>ssh_authorized_keys</code> folder.

==7. Connect Crash Cart==
#In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
# Plug-in the VGA/Video, keyboard and IC-OS USB stick
#:[[File:08.png|580px|screenshot]]

==8. UEFI Setup and Boot Menu==

Make sure that server date/time is set to UTC (Universal Time Coordinated)

Use the related page below to set up the BIOS/UEFI according to your hardware vendor.

*[[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]]
**[[IC-OS Installation - UEFI Configuration - Gen2 ASUS]]
*[[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]]
***
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.

Resume from this point when you are finished configuring the BIOS.

== 9. IC-OS Installation==
#Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
#:[[File:35-sm.png|580px|screenshot]]
#The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#:[[File:36-sm.png|580px|screenshot]]
#If the installation finished successfully, it will initiate a reboot.
#:[[File:38-sm.png|580px|screenshot]] 
==10. First Boot==
Please remember to check the [[Troubleshooting Node Deployment Errors]] page if you encounter any errors.
#Once you see this message, you may unplug the USB stick and VGA/Video.
#:[[File:Node join message.png|580px|screenshot]]

Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!

'''Note that if you do NOT see a "Join request successful" message, your node may still have successfully onboarded. Continue to the next step to attempt to verify node onboarding.'''

==11. Verify node onboarding==

#Obtain your Node ID
#*Your Node ID should have been outputted in the previous step. If it wasn't, '''please wait at least 10 minutes to see if the node ID is logged to the console.'''
#Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard]
#*The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node.
#*If the status of your node is either “Awaiting Subnet” or “Active in Subnet,” '''congratulations! Your machine successfully joined the Internet Computer!'''
#*If the status of your node is NOT either “Awaiting Subnet” or “Active in Subnet”, or if it is NOT listed under your Node Provider principal, you should consult the [[Troubleshooting Node Deployment Errors]] page.
#*:[[File:Node onboarding verification.png|680px|screenshot]]
#If deploying with IPv4, verify that IPv4 was successfully configured
#*Ten minutes after the initial <code>Join request successful!</code> message, you should see another log indicating a successful IPv4 deployment:
#*:[[File:IPv4 log.jpg|680px|screenshot]]
#*If your log says <code>IPv4: none configured</code>, then your IPv4 deployment failed.

If you are failing to verify your node onboarding, consult the [[Troubleshooting Node Deployment Errors]] page.

Node Provider Matrix channel

2024-10-01T12:53:49Z

Sat: Add Matrix space

There are Matrix rooms (channels) that are 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.

'''NOTE:''' these rooms should only be consulted for troubleshooting issues '''after consulting all relevant [[Node Provider Troubleshooting]] documentation.'''

There is a [https://matrix.to/#/!YEFYjPAwRoiyVaKfAp:matrix.org?via=matrix.org&via=greensteps.cn&via=rudd-o.com Matrix Space Internet Computer], that includes all relevant rooms and people -- please join that first!

After that, please join the following rooms (can all be found within the [https://matrix.to/#/!YEFYjPAwRoiyVaKfAp:matrix.org?via=matrix.org&via=greensteps.cn&via=rudd-o.com Matrix Space Internet Computer]):

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org (lots of activity)
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org (infrequent messages)
* Incident response: https://app.element.io/#/room/#ic-node-providers-incident-response:matrix.org (communication reserved only for incident response. Please join if you are a node provider, and enable all notifications!)

These rooms run 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.

'''NOTE: 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]. If possible, [https://element.io/help#settings3 enable notifications for missed messages], especially for rooms with lower activity.

If you are a Node Provider, please also add your contact details below, to facilitate communication.
{| class="wikitable"
|+
!Node Provider Name
!Node Provider Id
!DC list
!Can be reached on Matrix via
|-
|1G
|7k7b7-4pzhf-aivy6-y654t-uqyup-2auiz-ew2cm-4qkl4-nsl4v-bul5k-5qe
|fm1
|https://matrix.to/#/#ic-node-provider-7k7b7:matrix.org
|-
|43rd Big Idea Films
|sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe
|hu1
|John Harris, Charles Witte
https://matrix.to/#/#ic-node-provider-sqhxa:matrix.org
|-
|87m Neuron, LLC
|eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe
|pl1, dl1, lv1
|https://matrix.to/#/#ic-node-provider-eipr5:matrix.org
|-
|9Yards Capital
|spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe
|jv1, ch2, ny1
|https://matrix.to/#/#ic-node-provider-spp3m:matrix.org
|-
|ACCUSET SOLUTIONS
|cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe
|gn1
|sagcryptoicp
https://matrix.to/#/#ic-node-provider-cp5ib:matrix.org
|-
|Adam Dymecki
|n32q7-33lmk-m33tr-o5ltb-po6cb-tqqrr-2x6wp-pzhw7-ymizu-o3fyp-sqe
|
|https://matrix.to/#/#ic-node-provider-n32q7:matrix.org
|-
|A Dog's Boutique, LLC
|uvawj-nnt3i-4ch3a-hruy4-hyfjn-7owvl-wgkli-uq2hd-e6lkq-v4b2o-4ae
|
|https://matrix.to/#/#ic-node-provider-uvawj:matrix.org
|-
|AITUBI AG
|
|
|
|-
|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>
https://matrix.to/#/#ic-node-provider-rbn2y:matrix.org
|-
|Anonstake
|kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae
|
|https://matrix.to/#/#ic-node-provider-kos24:matrix.org
|-
|ANYPOINT PTY LTD
|fwnmn-zn7yt-5jaia-fkxlr-dzwyu-keguq-npfxq-mc72w-exeae-n5thj-oae
|
|https://matrix.to/#/#ic-node-provider-fwnmn:matrix.org
|-
|Archery Blockchain SCSp
|7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe
|
|https://matrix.to/#/#ic-node-provider-7ryes:matrix.org
|-
|Arjay LLC
|l2kri-jarwr-7whc4-pjdpn-n6hlb-45ltr-l6ghm-twttl-pcsvt-rynko-dqe
|
|https://matrix.to/#/#ic-node-provider-l2kri:matrix.org
|-
|Artem Horodyskyi
|diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe
|bt1, li1, ma1, pa2, rg3, ta2, wy1
|ar-111
https://matrix.to/#/#ic-node-provider-diyay:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-7a4u2:matrix.org
|-
|Bitmoon
|mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe
|
|https://matrix.to/#/#ic-node-provider-mjnyf:matrix.org
|-
|Blockchain Development Labs
|7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae
|to1, to2, bc1
|@injectedfusion:matrix.org
https://matrix.to/#/#ic-node-provider-7at4h:matrix.org
|-
|BlockTech Ventures, LLC
|ks7ow-zvs7i-ratdk-azq34-zio2b-gbekj-qjicg-pfhp3-ovhgu-k5qql-dae
|
|https://matrix.to/#/#ic-node-provider-ks7ow:matrix.org
|-
|BLP22, LLC
|sma3p-ivkif-hz7nu-ngmvq-ibnjg-nubke-zf6gh-wbnfc-2dlng-l3die-zqe
|
|https://matrix.to/#/#ic-node-provider-sma3p:matrix.org
|-
|Bohatyrov Volodymyr
|dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae
|bn1,ba1,ma1,rg3,si1,ta1,wa2
|volobo
https://matrix.to/#/#ic-node-provider-dhywe:matrix.org
|-
|Boolean Bit, LLC
|qdj4d-76lh3-w2q5i-kwjcd-643pq-pk42d-cziag-4hkau-35gib-m7s33-6qe
|
|https://matrix.to/#/#ic-node-provider-qdj4d:matrix.org
|-
|Brener, Inc.
|2wxxr-qwylo-n7dhz-6co6m-iektd-vl7dn-ocvyc-xazaf-hbfxq-66spe-aae
|
|https://matrix.to/#/#ic-node-provider-2wxxr:matrix.org
|-
|Conic Ventures
|i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe
|ns1, ld1
|Sebastian Mengwall
https://matrix.to/#/#ic-node-provider-i3cfo:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-7nxxb:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-bvcsg:matrix.org
|-
| 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
https://matrix.to/#/#ic-node-provider-bvcsg:matrix.org
|-
| 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
https://matrix.to/#/#ic-node-provider-bvcsg:matrix.org
|-
|DRMxTech Enterprises, LLC
|olgti-2hegv-ya7pd-ky2wt-of57j-tzs6q-ydrpy-hdxyy-cjnwx-ox5t4-3qe
|
|https://matrix.to/#/#ic-node-provider-olgti:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-olgti:matrix.org
|-
|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
|mb1, lj1
|@gorazd_o:matrix.org
https://matrix.to/#/#ic-node-provider-wdjjk:matrix.org
|-
|Fritz Huie
|67gkg-gkgzz-g2ubz-3cc6h-jr3zm-twsii-7i325-r3gzr-kp2kh-dwxg6-pqe
|
|https://matrix.to/#/#ic-node-provider-67gkg:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-eybf4:matrix.org
|-
|GeoNodes LLC
|5wedd-dwi2c-ybr2g-benav-qlgc7-vifbt-qz3ml-ymopp-uaide-ilpkb-tae
|
|@geo-nodes
https://matrix.to/#/#ic-node-provider-6sq7t:matrix.org
|-
|George Bassadone
|lksfo-j2smg-76m4c-jwasz-e5exl-gptsk-jvtc7-zvm34-ezk4g-p2xjt-dqe
|
|https://matrix.to/#/#ic-node-provider-vegae:matrix.org
|-
|Giant Leaf, LLC
|wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae
|
|https://matrix.to/#/#ic-node-provider-wwdbq:matrix.org
|-
|Goat, LLC
|p6fou-ngmgk-rxc6t-7ckzz-hojr2-kk6r3-xnlrk-ewzvu-g6xms-rfafz-zae
|
|https://matrix.to/#/#ic-node-provider-p6fou:matrix.org
|-
|Goodsir, LLC
|myrs2-bc6j6-mydpr-2jmli-l45mu-35ybt-c34mo-kjpve-zmaao-ajusy-nqe
|
|https://matrix.to/#/#ic-node-provider-myrs2:matrix.org
|-
|Honeycomb Capital (Pty) Ltd
|nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae
|
|honeycombcapital
https://matrix.to/#/#ic-node-provider-nmdd6:matrix.org
|-
|Iancu Aurel
|i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae
|
|https://matrix.to/#/#ic-node-provider-i7dto:matrix.org
|-
|Icaria Systems Pty Ltd
|ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe
|mn2
|Icarus
https://matrix.to/#/#ic-node-provider-ihbuj:matrix.org
|-
|Illusions In Art (Pty) Ltd
|optdi-nwa4m-hly3k-6ua4n-sqyxf-yahvb-wps77-ddayn-r7zcz-edla5-7qe
|
|https://matrix.to/#/#ic-node-provider-optdi:matrix.org
|-
|InfoObjects
|7ws2n-wqorv-vmo4m-5e222-n42c3-hk43s-ei3kp-4hpbn-xlkzo-jgv7i-tqe
|
|https://matrix.to/#/#ic-node-provider-7ws2n:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-ivf2y:matrix.org
|-
|Jeffrey Schnettler
|5zqo2-omblo-i7knq-qyrfu-mjccn-tljyd-qslab-b7ukn-7tshi-pbeke-pae
|
|https://matrix.to/#/#ic-node-provider-5zqo2:matrix.org
|-
|Jimmy Quach
|dzxyh-fo4sw-pxckk-kwqvc-xjten-3yqon-fm62b-2hz4s-raa4g-jzczg-iqe
|
|https://matrix.to/#/#ic-node-provider-dzxyh:matrix.org
|-
|Jonathan Ziskind
|qcs4o-yswwp-7ozhg-m2ago-ytjyl-zlckb-raykw-fi5hl-cflyt-4beyv-zqe
|
|https://matrix.to/#/#ic-node-provider-qcs4o:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-unqqg:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-py2kr:matrix.org
|-
|Krishna Enterprises
|zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae
|pl2
|@krishnaenterprises:matrix.org
https://matrix.to/#/#ic-node-provider-zy4m7: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
|
|https://matrix.to/#/#ic-node-provider-abscc:matrix.org
|-
|Lukas Helebrandt
|efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe
|bn1
|@lukas:greensteps.cn
https://matrix.to/#/#ic-node-provider-efem5:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-4r6qy:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-s5nvr:matrix.org
|-
|Marvelous Web3
|7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe
|
|https://matrix.to/#/#ic-node-provider-7uioy:matrix.org
|-
|Mary Ren
|vdzyg-amckj-thvl5-bsn52-2elzd-drgii-ryh4c-izba3-xaehb-sohtd-aae
|
|https://matrix.to/#/#ic-node-provider-vdzyg:matrix.org
|-
|MB Patrankos šūvis
|4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae
|bt1
|@methistos:matrix.org
https://matrix.to/#/#ic-node-provider-4jjya:matrix.org
|-
|Mika Properties, LLC
|3siog-htc6j-ed3wz-sguhu-2objz-g5qct-npoma-t3wwt-bd6wy-chwsi-4ae
|
|https://matrix.to/#/#ic-node-provider-3siog:matrix.org
|-
|MI Servers
|izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe
|
|https://matrix.to/#/#ic-node-provider-izmhk:matrix.org
|-
|Mitchel Guerra
|4anlt-yam7x-eodmx-ik7mo-nl3kx-t35fj-52hfy-uv4jj-u2iea-ntg76-pqe
|
|https://matrix.to/#/#ic-node-provider-4anlt:matrix.org
|-
|Moon Block Ventures
|sdal5-w2c3d-p3buy-zieck-2wyuj-eu5bn-rkfe6-uuspi-o4n2b-gpei7-iae
|
|https://matrix.to/#/#ic-node-provider-sdal5:matrix.org
|-
|Mostly Wholesome, Inc.
|ou3o7-akyjc-ldwd5-anyjn-l2buz-cwhbg-nehlc-abkde-qtc7w-fozdi-hae
|
|https://matrix.to/#/#ic-node-provider-ou3o7:matrix.org
|-
|Neptune Partners
|4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae
|
|https://matrix.to/#/#ic-node-provider-4dibr:matrix.org
|-
|NoviSystems, LLC
|hk7eo-22zam-kqmsx-dtfbj-k5i6f-jg65h-micpf-2cztc-t2eqk-efgvx-vqe
|ny2, fm1
|novisystems
https://matrix.to/#/#ic-node-provider-hk7eo:matrix.org
|-
|OneSixtyTwo Digital Capital
|6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe
|
|https://matrix.to/#/#ic-node-provider-6nbcy:matrix.org
|-
|Origin Game
|cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe
|
|https://matrix.to/#/#ic-node-provider-cgmhq:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-72idx:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-r3yjn:matrix.org
|-
|Power Meta Corporation
|4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae
|
|https://matrix.to/#/#ic-node-provider-4fedi:matrix.org
|-
|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)
https://matrix.to/#/#ic-node-provider-trxbq:matrix.org
|-
|Rachel Dymecki
|chnsu-yaqt5-6osy5-au4zn-li6yu-nufmw-dewrt-utkiu-twd76-ujypw-rae
|
|https://matrix.to/#/#ic-node-provider-chnsu:matrix.org
|-
|Richard Ma
|egb3e-rzi2e-vpsmm-akysp-l2owk-4dgst-b5hmg-xrkwa-cr3uk-zlzds-mae
|
|https://matrix.to/#/#ic-node-provider-egb3e:matrix.org
|-
|Richard Suarez
|cmcjw-6c5ve-4zjnt-lipnl-2lp43-oh5wk-ewciz-xyvnv-m2rz5-hkm6a-hqe
|
|https://matrix.to/#/#ic-node-provider-cmcjw:matrix.org
|-
|Ricky Sidhu
|q22bo-3uyqa-jvtpt-gapjk-pseor-esx4a-zyb74-vzea4-o7nx2-tafgq-hae
|
|https://matrix.to/#/#ic-node-provider-q22bo:matrix.org
|-
|Rishi Sachdev
|6tg64-cdfoh-kl35i-p6qti-sose3-746lr-jk5ex-phuvu-jfu3d-5svwa-7qe
|
|https://matrix.to/#/#ic-node-provider-6tg64:matrix.org
|-
|Rivram Inc
|ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae
|nm1,mtl1
|@ritvick
https://matrix.to/#/#ic-node-provider-ulyfm:matrix.org
|-
|Rodney Zorrilla
|bgprp-b2mnt-ci5in-57vuk-p7qvo-tj2tb-5w5su-qwenk-gbe77-mnuiq-sqe
|
|https://matrix.to/#/#ic-node-provider-bgprp:matrix.org
|-
|Ronnie Pellizzari
|wwxec-c2gd2-bu5on-ktpwz-z2ph3-vlr4p-m7ztf-6ck7r-nt3r4-fxbdq-mae
|
|https://matrix.to/#/#ic-node-provider-wwxec:matrix.org
|-
|Russell Ford
|p5jx4-lsrog-ep5o3-5uudg-opdg3-ur45z-xeefi-4ejfz-47t2k-riwfv-dae
|
|https://matrix.to/#/#ic-node-provider-p5jx4:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-a24zv:matrix.org
|-
|Starbase
|sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae
|
|https://matrix.to/#/#ic-node-provider-sixix:matrix.org
|-
| 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
|
|https://matrix.to/#/#ic-node-provider-6r5lw:matrix.org
|-
|Tomahawk.vc
|ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae
|
|https://matrix.to/#/#ic-node-provider-ucjqj:matrix.org
|-
|Virtual Hive Ltd
|wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae
|fr2
|Chris B
https://matrix.to/#/#ic-node-provider-wdnqm:matrix.org
|-
|Vladyslav Popov
|3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae
|pa2,ma2,si1,rg1, wy1,li1,ta2
|vladyslav_p
https://matrix.to/#/#ic-node-provider-3oqw6:matrix.org
|-
|Wancloud limited
|g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe
|hk1
|<nowiki>hashbamboo | HashQuark, Daniel | HashQuark</nowiki>
https://matrix.to/#/#ic-node-provider-g2ax6:matrix.org
|-
|Web3game
|64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe
|hk4
|web3game
https://matrix.to/#/#ic-node-provider-64xe5:matrix.org
|-
|William Zelver
|usau7-upgoh-sg464-6qnso-lud42-nxho6-ith26-a2jhq-q5bgy-ajeou-4ae
|
|https://matrix.to/#/#ic-node-provider-usau7:matrix.org
|-
|Wolfhound LLC
|6mifr-stcqy-w5pzr-qpijh-jopft-p6jl3-n2sww-jhmzg-uzknn-hte4m-pae
|
|https://matrix.to/#/#ic-node-provider-6mifr:matrix.org
|-
|Wolkboer (Pty) Ltd
|mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae
|jb3
|wolkboer
https://matrix.to/#/#ic-node-provider-mme7u:matrix.org
|-
|Zondax AG
|hzqcb-iiagd-4erjo-qn7rq-syqro-zztl6-cpble-atnkd-2c6bg-bxjoa-qae
|
|https://matrix.to/#/#ic-node-provider-hzqcb:matrix.org
|-
|ZTLC PTE LTD
|xsrwt-tl3tk-n3aya-rafh3-ta6xu-eviw5-ae5dg-2f3bf-siaab-wdwdo-dqe
|
|
|}

Node Provider Matrix channel

2024-10-01T12:21:44Z

Sat: Added a link to the Matrix room per NP

There are Matrix rooms (channels) that are 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.

'''NOTE:''' these rooms should only be consulted for troubleshooting issues '''after consulting all relevant [[Node Provider Troubleshooting]] documentation.'''

Please join the following rooms:

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org (lots of activity)
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org (infrequent messages)
* Incident response: https://app.element.io/#/room/#ic-node-providers-incident-response:matrix.org (communication reserved only for incident response. Please join if you are a node provider, and enable all notifications!)

These rooms run 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.

'''NOTE: 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]. If possible, [https://element.io/help#settings3 enable notifications for missed messages], especially for rooms with lower activity.

If you are a Node Provider, please also add your contact details below, to facilitate communication.
{| class="wikitable"
|+
!Node Provider Name
!Node Provider Id
!DC list
!Can be reached on Matrix via
|-
|1G
|7k7b7-4pzhf-aivy6-y654t-uqyup-2auiz-ew2cm-4qkl4-nsl4v-bul5k-5qe
|fm1
|https://matrix.to/#/#ic-node-provider-7k7b7:matrix.org
|-
|43rd Big Idea Films
|sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe
|hu1
|John Harris, Charles Witte
https://matrix.to/#/#ic-node-provider-sqhxa:matrix.org
|-
|87m Neuron, LLC
|eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe
|pl1, dl1, lv1
|https://matrix.to/#/#ic-node-provider-eipr5:matrix.org
|-
|9Yards Capital
|spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe
|jv1, ch2, ny1
|https://matrix.to/#/#ic-node-provider-spp3m:matrix.org
|-
|ACCUSET SOLUTIONS
|cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe
|gn1
|sagcryptoicp
https://matrix.to/#/#ic-node-provider-cp5ib:matrix.org
|-
|Adam Dymecki
|n32q7-33lmk-m33tr-o5ltb-po6cb-tqqrr-2x6wp-pzhw7-ymizu-o3fyp-sqe
|
|https://matrix.to/#/#ic-node-provider-n32q7:matrix.org
|-
|A Dog's Boutique, LLC
|uvawj-nnt3i-4ch3a-hruy4-hyfjn-7owvl-wgkli-uq2hd-e6lkq-v4b2o-4ae
|
|https://matrix.to/#/#ic-node-provider-uvawj:matrix.org
|-
|AITUBI AG
|
|
|
|-
|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>
https://matrix.to/#/#ic-node-provider-rbn2y:matrix.org
|-
|Anonstake
|kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae
|
|https://matrix.to/#/#ic-node-provider-kos24:matrix.org
|-
|ANYPOINT PTY LTD
|fwnmn-zn7yt-5jaia-fkxlr-dzwyu-keguq-npfxq-mc72w-exeae-n5thj-oae
|
|https://matrix.to/#/#ic-node-provider-fwnmn:matrix.org
|-
|Archery Blockchain SCSp
|7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe
|
|https://matrix.to/#/#ic-node-provider-7ryes:matrix.org
|-
|Arjay LLC
|l2kri-jarwr-7whc4-pjdpn-n6hlb-45ltr-l6ghm-twttl-pcsvt-rynko-dqe
|
|https://matrix.to/#/#ic-node-provider-l2kri:matrix.org
|-
|Artem Horodyskyi
|diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe
|bt1, li1, ma1, pa2, rg3, ta2, wy1
|ar-111
https://matrix.to/#/#ic-node-provider-diyay:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-7a4u2:matrix.org
|-
|Bitmoon
|mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe
|
|https://matrix.to/#/#ic-node-provider-mjnyf:matrix.org
|-
|Blockchain Development Labs
|7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae
|to1, to2, bc1
|@injectedfusion:matrix.org
https://matrix.to/#/#ic-node-provider-7at4h:matrix.org
|-
|BlockTech Ventures, LLC
|ks7ow-zvs7i-ratdk-azq34-zio2b-gbekj-qjicg-pfhp3-ovhgu-k5qql-dae
|
|https://matrix.to/#/#ic-node-provider-ks7ow:matrix.org
|-
|BLP22, LLC
|sma3p-ivkif-hz7nu-ngmvq-ibnjg-nubke-zf6gh-wbnfc-2dlng-l3die-zqe
|
|https://matrix.to/#/#ic-node-provider-sma3p:matrix.org
|-
|Bohatyrov Volodymyr
|dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae
|bn1,ba1,ma1,rg3,si1,ta1,wa2
|volobo
https://matrix.to/#/#ic-node-provider-dhywe:matrix.org
|-
|Boolean Bit, LLC
|qdj4d-76lh3-w2q5i-kwjcd-643pq-pk42d-cziag-4hkau-35gib-m7s33-6qe
|
|https://matrix.to/#/#ic-node-provider-qdj4d:matrix.org
|-
|Brener, Inc.
|2wxxr-qwylo-n7dhz-6co6m-iektd-vl7dn-ocvyc-xazaf-hbfxq-66spe-aae
|
|https://matrix.to/#/#ic-node-provider-2wxxr:matrix.org
|-
|Conic Ventures
|i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe
|ns1, ld1
|Sebastian Mengwall
https://matrix.to/#/#ic-node-provider-i3cfo:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-7nxxb:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-bvcsg:matrix.org
|-
| 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
https://matrix.to/#/#ic-node-provider-bvcsg:matrix.org
|-
| 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
https://matrix.to/#/#ic-node-provider-bvcsg:matrix.org
|-
|DRMxTech Enterprises, LLC
|olgti-2hegv-ya7pd-ky2wt-of57j-tzs6q-ydrpy-hdxyy-cjnwx-ox5t4-3qe
|
|https://matrix.to/#/#ic-node-provider-olgti:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-olgti:matrix.org
|-
|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
|mb1, lj1
|@gorazd_o:matrix.org
https://matrix.to/#/#ic-node-provider-wdjjk:matrix.org
|-
|Fritz Huie
|67gkg-gkgzz-g2ubz-3cc6h-jr3zm-twsii-7i325-r3gzr-kp2kh-dwxg6-pqe
|
|https://matrix.to/#/#ic-node-provider-67gkg:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-eybf4:matrix.org
|-
|GeoNodes LLC
|5wedd-dwi2c-ybr2g-benav-qlgc7-vifbt-qz3ml-ymopp-uaide-ilpkb-tae
|
|@geo-nodes
https://matrix.to/#/#ic-node-provider-6sq7t:matrix.org
|-
|George Bassadone
|lksfo-j2smg-76m4c-jwasz-e5exl-gptsk-jvtc7-zvm34-ezk4g-p2xjt-dqe
|
|https://matrix.to/#/#ic-node-provider-vegae:matrix.org
|-
|Giant Leaf, LLC
|wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae
|
|https://matrix.to/#/#ic-node-provider-wwdbq:matrix.org
|-
|Goat, LLC
|p6fou-ngmgk-rxc6t-7ckzz-hojr2-kk6r3-xnlrk-ewzvu-g6xms-rfafz-zae
|
|https://matrix.to/#/#ic-node-provider-p6fou:matrix.org
|-
|Goodsir, LLC
|myrs2-bc6j6-mydpr-2jmli-l45mu-35ybt-c34mo-kjpve-zmaao-ajusy-nqe
|
|https://matrix.to/#/#ic-node-provider-myrs2:matrix.org
|-
|Honeycomb Capital (Pty) Ltd
|nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae
|
|honeycombcapital
https://matrix.to/#/#ic-node-provider-nmdd6:matrix.org
|-
|Iancu Aurel
|i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae
|
|https://matrix.to/#/#ic-node-provider-i7dto:matrix.org
|-
|Icaria Systems Pty Ltd
|ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe
|mn2
|Icarus
https://matrix.to/#/#ic-node-provider-ihbuj:matrix.org
|-
|Illusions In Art (Pty) Ltd
|optdi-nwa4m-hly3k-6ua4n-sqyxf-yahvb-wps77-ddayn-r7zcz-edla5-7qe
|
|https://matrix.to/#/#ic-node-provider-optdi:matrix.org
|-
|InfoObjects
|7ws2n-wqorv-vmo4m-5e222-n42c3-hk43s-ei3kp-4hpbn-xlkzo-jgv7i-tqe
|
|https://matrix.to/#/#ic-node-provider-7ws2n:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-ivf2y:matrix.org
|-
|Jeffrey Schnettler
|5zqo2-omblo-i7knq-qyrfu-mjccn-tljyd-qslab-b7ukn-7tshi-pbeke-pae
|
|https://matrix.to/#/#ic-node-provider-5zqo2:matrix.org
|-
|Jimmy Quach
|dzxyh-fo4sw-pxckk-kwqvc-xjten-3yqon-fm62b-2hz4s-raa4g-jzczg-iqe
|
|https://matrix.to/#/#ic-node-provider-dzxyh:matrix.org
|-
|Jonathan Ziskind
|qcs4o-yswwp-7ozhg-m2ago-ytjyl-zlckb-raykw-fi5hl-cflyt-4beyv-zqe
|
|https://matrix.to/#/#ic-node-provider-qcs4o:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-unqqg:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-py2kr:matrix.org
|-
|Krishna Enterprises
|zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae
|pl2
|@krishnaenterprises:matrix.org
https://matrix.to/#/#ic-node-provider-zy4m7: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
|
|https://matrix.to/#/#ic-node-provider-abscc:matrix.org
|-
|Lukas Helebrandt
|efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe
|bn1
|@lukas:greensteps.cn
https://matrix.to/#/#ic-node-provider-efem5:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-4r6qy:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-s5nvr:matrix.org
|-
|Marvelous Web3
|7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe
|
|https://matrix.to/#/#ic-node-provider-7uioy:matrix.org
|-
|Mary Ren
|vdzyg-amckj-thvl5-bsn52-2elzd-drgii-ryh4c-izba3-xaehb-sohtd-aae
|
|https://matrix.to/#/#ic-node-provider-vdzyg:matrix.org
|-
|MB Patrankos šūvis
|4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae
|bt1
|@methistos:matrix.org
https://matrix.to/#/#ic-node-provider-4jjya:matrix.org
|-
|Mika Properties, LLC
|3siog-htc6j-ed3wz-sguhu-2objz-g5qct-npoma-t3wwt-bd6wy-chwsi-4ae
|
|https://matrix.to/#/#ic-node-provider-3siog:matrix.org
|-
|MI Servers
|izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe
|
|https://matrix.to/#/#ic-node-provider-izmhk:matrix.org
|-
|Mitchel Guerra
|4anlt-yam7x-eodmx-ik7mo-nl3kx-t35fj-52hfy-uv4jj-u2iea-ntg76-pqe
|
|https://matrix.to/#/#ic-node-provider-4anlt:matrix.org
|-
|Moon Block Ventures
|sdal5-w2c3d-p3buy-zieck-2wyuj-eu5bn-rkfe6-uuspi-o4n2b-gpei7-iae
|
|https://matrix.to/#/#ic-node-provider-sdal5:matrix.org
|-
|Mostly Wholesome, Inc.
|ou3o7-akyjc-ldwd5-anyjn-l2buz-cwhbg-nehlc-abkde-qtc7w-fozdi-hae
|
|https://matrix.to/#/#ic-node-provider-ou3o7:matrix.org
|-
|Neptune Partners
|4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae
|
|https://matrix.to/#/#ic-node-provider-4dibr:matrix.org
|-
|NoviSystems, LLC
|hk7eo-22zam-kqmsx-dtfbj-k5i6f-jg65h-micpf-2cztc-t2eqk-efgvx-vqe
|ny2, fm1
|novisystems
https://matrix.to/#/#ic-node-provider-hk7eo:matrix.org
|-
|OneSixtyTwo Digital Capital
|6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe
|
|https://matrix.to/#/#ic-node-provider-6nbcy:matrix.org
|-
|Origin Game
|cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe
|
|https://matrix.to/#/#ic-node-provider-cgmhq:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-72idx:matrix.org
|-
|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
https://matrix.to/#/#ic-node-provider-r3yjn:matrix.org
|-
|Power Meta Corporation
|4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae
|
|https://matrix.to/#/#ic-node-provider-4fedi:matrix.org
|-
|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)
https://matrix.to/#/#ic-node-provider-trxbq:matrix.org
|-
|Rachel Dymecki
|chnsu-yaqt5-6osy5-au4zn-li6yu-nufmw-dewrt-utkiu-twd76-ujypw-rae
|
|https://matrix.to/#/#ic-node-provider-chnsu:matrix.org
|-
|Richard Ma
|egb3e-rzi2e-vpsmm-akysp-l2owk-4dgst-b5hmg-xrkwa-cr3uk-zlzds-mae
|
|https://matrix.to/#/#ic-node-provider-egb3e:matrix.org
|-
|Richard Suarez
|cmcjw-6c5ve-4zjnt-lipnl-2lp43-oh5wk-ewciz-xyvnv-m2rz5-hkm6a-hqe
|
|https://matrix.to/#/#ic-node-provider-cmcjw:matrix.org
|-
|Ricky Sidhu
|q22bo-3uyqa-jvtpt-gapjk-pseor-esx4a-zyb74-vzea4-o7nx2-tafgq-hae
|
|https://matrix.to/#/#ic-node-provider-q22bo:matrix.org
|-
|Rishi Sachdev
|6tg64-cdfoh-kl35i-p6qti-sose3-746lr-jk5ex-phuvu-jfu3d-5svwa-7qe
|
|https://matrix.to/#/#ic-node-provider-6tg64:matrix.org
|-
|Rivram Inc
|ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae
|nm1,mtl1
|@ritvick
https://matrix.to/#/#ic-node-provider-ulyfm:matrix.org
|-
|Rodney Zorrilla
|bgprp-b2mnt-ci5in-57vuk-p7qvo-tj2tb-5w5su-qwenk-gbe77-mnuiq-sqe
|
|https://matrix.to/#/#ic-node-provider-bgprp:matrix.org
|-
|Ronnie Pellizzari
|wwxec-c2gd2-bu5on-ktpwz-z2ph3-vlr4p-m7ztf-6ck7r-nt3r4-fxbdq-mae
|
|https://matrix.to/#/#ic-node-provider-wwxec:matrix.org
|-
|Russell Ford
|p5jx4-lsrog-ep5o3-5uudg-opdg3-ur45z-xeefi-4ejfz-47t2k-riwfv-dae
|
|https://matrix.to/#/#ic-node-provider-p5jx4:matrix.org
|-
|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
|
|https://matrix.to/#/#ic-node-provider-a24zv:matrix.org
|-
|Starbase
|sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae
|
|https://matrix.to/#/#ic-node-provider-sixix:matrix.org
|-
| 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
|
|https://matrix.to/#/#ic-node-provider-6r5lw:matrix.org
|-
|Tomahawk.vc
|ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae
|
|https://matrix.to/#/#ic-node-provider-ucjqj:matrix.org
|-
|Virtual Hive Ltd
|wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae
|fr2
|Chris B
https://matrix.to/#/#ic-node-provider-wdnqm:matrix.org
|-
|Vladyslav Popov
|3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae
|pa2,ma2,si1,rg1, wy1,li1,ta2
|vladyslav_p
https://matrix.to/#/#ic-node-provider-3oqw6:matrix.org
|-
|Wancloud limited
|g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe
|hk1
|<nowiki>hashbamboo | HashQuark, Daniel | HashQuark</nowiki>
https://matrix.to/#/#ic-node-provider-g2ax6:matrix.org
|-
|Web3game
|64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe
|hk4
|web3game
https://matrix.to/#/#ic-node-provider-64xe5:matrix.org
|-
|William Zelver
|usau7-upgoh-sg464-6qnso-lud42-nxho6-ith26-a2jhq-q5bgy-ajeou-4ae
|
|https://matrix.to/#/#ic-node-provider-usau7:matrix.org
|-
|Wolfhound LLC
|6mifr-stcqy-w5pzr-qpijh-jopft-p6jl3-n2sww-jhmzg-uzknn-hte4m-pae
|
|https://matrix.to/#/#ic-node-provider-6mifr:matrix.org
|-
|Wolkboer (Pty) Ltd
|mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae
|jb3
|wolkboer
https://matrix.to/#/#ic-node-provider-mme7u:matrix.org
|-
|Zondax AG
|hzqcb-iiagd-4erjo-qn7rq-syqro-zztl6-cpble-atnkd-2c6bg-bxjoa-qae
|
|https://matrix.to/#/#ic-node-provider-hzqcb:matrix.org
|-
|ZTLC PTE LTD
|xsrwt-tl3tk-n3aya-rafh3-ta6xu-eviw5-ae5dg-2f3bf-siaab-wdwdo-dqe
|
|
|}

Node Provider Self Declarations

2024-09-30T14:53:39Z

Sat: Merge edit by Roald av8

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''

</blockquote>

[[43rd Big Idea Films, LLC]]

[[ACCUSET SOLUTIONS]]

[[Aitubi AG]]

[[Altimist Ltd]]

[[ALLUSION BV]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bitapp]]

[[Bitmoon]]

[[Blockchain Development Labs Inc]]

[[Blockchain Literacy Foundation]]

[[Blocktech Ventures LLC]]

[[BLP22, LLC]]

[[Bohatyrov Volodymyr]]

[[Buldakova Rehina]]

[[CarbonTwelve]]

[[CocoMango LLC]]

[[Conic Ventures]]

[[Eastman_Ventures_Pty_Ltd|Eastan_Ventures_Pty_Ltd]]

[[Exaion]]

[[User:FenexLLC|FenexLLC]]

[[Ferndale International]]

[[Geeta Kalwani]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[Giant Leaf, LLC]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital|HoneyCob Capital]]

[[Icaria_Systems_Pty_Ltd|Icaria_Systes_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Krzysztof Żelazko]]

[[Katerina Karapuz]]

[[Louise Velayo]]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Michael_and_Dominik_Peterer]]

[[Mariano Stoll]]

[[Neptune Partners]]

[[NODAL CAPITAL]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[Nataliia Nykyforak]]

[[Natalia Kulesha]]

[[Nikola Nikov]]

[[OneSixtyTwo Digital Capital]]

[[User:Soekawat|Origin Game]]

[[Paul Creasey]]

[[User:Protocol16|Philip Hur]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Rivram Inc]]

[[Stamper Co., Ltd.]]

[[Serenity lotus limited]]

[[Technical University of Munich]]

[[Tenderloin Ventures AG]]

[[Timur Rakhimzhan]]

[[Wolkboer (Pty) Ltd]]

[[WMA Investments Limited]]

[[VirtualHiveLtd|Virtual Hive Ltd]]

[[Vladyslav Popov]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />

Node Provider Maintenance Guide

2024-07-19T07:20:33Z

Sat: /* Common maintenance tasks */

== Troubleshooting ==
See the [[Node Provider Troubleshooting]] guide for info on troubleshooting failed onboardings, unhealthy nodes, networking, and more.

== Submitting NNS proposals ==
As a part of being a Node Provider, you will likely have to submit some NNS proposals. The page at the following link describes some of these proposals: [[Node Provider NNS proposals]]

== Monitoring ==
You are expected to regularly monitor the health of your nodes. Node health status is available on the public dashboard. Example: [https://dashboard.internetcomputer.org/node/235hh-hmjhq-dejel-3q5oi-pdz66-dygbp-yi2sy-zmuiq-rj7r7-65hue-wae node status].

You can also view your node's [https://internetcomputer.org/docs/current/references/node-providers/node-metrics#manually-obtaining-metrics public health metrics] and monitor it with the [https://internetcomputer.org/docs/current/references/node-providers/node-metrics IC observability stack].

===Community Tools and Resources===

Several node providers have generously shared tools to facilitate monitoring node health. These tools can provide notifications in case of node issues.

====Aviate Labs Node Monitor====

*'''Turnkey Solution''': Receive email alerts for unhealthy nodes.
*'''Link''': [https://www.aviatelabs.co/node-monitor AviateLabs Node Monitor]

====DIY Node Monitoring====

*'''GitHub Repository''': Run your own node monitoring system.
*'''Link''': [https://github.com/aviate-labs/node-monitor Aviate Labs GitHub]

====Prometheus Exporter for Node Status====

*'''GitHub Repository''': A tool for exporting node status to a Prometheus-compatible format.
*'''Link''': [https://github.com/virtualhive/ic-node-status-prometheus-exporter IC Node Status Prometheus Exporter]

== Common maintenance tasks ==
*[[Removing a Node From the Registry]]
*[[Adding additional node machines to existing Node Allowance]]
*[[Updating your node's IPv4 and domain name]]
*[[Changing IPv6 addresses of nodes]]
*[[Moving a node from one DC to another]]
*[[iDRAC access and TSR logs]]
*[[Checking node CPU and memory speed]]
*For changing your Node Provider or DC principal, please refer to [[Node Provider NNS proposals]]
*[[Updating Firmware]]
==Permitted tools==
For security and confidentiality reasons, other tools are not allowed to run on the same machine in parallel with the replica. In case you need to troubleshoot an issue, it is recommended to either boot the machine from a USB drive that has a live Linux distribution (e.g. [https://ubuntu.com/tutorials/try-ubuntu-before-you-install#3-boot-from-usb-flash-drive Ubuntu]) or to debug from an auxiliary machine in the same rack on which you have complete control, as described in [[Troubleshooting Unhealthy Nodes#Setting Up an Auxiliary Machine for Network Diagnostics|Unhealthy Nodes#Setting Up an Auxiliary Machine for Network Diagnostics]]

==Scheduled data center outages==
When your data center notifies you of a scheduled outage, you must:

*Notify DFINITY on the [[Node Provider Matrix channel]]
*Make sure your nodes return to one of the healthy statuses when the outage is resolved:
**Active in Subnet - The node is healthy and actively functioning within a subnet.
**Awaiting Subnet - The node is operational and prepared to join a subnet when necessary.
*If a node is degraded at first, give it a little bit of time in case it needs to catch up, but make sure that it does return to one of the two healthy statuses.

==Node rewards based on useful work==
The Internet Computer protocol can tolerate up to 1/3 of nodes misbehaving. There is an ongoing activity to automatically issue node rewards based on useful work, and also to automatically reduce node remuneration in case nodes are misbehaving. This will provide a financial incentive for honest behavior. Please follow the forum and the Matrix channel to stay informed about these activities.

In the meantime, the recommendation is to prepare for this by making sure that your nodes are online and healthy at all times, otherwise you risk penalties even before the automatic node rewards based on useful work become active.

== Subnet recovery==
In case subnet recovery is needed, we may have to reach out to you for assistance. Please make sure you closely follow activities in the Matrix Channel, and enable notifications on new messages -- especially direct mentions.

==General best practices==

# Keep a separate machine in the same rack with appropriate tools for network diagnostics and troubleshooting
# Engage with the node provider community for support and to share effective troubleshooting techniques
===Setting Up an Auxiliary Machine for Network Diagnostics===
Robust Internet connectivity is essential. Without access to internal node logs and metrics, troubleshooting requires alternative strategies, including the use of an auxiliary machine within the same rack. Here's a brief outline for setting up an auxiliary machine in the same rack while following best security practices:

# Hardware Setup:
#* Choose a server with sufficient resources to run diagnostic tools without impacting its performance. There is no need to follow the gen1/gen2 hardware requirements for this server (since this node would not be joining the IC network), but make sure the server is performant enough to run network tests.
#* Ensure that physical security measures are in place to prevent unauthorized access.
# Operating System and Software:
#* Install a secure operating system, like a minimal installation of Linux (we prefer Ubuntu 22.04), which reduces the attack surface.
#* Keep the system updated with the latest security patches and firmware updates.
# Network Configuration:
#* Configure the machine with an IPv6 address in the same range as the IC nodes for accurate testing.
#* Set up a restrictive firewall on the machine to allow ''only the necessary'' inbound and outbound traffic. Consider allowing Internet access for this machine only during troubleshooting sessions and keeping the machine behind a VPN at other times.
# Diagnostic Tools:
#* Install network diagnostic tools such as <code>ping</code>, <code>traceroute</code>, <code>nmap</code>, <code>tcpdump</code>, and <code>iperf</code>.
#* Configure monitoring tools to simulate node activities and track responsiveness.
# Security Measures:
#* Use strong, unique passwords for all accounts, and change them regularly. Or, preferably, do not use passwords at all and use key-based access instead.
#* Implement key-based SSH authentication and disable root login over SSH.
#* Regularly review logs for any unusual activities that might indicate a security breach.
# Maintenance and Updates:
#* Regularly update all software to the latest versions.
#* Periodically test your network diagnostic tools to ensure they are functioning as expected.

==Peer-support and bug reports / resolution: Node Provider Matrix Channel==

Node Providers are encouraged to join the dedicated [[Node Provider Matrix channel]]. This platform can be used for discussing maintenance-related queries and sharing insights, report issues, and search for previous resolutions for operations.

Please consult the Matrix channel for troubleshooting issues '''only after consulting the [[Node Provider Troubleshooting]] guide'''

'''Communication Guidelines on the Matrix Channel'''

As a Node Provider, ensure your notifications are enabled to receive new messages promptly. Your input or intervention might be crucial, especially in urgent situations.

It is recommended to add the node provider name to your alias (handle) on the communication platform, to facilitate communication and enable others to quickly and easily mention you.

Changing IPv6 addresses of nodes

2024-07-19T07:18:45Z

Sat: Add the initial doc with the process

Q: Is there a procedure to change IPv6 addresses of nodes without redeploying the nodes?

A: Thats sadly not possible at the moment. The IPv6 address is a read only record in the registry for the node, so the only way to change it at the moment (2024) is to redeploy a node.

Steps would be something along the following lines:

# Communicate the intention and get the green light (e.g. to make sure there are enough healthy nodes in subnets to prevent a bigger incident)
# Disconnect nodes from the Internet to prevent them from re-registering automatically
# Remove nodes assigned to subnets via NNS proposals, using DRE tool https://github.com/dfinity/dre
# Remove all unassigned nodes from the registry by following [[Removing_a_Node_From_the_Registry]]
# Redeploy all nodes as new nodes via standard USB installation.

For the node redeployment, you will need to update the config file in the installation USB to use the new IPv6 prefix.

You do not have to change the rewards configuration if you are not changing the number of nodes

Node Provider Matrix channel

2024-07-03T09:19:25Z

Sat:

There are Matrix rooms (channels) that are 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. '''NOTE:''' these rooms should only be consulted for troubleshooting issues '''after consulting all relevant [[Node Provider Troubleshooting]] documentation.'''

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org (lots of activity)
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org (infrequent messages)
* Incident response: https://app.element.io/#/room/#ic-node-providers-incident-response:matrix.org (communication reserved only for incident response. Please join if you are a node provider, and enable all notifications!)

These rooms run 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.

'''NOTE: 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]. If possible, [https://element.io/help#settings3 enable notifications for missed messages], especially for rooms with lower activity.

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, Charles Witte
|-
|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
|
|
|-
|AITUBI AG
|
|
|
|-
|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
|mb1, lj1
|@gorazd_o:matrix.org
|-
|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
|bt1
|@methistos:matrix.org
|-
|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
|mu1
|katernoir
|-
|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
|hk4
|web3game
|-
|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
|
|
|}

Node Provider Matrix channel

2024-07-03T09:13:29Z

Sat: web3game

There are Matrix rooms (channels) that are 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. '''NOTE:''' these rooms should only be consulted for troubleshooting issues '''after consulting all relevant [[Node Provider Troubleshooting]] documentation.'''

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org (lots of activity)
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org (infrequent messages)
* Incident response: https://app.element.io/#/room/#ic-node-providers-incident-response:matrix.org (communication reserved only for incident response. Please join if you are a node provider, and enable all notifications!)

These rooms run 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.

'''NOTE: 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]. If possible, [https://element.io/help#settings3 enable notifications for missed messages], especially for rooms with lower activity.

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, Charles Witte
|-
|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
|
|
|-
|AITUBI AG
|
|
|
|-
|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
|mu1
|katernoir
|-
|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
|hk4
|web3game
|-
|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
|
|
|}

Node Provider Onboarding

2024-06-24T08:25:36Z

Sat: Update dfx instructions

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/246d0ce0784d9990c06904809722ce5c2c816269/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 e3b2964d959509a2c3347503d02211a205b719d06c771d6bab4025d9e63d0605) && 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/246d0ce0784d9990c06904809722ce5c2c816269/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 1b9795f752c9854ad070fcc4b4ec0673978731d0c7e0d875db0c4872217f443d) && 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://internetcomputer.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. In particular, node providers onboarding [[Node Provider Machine Hardware Guide|Gen 2 hardware]] must onboard '''without''' a NitroKey HSM. If you will be onboarding '''without''' 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 Onboarding

2024-06-24T08:22:10Z

Sat: Update ic-admin version

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/246d0ce0784d9990c06904809722ce5c2c816269/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 e3b2964d959509a2c3347503d02211a205b719d06c771d6bab4025d9e63d0605) && 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/246d0ce0784d9990c06904809722ce5c2c816269/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 1b9795f752c9854ad070fcc4b4ec0673978731d0c7e0d875db0c4872217f443d) && 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. In particular, node providers onboarding [[Node Provider Machine Hardware Guide|Gen 2 hardware]] must onboard '''without''' a NitroKey HSM. If you will be onboarding '''without''' 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-06-07T07:31:38Z

Sat:

There are Matrix rooms (channels) that are 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:

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org (lots of activity)
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org (infrequent messages)
* Incident response: https://app.element.io/#/room/#ic-node-providers-incident-response:matrix.org (communication reserved only for incident response. Please join if you are a node provider, and enable all notifications!)

These rooms run 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.

'''NOTE: 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]. If possible, [https://element.io/help#settings3 enable notifications for missed messages], especially for rooms with lower activity.

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, Charles Witte
|-
|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
|
|
|-
|AITUBI AG
|
|
|
|-
|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
|mu1
|katernoir
|-
|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
|
|
|}

Node Provider Matrix channel

2024-05-30T09:35:59Z

Sat:

There are Matrix rooms (channels) that are 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:

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org (lots of activity)
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org (infrequent messages)
* Incident response: https://app.element.io/#/room/#ic-node-providers-incident-response:matrix.org (communication reserved only for incident response. Please join if you are a node provider, and enable all notifications!)

These rooms run 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.

'''NOTE: 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]. If possible, [https://element.io/help#settings3 enable notifications for missed messages], especially for rooms with lower activity.

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, Charles Witte
|-
|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
|
|
|-
|AITUBI AG
|
|
|
|-
|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
|
|
|}

Node Provider Matrix channel

2024-05-30T09:35:10Z

Sat: Added a link to the incident response room

There are Matrix rooms (channels) that are 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:

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org (lots of activity)
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org (infrequent messages)
* Incident response: https://app.element.io/#/room/#ic-node-providers-incident-response:matrix.org (communication reserved only for incident response. Please join if you are a node provider, and enable all notifications!)

These rooms run 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.

'''NOTE: 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, Charles Witte
|-
|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
|
|
|-
|AITUBI AG
|
|
|
|-
|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
|
|
|}

Troubleshooting Node Deployment Errors

2024-05-30T09:28:48Z

Sat: /* Troubleshooting IC-OS installation failure: Getting a shell */

This page has some error codes that may display as you are onboarding your nodes. '''Please review this guide in its entirety before reaching out on the IC Node Provider Matrix channel.'''

If you need Dell to service your machine, then these links will assist in [[Retrieving a Dell TSR Log|retrieving a Dell TSR Log]] and in resetting the iDRAC password.

== General troubleshooting steps ==
'''Please complete ALL these steps before messaging in the Matrix channel.'''

# Make sure you are using '''[https://dashboard.internetcomputer.org/releases the latest IC-OS release].''' If you are not sure if you are using the latest release, download the latest release and retry your node deployment.
# Make sure you are using the proper Node deployment guide:
#*[[Node Deployment Guide (with an HSM)|Legacy (Gen-1) Node Deployment Guide (with an HSM)]]
#* [[Node Deployment Guide|Current (Gen-2) Node Deployment Guide (without an HSM)]]
# Reread '''all''' the directions in your node deployment guide to make sure you aren’t missing something. The directions are precise, and they do change slightly over time.
# Reread the [[Node Provider Networking Guide]]. Make sure you aren’t violating anything in the networking “[[Node Provider Networking Guide#What NOT to do|What NOT to do]]” section.
# Confirm the networking information inputted to your <code>config.ini</code> file is correct.
#Restart '''everything''' you can between the node machine and the internet (router, firewall, etc.)
#Restart the node deployment process from the very beginning. Try to reproduce the error you are encountering.
#Try to deploy to a different node machine (one that is not being used in a subnet). Try to reproduce the error on multiple node machines.
#Take extra care to make sure you [[Node Provider Onboarding#5.%20Choose%20onboarding%20path%20.28HSM%20vs%20no%20HSM.29|set up you Node Operator keys correctly.]]

=== Support request information requirements===
If you are still encountering deployment issues, '''read the rest of this guide'''. If you still can't successfully deploy your nodes, post a support request message in the [https://app.element.io/#/room/#ic-node-providers:matrix.org IC Node Provider Matrix channel] containing '''ALL''' the following information:
*'''A confirmation that you ran through the above general troubleshooting steps'''
*A screenshot of your issue
*The stage of the onboarding in which you are failing
*What deployment method you are using:
**[[Node Deployment Guide (with an HSM)|Legacy (Gen-1) Node Deployment Guide (with an HSM)]]
**[[Node Deployment Guide|Current (Gen-2) Node Deployment Guide (without an HSM)]]
*Is this your first time performing an IC-OS installation?
* Is this your first time performing an IC-OS installation ''in this data center''?
*Is this your first time performing an IC-OS installation ''with this Node Operator Key?''
*Can you reproduce this issue?
*Machine hardware details (Gen1 / Gen2, server brand)
*The datacenter out of which you are attempting to deploy
* Any other details you see as relevant

If you post a support request message that doesn't include '''ALL''' the above information, you will be asked to do so.

==Node registration failure==
==== Example Error====
You successfully installed your node without errors, but now, your node is failing to register with the IC and your Node ID is not visible on the [https://dashboard.internetcomputer.org/ dashboard].

====Common Causes====
The node has installed and launched successfully, but is unable to join the network. This could be due to an out-of-date IC-OS installation image, trouble contacting the NNS, or node installation limits on the network.

====Suggested Solutions ====
Please verify that a recent [https://dashboard.internetcomputer.org/releases IC-OS installation] image version is being used, and check https://dashboard.internetcomputer.org/ to see how many nodes are currently registered under your Node Provider. If there are more nodes listed than expected, or if there are multiple nodes overlapping, please have any extra nodes removed from the network before attempting to install again. This can be caused if multiple installations have been performed on the same hardware, without cleaning up the records from the network.

Additionally, [https://wiki.internetcomputer.org/wiki/Node_Provider_Networking_Guide#What_NOT_to_do verify that there is no external network filtering] (external firewalls, packet filters, rate limiters).

==IC-OS installation failure: Missing Drives ==
==== Example Error ====
--------------------------------------------------------------------------------
INTERNET COMPUTER - SETUP - FAILED
--------------------------------------------------------------------------------

Please consult the wiki guide: Troubleshooting Node Deployment Errors.

--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------

Not enough drives found. Are all drives correctly installed?

--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------

'''Another version of it might say "Aggregate Disk size does not meet requirements"'''

==== Common Causes ====
This error means that the IC-OS installation medium could not detect all required drives. This is a common issue, even if you believe that all drives are installed correctly. Some of them may not be functioning properly, or may not be fully seated into the chassis.

====Suggested Solutions ====
Check that all drives are fully seated and installed correctly, or install the required number of drives. You may be able to check the drives for indication LEDs to see which may not be installed or functioning correctly.

==IC-OS installation failure: Invalid CPU Configuration ==
==== Example Error====

--------------------------------------------------------------------------------
INTERNET COMPUTER - SETUP - FAILED
--------------------------------------------------------------------------------

Please consult the wiki guide: Troubleshooting Node Deployment Errors.

--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------

Number of threads (16/32) does NOT meet system requirements.

--------------------------------------------------------------------------------
ERROR
-------------------------------------------------------------------------------- 
====Common Causes====
Issues related to CPU capability usually mean that the CPUs are not configured correctly in the system BIOS.

====Suggested Solutions====
Please check that BIOS settings are configured correctly. It may be helpful to reset all settings to factory defaults, and go through the BIOS configuration again.
==IC-OS installation failure: Unable to Reach Internet ==
==== Example Error====

--------------------------------------------------------------------------------
INTERNET COMPUTER - SETUP - FAILED
--------------------------------------------------------------------------------

Please consult the wiki guide: Troubleshooting Node Deployment Errors.

--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------

Unable to ping IPv6 gateway.

--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------

====Common Causes====
This error means that the node is not able to communicate with the network properly. This can be due to a misconfigured network configuration, or due to issues somewhere between the node and the rest of the internet.

====Suggested Solutions ====
Please try to capture any output that is displayed before this error shows. For example:
* Printing user defined network settings...
IPv6 Prefix : XXX
IPv6 Subnet : XXX
IPv6 Gateway: XXX

* Printing system's network settings...
IPv6 Prefix : XXX
IPv6 Subnet : XXX
IPv6 Gateway: XXX

* Printing IPv6 addresses...
SetupOS: XXX
HostOS : XXX
GuestOS: XXX

Please compare this, and the initial configuration, to what you expect. If this configuration does not match, please update the initial configuration, and try again.

If this does match the expected configuration, please attempt to diagnose any machines between this node and the rest of the internet. This could be due to improper firewall configuration, or an issue with the data center’s network. If all configuration looks correct, please attempt to reboot any machines between this node and the rest of the Internet. In most cases, this would be a firewall. Rebooting the firewall - even if it seems to be operating correctly - has resolved this issue many times.

==IC-OS installation failure: Unable to setup PV ==
==== Example Error====

--------------------------------------------------------------------------------
INTERNET COMPUTER - SETUP - FAILED
--------------------------------------------------------------------------------

Please consult the wiki guide: Troubleshooting Node Deployment Errors.

--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------

Unable to setup PV on drive '/dev/nvme8n1'.

--------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------

====Common Causes ====
This error means that the node is able to recognize that a drive is installed, but is unable to write to it. This could indicate that there is a hardware issue with the drive.

====Suggested Solutions ====
Please try to remove and re-install all drives, before attempting to install the node again. It may be helpful to independently verify that each drive is functioning correctly.

==Troubleshooting IC-OS installation failure: Getting a shell in SetupOS==
*During the IC-OS installation, you may hit enter to obtain console access to troubleshoot any issues you are encountering. You can also hit enter at the error page in order to access the console. Hit enter until you see a login prompt
*Log in with user <code>root</code> and empty password
*Now you have root access for diagnostics, etc.
Note that after the installation is finished and the machine reboots into HostOS, the same troubleshooting console isn't available anymore. It is only available in SetupOS, i.e., during IC-OS installation. After the OS is installed you may boot the machine from a live USB distribution such as [https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started Ubuntu Live USB], and troubleshoot that way.

Node Provider Matrix channel

2024-04-17T16:15:14Z

Sat: Add Charles Witte to hu1

There are Matrix rooms (channels) that are 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:

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org

These rooms run 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.

'''NOTE: 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, Charles Witte
|-
|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
|
|
|-
|AITUBI AG
|
|
|
|-
|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
|
|
|}

Node Provider Matrix channel

2024-04-12T08:36:04Z

Sat: Add the announcements channel

There are Matrix rooms (channels) that are 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:

* General discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org
* Announcements: https://app.element.io/#/room/#ic-node-providers-announcements:matrix.org

These rooms run 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.

'''NOTE: 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
|
|
|-
|AITUBI AG
|
|
|
|-
|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
|
|
|}

Troubleshooting Unhealthy Nodes

2024-03-11T10:51:47Z

Sat: /* Frequently Asked Questions */

=== '''Use [https://dashboard.internetcomputer.org/centers the dashboard] to verify that the node is healthy''' ===
*The node count for your data center should match the number of nodes in that data center.
* Look for the principal ID for the node which you are servicing. Status explanations are [https://wiki.internetcomputer.org/wiki/Node_Provider_Troubleshooting#Node_Status_on_the_Dashboard here].
* If the node isn't listed at all, then it needs to be [[IC-OS Installation Runbook|redeployed the node with a fresh IC-OS image]].

=== '''Degraded nodes statuses''' ===

==== '''>> IC_OrchestratorFlapping''' ====
'''Explanation:''' Orchestrator coordinates the execution of many IC GuestOS processes, including the IC Replica. If the orchestrator is repeatedly restarting, then the GuestOS and the Replica process likely do not operate as expected.

'''Possible causes:'''

* Networking issues
* Hardware issues
* Software problems

'''Troubleshooting and remediation:'''

* Check if any NNS proposals were recently executed for the nodes in question https://dashboard.internetcomputer.org/governance
* Check if there are some bandwidth limitations on these nodes, and ensure any traffic shaping, QoS, DOS protection, etc, are ''disabled'' on the ISP side
* Perform other [https://wiki.internetcomputer.org/w/index.php?title=Unhealthy_Nodes&veaction=edit#Setting_Up_an_Auxiliary_Machine_for_Network_Diagnostics network diagnostics checks]
* Inspect node logs and metrics, if possible
* Consult other node providers and DFINITY if there are any known software problems with the latest revision that the node(s) are running

==== '''>> IC_Replica_Behind''' ====
'''Explanation:''' IC Replica is the main process, that runs canisters (smart contracts). If the Replica process cannot catch up, then the replica (node) cannot be a productive member of the IC subnet.

'''Possible causes:'''

* Networking issues
* Hardware issues
* Software problems

'''Troubleshooting and remediation:'''

* Check if there are any hardware issues reported by the machine's BMC (Baseboard Management Controller)
* Perform [https://wiki.internetcomputer.org/wiki/Updating_Firmware firmware upgrade]
* Check if any NNS proposals were recently executed for the nodes in question https://dashboard.internetcomputer.org/governance
* Check if there are some bandwidth limitations on these nodes, and ensure any traffic shaping, QoS, DOS protection, etc, are ''disabled'' on the ISP side
* Perform other [https://wiki.internetcomputer.org/w/index.php?title=Unhealthy_Nodes&veaction=edit#Setting_Up_an_Auxiliary_Machine_for_Network_Diagnostics network diagnostics checks]
* Inspect node logs and metrics, if possible
* Consult other node providers and DFINITY if there are any known software problems with the latest revision that the node(s) are running

=== '''"Orchestrator Started" message on console screen''' ===
This message shown on console screens is not an error, nor is it confirmation that the node is running properly. This must be determined in other ways:

*'''Check [https://dashboard.internetcomputer.org/ the dashboard]''' to check the status of the node. (Status explanations are [https://wiki.internetcomputer.org/wiki/Node_Provider_Troubleshooting#Node_Status_on_the_Dashboard here].) Use the principal ID that was assigned to the node when it was onboarded to identify it.
*If the node is not visible on the dashboard, then it has not registered with the Internet Computer.
**If you have recently installed a current IC-OS image, then you can try inserting the HSM and/or a reboot to see if it joins. This would work if a recent IC-OS installation was successful and only the registration and joining was interrupted.
**If you have ''not'' recently installed a current IC-OS image, then do ''not'' insert the HSM. You do not want the node to rejoin with an old IC-OS image, as it will only fail again. Instead, you should consider [[Updating Firmware|upgrading the firmware]] if it is running on old versions, and then redeploy the node with [[IC-OS Installation Runbook|a fresh/current IC-OS image]] (which will assign a new principal to the node so that you can identify it in the dashboard.)

=== '''Offline nodes''' ===
Network issues are the main reason why nodes are in an "OFFLINE" state.

* Your node may not be reachable from the IC or
* you may not be able to reach other nodes the IC from your node or
* you may note be able to reach the monitoring servers from your node.

Please refer to the '''Networking Troubleshooting Steps''' below.

Another possible reason for an OFFLINE node may be that your GuestOS failed to start due to a RAM failure.

=== '''Server Troubleshooting Steps''' ===
These steps may help when a server is unhealthy or has been removed from the network, but the connectivity in the data center is functioning correctly:

#Verify if the server is up and running:
#*Check the power status of the server.
#*Check if the server is displaying any error messages or indicators.
#*If possible, access the server remotely or physically to ensure it is functioning properly.
#Hook up a crash cart and check for errors on the screen, troubleshoot as needed.
#Consider [[Updating Firmware|updating the firmware]] if it has been a long time, and/or if you have recently had other nodes that needed firmware upgrades to become healthy again.
# If no known error is found, please [[IC-OS Installation Runbook|redeploy the node with a fresh IC-OS image]].
#* The deployment process identifies/fixes many software issues.
#* Note that if an old IC-OS image is used, the node will "appear" to be healthy at first, but it will not be able to catch up to the blockchain and will therefore fall behind and become unhealthy again. '''Thus, a current IC-OS image must be used.'''
#* At the end, obtain the new principal ID for the node from the crash cart screen so you can check the dashboard status.
#*'''If a node is healthy ("Awaiting Subnet" status) for a while and then changes to "Offline," then whatever the issue was originally still exists.''' Troubleshoot hardware, upgrade firmware, etc to resolve the issue.

=== '''Networking Troubleshooting Steps''' ===

# Inspect network hardware in the rack for any visible signs of malfunction (e.g. red lights) or incorrect setup
# Verify the cabling and port status on the switch:
#*Check the physical connection of the network cable between the server and the switch.
#*Ensure that the cable is securely plugged into the correct port on both ends.
#*Look for any signs of damage or loose connections.
#*Test the connectivity by trying a different network cable or using the same cable on a different port.
#Check for recent port flaps/link failures or any other activities which might cause it:
#*Check the logs or monitoring systems for any indications of port flapping or link failures.
#*Investigate any recent changes or activities that could have affected the network connection.
#*Consider any software updates, configuration changes, or physical alterations made recently.
#Try to perform a re-seat of cable/breakout/SFP/QSFP toward the affected machine:
#*Disconnect and reconnect the network cable at both ends (server and switch).
#*If applicable, re-seat any breakout cables, SFP modules, or QSFP modules used in the connection.
#*Ensure a secure and proper connection is established.
#Check with the switch vendor:
#*If the issue persists, contact the switch vendor's support team for further assistance.
#*Provide them with detailed information about the problem and any troubleshooting steps you have already taken.
#*Follow vendor guidance to troubleshoot and resolve the issue.
#**If your vendor requires a TSR log, see [[IDRAC access and TSR logs]] for an example of how to retrieve one from a Dell server.
#**[[Updating_Firmware|Updating the firmware]] might also resolve the issue.
# Utilize an auxiliary machine within the same rack with full network access to run diagnostics tools like <code>ping</code>, <code>traceroute</code>, and <code>nmap</code>
# Work with the ISP to troubleshoot and resolve any network routing issues identified during diagnostics
# Prepare for future incidents by establishing network redundancy and failover mechanisms

=== '''Best practices''' ===

# Keep a separate machine in the same rack with appropriate tools for network diagnostics and troubleshooting
# Engage with the node provider community for support and to share effective troubleshooting techniques

=== '''Setting Up an Auxiliary Machine for Network Diagnostics''' ===
Robust Internet connectivity is essential. Without access to internal node logs and metrics, troubleshooting requires alternative strategies, including the use of an auxiliary machine within the same rack. Here's a brief outline for setting up an auxiliary machine in the same rack, while following best security practices:
# Hardware Setup:
#* Choose a server with sufficient resources to run diagnostic tools without impacting its performance. There is no need to follow the gen1/gen2 hardware requirements for this server (since this node would not be joining the IC network) but make sure the server is performant enough to run network tests.
#* Ensure physical security measures are in place to prevent unauthorized access.
# Operating System and Software:
#* Install a secure operating system, like a minimal installation of Linux (we prefer Ubuntu 22.04), which reduces the attack surface.
#* Keep the system updated with the latest security patches and firmware updates.
# Network Configuration:
#* Configure the machine with an IPv6 address in the same range as the IC nodes, for accurate testing.
#* Set up a restrictive firewall on the machine to allow ''only the necessary'' inbound and outbound traffic. Consider allowing Internet access for this machine only during troubleshooting sessions, and keeping the machine behind a VPN at other times.
# Diagnostic Tools:
#* Install network diagnostic tools such as <code>ping</code>, <code>traceroute</code>, <code>nmap</code>, <code>tcpdump</code>, and <code>iperf</code>.
#* Configure monitoring tools to simulate node activities and track responsiveness.
# Security Measures:
#* Use strong, unique passwords for all accounts and change them regularly. Or, preferably, do not use passwords at all, and use key-based access instead.
#* Implement key-based SSH authentication and disable root login over SSH.
#* Regularly review logs for any unusual activities that might indicate a security breach.
# Maintenance and Updates:
#* Regularly update all software to the latest versions.
#* Periodically test your network diagnostic tools to ensure they are functioning as expected.

=== '''Frequently Asked Questions''' ===
'''Q: Is the monitoring system open-sourced? How does it communicate with the nodes?'''

A: The monitoring system configuration is not currently open-sourced. However, the node configuration that is required for proper node operation is fully open source. For more information about the node-to-node and node-to-monitoring communication, refer to the [https://sourcegraph.com/github.com/dfinity/ic/-/blob/ic-os/hostos/rootfs/etc/nftables.conf?L54-112 nftables configuration], which is the definitive guide for required open ports on Host OS, and [https://sourcegraph.com/github.com/dfinity/ic/-/blob/ic-os/guestos/rootfs/opt/ic/share/ic.json5.template?L322 similar nftables configuration] for the Guest OS. You can find the configuration for DFINITY-owned DCs and Gen1 node providers here: nftables configuration. We use [https://docs.victoriametrics.com/ Victoria Metrics] for metrics scraping (documentation) and [https://vector.dev vector.dev] for log scraping.

'''Q: What are the destination IPs and Ports for Frankfurt, Chicago, and San Francisco for connectivity troubleshooting?'''

A: At present, detailed node/port information is not publicly accessible, as disclosing this information is considered a security risk. To effectively troubleshoot connectivity issues with your nodes, we recommend setting up a "spot instance" or a temporary virtual machine (VM) with a cloud provider in each of the geographical regions. This approach allows you to test both connectivity and connection stability to your nodes, providing a practical solution for identifying and resolving network-related issues.

'''Q: The dashboard shows offline or degraded status for <DC>, but everything seems fine. What should we do?'''

A: Check if any of these issues are present: firewall restrictions, traffic shaping, DOS protection, or QOS features enabled on the ISP side. These should all be disabled for optimal node operation.

'''Q: Under what circumstances is a node removed from the IC network?'''

A: A node is removed from the IC network when it's deemed unhealthy. The determination of a node's health is made using tooling from https://github.com/dfinity/dre. This tooling assesses nodes based on various metrics and submits a proposal for their removal to maintain the highest level of decentralization possible. However, there are exceptions. For example, an unhealthy node might be temporarily retained if there are ongoing efforts to recover and restore it.

'''Q: How long can a node be down before it's excluded from the IC network?'''

A: There's no set time limit for how long a node can be down before exclusion. The decision is more qualitative and depends on the overall health of the network. Currently, the IC network can tolerate up to 1/3 of nodes in a 13-node subnet being down or unhealthy. This means a subnet can function with up to 4 unhealthy nodes. If the unhealthy nodes do not exceed this threshold, a node might be left in the subnet for a longer period, especially if there are efforts underway to make it healthy again.

'''Q: When are nodes typically removed or replaced?'''

A: Node removals or replacements are currently conducted semi-manually and are typically scheduled for Mondays or Fridays. This timing allows Foundation voters to participate in the decision-making process at the start or end of the workweek. However, as this process is manually conducted, exceptions may occur based on specific circumstances.

'''Q: What are the future plans for node management in the IC network?'''

A: In the medium term, there are plans to automate node replacements. This means node swaps might occur more frequently and systematically, reducing the manual overhead and potentially enhancing the network's resilience and performance.

Note: As with all network operations, these practices are subject to change based on technological advancements and the evolving needs of the IC network. It's always good to refer to https://github.com/dfinity/dre for the most current information and tooling.

'''Q: What is the standard procedure if a faulty component occurs and we have to take the server down for maintenance?'''

At the moment the process is as follows:

# The node provider should give their best to bring the server back up, as soon as possible
# The DFINITY DRE team will monitor the situation and submit any proposals to replace faulty nodes, if necessary, or reach out to individual node providers if node replacements wouldn't be effective enough.

So feel free to do maintenance whenever you need to. If node is not in a subnet, there is no problem to take the node down as long as necessary. If the node is in a subnet, node replication should handle it without problems. Please be aware that we are actively working on reward adjustments based on the number of active and productive nodes, so please try not to make the downtime longer than absolutely necessary, to avoid reward reductions.

One thing that would be really helpful from your side is:

# find the subnet id in which the node is located, and check how many nodes in the subnet are currently unhealthy
# If there are more than 2 (e.g. 3, 4, ... nodes) unhealthy nodes in the subnet, please consider postponing the maintenance work until the number of unhealthy nodes in the subnet reduces again to under 2.

In the future, any NP will be able to run the [https://github.com/dfinity/dre DRE tooling] and there will be a financial incentive for the node providers to both a) keep all nodes in the subnet healthy, and b) submit proposals to replace unhealthy nodes or to improve decentralization.

Back to [[Node Provider Troubleshooting]]

Back to [[Node Provider Documentation]]

Node Provider NNS proposals

2024-02-16T09:06:28Z

Sat: Updated instructions to use ic-admin directly

== Background ==

Here are some NNS proposals you may have to submit after onboarding nodes. For other maintenance tasks please refer to [[Node Provider Maintenance Guide]].

'''NOTE: Please remember that you need community votes on these proposals. Without at least 3% of the community voting on the proposal within 4 days, the proposal will get automatically rejected. You are recommended to reach out to other community members (voters) on https://forum.dfinity.org and to try to convince them to vote on your proposal. The best approach is to explain why is it beneficial for them to vote for your proposal.'''

== Adjusting the node allowance in a Data Center ==
To adjust the node allowance for an existing node operator record, you would need to use the <code>propose-to-update-node-operator-config</code> subcommand of the <code>ic-admin</code> tool. You should typically not add a new node operator record if you just want to add more nodes to the ''existing'' DC.

Here's a step-by-step guide on how to do this:

1. '''Gather Necessary Information:''' Ensure you have the following details:
#<code>NODE_PROVIDER_ID</code>: The principal ID of the node provider under which the node operator record is registered.
#<code>NODE_OPERATOR_ID</code>: The principal ID of the node operator whose allowance you want to change.
#<code>NEURON_ID</code>: The ID of the neuron that will propose this change.
#<code>CURRENTLY_REMAINING_NODE_ALLOWANCE</code>: The number of nodes that the node operator is allowed to add to the network without submitting a proposal.
#<code>NEW_NODE_ALLOWANCE</code>: The new number of nodes that the node operator is allowed to add.
The parts 1, 2, and 3 should be in your records, and should be the same principals (IDs) used to onboard nodes ''in the given DC''. The part 4 can be obtained from the registry, with <code>ic-admin</code>
$ ic-admin --nns-url <nowiki>https://ic0.app</nowiki> get-node-operator $NODE_OPERATOR_ID
For example:
$ ic-admin --nns-url <nowiki>https://ic0.app</nowiki> get-node-operator yl63e-n74ks-fnefm-einyj-kwqot-7nkim-g5rq4-ctn3h-3ee6h-24fe4-uqe
Fetching the most recent value for key: node_operator_record_yl63e-n74ks-fnefm-einyj-kwqot-7nkim-g5rq4-ctn3h-3ee6h-24fe4-uqe
Most recent version is 35791. Value:
NodeOperator { node_operator_principal_id: yl63e-n74ks-fnefm-einyj-kwqot-7nkim-g5rq4-ctn3h-3ee6h-24fe4-uqe, node_allowance: 0, node_provider_principal_id: niw4y-easue-l3qvz-sozsi-tfkvb-cxcx6-pzslg-5dqld-ooudp-hsuui-xae, dc_id: "mu1", rewardable_nodes: {"type0": 0, "type1": 28}, ipv6: None }
In the above example, the <code>CURRENTLY_REMAINING_NODE_ALLOWANCE</code> is 0. So if you want to add 5 more nodes with the same node operator (i.e. in the same DC), you should use <code>NEW_NODE_ALLOWANCE=5</code>. However, if the <code>CURRENTLY_REMAINING_NODE_ALLOWANCE</code> had value 2, you would only need 3 more nodes on top of your currently remaining allowance (2+3=5), so you should use <code>NEW_NODE_ALLOWANCE=3</code> in the proposal

2. '''Prepare the Command''': Construct the <code>ic-admin</code> command using the gathered information. Here's an example template:
$ 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"
$ NEW_NODE_ALLOWANCE=5
$ DC_ID=xx
$ FORUM_POST_URL=[https://forum.dfinity.org/ https://forum.dfinity.org/...]

$ ./ic-admin \
--nns-url <nowiki>https://ic0.app</nowiki> \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-update-node-operator-config \
--node-provider-id $NODE_PROVIDER_PRINCIPAL \
--node-operator-id $NODE_OPERATOR_PRINCIPAL \
--summary "Node provider '$NODE_PROVIDER_NAME' is adjusting the node allowance $NODE_ALLOWANCE to nodes in the $DC_ID data center. Link to the forum post for: $FORUM_POST_URL" \
--proposer $NEURON_ID \
$NEW_NODE_ALLOWANCE
Replace all placeholder variables above with the actual values before submitting the proposal.

3. '''Dry Run (strongly recommended)''': To preview the proposal without actually submitting it, you can add the <code>--dry-run</code> flag to the above command. This is useful for checking the proposal payload and ensuring everything is correct before the actual submission.

4. '''Execute the Command''': Once you are sure about the command and the details, execute it in your terminal. This will submit a proposal to update the node allowance in the node operator's configuration.

5. '''Monitor and Voting''': After submitting the proposal, it will go through a voting process by the governance system. You should monitor this to see if the proposal gets accepted or rejected.

7. '''Verification (Post-Approval)''': If the proposal is approved, you may want to verify that the node allowance has been updated as expected. This might involve querying the node operator's record with <code>get-node-operator</code> as described above.

Note that the exact command and options will vary based on your specific configuration and requirements. Make sure to replace placeholders with actual values relevant to your setup.

To see all available options, you can run:
$ ic-admin --nns-url <nowiki>https://ic0.app</nowiki> propose-to-update-node-operator-config --help

== Changing Your Node Provider Principal ==
If you have lost access to your Node Provider Principal or are transferring ownership of your nodes from one legal entity to another, you will need to create a new principal and update the NNS.

# Go through steps 1-4 on the [[Node Provider Onboarding]] page to install the necessary software and create a principal with a Ledger device and the NNS front-end dapp
#* There is no need to create a new Node Operator Key, so long as you still have access to your Node Operator private key/HSM (steps 5-7).
# Follow step [[Node Provider Onboarding#8. Register your Node Provider principal to the network|8 on the Node Provider Onboarding]] page to register the principal in the NNS.
#* Create a post on https://forum.dfinity.org/ AND also
#* Add the following explanation to the proposal summary to explain the following:
#** '''Identify yourself as an existing NP and which one you are'''
#** '''Why you are registering a new principal?''' -- Please explain the situation with as many details as acceptable to you since you need to convince the community to vote for your proposal.
#** '''How can they verify that you are who you say you are?'''
#** '''Please add a link to the forum post in the proposal summary.'''
# After the proposal from item 2 above (step 8 on the Node Provider Onboarding Page) is approved and executed, you will then need to link the new Node Provider Principal with the Node Operator for the DC(s). In the next codeblock:
## Replace the <code>NEURON_ID</code> with the neuron ID you got in [[Node Provider Onboarding#3. Create and Manage Neuron via NNS Frontend Dapp and Internet Identity|step 3 of the Node Provider Onboarding page]] (item 1 above).
## Replace the <code>FIRST_PROPOSAL</code> with the proposal created in step [[Node Provider Onboarding#8. Register your Node Provider principal to the network|8 on the Node Provider Onboarding]] page (item 2 above).
## 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>NODE_PROVIDER_OPERATOR</code> value with the Node Operator principal.
##* IMPORTANT: Please make sure that you also update the --summary and include a link to your previous proposal (from item 2 above).
## Create the Proposal<syntaxhighlight lang="shell">
$ NEURON_ID=xxxxxx
$ FIRST_PROPOSAL=xxxxx
$ NODE_PROVIDER_NAME=xxxxxxxxxxx
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_PROVIDER_OPERATOR=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx

❯ ic-admin \
--use-hsm \
--pin <redacted> \
--slot 0 \
--key-id 01 \
--nns-url https://ic0.app/ \
propose-to-update-node-operator-config \
--dry-run \
--proposer $NEURON_ID \
--proposal-title "Update the NO record for '${NODE_PROVIDER_PRINCIPAL}'" \
--summary "Updating the new node provider principal ${NODE_PROVIDER_PRINCIPAL} / '${NODE_PROVIDER_NAME}', as a second step following the execution of proposal ${FIRST_PROPOSAL}" \
--node-operator-id "$NODE_PROVIDER_OPERATOR" \
--node-provider-id "$NODE_PROVIDER_PRINCIPAL"
submit_proposal payload:
UpdateNodeOperatorConfigPayload {
node_operator_id: Some(
"$NODE_PROVIDER_OPERATOR",
),
node_allowance: None,
dc_id: None,
rewardable_nodes: {},
node_provider_id: Some(
"$NODE_PROVIDER_PRINCIPAL",
),
ipv6: None,
set_ipv6_to_none: None,
}
</syntaxhighlight>
## Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it is executed.
## In order to expedite the speed of your proposal's approval, it is best to create a follow-up post in the forum thread to raise awareness of your proposal. \

== Changing Your Data Center Principal ==
(AKA Creating a new Node Operator Record)

If the HSM that was used to deploy your nodes gets lost or corrupted, you can either replace the HSM with a new one, or you can replace the principal using the HSM-less method.

To replace using the HSM-less method, use steps 1, 5, 6, 7, 10, of the [[Node Provider Onboarding|Node Provider Onboarding instructions]]. Please note:

* When the proposal is submitted in step 10, you will need to wait several days for the proposal to pass.
* Make sure you explain in your proposal who you are and why you are replacing the principal to help ensure that your proposal is accepted by the community.
* You will then create the IC-OS image with the new principal, and it will be used to onboard the nodes using the options in the onboarding directions for using a <code>node_operator_private_key.pem</code> file.

Node Provider Remuneration

2024-02-13T12:57:06Z

Sat: Added a short description and a mention of the trustworthy node metrics

== Rewards ==

Node Providers receive rewards (remuneration) for owning node machines that run in the Internet Computer network. Node Provider rewards are set by the NNS DAO, with changes only possible through NNS proposals adopted by the Internet Computer community.

The '''NNS mints Node Provider Rewards every ~2,629,700 seconds''', which is 1/12th of a year. It uses the 30-day moving average price of ICP in Special Drawing Rights (XDR), an international reserve asset created by the International Monetary Fund (IMF). This value is tracked on the [https://dashboard.internetcomputer.org Internet Computer Dashboard] on the "Conversion Rate" chart. (See [[How the 30-Day Moving Average Is Calculated]].) Rewards for the previous month are converted to ICP and transferred to account of the principal registered by the Node Provider in the [[Node Provider Onboarding|Node Onboarding]] process.

These are the current rewards, but reward changes can be proposed to the NNS and adopted by voters at any time.

== Remuneration models ==
The NNS distributes rewards depending on:

* The generation of the node hardware (gen-1/gen-2)
* Geographic location
* The total number of nodes a provider operates 
Different hardware generations lead to varying capital expenditures (CAPEX) and operating expenditures (OPEX), which can also fluctuate based on geographic location. Furthermore, certain locations are deemed more valuable for enhancing network decentralization, resulting in higher rewards for Node Providers in those areas.

Two [[Node Provider Machine Hardware Guide|node machine hardware generations]] are currently recognized: gen-1 and gen-2. Each hardware generation is associated with its own remuneration model. Some cost estimates are provided for the current 2nd generation, but keep in mind that actual hardware and operational expenses may differ.
{| class="wikitable"
|Hardware Type
|Remuneration Model
|-
|Gen-1
|Gen-1 type-0
|-
|Gen-1 + storage upgrade
|Gen-1 type-1
|-
|Gen-2
|V2: Gen-2 remuneration
V2.2: Gen-2 remuneration update
|-
|Gen-3
|V3: Gen-3 remuneration
|}In the future, a remuneration model will be proposed that includes both automated incentives, rewards, and penalties.

== Current Gen-1 Remuneration Model ==

Nodes purchased prior to Genesis were considered Gen-1 nodes. All nodes started out as type-0 with the following calculations:

{| class="wikitable"
|'''TYPE-0'''
|Reward per month (in XDR)
|-
|USA
|873
|-
|US - FL/GA/CA
|1087
|-
|EU
|1087
|-
|Asia
|1212
|}

After the first nodes were up and running, the decision was made to increase the storage capacity of all nodes to support larger subnet states. Thus, a type-1 table was created to reward for the additional costs that the extra storage incurred. Rewards were also broken down further by country. These type-1 values include both the original equipment costs incurred by Gen-1 Node Providers, their operating costs, and the varied costs that Node Providers incurred to purchase the additional storage, ship it to their data centers, and get it installed in each server.

{| class="wikitable"
|'''TYPE-1'''
|Total rewards per node (in XDR)
|-
|US - California
|1600
|-
|US - other
|1499
|-
|Canada
|1624
|-
|Slovenia
|1720
|-
|Switzerland
|1696
|-
|EU - other
|1584
|-
|Singapore
|1842
|-
|Japan
|1773
|}
A [[Proposed Gen-1 Remuneration Model]] is currently under discussion for when the original 48-month agreements are completed.

== Gen-2 Remuneration Model ==

This section presents the remuneration model for 2nd generation Node Providers.

Based on the feedback from Node Providers and the community, discussed in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/128?u=svenf forum post], the Gen2 remuneration model is based on the following principles:
* Higher rewards for the first nodes of a new Node Provider in order to attract more Node Providers in an effort to improve ownership decentralization.
* More refined rewards for nodes in new geographies, like South America, Africa, Asia and Australia, to stimulate further geographical decentralization.

The node reward model is parametrized by:
*'''Geography multiplier (mult)''': This multiplier will be lower, namely 2, for regions with many nodes (e.g. Europe and North America), and higher, namely 3, for regions where there are currently limited nodes present (such as Africa and South America)
*'''Reduction coefficient (r)''': The node reward of the n-th node of a Node Provider is multiplied by r ^ (n-1). The reduction coefficient r is dependent on the geography of the Node Provider. As a result, the first nodes of a Node Provider get attractive rewards, but it is increasingly less attractive to add additional nodes.

The rewards are furthermore dependent on estimated capital and operational expenses that vary based on geographies. A table with the concrete numbers follows below.

In summary, for a geography '''g''', let
* mult('''g''') be the geography multiplier
* cost('''g''') be the total costs over 4 years for acquiring and maintaining a gen 2 node in g in XDR
* r('''np''', '''g''') be the reduction coefficient

The monthly reward for the n-th node of a Node Provider ('''np''') in geography '''g''' are defined as follows:
reward('''g, n''') = cost('''g''') * mult('''g''') * r('''np, g''') ^ (n-1) / (4 * 12)
The total costs over 4 years are multiplied by the geography multiplier, multiplied by the reduction coefficient, and divided by 4 years times 12 months. As a result, rewards for nodes in new geographies and for Node Providers with few nodes are higher. Thereby, a geographical and ownership decentralization is incentivized. The following table shows the geography-dependent values and the monthly reward for the first node onboarded.

{| class="wikitable"
|Geography
|Total cost over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|USA
|31034
|2
|1294
|0.7
|-
|US - FL/GA/CA
|37031
|2
|1542
|0.7
|-
|EU
|36996
|2
|1542
|0.95
|-
|Asia Singapore/Japan
|40508
|2
|1688
|0.7
|-
|Asia non Singapore
|40508
|3
|2532
|0.98
|-
|South Africa
|43986
|3
|2748
|0.98
|}

Note that the reduction coefficient r('''np, g''') is applied per (Node Provider + Country) pair. This means if there is more than one Node Provider in the same country, r('''np, g''') is calculated separately for them. For instance: Node Provider A has 10 nodes in France (EU); reduction coefficient for the 1st node of Node Provider A is 0.95, and for the 10th node is 0.95 ^ 9 = 0.63. If there is Node Provider B with 10 nodes in France (EU) as well, they will get the same rewards as Node Provider A.

As an example, the below table shows the calculation of the rewards of the 1st to the 10th node for a Node Provider in South Africa.
reward('''south africa, n''')
= cost('''south africa''') * mult('''south africa''') * r('''south africa''') ^ ('''n'''-1) / (4 * 12)
= ( 21’455 + 22’531) * 3 * 0.98 ^ ('''n'''-1) / (4 * 12)
= 2748 * 0.98 ^ ('''n'''-1)
{| class="wikitable"
|N-th node
|Multiplier (rounded)
|Monthly remuneration (rounded, in XDR)
|-
|Node 1
|0.98 ^ (1-1) =1
|2748
|-
|Node 2
|0.98 ^ (2-1) =0.98
|2693
|-
|Node 3
|0.98 ^ (3-1) =0.96040
|2639
|-
|Node 4
|0.98 ^ (4-1) =0.941192
|2586
|-
|Node 5
|0.98 ^ (5-1) =0.92236816
|2534
|-
|Node 6
|0.98 ^ (6-1) =0.9039207968
|2483
|-
|Node 7
|0.98 ^ (7-1) =0.885842309
|2434
|-
|Node 8
|0.98 ^ (8-1) = 0.8681255332
|2385
|-
|Node 9
|0.98 ^ (9-1) =0.8507630226
|2337
|-
|Node 10
|0.98 ^ (10-1) =0.8337477621
|2291
|}

[[File:Profit margin for each additional node graph for remuneration V2.png|1000px]]

The above figure shows the additional cash flow (investments minus costs) a Node Provider receives for adding an additional node for three regions (South Africa, Europe and USA) that can be calculated based on the Version 2 remuneration model. Note that the calculation does not take into account the time value of the cash flows (i.e. discounted value), but purely the cash flows or rewards and expenses.

What is visible from this graph is that adding additional nodes only generates additional cash flow for a specific number of nodes, in a specific region. For example, in Europe adding up to approximately 15 nodes will generate additional cash flow, whereas for the US region, this is only 2 nodes.

Potential new Node Providers can make a full calculation themselves of the Internal Rate of Return, Payback period and cash flow based on their actual CAPEX and OPEX costs. Of course, these actual CAPEX and OPEX costs may differ from the costs on which the remuneration is based, depending on the specific contracts the new Node Provider has been able to negotiate with hardware vendors and DC operators.

=== Version 2.1 Remuneration Model ===
The Version 2.1 remuneration model replaces the Version 2 remuneration for 2nd generation Node Providers. It includes the following changes compared to Version 2, based on discussion in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/192 forum thread]:

* No entry for the region Asia will be used anymore. For the Asia region, specific country entries will be used.
* Specific entries for Hong Kong and India will be added to the remuneration table.
* The multiplier is set to a value of 2 for all countries. In future, this might be updated through a new NNS proposal if the community determines that the risk premium for projects should be different for different countries (for example, if the risk of running in node in one specific country is higher than the risk of running in node in another country, this might validate a different multiplier).
* A limit is set to the number of nodes in new countries for which the remuneration applies. Once this is reached, the reduction coefficient for additional nodes will be adjusted to allow adding only one or two nodes for this country, similar to existing countries like the U.S. and Switzerland. Currently, the limit of number of nodes per country is set to 50 nodes, which allows NP’s to add a node in that specific country to every available subnet and have a small set of additional nodes in case nodes are unhealthy or require maintenance.
* Version 2 was relevant for a limited time period in 2023. Version 2.1 became the current model as of May 2023.

The following table shows the geography-dependent values and the monthly reward for the first node onboarded based on the Remuneration Version 2.1.

With this latest update, there are sufficient node machines for running the current load of canisters on every subnet, and for the decentralisation of the subnets measured in Nakamoto coefficients; no new country entries will be added. Work is in progress on an IC Topology Roadmap for the next half year and the next year, with the objective to assess how many node machines and where new node machines are required for further growth and decentralisation of the IC network. Based on that it will be discussed on the IC forum what changes to make to the Node Provider remuneration table and subsequent proposals will be submitted to the NNS for the community to vote upon.

{| class="wikitable"
|Geography
|Total costs over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|US
|31034
|2
|1294
|0.7
|-
|US California
|37031
|2
|1543
|0.7
|-
|Canada
|37031
|2
|1543
|0.7
|-
|Germany
|36996
|2
|1542
|0.7
|-
|Switzerland
|36996
|2
|1542
|0.7
|-
|France
|36996
|2
|1542
|0.7
|-
|Belgium
|36996
|2
|1542
|0.7
|-
|Slovenia
|36996
|2
|1542
|0.7
|-
|Europe (other than above)
|36996
|2
|1542
|0.95
|-
|Proposed Israel
|49500
|2
|2063
|0.95
|-
|Japan
|40508
|2
|1688
|0.7
|-
|Singapore
|40508
|2
|1688
|0.7
|-
|Hong Kong
|46141
|2
|1922
|0.95
|-
|India
|50377
|2
|2100
|0.95
|-
|South Korea
|51774
|2
|2158
|0.95
|-
|Sri Lanka
|52800
|2
|2200
|0.95
|-
|Georgia
|57455
|2
|2394
|0.95
|-
|South Africa
|55455
|2
|2310
|0.95
|-
|Australia
|47000
|2
|1958
|0.95
|-
|Proposed New Zealand
|47000
|2
|1958
|0.95
|-
|Proposed Panama
|51774
|2
|2158
|0.95
|-
|Proposed Costa Rica
|51774
|2
|2158
|0.95
|-
|Proposed Colombia
|57455
|2
|2394
|0.95
|}

== Reward calculator ==
For your convenience, we prepared the following [https://www.calconic.com/calculator-widgets/ic-node-provider-rewards/659d42a6d96fa70029e56629?layouts=true calculator for the node rewards]

== Trustworthy Node Metrics ==
In February 2024, Trustworthy Node Metrics were introduced on the IC, in an attempt to provide greater visibility into node performance, stability, and reliability. These metrics could potentially be used to influence node rewards in the future.

There is a forum post here https://forum.dfinity.org/t/trustworthy-node-metrics-for-useful-work/22989, then

Blog post on Medium here: https://medium.com/dfinity/dont-trust-verify-new-node-metrics-on-the-internet-computer-367cc154a572

And technical documentation and instructions here: https://dfinity.github.io/dre/trustworthy-metrics/trustworthy-metrics.html

Node Provider Remuneration

2024-01-09T13:57:35Z

Sat: Add a link to the calculator for node rewards

== Rewards ==

Node Providers receive rewards (remuneration) for owning node machines that run in the Internet Computer network. Node Provider rewards are set by the NNS DAO, with changes only possible through NNS proposals adopted by the Internet Computer community.

The '''NNS mints Node Provider Rewards every ~2,629,700 seconds''', which is 1/12th of a year. It uses the 30-day moving average price of ICP in Special Drawing Rights (XDR), an international reserve asset created by the International Monetary Fund (IMF). This value is tracked on the [https://dashboard.internetcomputer.org Internet Computer Dashboard] on the "Conversion Rate" chart. Rewards for the previous month are converted to ICP and transferred to account of the principal registered by the Node Provider in the [[Node Provider Onboarding|Node Onboarding]] process.

These are the current rewards, but reward changes can be proposed to the NNS and adopted by voters at any time.

== Remuneration models ==
The NNS distributes rewards depending on:

* The generation of the node hardware (gen-1/gen-2)
* Geographic location
* The total number of nodes a provider operates 
Different hardware generations lead to varying capital expenditures (CAPEX) and operating expenditures (OPEX), which can also fluctuate based on geographic location. Furthermore, certain locations are deemed more valuable for enhancing network decentralization, resulting in higher rewards for Node Providers in those areas.

Two [[Node Provider Machine Hardware Guide|node machine hardware generations]] are currently recognized: gen-1 and gen-2. Each hardware generation is associated with its own remuneration model. Some cost estimates are provided for the current 2nd generation, but keep in mind that actual hardware and operational expenses may differ.
{| class="wikitable"
|Hardware Type
|Remuneration Model
|-
|Gen-1
|Gen-1 type-0
|-
|Gen-1 + storage upgrade
|Gen-1 type-1
|-
|Gen-2
|V2: Gen-2 remuneration
V2.2: Gen-2 remuneration update
|-
|Gen-3
|V3: Gen-3 remuneration
|}In the future, a remuneration model will be proposed that includes both automated incentives, rewards, and penalties.

== Current Gen-1 Remuneration Model ==

Nodes purchased prior to Genesis were considered Gen-1 nodes. All nodes started out as type-0 with the following calculations:

{| class="wikitable"
|'''TYPE-0'''
|Reward per month (in XDR)
|-
|USA
|873
|-
|US - FL/GA/CA
|1087
|-
|EU
|1087
|-
|Asia
|1212
|}

After the first nodes were up and running, the decision was made to increase the storage capacity of all nodes to support larger subnet states. Thus, a type-1 table was created to reward for the additional costs that the extra storage incurred. Rewards were also broken down further by country. These type-1 values include both the original equipment costs incurred by Gen-1 Node Providers, their operating costs, and the varied costs that Node Providers incurred to purchase the additional storage, ship it to their data centers, and get it installed in each server.

{| class="wikitable"
|'''TYPE-1'''
|Total rewards per node (in XDR)
|-
|US - California
|1600
|-
|US - other
|1499
|-
|Canada
|1624
|-
|Slovenia
|1720
|-
|Switzerland
|1696
|-
|EU - other
|1584
|-
|Singapore
|1842
|-
|Japan
|1773
|}
A [[Proposed Gen-1 Remuneration Model]] is currently under discussion for when the original 48-month agreements are completed.

== Gen-2 Remuneration Model ==

This section presents the remuneration model for 2nd generation Node Providers.

Based on the feedback from Node Providers and the community, discussed in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/128?u=svenf forum post], the Gen2 remuneration model is based on the following principles:
* Higher rewards for the first nodes of a new Node Provider in order to attract more Node Providers in an effort to improve ownership decentralization.
* More refined rewards for nodes in new geographies, like South America, Africa, Asia and Australia, to stimulate further geographical decentralization.

The node reward model is parametrized by:
*'''Geography multiplier (mult)''': This multiplier will be lower, namely 2, for regions with many nodes (e.g. Europe and North America), and higher, namely 3, for regions where there are currently limited nodes present (such as Africa and South America)
*'''Reduction coefficient (r)''': The node reward of the n-th node of a Node Provider is multiplied by r ^ (n-1). The reduction coefficient r is dependent on the geography of the Node Provider. As a result, the first nodes of a Node Provider get attractive rewards, but it is increasingly less attractive to add additional nodes.

The rewards are furthermore dependent on estimated capital and operational expenses that vary based on geographies. A table with the concrete numbers follows below.

In summary, for a geography '''g''', let
* mult('''g''') be the geography multiplier
* cost('''g''') be the total costs over 4 years for acquiring and maintaining a gen 2 node in g in XDR
* r('''np''', '''g''') be the reduction coefficient

The monthly reward for the n-th node of a Node Provider ('''np''') in geography '''g''' are defined as follows:
reward('''g, n''') = cost('''g''') * mult('''g''') * r('''np, g''') ^ (n-1) / (4 * 12)
The total costs over 4 years are multiplied by the geography multiplier, multiplied by the reduction coefficient, and divided by 4 years times 12 months. As a result, rewards for nodes in new geographies and for Node Providers with few nodes are higher. Thereby, a geographical and ownership decentralization is incentivized. The following table shows the geography-dependent values and the monthly reward for the first node onboarded.

{| class="wikitable"
|Geography
|Total cost over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|USA
|31034
|2
|1294
|0.7
|-
|US - FL/GA/CA
|37031
|2
|1542
|0.7
|-
|EU
|36996
|2
|1542
|0.95
|-
|Asia Singapore/Japan
|40508
|2
|1688
|0.7
|-
|Asia non Singapore
|40508
|3
|2532
|0.98
|-
|South Africa
|43986
|3
|2748
|0.98
|}

Note that the reduction coefficient r('''np, g''') is applied per (Node Provider + Country) pair. This means if there is more than one Node Provider in the same country, r('''np, g''') is calculated separately for them. For instance: Node Provider A has 10 nodes in France (EU); reduction coefficient for the 1st node of Node Provider A is 0.95, and for the 10th node is 0.95 ^ 9 = 0.63. If there is Node Provider B with 10 nodes in France (EU) as well, they will get the same rewards as Node Provider A.

As an example, the below table shows the calculation of the rewards of the 1st to the 10th node for a Node Provider in South Africa.
reward('''south africa, n''')
= cost('''south africa''') * mult('''south africa''') * r('''south africa''') ^ ('''n'''-1) / (4 * 12)
= ( 21’455 + 22’531) * 3 * 0.98 ^ ('''n'''-1) / (4 * 12)
= 2748 * 0.98 ^ ('''n'''-1)
{| class="wikitable"
|N-th node
|Multiplier (rounded)
|Monthly remuneration (rounded, in XDR)
|-
|Node 1
|0.98 ^ (1-1) =1
|2748
|-
|Node 2
|0.98 ^ (2-1) =0.98
|2693
|-
|Node 3
|0.98 ^ (3-1) =0.96040
|2639
|-
|Node 4
|0.98 ^ (4-1) =0.941192
|2586
|-
|Node 5
|0.98 ^ (5-1) =0.92236816
|2534
|-
|Node 6
|0.98 ^ (6-1) =0.9039207968
|2483
|-
|Node 7
|0.98 ^ (7-1) =0.885842309
|2434
|-
|Node 8
|0.98 ^ (8-1) = 0.8681255332
|2385
|-
|Node 9
|0.98 ^ (9-1) =0.8507630226
|2337
|-
|Node 10
|0.98 ^ (10-1) =0.8337477621
|2291
|}

[[File:Profit margin for each additional node graph for remuneration V2.png|1000px]]

The above figure shows the additional cash flow (investments minus costs) a Node Provider receives for adding an additional node for three regions (South Africa, Europe and USA) that can be calculated based on the Version 2 remuneration model. Note that the calculation does not take into account the time value of the cash flows (i.e. discounted value), but purely the cash flows or rewards and expenses.

What is visible from this graph is that adding additional nodes only generates additional cash flow for a specific number of nodes, in a specific region. For example, in Europe adding up to approximately 15 nodes will generate additional cash flow, whereas for the US region, this is only 2 nodes.

Potential new Node Providers can make a full calculation themselves of the Internal Rate of Return, Payback period and cash flow based on their actual CAPEX and OPEX costs. Of course, these actual CAPEX and OPEX costs may differ from the costs on which the remuneration is based, depending on the specific contracts the new Node Provider has been able to negotiate with hardware vendors and DC operators.

=== Version 2.1 Remuneration Model ===
The Version 2.1 remuneration model replaces the Version 2 remuneration for 2nd generation Node Providers. It includes the following changes compared to Version 2, based on discussion in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/192 forum thread]:

* No entry for the region Asia will be used anymore. For the Asia region, specific country entries will be used.
* Specific entries for Hong Kong and India will be added to the remuneration table.
* The multiplier is set to a value of 2 for all countries. In future, this might be updated through a new NNS proposal if the community determines that the risk premium for projects should be different for different countries (for example, if the risk of running in node in one specific country is higher than the risk of running in node in another country, this might validate a different multiplier).
* A limit is set to the number of nodes in new countries for which the remuneration applies. Once this is reached, the reduction coefficient for additional nodes will be adjusted to allow adding only one or two nodes for this country, similar to existing countries like the U.S. and Switzerland. Currently, the limit of number of nodes per country is set to 50 nodes, which allows NP’s to add a node in that specific country to every available subnet and have a small set of additional nodes in case nodes are unhealthy or require maintenance.
* Version 2 was relevant for a limited time period in 2023. Version 2.1 became the current model as of May 2023.

The following table shows the geography-dependent values and the monthly reward for the first node onboarded based on the Remuneration Version 2.1.

With this latest update, there are sufficient node machines for running the current load of canisters on every subnet, and for the decentralisation of the subnets measured in Nakamoto coefficients; no new country entries will be added. Work is in progress on an IC Topology Roadmap for the next half year and the next year, with the objective to assess how many node machines and where new node machines are required for further growth and decentralisation of the IC network. Based on that it will be discussed on the IC forum what changes to make to the Node Provider remuneration table and subsequent proposals will be submitted to the NNS for the community to vote upon.

{| class="wikitable"
|Geography
|Total costs over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|US
|31034
|2
|1294
|0.7
|-
|US California
|37031
|2
|1543
|0.7
|-
|Canada
|37031
|2
|1543
|0.7
|-
|Germany
|36996
|2
|1542
|0.7
|-
|Switzerland
|36996
|2
|1542
|0.7
|-
|France
|36996
|2
|1542
|0.7
|-
|Belgium
|36996
|2
|1542
|0.7
|-
|Slovenia
|36996
|2
|1542
|0.7
|-
|Europe (other than above)
|36996
|2
|1542
|0.95
|-
|Japan
|40508
|2
|1688
|0.7
|-
|Singapore
|40508
|2
|1688
|0.7
|-
|Asia HK
|46141
|2
|1922
|0.95
|-
|Asia India
|50377
|2
|2100
|0.95
|-
|Asia South Korea
|51774
|2
|2158
|0.95
|-
|Asia Sri Lanka
|52800
|2
|2200
|0.95
|-
|Asia Georgia
|57455
|2
|2394
|0.95
|-
|South Africa
|55455
|2
|2310
|0.95
|-
|Australia
|47000
|2
|1958
|0.95
|}

== Reward calculator ==
For your convenience, we prepared the following [https://www.calconic.com/calculator-widgets/ic-node-provider-rewards/659d42a6d96fa70029e56629?layouts=true calculator for the node rewards]

Node Provider Remuneration

2024-01-09T12:22:58Z

Sat: Clarification for XDR

== Rewards ==

Node Providers receive rewards (remuneration) for owning node machines that run in the Internet Computer network. Node Provider rewards are set by the NNS DAO, with changes only possible through NNS proposals adopted by the Internet Computer community.

The '''NNS mints Node Provider Rewards every ~2,629,700 seconds''', which is 1/12th of a year. It uses the 30-day moving average price of ICP in Special Drawing Rights (XDR), an international reserve asset created by the International Monetary Fund (IMF). This value is tracked on the [https://dashboard.internetcomputer.org Internet Computer Dashboard] on the "Conversion Rate" chart. Rewards for the previous month are converted to ICP and transferred to account of the principal registered by the Node Provider in the [[Node Provider Onboarding|Node Onboarding]] process.

These are the current rewards, but reward changes can be proposed to the NNS and adopted by voters at any time.

== Remuneration models ==
The NNS distributes rewards depending on:

* The generation of the node hardware (gen-1/gen-2)
* Geographic location
* The total number of nodes a provider operates 
Different hardware generations lead to varying capital expenditures (CAPEX) and operating expenditures (OPEX), which can also fluctuate based on geographic location. Furthermore, certain locations are deemed more valuable for enhancing network decentralization, resulting in higher rewards for Node Providers in those areas.

Two [[Node Provider Machine Hardware Guide|node machine hardware generations]] are currently recognized: gen-1 and gen-2. Each hardware generation is associated with its own remuneration model. Some cost estimates are provided for the current 2nd generation, but keep in mind that actual hardware and operational expenses may differ.
{| class="wikitable"
|Hardware Type
|Remuneration Model
|-
|Gen-1
|Gen-1 type-0
|-
|Gen-1 + storage upgrade
|Gen-1 type-1
|-
|Gen-2
|V2: Gen-2 remuneration
V2.2: Gen-2 remuneration update
|-
|Gen-3
|V3: Gen-3 remuneration
|}In the future, a remuneration model will be proposed that includes both automated incentives, rewards, and penalties.

== Current Gen-1 Remuneration Model ==

Nodes purchased prior to Genesis were considered Gen-1 nodes. All nodes started out as type-0 with the following calculations:

{| class="wikitable"
|'''TYPE-0'''
|Reward per month (in XDR)
|-
|USA
|873
|-
|US - FL/GA/CA
|1087
|-
|EU
|1087
|-
|Asia
|1212
|}

After the first nodes were up and running, the decision was made to increase the storage capacity of all nodes to support larger subnet states. Thus, a type-1 table was created to reward for the additional costs that the extra storage incurred. Rewards were also broken down further by country. These type-1 values include both the original equipment costs incurred by Gen-1 Node Providers, their operating costs, and the varied costs that Node Providers incurred to purchase the additional storage, ship it to their data centers, and get it installed in each server.

{| class="wikitable"
|'''TYPE-1'''
|Total rewards per node (in XDR)
|-
|US - California
|1600
|-
|US - other
|1499
|-
|Canada
|1624
|-
|Slovenia
|1720
|-
|Switzerland
|1696
|-
|EU - other
|1584
|-
|Singapore
|1842
|-
|Japan
|1773
|}
A [[Proposed Gen-1 Remuneration Model]] is currently under discussion for when the original 48-month agreements are completed.

== Gen-2 Remuneration Model ==

This section presents the remuneration model for 2nd generation Node Providers.

Based on the feedback from Node Providers and the community, discussed in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/128?u=svenf forum post], the Gen2 remuneration model is based on the following principles:
* Higher rewards for the first nodes of a new Node Provider in order to attract more Node Providers in an effort to improve ownership decentralization.
* More refined rewards for nodes in new geographies, like South America, Africa, Asia and Australia, to stimulate further geographical decentralization.

The node reward model is parametrized by:
*'''Geography multiplier (mult)''': This multiplier will be lower, namely 2, for regions with many nodes (e.g. Europe and North America), and higher, namely 3, for regions where there are currently limited nodes present (such as Africa and South America)
*'''Reduction coefficient (r)''': The node reward of the n-th node of a Node Provider is multiplied by r ^ (n-1). The reduction coefficient r is dependent on the geography of the Node Provider. As a result, the first nodes of a Node Provider get attractive rewards, but it is increasingly less attractive to add additional nodes.

The rewards are furthermore dependent on estimated capital and operational expenses that vary based on geographies. A table with the concrete numbers follows below.

In summary, for a geography '''g''', let
* mult('''g''') be the geography multiplier
* cost('''g''') be the total costs over 4 years for acquiring and maintaining a gen 2 node in g in XDR
* r('''np''', '''g''') be the reduction coefficient

The monthly reward for the n-th node of a Node Provider ('''np''') in geography '''g''' are defined as follows:
reward('''g, n''') = cost('''g''') * mult('''g''') * r('''np, g''') ^ (n-1) / (4 * 12)
The total costs over 4 years are multiplied by the geography multiplier, multiplied by the reduction coefficient, and divided by 4 years times 12 months. As a result, rewards for nodes in new geographies and for Node Providers with few nodes are higher. Thereby, a geographical and ownership decentralization is incentivized. The following table shows the geography-dependent values and the monthly reward for the first node onboarded.

{| class="wikitable"
|Geography
|Total cost over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|USA
|31034
|2
|1294
|0.7
|-
|US - FL/GA/CA
|37031
|2
|1542
|0.7
|-
|EU
|36996
|2
|1542
|0.95
|-
|Asia Singapore/Japan
|40508
|2
|1688
|0.7
|-
|Asia non Singapore
|40508
|3
|2532
|0.98
|-
|South Africa
|43986
|3
|2748
|0.98
|}

Note that the reduction coefficient r('''np, g''') is applied per (Node Provider + Country) pair. This means if there is more than one Node Provider in the same country, r('''np, g''') is calculated separately for them. For instance: Node Provider A has 10 nodes in France (EU); reduction coefficient for the 1st node of Node Provider A is 0.95, and for the 10th node is 0.95 ^ 9 = 0.63. If there is Node Provider B with 10 nodes in France (EU) as well, they will get the same rewards as Node Provider A.

As an example, the below table shows the calculation of the rewards of the 1st to the 10th node for a Node Provider in South Africa.
reward('''south africa, n''')
= cost('''south africa''') * mult('''south africa''') * r('''south africa''') ^ ('''n'''-1) / (4 * 12)
= ( 21’455 + 22’531) * 3 * 0.98 ^ ('''n'''-1) / (4 * 12)
= 2748 * 0.98 ^ ('''n'''-1)
{| class="wikitable"
|N-th node
|Multiplier (rounded)
|Monthly remuneration (rounded, in XDR)
|-
|Node 1
|0.98 ^ (1-1) =1
|2748
|-
|Node 2
|0.98 ^ (2-1) =0.98
|2693
|-
|Node 3
|0.98 ^ (3-1) =0.96040
|2639
|-
|Node 4
|0.98 ^ (4-1) =0.941192
|2586
|-
|Node 5
|0.98 ^ (5-1) =0.92236816
|2534
|-
|Node 6
|0.98 ^ (6-1) =0.9039207968
|2483
|-
|Node 7
|0.98 ^ (7-1) =0.885842309
|2434
|-
|Node 8
|0.98 ^ (8-1) = 0.8681255332
|2385
|-
|Node 9
|0.98 ^ (9-1) =0.8507630226
|2337
|-
|Node 10
|0.98 ^ (10-1) =0.8337477621
|2291
|}

[[File:Profit margin for each additional node graph for remuneration V2.png|1000px]]

The above figure shows the additional cash flow (investments minus costs) a Node Provider receives for adding an additional node for three regions (South Africa, Europe and USA) that can be calculated based on the Version 2 remuneration model. Note that the calculation does not take into account the time value of the cash flows (i.e. discounted value), but purely the cash flows or rewards and expenses.

What is visible from this graph is that adding additional nodes only generates additional cash flow for a specific number of nodes, in a specific region. For example, in Europe adding up to approximately 15 nodes will generate additional cash flow, whereas for the US region, this is only 2 nodes.

Potential new Node Providers can make a full calculation themselves of the Internal Rate of Return, Payback period and cash flow based on their actual CAPEX and OPEX costs. Of course, these actual CAPEX and OPEX costs may differ from the costs on which the remuneration is based, depending on the specific contracts the new Node Provider has been able to negotiate with hardware vendors and DC operators.

=== Version 2.1 Remuneration Model ===
The Version 2.1 remuneration model replaces the Version 2 remuneration for 2nd generation Node Providers. It includes the following changes compared to Version 2, based on discussion in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/192 forum thread]:

* No entry for the region Asia will be used anymore. For the Asia region, specific country entries will be used.
* Specific entries for Hong Kong and India will be added to the remuneration table.
* The multiplier is set to a value of 2 for all countries. In future, this might be updated through a new NNS proposal if the community determines that the risk premium for projects should be different for different countries (for example, if the risk of running in node in one specific country is higher than the risk of running in node in another country, this might validate a different multiplier).
* A limit is set to the number of nodes in new countries for which the remuneration applies. Once this is reached, the reduction coefficient for additional nodes will be adjusted to allow adding only one or two nodes for this country, similar to existing countries like the U.S. and Switzerland. Currently, the limit of number of nodes per country is set to 50 nodes, which allows NP’s to add a node in that specific country to every available subnet and have a small set of additional nodes in case nodes are unhealthy or require maintenance.
* Version 2 was relevant for a limited time period in 2023. Version 2.1 became the current model as of May 2023.

The following table shows the geography-dependent values and the monthly reward for the first node onboarded based on the Remuneration Version 2.1.

With this latest update, there are sufficient node machines for running the current load of canisters on every subnet, and for the decentralisation of the subnets measured in Nakamoto coefficients; no new country entries will be added. Work is in progress on an IC Topology Roadmap for the next half year and the next year, with the objective to assess how many node machines and where new node machines are required for further growth and decentralisation of the IC network. Based on that it will be discussed on the IC forum what changes to make to the Node Provider remuneration table and subsequent proposals will be submitted to the NNS for the community to vote upon.

{| class="wikitable"
|Geography
|Total costs over 4 years
|Multiplier
|Monthly reward for 1st node (in XDR)
|Reduction coefficient r
|-
|US
|31034
|2
|1294
|0.7
|-
|US California
|37031
|2
|1543
|0.7
|-
|Canada
|37031
|2
|1543
|0.7
|-
|Germany
|36996
|2
|1542
|0.7
|-
|Switzerland
|36996
|2
|1542
|0.7
|-
|France
|36996
|2
|1542
|0.7
|-
|Belgium
|36996
|2
|1542
|0.7
|-
|Slovenia
|36996
|2
|1542
|0.7
|-
|Europe (other than above)
|36996
|2
|1542
|0.95
|-
|Japan
|40508
|2
|1688
|0.7
|-
|Singapore
|40508
|2
|1688
|0.7
|-
|Asia HK
|46141
|2
|1922
|0.95
|-
|Asia India
|50377
|2
|2100
|0.95
|-
|Asia South Korea
|51774
|2
|2158
|0.95
|-
|Asia Sri Lanka
|52800
|2
|2200
|0.95
|-
|Asia Georgia
|57455
|2
|2394
|0.95
|-
|South Africa
|55455
|2
|2310
|0.95
|-
|Australia
|47000
|2
|1958
|0.95
|}

Troubleshooting Unhealthy Nodes

2024-01-03T09:08:24Z

Sat: /* Frequently Asked Questions */

=== '''Use [https://dashboard.internetcomputer.org/centers the dashboard] to verify that the node is healthy''' ===
*The node count for your data center should match the number of nodes in that data center.
* Look for the principal ID for the node which you are servicing. Status explanations are [https://wiki.internetcomputer.org/wiki/Node_Provider_Troubleshooting#Node_Status_on_the_Dashboard here].
* If the node isn't listed at all, then it needs to be [[IC-OS Installation Runbook|redeployed the node with a fresh IC-OS image]].

=== '''Degraded nodes statuses''' ===

==== IC_OrchestratorFlapping ====
'''Explanation:''' Orchestrator coordinates the execution of many IC GuestOS processes, including the IC Replica. If the orchestrator is repeatedly restarting, then the GuestOS and the Replica process likely do not operate as expected.

'''Possible causes:'''

* Networking issues
* Hardware issues
* Software problems

'''Troubleshooting and remediation:'''

* Check if any NNS proposals were recently executed for the nodes in question https://dashboard.internetcomputer.org/governance
* Check if there are some bandwidth limitations on these nodes, and ensure any traffic shaping, QoS, DOS protection, etc, are ''disabled'' on the ISP side
* Perform other [https://wiki.internetcomputer.org/w/index.php?title=Unhealthy_Nodes&veaction=edit#Setting_Up_an_Auxiliary_Machine_for_Network_Diagnostics network diagnostics checks]
* Inspect node logs and metrics, if possible
* Consult other node providers and DFINITY if there are any known software problems with the latest revision that the node(s) are running

==== IC_Replica_Behind ====
'''Explanation:''' IC Replica is the main process, that runs canisters (smart contracts). If the Replica process cannot catch up, then the replica (node) cannot be a productive member of the IC subnet.

'''Possible causes:'''

* Networking issues
* Hardware issues
* Software problems

'''Troubleshooting and remediation:'''

* Check if there are any hardware issues reported by the machine's BMC (Baseboard Management Controller)
* Perform [https://wiki.internetcomputer.org/wiki/Updating_Firmware firmware upgrade]
* Check if any NNS proposals were recently executed for the nodes in question https://dashboard.internetcomputer.org/governance
* Check if there are some bandwidth limitations on these nodes, and ensure any traffic shaping, QoS, DOS protection, etc, are ''disabled'' on the ISP side
* Perform other [https://wiki.internetcomputer.org/w/index.php?title=Unhealthy_Nodes&veaction=edit#Setting_Up_an_Auxiliary_Machine_for_Network_Diagnostics network diagnostics checks]
* Inspect node logs and metrics, if possible
* Consult other node providers and DFINITY if there are any known software problems with the latest revision that the node(s) are running

=== '''"Orchestrator Started" message''' ===
This message is not an error, nor is it confirmation that the node is running properly. This must be determined in other ways:

*'''Check [https://dashboard.internetcomputer.org/ the dashboard]''' to check the status of the node. (Status explanations are [https://wiki.internetcomputer.org/wiki/Node_Provider_Troubleshooting#Node_Status_on_the_Dashboard here].) Use the principal ID that was assigned to the node when it was onboarded to identify it.
*If the node is not visible on the dashboard, then it has not registered with the Internet Computer.
**If you have recently installed a current IC-OS image, then you can try inserting the HSM and/or a reboot to see if it joins. This would work if a recent IC-OS installation was successful and only the registration and joining was interrupted.
**If you have ''not'' recently installed a current IC-OS image, then do ''not'' insert the HSM. You do not want the node to rejoin with an old IC-OS image, as it will only fail again. Instead, you should consider [[Updating Firmware|upgrading the firmware]] if it is running on old versions, and then redeploy the node with [[IC-OS Installation Runbook|a fresh/current IC-OS image]] (which will assign a new principal to the node so that you can identify it in the dashboard.)

=== '''Offline nodes''' ===
Network issues are the main reason why nodes are in an "OFFLINE" state.

* Your node may not be reachable from the IC or
* you may not be able to reach other nodes the IC from your node or
* you may note be able to reach the monitoring servers from your node.

Please refer to the '''Networking Troubleshooting Steps''' below.

Another possible reason for an OFFLINE node may be that your GuestOS failed to start due to a RAM failure.

=== '''Server Troubleshooting Steps''' ===
These steps may help when a server is unhealthy or has been removed from the network, but the connectivity in the data center is functioning correctly:

#Verify if the server is up and running:
#*Check the power status of the server.
#*Check if the server is displaying any error messages or indicators.
#*If possible, access the server remotely or physically to ensure it is functioning properly.
#Hook up a crash cart and check for errors on the screen, troubleshoot as needed.
#Consider [[Updating Firmware|updating the firmware]] if it has been a long time, and/or if you have recently had other nodes that needed firmware upgrades to become healthy again.
# If no known error is found, please [[IC-OS Installation Runbook|redeploy the node with a fresh IC-OS image]].
#* The deployment process identifies/fixes many software issues.
#* Note that if an old IC-OS image is used, the node will "appear" to be healthy at first, but it will not be able to catch up to the blockchain and will therefore fall behind and become unhealthy again. '''Thus, a current IC-OS image must be used.'''
#* At the end, obtain the new principal ID for the node from the crash cart screen so you can check the dashboard status.
#*'''If a node is healthy ("Awaiting Subnet" status) for a while and then changes to "Offline," then whatever the issue was originally still exists.''' Troubleshoot hardware, upgrade firmware, etc to resolve the issue.

=== '''Networking Troubleshooting Steps''' ===

# Inspect network hardware in the rack for any visible signs of malfunction (e.g. red lights) or incorrect setup
# Verify the cabling and port status on the switch:
#*Check the physical connection of the network cable between the server and the switch.
#*Ensure that the cable is securely plugged into the correct port on both ends.
#*Look for any signs of damage or loose connections.
#*Test the connectivity by trying a different network cable or using the same cable on a different port.
#Check for recent port flaps/link failures or any other activities which might cause it:
#*Check the logs or monitoring systems for any indications of port flapping or link failures.
#*Investigate any recent changes or activities that could have affected the network connection.
#*Consider any software updates, configuration changes, or physical alterations made recently.
#Try to perform a re-seat of cable/breakout/SFP/QSFP toward the affected machine:
#*Disconnect and reconnect the network cable at both ends (server and switch).
#*If applicable, re-seat any breakout cables, SFP modules, or QSFP modules used in the connection.
#*Ensure a secure and proper connection is established.
#Check with the switch vendor:
#*If the issue persists, contact the switch vendor's support team for further assistance.
#*Provide them with detailed information about the problem and any troubleshooting steps you have already taken.
#*Follow vendor guidance to troubleshoot and resolve the issue.
#**If your vendor requires a TSR log, see [[IDRAC access and TSR logs]] for an example of how to retrieve one from a Dell server.
#**[[Updating_Firmware|Updating the firmware]] might also resolve the issue.
# Utilize an auxiliary machine within the same rack with full network access to run diagnostics tools like <code>ping</code>, <code>traceroute</code>, and <code>nmap</code>
# Work with the ISP to troubleshoot and resolve any network routing issues identified during diagnostics
# Prepare for future incidents by establishing network redundancy and failover mechanisms

=== '''Best practices''' ===

# Keep a separate machine in the same rack with appropriate tools for network diagnostics and troubleshooting
# Engage with the node provider community for support and to share effective troubleshooting techniques

=== '''Setting Up an Auxiliary Machine for Network Diagnostics''' ===
Robust Internet connectivity is essential. Without access to internal node logs and metrics, troubleshooting requires alternative strategies, including the use of an auxiliary machine within the same rack. Here's a brief outline for setting up an auxiliary machine in the same rack, while following best security practices:
# Hardware Setup:
#* Choose a server with sufficient resources to run diagnostic tools without impacting its performance. There is no need to follow the gen1/gen2 hardware requirements for this server (since this node would not be joining the IC network) but make sure the server is performant enough to run network tests.
#* Ensure physical security measures are in place to prevent unauthorized access.
# Operating System and Software:
#* Install a secure operating system, like a minimal installation of Linux (we prefer Ubuntu 22.04), which reduces the attack surface.
#* Keep the system updated with the latest security patches and firmware updates.
# Network Configuration:
#* Configure the machine with an IPv6 address in the same range as the IC nodes, for accurate testing.
#* Set up a restrictive firewall on the machine to allow ''only the necessary'' inbound and outbound traffic. Consider allowing Internet access for this machine only during troubleshooting sessions, and keeping the machine behind a VPN at other times.
# Diagnostic Tools:
#* Install network diagnostic tools such as <code>ping</code>, <code>traceroute</code>, <code>nmap</code>, <code>tcpdump</code>, and <code>iperf</code>.
#* Configure monitoring tools to simulate node activities and track responsiveness.
# Security Measures:
#* Use strong, unique passwords for all accounts and change them regularly. Or, preferably, do not use passwords at all, and use key-based access instead.
#* Implement key-based SSH authentication and disable root login over SSH.
#* Regularly review logs for any unusual activities that might indicate a security breach.
# Maintenance and Updates:
#* Regularly update all software to the latest versions.
#* Periodically test your network diagnostic tools to ensure they are functioning as expected.

=== '''Frequently Asked Questions''' ===
'''Q: Is the monitoring system open-sourced? How does it communicate with the nodes?'''

A: The monitoring system configuration is not currently open-sourced. However, the node configuration that is required for proper node operation is fully open source. For more information about the node-to-node and node-to-monitoring communication, refer to the [https://sourcegraph.com/github.com/dfinity/ic/-/blob/ic-os/hostos/rootfs/etc/nftables.conf?L54-112 nftables configuration], which is the definitive guide for required open ports on Host OS, and [https://sourcegraph.com/github.com/dfinity/ic/-/blob/ic-os/guestos/rootfs/opt/ic/share/ic.json5.template?L322 similar nftables configuration] for the Guest OS. You can find the configuration for DFINITY-owned DCs and Gen1 node providers here: nftables configuration. We use [https://docs.victoriametrics.com/ Victoria Metrics] for metrics scraping (documentation) and [https://vector.dev vector.dev] for log scraping.

'''Q: What are the destination IPs and Ports for Frankfurt, Chicago, and San Francisco for connectivity troubleshooting?'''

A: At present, detailed node/port information is not publicly accessible, as disclosing this information is considered a security risk. To effectively troubleshoot connectivity issues with your nodes, we recommend setting up a "spot instance" or a temporary virtual machine (VM) with a cloud provider in each of the geographical regions. This approach allows you to test both connectivity and connection stability to your nodes, providing a practical solution for identifying and resolving network-related issues.

'''Q: The dashboard shows offline or degraded status for <DC>, but everything seems fine. What should we do?'''

A: Check if any of these issues are present: firewall restrictions, traffic shaping, DOS protection, or QOS features enabled on the ISP side. These should all be disabled for optimal node operation.

'''Q: Under what circumstances is a node removed from the IC network?'''

A: A node is removed from the IC network when it's deemed unhealthy. The determination of a node's health is made using tooling from https://github.com/dfinity/dre. This tooling assesses nodes based on various metrics and submits a proposal for their removal to maintain the highest level of decentralization possible. However, there are exceptions. For example, an unhealthy node might be temporarily retained if there are ongoing efforts to recover and restore it.

'''Q: How long can a node be down before it's excluded from the IC network?'''

A: There's no set time limit for how long a node can be down before exclusion. The decision is more qualitative and depends on the overall health of the network. Currently, the IC network can tolerate up to 1/3 of nodes in a 13-node subnet being down or unhealthy. This means a subnet can function with up to 4 unhealthy nodes. If the unhealthy nodes do not exceed this threshold, a node might be left in the subnet for a longer period, especially if there are efforts underway to make it healthy again.

'''Q: When are nodes typically removed or replaced?'''

A: Node removals or replacements are currently conducted semi-manually and are typically scheduled for Mondays or Fridays. This timing allows Foundation voters to participate in the decision-making process at the start or end of the workweek. However, as this process is manually conducted, exceptions may occur based on specific circumstances.

'''Q: What are the future plans for node management in the IC network?'''

A: In the medium term, there are plans to automate node replacements. This means node swaps might occur more frequently and systematically, reducing the manual overhead and potentially enhancing the network's resilience and performance.

Note: As with all network operations, these practices are subject to change based on technological advancements and the evolving needs of the IC network. It's always good to refer to https://github.com/dfinity/dre for the most current information and tooling.

Back to [[Node Provider Troubleshooting]]

Back to [[Node Provider Documentation]]

Neptune Partners

2023-12-19T16:24:03Z

Sat: Merge edit by Neptune

==Self-Declaration==
The self-declaration document can be found here:
[[File:Self Declaration Neptune.pdf|thumb|alt=|center]]
The SHA256 hash of the linked PDF is 212c43503bbbe421e213a7b46da2c91c70c80ae7326b91d2ddedc29f4e26a984.

==Identity Proof==
Company information can be verified by entering UEN number : ''201813417G on the following website.''

https://www.uen.gov.sg/ueninternet/faces/pages/uenSrch.jspx

Attached Copy :
[[File:Certificate of Incorporate.pdf|center|thumb]]

The SHA256 hash of the linked PDF is 78588307b8273d3b9ac7f4e26194c76da7a5c74aea91b4246def566ab97cd568.

== Proof of Hardware Order ==

SHA256 hash of linked PDF is 35712cda62bf07210b3851365dfec40d356265caa549e2b69b899e96f6849102
[[File:Dell Invoice Neptune Partners.pdf|center|thumb|1133x1133px]]

Node Provider Self Declarations

2023-12-18T15:23:50Z

Sat:

Node Provider Matrix channel

2023-12-18T15:21:30Z

Sat:

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 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
|
|
|-
|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
|
|
|-
|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
|
|
|-
|GeoNodes LLC
|5wedd-dwi2c-ybr2g-benav-qlgc7-vifbt-qz3ml-ymopp-uaide-ilpkb-tae
|
|
|-
|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
|
|
|-
|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
|-
|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
|
|
|-
|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
|
|
|}

Node Deployment Guide

2023-12-13T16:30:05Z

Sat: /* 10. First Boot */

This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS).

The physical machine is expected to be racked and stacked according to its respective manual.

To complete these steps, you are expected to by physically present with your machine(s). Once you successfully onboarded your first node, you can bring up the other nodes in parallel.

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]].

==1. Choose onboarding path (HSM vs. no HSM)==
If you chose the [[Node Provider Onboarding#5. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], follow the [[NitroKey HSM installation runbook]] to onboard your nodes.

If you chose to onboard '''without''' a Nitrokey HSM, '''continue to the next step.'''

==2. Obtain requirements ==
*A USB (3.0 speed that can hold at least 4GB) to put the image file on.
**Faster USBs will allow the process to go much faster.
*The <code>node_operator_private_key.pem</code> for your data center (Acquired from [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]])
* It is recommended that each server have a label with the BMC's MAC address for ease of identification in future dashboard upgrades.

== 3. Download installation image==
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases].
*Note that you should always use a release that is less than 6 weeks old in order to ensure that your node can keep up with the blockchain.

== 4. Verify checksum and unarchive file==
===Mac OS X ===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.gz</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.gz</syntaxhighlight>

===Linux / Ubuntu===
#Open the Terminal and type:
#:<syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.gz</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.gz</syntaxhighlight>

===Windows===
#Open PowerShell and type:
#:<syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.gz</syntaxhighlight>
#Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#:Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.gz</syntaxhighlight>

==5. Create Bootable USB Stick ==
===Mac OS X===
# Open the Terminal and type:
#:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight>
#All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight>
#The file path is an example. Use the absolute path to the downloaded image. '''Warning:''' You risk losing your own data if you specify a wrong device.
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight>

=== Linux / Ubuntu===
#Open the Terminal and type
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight>
# All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight>
#Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=~/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M</syntaxhighlight>

===Windows===
#Download and install [https://rufus.ie/en/ Rufus Portable]
#Start Rufus
#Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
#:[[File:05.png|480px|screenshot]]
#You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
#:[[File:06.png|480px|screenshot]]
#:[[File:07.png|480px|screenshot]]
# The "Ready" bar will go from left to right as it completes.

==6. Add configuration==

===A. Open Config.ini in a text editor===

===='''Mac OS X'''====

#Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:mac_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in TextEdit.

===='''Linux'''====

#Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:linux_01.png|580px|screenshot]]
#Double-click <code>config.ini</code> to open it in KWrite.

===='''Windows'''====

#Open the Disk Management utility with a right click on the Start menu
#:[[File:09-b.png|300px|screenshot]]#:
#Right click the CONFIG partition
# Select Change drive letter or paths...
#:[[File:10-b.png|780px|screenshot]]
# Select any letter from the drop-down list
#:[[File:11-b.png|480px|screenshot]]
#Click OK.
#You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file
#:[[File:12-b.png|780px|screenshot]]
#Click on Edit to open it.

===B. Edit Config.ini===

#Insert your IPv6 prefix, subnet and gateway.
#:[[File:Edit config ini.png|580px|screenshot]]
#:*The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
#:*For example, a valid prefix could look like this: <code>2a00:fb01:400:100</code>
#:*'''Important:'''
#:**The prefix should not have a trailing ':'
#:**IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. Hence, the '::' shorthand should '''not''' be used: even if some groups are all zeros, they must be explicitly written out.
#Save the changes.
#:* If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
#:* If you need help, please do not hesitate to post your issue in the [[Node Provider Matrix channel]].
#:*:[[File:mac_03.png|580px|screenshot]]

=== C. Copy Node Operator private key to config partition===

#Copy <code>node_operator_private_key.pem</code> (created in [[Node Provider Onboarding#6. Setup the Node Operator keys|Node Provider Onboarding step 6]]) to the <code>CONFIG</code> partition. This file should have the name <code>node_operator_private_key.pem</code>, and sit next to <code>config.ini</code>, NOT inside the <code>ssh_authorized_keys</code> folder.

==7. Connect Crash Cart==
#In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
#Plug-in the VGA/Video, keyboard and IC-OS USB stick
#:[[File:08.png|580px|screenshot]]

==8. UEFI Setup and Boot Menu==

Make sure that server date/time is set to UTC (Universal Time Coordinated)

Use the related page below to set up the BIOS/UEFI according to your hardware vendor.

*[[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]]
** [[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]]
** [[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]]
**[[IC-OS Installation - UEFI Configuration - Gen2 ASUS]]
*[[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]]
***
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.

Resume from this point when you are finished configuring the BIOS.

==9. IC-OS Installation==
#Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
#:[[File:35-sm.png|580px|screenshot]]
#The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Possible Node Onboarding Errors]] page if you encounter any errors.
#:[[File:36-sm.png|580px|screenshot]]
#If the installation finished successfully, it will initiate a reboot.
#:[[File:38-sm.png|580px|screenshot]] 
==10. First Boot==
Please remember to check the [[Possible Node Onboarding Errors]] page if you encounter any errors onboarding.
#Once you see this message, you may unplug the USB stick and VGA/Video.
#:[[File:Node join message.png|580px|screenshot]]

Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!

==11. Verify node onboarding==

#Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard] is set to either “Awaiting Subnet” or “Active in Subnet”.
#*The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node (Node ID is outputted in step 10).
#*If the status of your node is not either “Awaiting Subnet” or “Active in Subnet”, or if it is not listed under your Node Provider principal, you should contact the [[Node Provider Matrix channel]] for assistance.
#*:[[File:Dashboard-node-verification.png|thumb|998x998px]]

Geeta Kalwani

2023-12-12T09:46:30Z

Sat: Merge edit by Geeta23

== Self declaration document ==
[[File:Geeta Kalwani Self declaration.pdf|center|thumb|1131x1131px|Geeta Kalwani Self Declaration]]

Self-declaration SHA256: 454e41ea6b63fc2fc6c25f5353c3138da6d84ff49d92fd422c1db06706355bec

== Proof of identity document ==
[[File:Geeta Kalwani Identity Proof.pdf|center|thumb|1133x1133px]]

Proof of identity SHA256: 06d21b40f5d1739418e661cd489aebcc147b41b7e1fc387e3cf3fd13cb960072

Troubleshooting Unhealthy Nodes

2023-12-11T18:22:23Z

Sat: Added two alert runbooks

=== '''Use [https://dashboard.internetcomputer.org/centers the dashboard] to verify that the node is healthy''' ===
*The node count for your data center should match the number of nodes in that data center.
* Look for the principal ID for the node which you are servicing. Status explanations are [https://wiki.internetcomputer.org/wiki/Node_Provider_Troubleshooting#Node_Status_on_the_Dashboard here].
* If the node isn't listed at all, then it needs to be [[IC-OS Installation Runbook|redeployed the node with a fresh IC-OS image]].

=== '''Degraded nodes statuses''' ===

==== IC_OrchestratorFlapping ====
'''Explanation:''' Orchestrator coordinates the execution of many IC GuestOS processes, including the IC Replica. If the orchestrator is repeatedly restarting, then the GuestOS and the Replica process likely do not operate as expected.

'''Possible causes:'''

* Networking issues
* Hardware issues
* Software problems

'''Troubleshooting and remediation:'''

* Check if any NNS proposals were recently executed for the nodes in question https://dashboard.internetcomputer.org/governance
* Check if there are some bandwidth limitations on these nodes, and ensure any traffic shaping, QoS, DOS protection, etc, are ''disabled'' on the ISP side
* Perform other [https://wiki.internetcomputer.org/w/index.php?title=Unhealthy_Nodes&veaction=edit#Setting_Up_an_Auxiliary_Machine_for_Network_Diagnostics network diagnostics checks]
* Inspect node logs and metrics, if possible
* Consult other node providers and DFINITY if there are any known software problems with the latest revision that the node(s) are running

==== IC_Replica_Behind ====
'''Explanation:''' IC Replica is the main process, that runs canisters (smart contracts). If the Replica process cannot catch up, then the replica (node) cannot be a productive member of the IC subnet.

'''Possible causes:'''

* Networking issues
* Hardware issues
* Software problems

'''Troubleshooting and remediation:'''

* Check if there are any hardware issues reported by the machine's BMC (Baseboard Management Controller)
* Perform [https://wiki.internetcomputer.org/wiki/Updating_Firmware firmware upgrade]
* Check if any NNS proposals were recently executed for the nodes in question https://dashboard.internetcomputer.org/governance
* Check if there are some bandwidth limitations on these nodes, and ensure any traffic shaping, QoS, DOS protection, etc, are ''disabled'' on the ISP side
* Perform other [https://wiki.internetcomputer.org/w/index.php?title=Unhealthy_Nodes&veaction=edit#Setting_Up_an_Auxiliary_Machine_for_Network_Diagnostics network diagnostics checks]
* Inspect node logs and metrics, if possible
* Consult other node providers and DFINITY if there are any known software problems with the latest revision that the node(s) are running

=== '''"Orchestrator Started" message''' ===
This message is not an error, nor is it confirmation that the node is running properly. This must be determined in other ways:

*'''Check [https://dashboard.internetcomputer.org/ the dashboard]''' to check the status of the node. (Status explanations are [https://wiki.internetcomputer.org/wiki/Node_Provider_Troubleshooting#Node_Status_on_the_Dashboard here].) Use the principal ID that was assigned to the node when it was onboarded to identify it.
*If the node is not visible on the dashboard, then it has not registered with the Internet Computer.
**If you have recently installed a current IC-OS image, then you can try inserting the HSM and/or a reboot to see if it joins. This would work if a recent IC-OS installation was successful and only the registration and joining was interrupted.
**If you have ''not'' recently installed a current IC-OS image, then do ''not'' insert the HSM. You do not want the node to rejoin with an old IC-OS image, as it will only fail again. Instead, you should consider [[Updating Firmware|upgrading the firmware]] if it is running on old versions, and then redeploy the node with [[IC-OS Installation Runbook|a fresh/current IC-OS image]] (which will assign a new principal to the node so that you can identify it in the dashboard.)

=== '''Server Troubleshooting Steps''' ===
These steps may help when a server is unhealthy or has been removed from the network, but the connectivity in the data center is functioning correctly:

#Verify if the server is up and running:
#*Check the power status of the server.
#*Check if the server is displaying any error messages or indicators.
#*If possible, access the server remotely or physically to ensure it is functioning properly.
#Hook up a crash cart and check for errors on the screen, troubleshoot as needed.
#Consider [[Updating Firmware|updating the firmware]] if it has been a long time, and/or if you have recently had other nodes that needed firmware upgrades to become healthy again.
# If no known error is found, please [[IC-OS Installation Runbook|redeploy the node with a fresh IC-OS image]].
#* The deployment process identifies/fixes many software issues.
#* Note that if an old IC-OS image is used, the node will "appear" to be healthy at first, but it will not be able to catch up to the blockchain and will therefore fall behind and become unhealthy again. '''Thus, a current IC-OS image must be used.'''
#* At the end, obtain the new principal ID for the node from the crash cart screen so you can check the dashboard status.
#*'''If a node is healthy ("Awaiting Subnet" status) for a while and then changes to "Offline," then whatever the issue was originally still exists.''' Troubleshoot hardware, upgrade firmware, etc to resolve the issue.

=== '''Networking Troubleshooting Steps''' ===

# Inspect network hardware in the rack for any visible signs of malfunction (e.g. red lights) or incorrect setup
# Verify the cabling and port status on the switch:
#*Check the physical connection of the network cable between the server and the switch.
#*Ensure that the cable is securely plugged into the correct port on both ends.
#*Look for any signs of damage or loose connections.
#*Test the connectivity by trying a different network cable or using the same cable on a different port.
#Check for recent port flaps/link failures or any other activities which might cause it:
#*Check the logs or monitoring systems for any indications of port flapping or link failures.
#*Investigate any recent changes or activities that could have affected the network connection.
#*Consider any software updates, configuration changes, or physical alterations made recently.
#Try to perform a re-seat of cable/breakout/SFP/QSFP toward the affected machine:
#*Disconnect and reconnect the network cable at both ends (server and switch).
#*If applicable, re-seat any breakout cables, SFP modules, or QSFP modules used in the connection.
#*Ensure a secure and proper connection is established.
#Check with the switch vendor:
#*If the issue persists, contact the switch vendor's support team for further assistance.
#*Provide them with detailed information about the problem and any troubleshooting steps you have already taken.
#*Follow vendor guidance to troubleshoot and resolve the issue.
#**If your vendor requires a TSR log, see [[IDRAC access and TSR logs]] for an example of how to retrieve one from a Dell server.
#**[[Updating_Firmware|Updating the firmware]] might also resolve the issue.
# Utilize an auxiliary machine within the same rack with full network access to run diagnostics tools like <code>ping</code>, <code>traceroute</code>, and <code>nmap</code>
# Work with the ISP to troubleshoot and resolve any network routing issues identified during diagnostics
# Prepare for future incidents by establishing network redundancy and failover mechanisms

=== '''Best practices''' ===

# Keep a separate machine in the same rack with appropriate tools for network diagnostics and troubleshooting
# Engage with the node provider community for support and to share effective troubleshooting techniques

=== '''Setting Up an Auxiliary Machine for Network Diagnostics''' ===
Robust Internet connectivity is essential. Without access to internal node logs and metrics, troubleshooting requires alternative strategies, including the use of an auxiliary machine within the same rack. Here's a brief outline for setting up an auxiliary machine in the same rack, while following best security practices:
# Hardware Setup:
#* Choose a server with sufficient resources to run diagnostic tools without impacting its performance. There is no need to follow the gen1/gen2 hardware requirements for this server (since this node would not be joining the IC network) but make sure the server is performant enough to run network tests.
#* Ensure physical security measures are in place to prevent unauthorized access.
# Operating System and Software:
#* Install a secure operating system, like a minimal installation of Linux (we prefer Ubuntu 22.04), which reduces the attack surface.
#* Keep the system updated with the latest security patches and firmware updates.
# Network Configuration:
#* Configure the machine with an IPv6 address in the same range as the IC nodes, for accurate testing.
#* Set up a restrictive firewall on the machine to allow ''only the necessary'' inbound and outbound traffic. Consider allowing Internet access for this machine only during troubleshooting sessions, and keeping the machine behind a VPN at other times.
# Diagnostic Tools:
#* Install network diagnostic tools such as <code>ping</code>, <code>traceroute</code>, <code>nmap</code>, <code>tcpdump</code>, and <code>iperf</code>.
#* Configure monitoring tools to simulate node activities and track responsiveness.
# Security Measures:
#* Use strong, unique passwords for all accounts and change them regularly. Or, preferably, do not use passwords at all, and use key-based access instead.
#* Implement key-based SSH authentication and disable root login over SSH.
#* Regularly review logs for any unusual activities that might indicate a security breach.
# Maintenance and Updates:
#* Regularly update all software to the latest versions.
#* Periodically test your network diagnostic tools to ensure they are functioning as expected.

=== '''Frequently Asked Questions''' ===
Q: Is the monitoring system open-sourced? How does it communicate with the nodes?

A: The monitoring system configuration is not currently open-sourced. However, the node configuration that is required for proper node operation is fully open source. For more information about the node-to-node and node-to-monitoring communication, refer to the [https://sourcegraph.com/github.com/dfinity/ic/-/blob/ic-os/hostos/rootfs/etc/nftables.conf?L54-112 nftables configuration], which is the definitive guide for required open ports on Host OS, and [https://sourcegraph.com/github.com/dfinity/ic/-/blob/ic-os/guestos/rootfs/opt/ic/share/ic.json5.template?L322 similar nftables configuration] for the Guest OS. You can find the configuration for DFINITY-owned DCs and Gen1 node providers here: nftables configuration. We use [https://docs.victoriametrics.com/ Victoria Metrics] for metrics scraping (documentation) and [https://vector.dev vector.dev] for log scraping.

Q: What are the destination IPs and Ports for Frankfurt, Chicago, and San Francisco for connectivity troubleshooting?

A: At present, detailed node/port information is not publicly accessible, as disclosing this information is considered a security risk. To effectively troubleshoot connectivity issues with your nodes, we recommend setting up a "spot instance" or a temporary virtual machine (VM) with a cloud provider in each of the geographical regions. This approach allows you to test both connectivity and connection stability to your nodes, providing a practical solution for identifying and resolving network-related issues.

Q: The dashboard shows offline or degraded status for <DC>, but everything seems fine. What should we do?

A: Check if any of these issues are present: firewall restrictions, traffic shaping, DOS protection, or QOS features enabled on the ISP side. These should all be disabled for optimal node operation.

Back to [[Node Provider Troubleshooting]]

Back to [[Node Provider Documentation]]

Node Provider Matrix channel

2023-12-11T16:29:51Z

Sat:

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 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
|
|-
|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
|
|-
|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
|
|
|-
|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
|
|
|-
|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
|
|
|-
|GeoNodes LLC
|5wedd-dwi2c-ybr2g-benav-qlgc7-vifbt-qz3ml-ymopp-uaide-ilpkb-tae
|
|
|-
|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
|
|
|-
|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
|-
|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
|-
|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
|
|
|-
|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
|
|
|}