In line with motion proposal 132553 for node rewards after 48 months, set rewards for the following nodes:

* rm5ia-lmctw-ylpu6-j7sx2-h7zgv-whmjk-4guew-6n3li-mwdjx-clfg3-vqe

This node was not in previous proposals (136012, 135606 and 135454) due to hardware issues that took time to resolve.

For more information, please visit these forum posts/pages https://forum.dfinity.org/t/new-node-provider-proposals/16643/715, https://forum.dfinity.org/t/proposal-update-interim-gen-1-node-provider-remuneration-after-48-months/35001/5, https://wiki.internetcomputer.org/wiki/100_Count_Holdings,_LLC

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/136067)

NodeAdmin(136067): Update config of Node Operator: kguzs

Set Topic for Vote on NNS proposal to Application Business Logic.
--------------------------------
<br><br>
This proposal was created using [https://ic-toolkit.app](https://ic-toolkit.app)
<br><br>


Set Topic for Vote on NNS proposal to Application Business Logic

Set rewards for the following nodes (The proof of hardware order is available at https://wiki.internetcomputer.org/wiki/Bitmoon with SHA256 AB48EE944F97011FF833229C44DBFA15A6289C68724592E3C62F226A668D1B3D)


* 6hqi5-ctyoo-qijwz-dtvwo-g5puo-yaftz-dmaid-rambc-li5dx-q46y2-sae
* l7jrv-cork3-yugm-545hs-bn3sa-sedzb-y4w2t-kbfyn-5ughu-ccr32-nqe


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134333)

Update config of Node Operator: nvocp - NodeAdmin - NNS Id 134333

# Replace nodes in subnet tdb26

Motivation: 
 - replacing dead node 2tk2h-7snvn-clgy3-g33vp-fc57w-ptljs-xujfq-fu47q-ludhi-g7zzf-xqe
 - replacing node mf3d3-z5tww-ii4jn-zhy4f-ah3un-wpre7-edsb4-ktrb5-h7f3f-uz7rv-bqe to optimize network topology
 - replacing node wazkf-2xehg-y26ek-2uq64-pkrbh-6frmq-4q7lf-5gaya-44q4p-v5r5z-cqe to optimize network topology

Calculated impact on subnet decentralization if replacing:

- 1 additional node: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.7500 to 2.7753
- 2 additional nodes: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.7753 to 2.7982
- 3 additional nodes: (gets worse) the average log2 of Nakamoto Coefficients across all features decreases from 2.7982 to 2.7914
- 4 additional nodes: equal decentralization across all features
- 5 additional nodes: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.7914 to 2.7982

Based on the calculated impact, replacing 2 additional nodes to improve optimization

Note: the heuristic for node replacement relies not only on the Nakamoto coefficient but also on other factors that iteratively optimize network topology.
Due to this, Nakamoto coefficients may not directly increase in every node replacement proposal.
Code for comparing decentralization of two candidate subnet topologies is at:
https://github.com/dfinity/dre/blob/79066127f58c852eaf4adda11610e815a426878c/rs/decentralization/src/nakamoto/mod.rs#L342

Note: the information below is provided for your convenience. Please independently verify the decentralization changes rather than relying solely on this summary.
Here is [an explaination of how decentralization is currently calculated](https://dfinity.github.io/dre/decentralization.html), 
and there are also [instructions for performing what-if analysis](https://dfinity.github.io/dre/subnet-decentralization-whatif.html) if you are wondering if another node would have improved decentralization more.



Decentralization Nakamoto coefficient changes for subnet `tdb26-jop6k-aogll-7ltgs-eruif-6kk7m-qpktf-gdiqx-mxtrf-vb5e6-eqe`:
```
  node_provider: 11.00 -> 12.00    (+9%)
    data_center: 13.00 -> 13.00    (+0%)
data_center_owner: 12.00 -> 11.00    (-8%)
            city: 9.00 -> 11.00   (+22%)
          country: 6.00 -> 6.00    (+0%)
        continent: 1.00 -> 1.00    (+0%)
```

**Mean Nakamoto comparison:** 8.67 -> 9.00  (+4%)

Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.7500 to 2.7982

# Details


Nodes removed:
- `2tk2h-7snvn-clgy3-g33vp-fc57w-ptljs-xujfq-fu47q-ludhi-g7zzf-xqe` [health: dead, impact on decentralization: (gets better) the number of nodes controlled by dominant Country actors decreases from 15 to 14]
- `mf3d3-z5tww-ii4jn-zhy4f-ah3un-wpre7-edsb4-ktrb5-h7f3f-uz7rv-bqe` [health: healthy, impact on decentralization: (gets worse) the average log2 of Nakamoto Coefficients across all features decreases from 2.7500 to 2.7098]
- `wazkf-2xehg-y26ek-2uq64-pkrbh-6frmq-4q7lf-5gaya-44q4p-v5r5z-cqe` [health: healthy, impact on decentralization: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.7098 to 2.7351]

Nodes added:
- `zxt3p-naibu-wlon6-w2h5f-ur74w-wxde7-x4zxc-ghfgs-dgbpr-65lnr-wqe` [health: healthy, impact on decentralization: (gets worse) the number of nodes controlled by dominant Country actors increases from 13 to 14]
- `4p3lu-7sy3a-ph47t-wlvb6-naehi-oki2f-pkokv-hovam-s5iul-sxvwk-3ae` [health: healthy, impact on decentralization: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.7351 to 2.8191]
- `lwxeh-xayoz-wu5eb-hwraj-a3pew-yeioj-cnwat-5uow4-ugxkc-kx44o-4ae` [health: healthy, impact on decentralization: (gets worse) the average log2 of Nakamoto Coefficients across all features decreases from 2.8191 to 2.7982]


```
    node_provider                                                              data_center            data_center_owner                                    city                             country            continent              
    -------------                                                              -----------            -----------------                                    ----                             -------            ---------              
    3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae       1    ar1               1    Africa Data Centres                        1 -> 0    Barreiro                    1    AR            1    Africa           3 -> 2
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    ba1               1    Anonstake                                       1    British Columbia            1    AU            2    Asia                 12
    4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae       1    bc1               1    Baltneta                                        1    Brussels Capital            1    BE            1    Europe         16 -> 17
    4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae       1    bn1               1    Celeste                                         1    Bucuresti                   1    CA            2    North America         6
    4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae       1    bo1               1    Cloud9                                          1    CABA                        1    CH            3    Oceania               2
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe  2 -> 1    br1               1    CyrusOne                                   1 -> 0    Cape Town                   1    CR            1    South America         1
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe       2    bt1               1    Cyxtera                                         1    Colombo                     1    CZ            2                           
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    bu1               1    DataHouse                                       1    Gauteng                2 -> 1    DE       0 -> 1                           
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    ch2          0 -> 1    Digital Realty                                  1    Geneva                      1    EE            1                           
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe       1    ch3          1 -> 0    Equinix                                    1 -> 2    Hesse                  0 -> 1    FR            1                           
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       2    cm1               1    Everyware                                       2    HongKong                    2    GE            1                           
    cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe       1    cr1               1    HighDC                                          1    Illinois                    1    HK            2                           
    dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae       1    ct2               1    INAP                                            1    Ljubljana                   1    IL            1                           
    diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe       1    fr2          0 -> 1    InfonetDC                                       1    London                      1    IN       2 -> 3                           
    efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe       1    ge1               1    Interhost                                       1    Maribor                     1    JP            1                           
    eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe       1    hk3               1    KT                                              1    Massachusetts               1    KR            2                           
    i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe       1    hk4               1    Latitude.sh                                     1    Melbourne                   1    LK            1                           
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    hu1               1    Leaseweb                                        1    Navi Mumbai                 1    LT            1                           
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    jb2          1 -> 0    M247                                            1    New Delhi              0 -> 1    LV            1                           
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae       1    jb3               1    Marvelous Web3 DC                          0 -> 1    Panvel                      1    PL            1                           
    izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe  1 -> 0    kr1               1    Master Internet                                 1    Paris                       1    PT            1                           
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    ld1               1    MasterDC                                        1    Praha                       1    RO            1                           
    lq5ra-f4ibl-t7wpy-hennc-m4eb7-tnfxe-eorgd-onpsl-wervo-7chjj-6qe       1    lj2               1    Megazone Cloud                                  1    Quebec                      1    SG       2 -> 1                           
    mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae       1    mb1               1    NEXTDC                                          2    Queensland                  1    SI            2                           
    nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae  1 -> 0    mn2               1    Nano                                            1    Riga                        1    UK            1                           
    pa5mu-yxsey-b4yrk-bodka-dhjnm-a3nx4-w2grw-3b766-ddr6e-nupu4-pqe  0 -> 1    mtl1              1    Navegalo                                        1    San Jose                    1    US            3                           
    py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe       1    nd1          0 -> 1    Online                                          1    Seoul                       2    ZA       3 -> 2                           
    qsdw4-ao5ye-6rtq4-y3zhm-icjbj-lutd2-sbejz-4ajqz-pcflr-xrhsg-jae       1    nm1               1    OrionStellar                                    1    Singapore              2 -> 1                                              
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae       1    pa1               1    Posita.si                                       1    South Moravian Region       1                                              
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    pl2               1    Racks Central                              1 -> 0    Tallinn                     1                                              
    s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae       1    pr1               1    Rivram                                          1    Tbilisi                     1                                              
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    rg3               1    SyT - Servicios y Telecomunicaciones S.A.       1    Tel Aviv                    1                                              
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe  0 -> 1    sc1               1    TRG                                             1    Texas                       1                                              
    sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe       1    sg1               1    Telin                                           1    Tokyo                       1                                              
    ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae       1    sg3          1 -> 0    Teraco                                          1    Vilnius                     1                                              
    unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe       1    sl1               1    Tierpoint                                  0 -> 1    Warszawa                    1                                              
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    ta1               1    Xneelo                                          1    Zurich                      2                                              
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    tb1               1    Yotta                                           1                                                                               
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae  0 -> 1    tv1               1    hkcolo                                          1                                                                               
    zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae       1    ty3               1    hkntt                                           1                                                                               
                                                                               wa3               1                                                                                                                                    
                                                                               zh2               2                                                                                                                                    
```

### Business rules analysis
Subnet extension with 3 nodes finished with the total penalty 90. Penalty causes throughout the extension:

- adding node 1 of 3 (zxt3p): node_provider 6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- adding node 1 of 3 (zxt3p): data_center zh2 controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- adding node 1 of 3 (zxt3p): data_center_owner Everyware controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- adding node 2 of 3 (4p3lu): node_provider 6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- adding node 2 of 3 (4p3lu): data_center zh2 controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- adding node 2 of 3 (4p3lu): data_center_owner Everyware controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- adding node 3 of 3 (lwxeh): node_provider 6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- adding node 3 of 3 (lwxeh): data_center zh2 controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- adding node 3 of 3 (lwxeh): data_center_owner Equinix controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.

Business rules analysis is calculated on each operation. Typically only the last operation is relevant, although this may depend on the case.


Forum post link: https://forum.dfinity.org/t/subnet-management-tdb26-nns/336633


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/133078)

Replace nodes in subnet tdb26 - SubnetManagement - NNS Id 133078


This proposal transfers max weekly amount of ICP to the 8-year neuron of the protocol.
A rehearsal of the proposal has been previously [made](https://nns.ic0.app/proposal/?u=jmod6-4iaaa-aaaaq-aadkq-cai&proposal=20), parameters should be the same.
            

Transfer Maximum Weekly ICP to 8-year neuron

# Summary
This is the Tunebook proposal for the NNS to create an SNS DAO. This forum post is an opportunity for the IC community to learn more about [Tunebook](https://tunebook.io) and ask questions.
# About
Tunebook's mission is to preserve Trad music, connect musicians, and provide a hub for sharing, discovering, and trading within the Trad music community.
Tunebook is a decentralized platform for Trad musicians, built on the Internet Computer. By leveraging the unique features of ICP, Tunebook ensures the permanence of its database of tunes, a seamless user experience, and a decentralized governance structure. The platform also includes a marketplace where musicians can buy and sell bespoke and rare instruments, with seller participation secured by locking Tunebook tokens.
# Proposed Token Distribution
Total TUNE tokens to be created: 10,000,000
Initially distributed:
- 25%: Treasury (2,500,000 TUNE tokens) - 30%: Public Sale (3,000,000 TUNE tokens) - 30%: Team Allocation (3,000,000 TUNE tokens) - 9%: Airdrop For Early Adopters (900,000 TUNE tokens) - 6%: DEX Liquidity (600,000 TUNE tokens)
Ledger transaction fee: 0.0001 TUNE tokens
For more information on the Tunebook SNS, please read our [Whitepaper](https://docs.google.com/document/d/1QmzpjnhSHRE17cuqVqN_jymYKEhj806jN6vQSebDtQQ/edit?usp=sharing).
# Decentralization SNS Swap
30% of the total supply of tokens is proposed to be distributed via an SNS decentralization swap.
Swap participation parameters:
- Min participation: 1 ICP   - Max participation: 10,000 ICP   - Max to be raised: 70,000 ICP   - Min to be raised: 7,000 ICP   - Min participants: 100  
The sale is open to anyone outside of the United States of America.
Participation is either via the launchpad in the NNS front end: https://nns.ic0.app/ or on the command line using [quill](https://wiki.internetcomputer.org/wiki/How-To:_Participate_in_the_SNS_decentralization_sale_via_quill).
You can review the Tunebook SNS Configuration [here](https://docs.google.com/spreadsheets/d/1zRlAY2_gsuXHQCSD0cJkUaVIrHT_OBKn09rZJ7thz8Q/edit?usp=sharing).
# Use of Funds
The Tunebook team [Celtic Crossroads Foundation] will submit quarterly proposals to withdraw from the treasury to pay for development and expenses outlined below:
- Funding for cycles to maintain the application   - Further development of the marketplace and platform features   - Funding the core team  
For more information, please refer to section 10.1.4.1 of the [Tunebook DAO Whitepaper](https://docs.google.com/document/d/1QmzpjnhSHRE17cuqVqN_jymYKEhj806jN6vQSebDtQQ/edit?usp=sharing).
# Source Code
Tunebook's source code can be found [here](https://github.com/Tunebook/Tunebook).
# Notes
You can access the [Tunebook SNS Whitepaper here](https://docs.google.com/document/d/1QmzpjnhSHRE17cuqVqN_jymYKEhj806jN6vQSebDtQQ/edit?usp=sharing).   You can access the [Tunebook SNS Tokenomics here](https://docs.google.com/spreadsheets/d/1zRlAY2_gsuXHQCSD0cJkUaVIrHT_OBKn09rZJ7thz8Q/edit?usp=sharing).  
You can sign up and test out our dApp here: https://tunebook.io.
# Disclaimer
This swap is open to any persons or entities other than those who are citizens of, or reside or are located, incorporated, or have a registered office in the United States of America or (i) any country embargoed by the government of Canada, the United States, the United Kingdom, or the European Union or are a foreign person or entity blocked or denied by the Canadian, United States, the United Kingdom, or any European Union government or (ii) a country which has been sanctioned by the United Nations, including without limitation Iran, Cuba, North Korea, Syria, Myanmar (Burma), and the regions of Crimea, Donetsk, and Luhansk.


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134350)

NNS Proposal to create an SNS named 'Tunebook' - SnsAndCommunityFund - NNS Id 134350

Today the [NNS dapp launchpad](https://nns.ic0.app/launchpad/) has the potential to mislead users, as demonstrated in the [screenshot shared on the DFINITY forum](https://forum.dfinity.org/t/nns-dapp-launchpad-is-misleading/38588).

> 'Looks like there are no SNS decentralisation swaps running right now'

The above statement on the NNS dapp launchpad is inaccurate. There's currently an assumption that SNS decentralisation swaps take place in 1 round, and 1 round only. This is a limitation of the NNS dapp launchpad, but an SNS can host further decentralisation swaps independently (as [**WaterNeuron** is currently doing](https://waterneuron.fi/launchpad)).

--------------

## WaterNeuron's Decentralisation Swap - Round 2 (Papaya Era)

**As an example**, **[WaterNeuron](https://waterneuron.fi/)** is currently seeding a large amount of governance power to the IC community, as originally planned in the roadmap.

Given WaterNeuron's significance as a IC governance project, it's huge position leading liquid staking on the IC, and the potential for the project to become a massive influence in terms of IC governance power, I think it's vital to effective decentralisation of the IC that the community at large is made aware of this decentralisation swap.

If participation is low, it's not unlikely that a large player will swoop in just before the end of the swap and scoop up the majority of the token. WaterNeuron has a very promising road ahead, and the community should be given every opportunity to share in this, and improve the state of IC governance as a result.


------

This motion proposal asks the community to vote yes if you believe that the NNS dapp launchpad is currently misleading, and that this is problematic. Voting yes means either the wording should be changed to make fewer assumptions, or ideally users should be directed to decentralisation swaps that are currently taking place (ones that are hosted by an existing SNS).

Before you vote on this proposal, consider contributing to decentralisation of WaterNeuron (and therefore decentralisation of IC governance) by committing a small amount of ICP to the swap. If everyone commits a small amount, the IC will be well on it's way to becoming far more decentralised than it is now.

[First you register your WTN NNS principal]((https://waterneuron.fi/launchpad)) (check the address for [holding WTN in your NNS wallet](https://nns.ic0.app/wallet/?u=jmod6-4iaaa-aaaaq-aadkq-cai)). Then you transfer ICP to the principal provided on the launchpad (displayed when you registered your WTN NNS principal).



*This proposal was submitted by [Alex Lorimer](https://forum.dfinity.org/u/lorimer/summary) ([11086350816921594616](https://dashboard.internetcomputer.org/neuron/11086350816921594616)), which can be verified by checking the neuron ID with the one registered on the [D-QUORUM neuron](https://dashboard.internetcomputer.org/neuron/4713806069430754115).*

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134421)

Decentralisation Swap Visibility - Governance - NNS Id 134421

# Proposal to upgrade the BTC Checker canister

Repository: `https://github.com/dfinity/ic.git`

Git hash: `c58e00fe2271d77ede9ccab5a6b317689859ea98`

New compressed Wasm hash: `1e174def478e8324f025eda7f4d723dc76638ed2a1200a3de934850c6ec1da9b`

Upgrade args hash: `1115f49331a1f7e6fddbcab23cdc8932508c193782fa42d80579a19981fe211f`

Target canister: `oltsj-fqaaa-aaaar-qal5q-cai`

Previous BTC Checker proposal: https://dashboard.internetcomputer.org/proposal/134442

---

## Motivation

Upgrade the Bitcoin Checker canister to fix errors when making RPC https calls over http/2 and improve usability.

## Upgrade args

```
git fetch
git checkout c58e00fe2271d77ede9ccab5a6b317689859ea98
cd rs/bitcoin/checker
didc encode -d btc_checker_canister.did -t '(CheckArg)' '(variant { UpgradeArg = null })' | xxd -r -p | sha256sum
```

## Release Notes

```
git log --format='%C(auto) %h %s' f901615f3daa36a5f3a9a6277140e1895ed53d2d..c58e00fe2271d77ede9ccab5a6b317689859ea98 -- rs/bitcoin/checker
c58e00fe22 fix(ckbtc): Drop Host header from https outcall request (#3115)
57362c30e3 fix(ckbtc): state schema upgrade (#3071)
 ```

## Wasm Verification

Verify that the hash of the gzipped WASM matches the proposed hash.

```
git fetch
git checkout c58e00fe2271d77ede9ccab5a6b317689859ea98
"./ci/container/build-ic.sh" "--canisters"
sha256sum ./artifacts/canisters/ic-btc-checker.wasm.gz
```


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134466)

Upgrade NNS Canister: oltsj-fqaaa-aaaar-qal5q-cai to wasm with hash: 1e174def478e8324f025eda7f4d723dc76638ed2a1200a3de934850c6ec1da9b - NetworkCanisterManagement - NNS Id 134466

Update subnet nl6hn-ja4yw-wvmpy-3z2jx-ymc34-pisx3-3cp5z-3oj4a-qzzny-jbsv3-4qe to replica version [d9fe2076f677a08734bed90c67b1c3f4056ed621](https://dashboard.internetcomputer.org/release/d9fe2076f677a08734bed90c67b1c3f4056ed621)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134480)

Update subnet nl6hn to replica version d9fe207 - IcOsVersionDeployment - NNS Id 134480

Update subnet w4asl-4nmyj-qnr7c-6cqq4-tkwmt-o26di-iupkq-vx4kt-asbrx-jzuxh-4ae to replica version [d9fe2076f677a08734bed90c67b1c3f4056ed621](https://dashboard.internetcomputer.org/release/d9fe2076f677a08734bed90c67b1c3f4056ed621)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134443)

Update subnet w4asl to replica version d9fe207 - IcOsVersionDeployment - NNS Id 134443

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Subnet management

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/83)
Hi, my name's **Alex Lorimer** (known neuron [LORIMER](https://forum.dfinity.org/t/known-neuron-proposal-lorimer/33850)). I'm an experienced full-stack Web2 developer who discovered the IC within the last year. I'd like to formally register my application as a **Subnet Management** proposal reviewer. I'm a member of [Synapse](https://www.synapse.vote/voting-members) and [CodeGov](https://www.codegov.org/neuron), and also regularly review TAGGR releases (when I have the time). 

This activity is evident by checking any one of the [IC-OS releases](https://forum.dfinity.org/search?q=release%20rc-2024-%20%23release) over the last few months. My activity is also evident on TAGGR, and has involved identifying a [Severity 1 bug](https://taggr.link/#/post/1159468) among other contributions.

#### Why I'm Applying As An Individual

I'm applying for this topic as an individual reviewer (while I'll still be participating in IC-OS election propopsal reviews as part of CodeGov, as @wpb mentioned above). My motivation for applying as an individual is that I believe the funded time allocation for Subnet Management is too small to be able to make as significant an impact as I'd like (when split multiple ways).

Subnet Management is an important topic that I believe currently suffers from a lack of easily accessible contextual information during the voting process. If I'm selected as a reviewer I'll endeavour to make this job easier by building reporting tools that quickly highlight details that may not otherwise have been obvious. The long-term idea would be to make these tools publicly accessible (once refined) for the sake of greater governance decentralisation. Ideas that I'm toying with are...
- Visualise added/removed nodes (e.g. [fuqsr](https://forum.dfinity.org/t/subnet-management-fuqsr-application/33655/2)) and flag up scenarios that would result in reduced decentralisation (due to an over-represented country, node provider and/or data centre) and automatically verify the proposed nodes are currently unassigned.

- Display version deployments and config updates over time using a Gantt chart format, alongside timeseries data (subnet performance metrics and config values) in order to more easily verify claims made in proposal summaries, and spot potential for unintended consequences based on how other subnets have behaved.
- Visually cluster subnets with similar config, illustrating when a config update proposal would cause a subnet to diverge and/or converge with another *cluster* of subnets.

I believe convenient visibility of the above sorts of information is half the picture. The other half requires a reviewer to keep up-to-date with IC-OS changes (something which I believe puts CodeGov in a very strong position for Subnet Management - few others have put themselves forward for the IC-OS topic). Note that recent downtime events resulted from unintended interactions between IC-OS changes and subnet config (e.g. [System (II)](https://forum.dfinity.org/t/post-mortem-subnet-uzr34-failed-upgrade-process-on-may-13-2024/30895), [System (NNS)](https://forum.dfinity.org/t/june-14th-2024-nns-subnet-incident-retrospective/32198)). Oversight of both in unison is therefore invaluable.

Anyone who's followed my comments on IC-OS releases will know that I think proposal summaries are extremely important, and I reject proposals where these are inaccurate (as a matter of principle). I plan to carry this conviction into Subnet Management proposals. My belief is that the role of a reviewer isn't just to provide a neuron to be followed, but also to facilitate others in making up their own mind. I expect many in the community will take proposal summaries at face value. There's nothing wrong with that so long as others in the community take it upon themselves to validate the accuracy of these summaries, and reject when they are wrong or misleading.

-----

🙏 **Thanks for your time everyone!** I'd also like to say that I'm super excited to see such a turn out for these grants. I'm looking forward to seeing more governance activity on this forum for technical topics 🙌 Whatever the outcome regarding the grants, I'll be happy.

I've recently been creating dedicated [Subnet Management topics](https://forum.dfinity.org/t/subnet-management-fuqsr-application/33655) for each subnet on this forum, and I invite other Subnet Management candidates to engage in discussion on these and share your insights as new proposals emerge 🙂 (and create new topics if one doesn't already exist for the relevant subnet). Good luck everyone!



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131762)

Voting grant application of Alex Lorimer for topic Subnet management - Governance - NNS Id 131762

Release Notes for [**release-2024-08-08\_07-48-base**](https://github.com/dfinity/ic/tree/release-2024-08-08_07-48-base) (94fd38099f0e63950eb5d5673b7b9d23780ace2d)
===================================================================================================================================================================

This release is based on changes since [release-2024-08-02\_01-30-base](https://dashboard.internetcomputer.org/release/3d0b3f10417fc6708e8b5d844a0bac5e86f3e17d) (3d0b3f10417fc6708e8b5d844a0bac5e86f3e17d).

Please note that some commits may be excluded from this release if they're not relevant, or not modifying the GuestOS image. Additionally, descriptions of some changes might have been slightly modified to fit the release notes format.

To see a full list of commits added since last release, compare the revisions on [GitHub](https://github.com/dfinity/ic/compare/release-2024-08-02_01-30-base...release-2024-08-08_07-48-base).

Features:
---------

* [`23af050fb`](https://github.com/dfinity/ic/commit/23af050fb) Crypto,Interface(crypto): Support key derivation in ic\_crypto\_ecdsa\_secp256k1 ([#706](https://github.com/dfinity/ic/pull/706))
* [`951e895c7`](https://github.com/dfinity/ic/commit/951e895c7) Execution,Interface: Handle stable\_read/write with Wasm64 heaps and testing infrastructure ([#781](https://github.com/dfinity/ic/pull/781))
* [`07786ecc4`](https://github.com/dfinity/ic/commit/07786ecc4) Execution,Interface: add allowed\_viewers to canister log visibility management canister types ([#606](https://github.com/dfinity/ic/pull/606))
* [`f116e5713`](https://github.com/dfinity/ic/commit/f116e5713) Execution,Interface: Limit number of snapshots stored per canister ([#726](https://github.com/dfinity/ic/pull/726))
* [`78dca2f91`](https://github.com/dfinity/ic/commit/78dca2f91) Execution,Interface: add support on canister manager for get block headers ([#381](https://github.com/dfinity/ic/pull/381))
* [`c0373c673`](https://github.com/dfinity/ic/commit/c0373c673) Execution,Interface,Message Routing: Parallel dirty page copying for page allocator ([#733](https://github.com/dfinity/ic/pull/733))
* [`2e6584c42`](https://github.com/dfinity/ic/commit/2e6584c42) Interface(nns): Implement the execution of UpdateCanisterSettings proposals ([#731](https://github.com/dfinity/ic/pull/731))
* [`168e5cc2f`](https://github.com/dfinity/ic/commit/168e5cc2f) Interface(ckerc20): NNS proposal to add ckWSTETH ([#612](https://github.com/dfinity/ic/pull/612))
* [`71838e9c1`](https://github.com/dfinity/ic/commit/71838e9c1) Interface,Message Routing: Checkpointing for canister snapshots ([#702](https://github.com/dfinity/ic/pull/702))
* [`2bf9d4463`](https://github.com/dfinity/ic/commit/2bf9d4463) Interface,Message Routing: State layout of canister snapshots ([#645](https://github.com/dfinity/ic/pull/645))

Bugfixes:
---------

* [`799cf9f94`](https://github.com/dfinity/ic/commit/799cf9f94) Consensus,Interface(types): Remove serde derive from ThresholdSigInputRefs ([#760](https://github.com/dfinity/ic/pull/760))
* [`e8a163fda`](https://github.com/dfinity/ic/commit/e8a163fda) Execution,Interface: Fix the return type of some System APIs ([#785](https://github.com/dfinity/ic/pull/785))
* [`82c76c1bb`](https://github.com/dfinity/ic/commit/82c76c1bb) Execution,Interface: Fix a debug assertion in update\_socket\_timeout ([#779](https://github.com/dfinity/ic/pull/779))
* [`8db01a49c`](https://github.com/dfinity/ic/commit/8db01a49c) Execution,Interface: Update heap delta debit and estimate when handling snapshots ([#727](https://github.com/dfinity/ic/pull/727))
* [`83b0fa536`](https://github.com/dfinity/ic/commit/83b0fa536) Execution,Interface,Message Routing: Consider canister snapshots when calculating available subnet memory ([#753](https://github.com/dfinity/ic/pull/753))

Chores:
-------

* [`0a12c4b66`](https://github.com/dfinity/ic/commit/0a12c4b66) Crypto,Interface(crypto): Annotate where parallelism can be used in NIDKG ([#671](https://github.com/dfinity/ic/pull/671))
* [`dae6bbe95`](https://github.com/dfinity/ic/commit/dae6bbe95) Interface: Update visibility of dfn\_\* libraries ([#804](https://github.com/dfinity/ic/pull/804))
* [`80ebdebe5`](https://github.com/dfinity/ic/commit/80ebdebe5) Interface: Update gz references ([#701](https://github.com/dfinity/ic/pull/701))
* [`fc4f2e385`](https://github.com/dfinity/ic/commit/fc4f2e385) Interface(IDX): specify which NNS canisters to use via env vars ([#675](https://github.com/dfinity/ic/pull/675))
* [`b0f4527a2`](https://github.com/dfinity/ic/commit/b0f4527a2) Interface,Networking(http-handler): Only log every 10 second in the call-v3 handler ([#717](https://github.com/dfinity/ic/pull/717))
* [`44a966ec6`](https://github.com/dfinity/ic/commit/44a966ec6) Interface,Networking(http-handler): Add a 1 second timeout when creating a subscriber in call-v3 handler ([#716](https://github.com/dfinity/ic/pull/716))
* [`0bd54a27f`](https://github.com/dfinity/ic/commit/0bd54a27f) Interface,Node: Remove obsolete set-node-id command ([#778](https://github.com/dfinity/ic/pull/778))
* [`4b51b1e23`](https://github.com/dfinity/ic/commit/4b51b1e23) Node: Update Base Image Refs [2024-08-06-0146] ([#765](https://github.com/dfinity/ic/pull/765))

Refactoring:
------------

* [`12e89bb81`](https://github.com/dfinity/ic/commit/12e89bb81) Interface: Migrate more type dependencies to use ic\_nns\_governance\_api ([#628](https://github.com/dfinity/ic/pull/628))

Tests:
------

* [`1a5c96918`](https://github.com/dfinity/ic/commit/1a5c96918) Consensus,Interface(consensus): Add exhaustive serialization->deserialization test for ConsensusMessage ([#795](https://github.com/dfinity/ic/pull/795))
* [`d5511c98e`](https://github.com/dfinity/ic/commit/d5511c98e) Interface,Message Routing: more complex input queues scenario for queue compatibility tests ([#745](https://github.com/dfinity/ic/pull/745))

Documentation:
--------------

* [`192fc1e12`](https://github.com/dfinity/ic/commit/192fc1e12) Node: fix upgrade-install documentation ([#786](https://github.com/dfinity/ic/pull/786))

# IC-OS Verification

To build and verify the IC-OS disk image, run:

```
# From https://github.com/dfinity/ic#verifying-releases
sudo apt-get install -y curl && curl --proto '=https' --tlsv1.2 -sSLO https://raw.githubusercontent.com/dfinity/ic/94fd38099f0e63950eb5d5673b7b9d23780ace2d/gitlab-ci/tools/repro-check.sh && chmod +x repro-check.sh && ./repro-check.sh -c 94fd38099f0e63950eb5d5673b7b9d23780ace2d
```

The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal.


Link to the forum post: https://forum.dfinity.org/t/proposal-to-elect-new-release-rc-2024-08-08-07-48/34014/1

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131697)

Elect new IC/Replica revision (commit 94fd380) - IcOsVersionElection - NNS Id 131697

## Security concerns:

this neuron is owned by the infamous rugger scott summers please transfer its controller to sneed dao to punish him for rugging macdomalds token

11\. What is asked of the community

Sneed it 

- Review comments, ask questions, give feedback

- Vote accept or reject on NNS Motion

Developer forum: https://forum.dfinity.org/t/long-term-r-d-tokenomics-proposal/9392/3

---

This proposal was crafted and submitted with [proposals.network](https://proposals.network) – where ideas meet the ICP governance.

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134364)

Transfer controller of neuron 9545425697310754533 to fp274-iaaaa-aaaaq-aacha-cai - Governance - NNS Id 134364

# Replace a node in subnet pzp6e

Motivation: The node operator `u4f3y` (under NP [spp3m](https://dashboard.internetcomputer.org/provider/spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe)) has 13 nodes in total but currently does not have active nodes in any subnet. To gain insights into the stability of the nodes of this node operator, we propose to add one of the operator's nodes to subnet pzp6e.

Decentralization Nakamoto coefficient changes for subnet `pzp6e-ekpqk-3c5x7-2h6so-njoeq-mt45d-h3h6c-q3mxf-vpeq5-fk5o7-yae`:
```
  node_provider: 12.00 -> 12.00    (+0%)
    data_center: 12.00 -> 12.00    (+0%)
data_center_owner: 12.00 -> 12.00    (+0%)
            area: 9.00 -> 10.00   (+11%)
          country: 5.00 -> 5.00    (+0%)
```

**Mean Nakamoto comparison:** 10.00 -> 10.20  (+2%)

Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 3.2493 to 3.2797


# Details

Nodes removed:
- `jlifv-mddo3-zfwdc-x2wmu-xklbj-dai3i-3pvjy-j4hqm-sarqr-fhkq6-zae` [health: healthy]

Nodes added:
- `rzmf2-bann2-xwd4z-7nyz4-jniay-7lqod-nom4t-yg2lx-tjros-wzzti-7ae` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner              area                             country        
    -------------                                                              -----------            -----------------              ----                             -------        
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    ba1               1    Adam                      1    Barcelona                   1    AU            2
    4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae       1    bg1               1    Africa Data Centres       1    Barreiro                    1    BE            1
    4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae       1    bn1               1    Anonstake                 1    Bogota                      1    CA            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    br2               1    AtlasEdge                 1    Brussels Capital            1    CH            2
    6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe       1    bt1               1    Baltneta                  1    Bucuresti                   1    CO            1
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe       1    bu1               1    Cloud9                    1    Cape Town                   1    CR            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    ch3               1    CyrusOne                  1    Colombo                     1    CZ            1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    cm1               1    Cyxtera                   1    Florida                     1    ES            1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe       1    cr1               1    DEAC                      1    Gauteng                2 -> 1    GE            1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    ct2               1    Datasite                  1    Geneva                      1    HK            2
    cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe       1    es1               1    Digital Realty            1    Greater Noida               1    HR            1
    cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe       1    ge2               1    Dotsi                     1    HongKong                    2    IN            3
    diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe       1    gn1               1    EdgeUno                   1    Illinois                    1    JP            1
    efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe       1    hk3               1    Equinix                   1    Lisbon                      1    KR            2
    eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe       1    hk4               1    Green.ch                  1    Ljubljana                   1    LK            1
    i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe       1    jb2               1    KT                        1    Navi Mumbai                 1    LT            1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    jb3          1 -> 0    Latitude.sh               1    New Delhi                   1    LV            1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae       1    kr1               1    M247                      1    New South Wales             1    PT            2
    izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe       1    li1               1    Marvelous Web3 DC         1    New York               0 -> 1    RO            1
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    lj1               1    Master Internet           1    Ontario                     1    SE            1
    mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe       1    nd1               1    Megazone Cloud            1    Queensland                  1    SG            1
    mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae  1 -> 0    nm1               1    NEXTDC                    1    Riga                        1    SI            1
    nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae       1    ns1               1    Navegalo                  1    San Jose                    1    US       2 -> 3
    otzuu-dldzs-avvu2-qwowd-hdj73-aocy7-lacgi-carzj-m6f2r-ffluy-fae       1    ny1          0 -> 1    Online                    1    Seoul                       2    ZA       3 -> 2
    py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe       1    or1               1    OrionStellar              1    Singapore                   1                   
    qsdw4-ao5ye-6rtq4-y3zhm-icjbj-lutd2-sbejz-4ajqz-pcflr-xrhsg-jae       1    rg1               1    Posita.si                 1    South Moravian Region       1                   
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae       1    sc1               1    Rivram                    1    Stockholm                   1                   
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    sg1               1    SafeHost                  1    Tbilisi                     1                   
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sh1               1    Telin                     1    Tokyo                       1                   
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe  0 -> 1    sl1               1    Teraco                    1    Vilnius                     1                   
    ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae       1    tb1               1    Tierpoint            0 -> 1    Zagreb                      1                   
    unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe       1    to2               1    Xneelo               1 -> 0    Zurich                      1                   
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    ty2               1    Yotta                     1                                                    
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    zg1               1    hkcolo                    1                                                    
    wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae       1    zh6               1    hkntt                     1                                                    
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-pzp6e/38509


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134403)

Replace a node in subnet pzp6e - SubnetManagement - NNS Id 134403

# Replace a node in subnet x33ed

Motivation: The node operator `nhr3z` (under NP [trxbq](https://dashboard.internetcomputer.org/provider/trxbq-wy5xi-3y27q-bkpaf-mhi2m-puexs-yatgt-nhwiy-dh6jy-rolw5-zqe)) has 3 nodes in total but currently does not have active nodes in any subnet. To gain insights into the stability of the nodes of this node operator, we propose to add one of the operator's nodes to subnet x33ed.

Decentralization Nakamoto coefficient changes for subnet `x33ed-h457x-bsgyx-oqxqf-6pzwv-wkhzr-rm2j3-npodi-purzm-n66cg-gae`:
```
  node_provider: 12.00 -> 12.00    (+0%)
    data_center: 12.00 -> 12.00    (+0%)
data_center_owner: 12.00 -> 12.00    (+0%)
           area: 10.00 -> 11.00   (+10%)
          country: 5.00 -> 5.00    (+0%)
```

**Mean Nakamoto comparison:** 10.20 -> 10.40  (+2%)

Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 3.2797 to 3.3072


# Details

Nodes removed:
- `yikms-ku6l6-3brmt-a7wji-oizgc-gopwj-my4wn-y2nsq-mjq6q-acuaw-7ae` [health: healthy]

Nodes added:
- `ct3c3-aaohu-xben4-mbsjf-evtcb-bvf4i-qax6r-i4lm2-tcn6j-ybqpz-wae` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner              area                                  country        
    -------------                                                              -----------            -----------------              ----                                  -------        
    3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae       1    an1               1    Africa Data Centres       1    Bogota                           1    AU            2
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    at2               1    Anonstake                 1    Bucuresti                        1    BE            1
    4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae       1    bg1               1    Baltneta                  1    Cape Town                        1    CA            2
    4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae       1    bn1               1    Celeste                   1    Colombo                          1    CH       3 -> 2
    64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe       1    bt1               1    Cloud9                    1    Flanders                         1    CO            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    bu1               1    Coolhousing               1    Florida                          1    CZ            2
    6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe  1 -> 0    cm1               1    Cyxtera                   1    Gauteng                          2    EE            1
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe       1    ct1               1    DataHouse                 1    Geneva                           1    ES            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    dr1          0 -> 1    Datacenter United         1    Georgia                          1    FR            2
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    ge2               1    Datasite                  1    Greater Noida                    1    GE            1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe       1    gn1               1    Digital Realty            1    HongKong                         1    HK            1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    hk4               1    EdgeUno                   1    Ljubljana                        1    IL            1
    cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe       1    jb1               1    Equinix                   1    Madrid                           1    IN            2
    dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae       1    jb3               1    FiberState           0 -> 1    Maribor                          1    JP            1
    efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe       1    jv1               1    Ginernet                  1    Melbourne                        1    KR            1
    eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe       1    lj2               1    Green.ch             1 -> 0    Navi Mumbai                      1    LK            1
    i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe       1    ma1               1    InfonetDC                 1    New South Wales                  1    LT            1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    mb1               1    Interhost                 1    Ontario                          1    PL            1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    mn2               1    Latitude.sh               1    Paris                            1    RO            1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae       1    mr1               1    Leaseweb                  1    Praha                            1    SG            1
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    mtl1              1    M247                      1    Provence-Alpes-Cote d'Azur       1    SI            2
    mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae       1    nm1               1    Master Internet           1    Quebec                           1    US       2 -> 3
    optdi-nwa4m-hly3k-6ua4n-sqyxf-yahvb-wps77-ddayn-r7zcz-edla5-7qe       1    ns1               1    Megazone Cloud            1    Seoul                            1    ZA            3
    otzuu-dldzs-avvu2-qwowd-hdj73-aocy7-lacgi-carzj-m6f2r-ffluy-fae       1    pa2               1    NEXTDC                    1    Singapore                        1                   
    qsdw4-ao5ye-6rtq4-y3zhm-icjbj-lutd2-sbejz-4ajqz-pcflr-xrhsg-jae       1    pr1               1    Nine.Ch                   1    South Moravian Region            1                   
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    sg3               1    OrionStellar              1    Tallinn                          1                   
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sl1               1    Posita.si                 1    Tbilisi                          1                   
    sma3p-ivkif-hz7nu-ngmvq-ibnjg-nubke-zf6gh-wbnfc-2dlng-l3die-zqe       1    ta1               1    Racks Central             1    Tel Aviv                         1                   
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe       1    tb1               1    Rivram                    1    Tokyo                            1                   
    trxbq-wy5xi-3y27q-bkpaf-mhi2m-puexs-yatgt-nhwiy-dh6jy-rolw5-zqe  0 -> 1    to1               1    SafeHost                  1    Utah                        0 -> 1                   
    ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae       1    tv1               1    Teraco                    1    Vilnius                          1                   
    ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae       1    ty2               1    Tierpoint                 1    Warszawa                         1                   
    unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe       1    wa3               1    Xneelo                    1    Zurich                      2 -> 1                   
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    zh4               1    Yotta                     1                                                         
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    zh7          1 -> 0    hkntt                     1                                                         
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-x33ed/38507


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134401)

Replace a node in subnet x33ed - SubnetManagement - NNS Id 134401

# Replace a node in subnet io67a

Motivation: The node operator qaes5 (under NP [eatbv](https://dashboard.internetcomputer.org/provider/eatbv-nlydd-n655c-g7j7p-gnmpz-pszdg-6e6et-veobv-ftz2y-4m752-vqe)) has 4 nodes in total and currently has all nodes assigned to subnets. We propose to remove one of the operator's nodes from subnet io67a to allow optimization of the overall network topology. The removal of the node from the subnet does not worsen subnet decentralization, and may allow the node to be assigned to subnet where it would improve decentralization.

Decentralization Nakamoto coefficient changes for subnet `io67a-2jmkw-zup3h-snbwi-g6a5n-rm5dn-b6png-lvdpl-nqnto-yih6l-gqe`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 5.00 -> 5.00    (+0%)
```

**Mean Nakamoto comparison:** 5.00 -> 5.00  (+0%)

Overall replacement impact: equal decentralization across all features


# Details

Nodes removed:
- `2xph2-xvn4v-pc5xz-3upfj-etpio-qaf2k-d2s3v-jnceu-vcher-qhqav-rqe` [health: healthy]

Nodes added:
- `llbvn-f4hq5-tg7bl-tdvr7-zs2cb-7uwfz-dhshp-aaomw-urgqo-gyll2-tqe` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner              area                        country        
    -------------                                                              -----------            -----------------              ----                        -------        
    3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae       1    bc1               1    Africa Data Centres       1    British Columbia       1    AU            1
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae  0 -> 1    bo1               1    Anonstake                 1    Brussels Capital       1    BE            1
    64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe       1    br1               1    Cloud9                    1    Cape Town              1    CA            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    ct1               1    Cyxtera                   1    HongKong               1    CH            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    hk4               1    DEAC                      1    Ljubljana              1    GE            1
    eatbv-nlydd-n655c-g7j7p-gnmpz-pszdg-6e6et-veobv-ftz2y-4m752-vqe  1 -> 0    lj2               1    Digital Realty            1    Massachusetts          1    HK            1
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    pc1          1 -> 0    Equinix                   1    Panama City       1 -> 0    JP            1
    lq5ra-f4ibl-t7wpy-hennc-m4eb7-tnfxe-eorgd-onpsl-wervo-7chjj-6qe       1    rg1               1    INAP                      1    Queensland             1    KR       0 -> 1
    optdi-nwa4m-hly3k-6ua4n-sqyxf-yahvb-wps77-ddayn-r7zcz-edla5-7qe       1    sc1               1    Megazone Cloud       0 -> 1    Riga                   1    LV            1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    sg3               1    NEXTDC                    1    Seoul             0 -> 1    PA       1 -> 0
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sl1          0 -> 1    Navegalo             1 -> 0    Singapore              1    SG            1
    ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae       1    tb1               1    Nine.Ch                   1    Tbilisi                1    SI            1
    unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe       1    ty2               1    Racks Central             1    Tokyo                  1    US            1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    zh4               1    hkntt                     1    Zurich                 1    ZA            1
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-io67a/38511


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134405)

Replace a node in subnet io67a - SubnetManagement - NNS Id 134405

# Replace a node in subnet mpubz

Motivation: The following nodes in subnet `mpubz` have been cordoned and will be removed:
- dafyf: offboarding CH3 DC after 48 months; https://forum.dfinity.org/t/proposal-update-interim-gen-1-node-provider-remuneration-after-48-months/35001/16

Decentralization Nakamoto coefficient changes for subnet `mpubz-g52jc-grhjo-5oze5-qcj74-sex34-omprz-ivnsm-qvvhr-rfzpv-vae`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 4.00 -> 4.00    (+0%)
```

**Mean Nakamoto comparison:** 4.80 -> 4.80  (+0%)

Overall replacement impact: equal decentralization across all features


# Details

Nodes removed:
- `dafyf-uvzhi-ypecj-c6ujq-e7aae-m6y2m-5f4pp-v64pz-lfebd-awmre-cqe` [health: healthy]

Nodes added:
- `ad6tc-euwqd-mflr6-rwpc5-pfhvn-vqrq2-oyula-2vdkb-c7bsn-gdrkk-uae` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner            area                        country   
    -------------                                                              -----------            -----------------            ----                        -------   
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    br2               1    AtlasEdge               1    Brussels Capital       1    AU       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    bu1               1    CyrusOne           1 -> 0    Bucuresti              1    BE       1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    ch3          1 -> 0    Cyxtera                 1    Florida           0 -> 1    CA       1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    fr2               1    Datasite           0 -> 1    Geneva                 1    CH       2
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    ge1               1    Digital Realty          1    Hesse                  1    DE       1
    g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe       1    hk1               1    Equinix                 1    HongKong               1    HK       1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    mb1               1    HighDC                  1    Illinois          1 -> 0    KR       1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    mn2               1    M247                    1    Maribor                1    RO       1
    izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe  1 -> 0    or1          0 -> 1    Megazone Cloud          1    Melbourne              1    SE       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    sg3               1    NEXTDC                  1    Ontario                1    SG       1
    ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae       1    sh1               1    Nine.Ch                 1    Seoul                  1    SI       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    sl1               1    Posita.si               1    Singapore              1    US       1
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae       1    to2               1    Racks Central           1    Stockholm              1              
    wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae  0 -> 1    zh4               1    Unicom                  1    Zurich                 1              
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-mpubz/38515


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134409)

Replace a node in subnet mpubz - SubnetManagement - NNS Id 134409

# Replace a node in subnet jtdsg

Motivation: The following nodes in subnet `jtdsg` have been cordoned and will be removed:
- 637ii: NP is selling the PL1 DC after 48 months; https://forum.dfinity.org/t/subnet-management-general-discussion/34091/110

Decentralization Nakamoto coefficient changes for subnet `jtdsg-3h6gi-hs7o5-z2soi-43w3z-soyl3-ajnp3-ekni5-sw553-5kw67-nqe`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 5.00 -> 5.00    (+0%)
```

**Mean Nakamoto comparison:** 5.00 -> 5.00  (+0%)

Overall replacement impact: equal decentralization across all features


# Details

Nodes removed:
- `637ii-3bf4g-arp6y-a64q2-memci-bszoe-vqykw-4smuy-pew4q-bkg4j-oae` [health: healthy]

Nodes added:
- `46qvk-mdby5-dbzf3-mpwtq-axasp-rkf37-wawoc-7edbb-drt46-oq3xy-vae` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner            area                        country   
    -------------                                                              -----------            -----------------            ----                        -------   
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    br1               1    Anonstake               1    Brussels Capital       1    AU       1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    bu1               1    Cyxtera                 1    Bucuresti              1    BE       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    ct2               1    Datasite           0 -> 1    Cape Town              1    CA       1
    dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae       1    hk1               1    Digital Realty          1    Florida           0 -> 1    CH       1
    eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe  1 -> 0    lj1               1    Equinix                 1    HongKong               1    HK       1
    g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe       1    or1          0 -> 1    Everyware               1    Ljubljana              1    HR       1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    pl1          1 -> 0    Flexential         1 -> 0    Ontario                1    JP       1
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    rg3               1    M247                    1    Oregon            1 -> 0    LV       1
    py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe       1    sc1               1    NEXTDC                  1    Queensland             1    RO       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    sg3               1    Nano                    1    Riga                   1    SG       1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    to2               1    Posita.si               1    Singapore              1    SI       1
    unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe       1    ty3               1    Racks Central           1    Tokyo                  1    US       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    zg1               1    Teraco                  1    Zagreb                 1    ZA       1
    wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae  0 -> 1    zh2               1    Unicom                  1    Zurich                 1              
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-jtdsg/38514


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134407)

Replace a node in subnet jtdsg - SubnetManagement - NNS Id 134407

# Replace a node in subnet o3ow2

Motivation: The node operator 5p6xp (under NP [s5nvr](https://dashboard.internetcomputer.org/provider/s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae)) has 4 nodes in total and currently has all nodes assigned to subnets. We propose to remove one of the operator's nodes from subnet o3ow2 to allow optimization of the overall network topology. The removal of the node from the subnet does not worsen subnet decentralization, and may allow the node to be assigned to subnet where it would improve decentralization.

Decentralization Nakamoto coefficient changes for subnet `o3ow2-2ipam-6fcjo-3j5vt-fzbge-2g7my-5fz2m-p4o2t-dwlc4-gt2q7-5ae`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 5.00 -> 5.00    (+0%)
```

**Mean Nakamoto comparison:** 5.00 -> 5.00  (+0%)

Overall replacement impact: equal decentralization across all features


# Details

Nodes removed:
- `5resh-f6n7z-xxkbq-7lpod-spptk-nyt7n-tcvf6-f5ecb-ixxwc-6k5ai-rqe` [health: healthy]

Nodes added:
- `h3g2z-jgfid-7hvbw-jyfw7-4jiza-iyy4w-bvx44-nizgh-kct53-ffjtz-lae` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner                                    area                                  country        
    -------------                                                              -----------            -----------------                                    ----                                  -------        
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    an1               1    Africa Data Centres                             1    CABA                        1 -> 0    AR       1 -> 0
    4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae       1    ar1          1 -> 0    Cloud9                                          1    Flanders                         1    AU            1
    6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe  0 -> 1    ch2               1    Cyxtera                                         1    Gauteng                          1    BE            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    hk3               1    Datacenter United                               1    HongKong                         1    CA            1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    jb2               1    Digital Realty                                  1    Illinois                         1    CH       0 -> 1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    mb1               1    Equinix                                         1    Maribor                          1    FR            1
    nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae       1    mn2               1    Green.ch                                   0 -> 1    Melbourne                        1    GE            1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    mr1               1    Megazone Cloud                                  1    Navi Mumbai                      1    HK            1
    s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae  1 -> 0    nm1               1    NEXTDC                                          1    Ontario                          1    IN            1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sl1               1    Posita.si                                       1    Provence-Alpes-Cote d'Azur       1    JP            1
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe       1    tb1               1    Rivram                                          1    Seoul                            1    KR            1
    ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae       1    to2               1    SyT - Servicios y Telecomunicaciones S.A.  1 -> 0    Tbilisi                          1    SI            1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    ty1               1    Tierpoint                                       1    Tokyo                            1    US            1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    zh6          0 -> 1    hkcolo                                          1    Zurich                      0 -> 1    ZA            1
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-o3ow2/38510


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134404)

Replace a node in subnet o3ow2 - SubnetManagement - NNS Id 134404

# Replace a node in subnet uzr34

Motivation: The node operator `bmlhw` (under NP [wwdbq](https://dashboard.internetcomputer.org/provider/wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae)) has 14 nodes in total but currently does not have active nodes in any subnet. To gain insights into the stability of the nodes of this node operator, we propose to add one of the operator's nodes to subnet uzr34.

Decentralization Nakamoto coefficient changes for subnet `uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe`:
```
  node_provider: 11.00 -> 11.00    (+0%)
    data_center: 11.00 -> 11.00    (+0%)
data_center_owner: 11.00 -> 11.00    (+0%)
           area: 11.00 -> 11.00    (+0%)
          country: 7.00 -> 7.00    (+0%)
```

**Mean Nakamoto comparison:** 10.20 -> 10.20  (+0%)

Overall replacement impact: equal decentralization across all features


# Details

Nodes removed:
- `z5a4h-43szy-vvp4j-xorii-l6yma-4iyzt-7o3ry-frvqe-azkit-5iag2-rqe` [health: healthy]

Nodes added:
- `vqucp-jq7oa-t3iwb-hdfmp-n7zer-futce-i7rmw-23e6i-ketsi-m6gnb-iqe` [health: healthy]


```
    node_provider                                                         data_center            data_center_owner                               area                             country   
    -------------                                                         -----------            -----------------                               ----                             -------   
    4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae  1    an1               1    Anonstake                                  1    Bogota                      1    AR       1
    4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae  1    ar1               1    Celeste                                    1    Bucuresti                   1    AU       1
    64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe  1    at2          0 -> 1    Cloud9                                     1    CABA                        1    BE       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe  1    bg1               1    CyrusOne                                   1    Cape Town                   1    CA       1
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe  1    bn1               1    Cyxtera                                    1    Colombo                     1    CH       1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae  1    bu1               1    DEAC                                       1    Flanders                    1    CO       1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe  1    ch3               1    Datacenter United                          1    Florida                1 -> 0    CZ       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe  1    cm1               1    Datasite                                   1    Gauteng                     1    EE       1
    diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe  1    ct2               1    Digital Realty                             1    Georgia                0 -> 1    ES       1
    eatbv-nlydd-n655c-g7j7p-gnmpz-pszdg-6e6et-veobv-ftz2y-4m752-vqe  1    hk1               1    EdgeUno                                    1    HongKong                    1    FR       1
    eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe  1    jb3               1    Equinix                                    1    Illinois                    1    GE       1
    fwnmn-zn7yt-5jaia-fkxlr-dzwyu-keguq-npfxq-mc72w-exeae-n5thj-oae  1    kr2               1    Gasan                                      1    Ljubljana                   1    HK       1
    i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe  1    ld1               1    Ginernet                                   1    London                      1    HR       1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae  1    lj1               1    Interhost                                  1    Madrid                      1    IL       1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae  1    ma1               1    Latitude.sh                                1    Navi Mumbai                 1    IN       3
    izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe  1    nd1               1    M247                                       1    New Delhi                   1    JP       1
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae  1    nm1               1    Marvelous Web3 DC                          1    Ontario                     1    KR       1
    mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae  1    or1          1 -> 0    Master Internet                            1    Panama City                 1    LK       1
    otzuu-dldzs-avvu2-qwowd-hdj73-aocy7-lacgi-carzj-m6f2r-ffluy-fae  1    pc1               1    NEXTDC                                     1    Panvel                      1    LV       1
    py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe  1    pl2               1    Navegalo                                   1    Paris                       1    PA       1
    qsdw4-ao5ye-6rtq4-y3zhm-icjbj-lutd2-sbejz-4ajqz-pcflr-xrhsg-jae  1    pr1               1    Nine.Ch                                    1    Queensland                  1    RO       1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae  1    rg1               1    OrionStellar                               1    Riga                        1    SE       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae  1    sc1               1    Posita.si                                  1    Seoul                       1    SG       1
    s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae  1    sg2               1    Rivram                                     1    Singapore                   1    SI       1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae  1    sh1               1    SyT - Servicios y Telecomunicaciones S.A.  1    South Moravian Region       1    UK       1
    ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae  1    ta2               1    Telia DC                                   1    Stockholm                   1    US       2
    ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae  1    tb1               1    Telin                                      1    Tallinn                     1    ZA       2
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe  1    to1               1    Teraco                                     1    Tbilisi                     1              
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae  1    tv1               1    Unicom                                     1    Tel Aviv                    1              
    wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae  1    ty1               1    Xneelo                                     1    Tokyo                       1              
    zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae  1    zg1               1    Yotta                                      1    Zagreb                      1              
                                                                          zh3               1                                                    Zurich                      1              
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-uzr34/38506


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134400)

Replace a node in subnet uzr34 - SubnetManagement - NNS Id 134400

# Replace a node in subnet 3hhby

Motivation: The node operator `eikix` (under NP [ks7ow](https://dashboard.internetcomputer.org/provider/ks7ow-zvs7i-ratdk-azq34-zio2b-gbekj-qjicg-pfhp3-ovhgu-k5qql-dae)) has 26 nodes in total but currently does not have active nodes in any subnet. To gain insights into the stability of the nodes of this node operator, we propose to add one of the operator's nodes to subnet 3hhby.

Decentralization Nakamoto coefficient changes for subnet `3hhby-wmtmw-umt4t-7ieyg-bbiig-xiylg-sblrt-voxgt-bqckd-a75bf-rqe`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 4.00 -> 4.00    (+0%)
```

**Mean Nakamoto comparison:** 4.80 -> 4.80  (+0%)

Overall replacement impact: equal decentralization across all features


# Details

Nodes removed:
- `ega5w-ekfo7-lejfc-fve6j-vnml3-2nmxj-flw2p-564o4-rhier-bz73x-aae` [health: healthy]

Nodes added:
- `5u6dm-zixbp-mbblj-xc7en-hsc7i-upw4t-3dzyb-63tfg-h3f5p-3q3b5-4qe` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner            area                     country        
    -------------                                                              -----------            -----------------            ----                     -------        
    4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae       1    an1               1    Anonstake               1    Bucuresti           1    AU            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    bt1               1    Baltneta                1    California     0 -> 1    BE            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    bu1               1    CyrusOne                1    Flanders            1    CA            1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe  1 -> 0    ch3               1    Cyxtera                 1    Geneva         1 -> 0    CH       2 -> 1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    fr2               1    DEAC                    1    Greater Noida       1    DE            1
    cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe       1    ge2          1 -> 0    Datacenter United       1    Hesse               1    IN            1
    diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe       1    gn1               1    Digital Realty     0 -> 1    Illinois            1    LT            1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    lj2               1    Equinix                 1    Ljubljana           1    LV            1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    mn2               1    Everyware               1    Melbourne           1    RO            1
    izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe       1    rg1               1    M247                    1    Ontario             1    SG            1
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    sg1               1    NEXTDC                  1    Riga                1    SI            1
    ks7ow-zvs7i-ratdk-azq34-zio2b-gbekj-qjicg-pfhp3-ovhgu-k5qql-dae  0 -> 1    sj2          0 -> 1    SafeHost           1 -> 0    Singapore           1    US       1 -> 2
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    to2               1    Telin                   1    Vilnius             1                   
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae       1    zh2               1    Yotta                   1    Zurich              1                   
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-3hhby/38512


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134406)

Replace a node in subnet 3hhby - SubnetManagement - NNS Id 134406

Update subnet lhg73-sax6z-2zank-6oer2-575lz-zgbxx-ptudx-5korm-fy7we-kh4hl-pqe to replica version [3e24396441e4c7380928d4e8b4ccff7de77d0e7e](https://dashboard.internetcomputer.org/release/3e24396441e4c7380928d4e8b4ccff7de77d0e7e)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134512)

Update subnet lhg73 to replica version 3e24396 - IcOsVersionDeployment - NNS Id 134512

Update subnet k44fs-gm4pv-afozh-rs7zw-cg32n-u7xov-xqyx3-2pw5q-eucnu-cosd4-uqe to replica version [3e24396441e4c7380928d4e8b4ccff7de77d0e7e](https://dashboard.internetcomputer.org/release/3e24396441e4c7380928d4e8b4ccff7de77d0e7e)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134511)

Update subnet k44fs to replica version 3e24396 - IcOsVersionDeployment - NNS Id 134511

# Replace a node in subnet pae4o

Motivation: The following nodes in subnet `pae4o` have been cordoned and will be removed:
- q2gfr: NP is selling the PL1 DC after 48 months; https://forum.dfinity.org/t/subnet-management-general-discussion/34091/110

Decentralization Nakamoto coefficient changes for subnet `pae4o-o6dxf-xki7q-ezclx-znyd6-fnk6w-vkv5z-5lfwh-xym2i-otrrw-fqe`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 3.00 -> 3.00    (+0%)
```

**Mean Nakamoto comparison:** 4.60 -> 4.60  (+0%)

Overall replacement impact: equal decentralization across all features


# Details

Nodes removed:
- `q2gfr-yfiod-ohoo3-czlr4-ghfbs-bp7pr-zefjc-gbpyy-lfg4y-etedq-lqe` [health: healthy]

Nodes added:
- `owedb-225ie-3nagr-r7p27-jbwtd-745nr-rl5nh-qka5h-adlww-uu33p-oqe` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner            area                 country   
    -------------                                                              -----------            -----------------            ----                 -------   
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    an1               1    Anonstake               1    Flanders        1    AU       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    ge1               1    Datacenter United       1    Florida    0 -> 1    BE       1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    hk1               1    Datasite           0 -> 1    Gauteng         1    CH       2
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    jb1               1    Digital Realty          1    Geneva          1    HK       1
    eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe  1 -> 0    lj2               1    Equinix                 1    HongKong        1    JP       1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    mb1               1    Flexential         1 -> 0    Ljubljana       1    KR       1
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    mn2               1    HighDC                  1    Maribor         1    SE       1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae       1    or1          0 -> 1    Megazone Cloud          1    Melbourne       1    SG       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    pl1          1 -> 0    NEXTDC                  1    Oregon     1 -> 0    SI       2
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sg3               1    Nine.Ch                 1    Seoul           1    US       1
    ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae       1    sh1               1    Posita.si               1    Singapore       1    ZA       1
    unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe       1    sl1               1    Racks Central           1    Stockholm       1              
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    ty2               1    Teraco                  1    Tokyo           1              
    wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae  0 -> 1    zh4               1    Unicom                  1    Zurich          1              
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-pae4o/38517


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134411)

Replace a node in subnet pae4o - SubnetManagement - NNS Id 134411

# Replace a node in subnet nl6hn

Motivation: The following nodes in subnet `nl6hn` have been cordoned and will be removed:
- 5hpo7: NP is selling the PL1 DC after 48 months; https://forum.dfinity.org/t/subnet-management-general-discussion/34091/110

Decentralization Nakamoto coefficient changes for subnet `nl6hn-ja4yw-wvmpy-3z2jx-ymc34-pisx3-3cp5z-3oj4a-qzzny-jbsv3-4qe`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 3.00 -> 4.00   (+33%)
```

**Mean Nakamoto comparison:** 4.60 -> 4.80  (+4%)

Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.1745 to 2.2575


# Details

Nodes removed:
- `5hpo7-g35qx-gomzb-ev6u4-uuhmm-mx3vz-dtx6z-ey7jc-bgzgw-hhv2i-sae` [health: healthy]

Nodes added:
- `6bt7p-6zrhd-xi3rj-jsugy-c6qzy-nvip5-7thap-gk6po-ygo5h-mh4jk-tae` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner            area                     country        
    -------------                                                              -----------            -----------------            ----                     -------        
    64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe       1    an1               1    Cyxtera                 1    Flanders            1    AU       0 -> 1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    fr2               1    Datacenter United       1    Florida             1    BE            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    ge2               1    Digital Realty          1    Geneva              1    CA            1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    gn1               1    Equinix                 1    Greater Noida       1    CH            2
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    hk4               1    Flexential         1 -> 0    Hesse               1    DE            1
    cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe       1    jv1               1    Gasan                   1    HongKong            1    HK            1
    cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe       1    kr2               1    NEXTDC             0 -> 1    Ljubljana           1    IN            1
    eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe  1 -> 0    lj1               1    Nine.Ch                 1    Melbourne      0 -> 1    KR            1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe  0 -> 1    mn2          0 -> 1    Posita.si               1    Ontario             1    SE            1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    pl1          1 -> 0    SafeHost                1    Oregon         1 -> 0    SG            1
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe       1    sg1               1    Telin                   1    Seoul               1    SI            1
    ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae       1    sh1               1    Tierpoint               1    Singapore           1    US       2 -> 1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    to1               1    Yotta                   1    Stockholm           1                   
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae       1    zh4               1    hkntt                   1    Zurich              1                   
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-nl6hn/38516


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134410)

Replace a node in subnet nl6hn - SubnetManagement - NNS Id 134410

Release Notes for [**release\-2024\-12\-06\_03\-16\-base**](https://github.com/dfinity/ic/tree/release-2024-12-06_03-16-base) (d9fe2076f677a08734bed90c67b1c3f4056ed621\)
=========================================================================================================================================================================

This release is based on changes since [release\-2024\-11\-28\_03\-15\-base](https://dashboard.internetcomputer.org/release/2d8611eb4efa8e69c4dd567546c1c353a545e0a6) (2d8611eb4efa8e69c4dd567546c1c353a545e0a6\).

Please note that some commits may be excluded from this release if they're not relevant, or not modifying the GuestOS image. Additionally, descriptions of some changes might have been slightly modified to fit the release notes format.

To see a full list of commits added since last release, compare the revisions on [GitHub](https://github.com/dfinity/ic/compare/release-2024-11-28_03-15-base...release-2024-12-06_03-16-base).

Features:
---------

* [`ad36e6b0d`](https://github.com/dfinity/ic/commit/ad36e6b0d) Consensus,Interface: make orchestrator load env vars for ic\-boundary ([\#2879](https://github.com/dfinity/ic/pull/2879))
* [`af2605ffb`](https://github.com/dfinity/ic/commit/af2605ffb) Crypto,Interface,Node: discard for data partition ([\#2953](https://github.com/dfinity/ic/pull/2953))
* [`8ec2ca18b`](https://github.com/dfinity/ic/commit/8ec2ca18b) Execution,Interface: Enable tail\_call in wasmtime. ([\#2826](https://github.com/dfinity/ic/pull/2826))
* [`a2a6247f8`](https://github.com/dfinity/ic/commit/a2a6247f8) Interface(crypto): Add support for BIP341 Taproot signatures ([\#2523](https://github.com/dfinity/ic/pull/2523))
* [`8d726cc67`](https://github.com/dfinity/ic/commit/8d726cc67) Interface(ICRC\-ledger): Implement V3 for ICRC ledger \- migrate allowances to stable structures ([\#1513](https://github.com/dfinity/ic/pull/1513))
* [`bed178d77`](https://github.com/dfinity/ic/commit/bed178d77) Interface,Message Routing: Add various subnet info metrics ([\#2969](https://github.com/dfinity/ic/pull/2969))
* [`e41a4efb7`](https://github.com/dfinity/ic/commit/e41a4efb7) Interface,Message Routing: More latency metrics ([\#2905](https://github.com/dfinity/ic/pull/2905))
* [`b6e0faa05`](https://github.com/dfinity/ic/commit/b6e0faa05) Interface,Node(node): update\-config.service ([\#2393](https://github.com/dfinity/ic/pull/2393))
* [`8a538aac7`](https://github.com/dfinity/ic/commit/8a538aac7) Owners(IDX): Force static link of lmdb ([\#2941](https://github.com/dfinity/ic/pull/2941))
* [`ee08c5875`](https://github.com/dfinity/ic/commit/ee08c5875) Node: Create and use a faster alternative to prestorecon ([\#2980](https://github.com/dfinity/ic/pull/2980))

Bugfixes:
---------

* [`bd92560a7`](https://github.com/dfinity/ic/commit/bd92560a7) Execution,Interface(crypto): Fix the management canister interface for Schnorr aux inputs ([\#2952](https://github.com/dfinity/ic/pull/2952))
* [`05f660259`](https://github.com/dfinity/ic/commit/05f660259) Interface(BOUN): Integrate log anonymization into ic\-boundary ([\#2665](https://github.com/dfinity/ic/pull/2665))
* [`1368f04cc`](https://github.com/dfinity/ic/commit/1368f04cc) Interface(EXC): Make expensive debug assert conditional ([\#2820](https://github.com/dfinity/ic/pull/2820))
* [`df6e86ced`](https://github.com/dfinity/ic/commit/df6e86ced) Interface,Node: Revert from 24\.04 build container ([\#2951](https://github.com/dfinity/ic/pull/2951))
* [`23d181e50`](https://github.com/dfinity/ic/commit/23d181e50) Interface,Node: Update Elasticsearch URLs and index patterns for testnet environment ([\#2888](https://github.com/dfinity/ic/pull/2888))
* [`4158ba727`](https://github.com/dfinity/ic/commit/4158ba727) Node: Fixup colliding permission services ([\#2933](https://github.com/dfinity/ic/pull/2933))

Performance improvements:
-------------------------

* [`796a29be6`](https://github.com/dfinity/ic/commit/796a29be6) Interface,Message Routing: Copy outside write lock ([\#2963](https://github.com/dfinity/ic/pull/2963))

Chores:
-------

* [`05c96cbd1`](https://github.com/dfinity/ic/commit/05c96cbd1) Execution,Interface: Rename IDKG test functions and struct fields in Network and SubnetTopology ([\#2741](https://github.com/dfinity/ic/pull/2741))
* [`57dc741a9`](https://github.com/dfinity/ic/commit/57dc741a9) Interface: Remove deprecated scenario tests ([\#2866](https://github.com/dfinity/ic/pull/2866))
* [`b3ab4bf9a`](https://github.com/dfinity/ic/commit/b3ab4bf9a) Interface,Networking: merge infallible errors, improve expect statements and use {:\#?} for anyhow error formatting ([\#2964](https://github.com/dfinity/ic/pull/2964))
* [`a8d210455`](https://github.com/dfinity/ic/commit/a8d210455) Interface,Networking: split out parsing the read state response into a separate create ([\#2899](https://github.com/dfinity/ic/pull/2899))
* [`3466a3205`](https://github.com/dfinity/ic/commit/3466a3205) Owners(IDX): Use pigz from Bazel Central Registry ([\#2945](https://github.com/dfinity/ic/pull/2945))
* [`9f5674ce6`](https://github.com/dfinity/ic/commit/9f5674ce6) Node: Update Base Image Refs \[2024\-12\-05\-0808] ([\#2982](https://github.com/dfinity/ic/pull/2982))
* [`2a400f53b`](https://github.com/dfinity/ic/commit/2a400f53b) Node: Update Base Image Refs \[2024\-11\-28\-1813] ([\#2887](https://github.com/dfinity/ic/pull/2887))

Refactoring:
------------

* [`0ab07de46`](https://github.com/dfinity/ic/commit/0ab07de46) Interface: Rename idkg\_subnet\_public\_keys in Consensus and Execution ([\#2817](https://github.com/dfinity/ic/pull/2817))
* [`006709366`](https://github.com/dfinity/ic/commit/006709366) Interface,Networking: small improvement on error handling in transport ([\#2878](https://github.com/dfinity/ic/pull/2878))
* [`697c20ccd`](https://github.com/dfinity/ic/commit/697c20ccd) Interface,Node(node): follow\-ups to deterministic\_ips/ consolidation ([\#2845](https://github.com/dfinity/ic/pull/2845))

Tests:
------

* [`51f1c7e21`](https://github.com/dfinity/ic/commit/51f1c7e21) Consensus,Interface: Enable cup\_compatibility\_test for new NiDkgTag::HighThresholdForKey ([\#2840](https://github.com/dfinity/ic/pull/2840))
* [`9a95ec743`](https://github.com/dfinity/ic/commit/9a95ec743) Execution,Interface(EXC): Fix race condition in tests ([\#2828](https://github.com/dfinity/ic/pull/2828))
* [`aab432742`](https://github.com/dfinity/ic/commit/aab432742) Interface: Deriving reject code from error code ([\#2871](https://github.com/dfinity/ic/pull/2871))

-------------------------------------------
Full list of changes (including the ones that are not relevant to GuestOS) can be found on [GitHub](https://github.com/dfinity/dre/blob/945af63d7044f58be8dd115662408c08bb8dbab0/replica-releases/d9fe2076f677a08734bed90c67b1c3f4056ed621.md).

# IC-OS Verification

To build and verify the IC-OS disk image, run:

```
# From https://github.com/dfinity/ic#verifying-releases
sudo apt-get install -y curl && curl --proto '=https' --tlsv1.2 -sSLO https://raw.githubusercontent.com/dfinity/ic/d9fe2076f677a08734bed90c67b1c3f4056ed621/ci/tools/repro-check.sh && chmod +x repro-check.sh && ./repro-check.sh -c d9fe2076f677a08734bed90c67b1c3f4056ed621 --guestos
```

The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal.

While not required for this NNS proposal, as we are only electing a new GuestOS version here, you have the option to verify the build reproducibility of the HostOS by passing `--hostos` to the script above instead of `--guestos`, or the SetupOS by passing `--setupos`.


Link to the forum post: https://forum.dfinity.org/t/proposal-to-elect-new-release-rc-2024-12-06-03-16/38494/1

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134408)

Elect new IC/Replica revision (commit d9fe207) - IcOsVersionElection - NNS Id 134408

# Upgrade frontend NNS Dapp canister to commit `165b0b4aaefdd075c48932302aba7c1b4bca1d36`
Wasm sha256 hash: `af33eac1b7d02db29a978020520a414e730c89fde4eecf0d33a8a7b84aff100c` (`https://github.com/dfinity/nns-dapp/actions/runs/11816928413`)

## Change Log

### Changed

* Claim unclaimed neurons from the frontend instead of the backend.

### Removed

* Stop storing neuron accounts in the nns-dapp canister.

### Fixed

* Stop trying to get swap commitments from aborted SNSes.
* Stop making unnecessary calls to SNS-W and SNS root canisters.
* User gets the wrong identity when connecting different hardware wallets devices in a certain order.

## Commit Log

```
+ bash -xc "git log --format='%C(auto) %h %s' 135d97145..165b0b4aa"
 165b0b4aa Restore all mocks in NnsProposalDetail.spec.ts (#5769)
 9fe7ff8c9 Always build SNS wrappers from aggregator data (#5768)
 8d59bb7fa Remove neuron_accounts field from AccountsStore (#5767)
 e1b330064 Add getLoadedSnsAggregatorData (#5765)
 1d2f73d82 NNS1-3310: ConfirmationModal footer (#5749)
 21ef0bed3 NNS1-3435: use & operator for combined class selectors (#5764)
 8c0f8ed3e Fix caching of ledger identity (#5757)
 230c60d98 NNS1-3435: New icon with color hints (#5759)
 12b4c27d9 bot: Bump gix-components (#5762)
 286399cd3 bot: Update sns_aggregator candid bindings (#5761)
 77b14365d test: get test coverage insight (#5758)
 8156d8960 Update changelog after release (#5760)
 5124e7997 Bump ic-cdk-macros from 0.16.0 to 0.17.0 (#5754)
 f8197c10c bot: Update proposals candid bindings (#5756)
 7da2f2597 Bump ic-cdk-timers from 0.10.0 to 0.11.0 (#5752)
 0d923e89d Bump ic-cdk from 0.16.0 to 0.17.0 (#5755)
 cffc9399e NNS1-3435: Applies new styles to ConfirmationModal's content (#5748)
 07cf22df4 Add missing arg-sha256 parameter to release (#5747)
 f4b5a03dd bot: Update IC Cargo Dependencies to release-2024-11-07_03-07-6.11-kernel (#5750)
 854210bbd Chore: Add yhabib to reviewers (#5746)
 2eae81c08 NNS1-3435: Reuse ConfirmationModal styles through other consumers of ConfirmationModal (#5740)
 fc453721f bot: Update snsdemo to release-2024-11-06 (#5744)
 1af0d67d9 bot: Bump gix-components (#5745)
 8509c8c51 Don't build wrappers for aborted SNSes (#5742)
 699e87583 Add beta network to dfx.json (#5743)
 389f50b8b FOLLOW-244: Stop storing neuron accounts in stable memory (#5739)
 36f052e03 FOLLOW-244: Stop claiming neurons in the nns-dapp canister (#5738)
 babf022bd Remove subscribe from sns.services.spec.ts (#5741)
 94df88c1e Aligns text to the left for confirmation modal (#5730)
 c68de13ab bot: Update SNS Aggregator Response (#5737)
 73caf9c7f FOLLOW-244: Stop inserting into AccountsStore.neuron_accounts (#5736)
 b1ad6c0fd FOLLOW-244: Remove MultiPartTransactionToBeProcessed::TopUpNeuron (#5735)
 fbf8c3d3a FOLLOW-244: Claim unclaimed neurons from the frontend (#5734)
 86de7da5a Enforces an exact match of replica processes (#5732)
```

## Wasm Verification

To build the wasm module yourself and verify its hash, run the following commands from the root of the [nns-dapp repo](https://github.com/dfinity/nns-dapp):

```
git fetch  # to ensure you have the latest changes.
git checkout "165b0b4aaefdd075c48932302aba7c1b4bca1d36"
git merge-base --is-ancestor HEAD origin/main && echo "OK" || echo "Commit is not on main branch!"
./scripts/docker-build
sha256sum nns-dapp.wasm.gz
```

You may also want to verify the canister arguments.  In the proposal they are
binary, which is not very readable. Docker provides both binary and text formats
and you can verify that the text format corresponds to the binary `arg_hex`
field in the proposal.

```
cat nns-dapp-arg-mainnet.did
didc encode "$(cat nns-dapp-arg-mainnet.did)" | xxd -r -p | sha256sum
```


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134171)

Upgrade NNS Canister: qoctq-giaaa-aaaaa-aaaea-cai to wasm with hash: af33eac1b7d02db29a978020520a414e730c89fde4eecf0d33a8a7b84aff100c - NetworkCanisterManagement - NNS Id 134171

# Replace a node in subnet snjp4

Motivation: The following nodes in subnet `snjp4` have been cordoned and will be removed:
- 7pfb3: NP is selling the PL1 DC after 48 months; https://forum.dfinity.org/t/subnet-management-general-discussion/34091/110

Decentralization Nakamoto coefficient changes for subnet `snjp4-xlbw4-mnbog-ddwy6-6ckfd-2w5a2-eipqo-7l436-pxqkh-l6fuv-vae`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 5.00 -> 5.00    (+0%)
```

**Mean Nakamoto comparison:** 5.00 -> 5.00  (+0%)

Overall replacement impact: equal decentralization across all features


# Details

Nodes removed:
- `7pfb3-xfk5a-rkqk7-pa2up-xnthp-vsdo7-iyouf-hsh3e-zijpc-kk3f5-uqe` [health: healthy]

Nodes added:
- `aiqux-sozuk-rzknl-zso62-hlr7c-gn6bw-gzgwj-cp3uk-wrmnf-hq7jj-rqe` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner                                    area                                  country   
    -------------                                                              -----------            -----------------                                    ----                                  -------   
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    ar1               1    Africa Data Centres                             1    British Columbia                 1    AR       1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    bc1               1    Cloud9                                          1    CABA                             1    AU       1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    ct1               1    Cyxtera                                         1    Cape Town                        1    CA       1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe       1    fr2               1    Datasite                                   0 -> 1    Florida                     0 -> 1    CH       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    ge1               1    Digital Realty                                  1    Geneva                           1    DE       1
    eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe  1 -> 0    hk1               1    Equinix                                         1    Hesse                            1    FR       1
    fwnmn-zn7yt-5jaia-fkxlr-dzwyu-keguq-npfxq-mc72w-exeae-n5thj-oae       1    lj1               1    Flexential                                 1 -> 0    HongKong                         1    GE       1
    optdi-nwa4m-hly3k-6ua4n-sqyxf-yahvb-wps77-ddayn-r7zcz-edla5-7qe       1    mr1               1    HighDC                                          1    Ljubljana                        1    HK       1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae       1    nd1               1    Marvelous Web3 DC                               1    New Delhi                        1    IN       1
    s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae       1    or1          0 -> 1    NEXTDC                                          1    Oregon                      1 -> 0    SG       1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    pl1          1 -> 0    Posita.si                                       1    Provence-Alpes-Cote d'Azur       1    SI       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    sc1               1    SyT - Servicios y Telecomunicaciones S.A.       1    Queensland                       1    US       1
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae       1    sg1               1    Telin                                           1    Singapore                        1    ZA       1
    wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae  0 -> 1    tb1               1    Unicom                                          1    Tbilisi                          1              
```


Forum post link: https://forum.dfinity.org/t/replacing-nodes-in-subnet-snjp4/38518


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134412)

Replace a node in subnet snjp4 - SubnetManagement - NNS Id 134412

Update subnet x33ed-h457x-bsgyx-oqxqf-6pzwv-wkhzr-rm2j3-npodi-purzm-n66cg-gae to replica version [f88938214b16584075196e13d0af7c50f671131a](https://dashboard.internetcomputer.org/release/f88938214b16584075196e13d0af7c50f671131a)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134087)

Update subnet x33ed to replica version f889382 - IcOsVersionDeployment - NNS Id 134087

Update subnet gmq5v-hbozq-uui6y-o55wc-ihop3-562wb-3qspg-nnijg-npqp5-he3cj-3ae to replica version [cd26db8c93f887e76baae202aab150390e41983f](https://dashboard.internetcomputer.org/release/cd26db8c93f887e76baae202aab150390e41983f)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134089)

Update subnet gmq5v to replica version cd26db8 - IcOsVersionDeployment - NNS Id 134089

Update subnet jtdsg-3h6gi-hs7o5-z2soi-43w3z-soyl3-ajnp3-ekni5-sw553-5kw67-nqe to replica version [cd26db8c93f887e76baae202aab150390e41983f](https://dashboard.internetcomputer.org/release/cd26db8c93f887e76baae202aab150390e41983f)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134085)

Update subnet jtdsg to replica version cd26db8 - IcOsVersionDeployment - NNS Id 134085

Update subnet fuqsr-in2lc-zbcjj-ydmcw-pzq7h-4xm2z-pto4i-dcyee-5z4rz-x63ji-nae to replica version [d9fe2076f677a08734bed90c67b1c3f4056ed621](https://dashboard.internetcomputer.org/release/d9fe2076f677a08734bed90c67b1c3f4056ed621)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134433)

Update subnet fuqsr to replica version d9fe207 - IcOsVersionDeployment - NNS Id 134433

**I. Token Distribution** 
* Allocated to Treasury - 63% * Allocated to SNS Swap - 20%  * Team & Advisors - 17% * The Ledger Transaction fee is 0.01 CANI
**II. Governance**
The governance model includes staking, voting, and other relevant details. The minimum amount of SNS tokens to stake a neuron is 50 tokens. The minimum dissolve  delay a neuron must have to be able to cast votes on proposals is 1 month and the maximum dissolve delay is 3 years.
Decentralization Sale * Min participation - 1 ICP * Min participants - 10 * Min to be raised - 50,000 ICP * Max to be raised - 250,000 ICP
**III. The DApps**
Cani ecosystem consists of a set of dpps including services deployed on EU subnet,  with the SNS directly controlling the following canisters.
* cani_dao: tlcef-5iaaa-aaaas-akjmq-cai * cani_indexer: tqhya-hqaaa-aaaas-akjoa-cai * cani_platform: tfajn-gyaaa-aaaas-akjnq-cai * cani_user: tcbpz-laaaa-aaaas-akjna-cai
**IV. Verification**
The above details can be verified through: * Whitepaper: https://docs.canistore.io * Github: https://github.com/Canistore/CANI_DAPP * Product: https://canisafe.app, https://canistore.app, https://caniplay.app * Product video: https://www.youtube.com/watch?v=5iXrPFOG7q0 * Main website: https://canistore.io


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134422)

NNS Proposal to create an SNS named 'Cani DAO' - SnsAndCommunityFund - NNS Id 134422

Enable the HTTPS outcalls feature on subnet 4zbus, which should be enabled on all application subnets but was accidentally never enabled on this subnet. Note that this is a duplicate of proposal 134382 which failed to execute due to a bug in the registry, which is should be fixed by proposal 134437.

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134441)

Update configuration of subnet: 4zbus - SubnetManagement - NNS Id 134441

# Upgrade the Registry Canister to Commit 8622959

__Proposer__: maximilian.summe at dfinity.org

__Source code__: [86229594d61b433c39fc5331ab818ccb6c6aa6a7][new-commit]

[new-commit]: https://github.com/dfinity/ic/tree/86229594d61b433c39fc5331ab818ccb6c6aa6a7

## Summary

This release includes a bug fix that prevented setting any subnet features if the subnet record did not contain any existing feature settings.

Also includes several refactorings.

## New Commits

```
$ git log --format="%C(auto) %h %s" d265b130647f04aa25909ec1fbb8294ce0139d1c..86229594d61b433c39fc5331ab818ccb6c6aa6a7 --  ./rs/registry/canister
 c2e11ca2ae fix(registry): Ensure subnet features can be changed for subnets without any features (#3044)
 3e0cf89b23 test(IDX): depend on the universal canister at run-time instead of at build-time (#2502)
 3c3d9cd360 refactor(crypto): CRP-2597 move MasterPublicKeyId protobuf from registry/crypto to types (#2406)
 44095f27bb chore(CRP-2617): Generalize CUP’s ChainKeyInitialization (#2337)
```


## Current Version

__Current git hash__: d265b130647f04aa25909ec1fbb8294ce0139d1c

__Current wasm hash__: 2fabd44386a8af5a579a72af4a27c6b844a8a88aced49d16f286187e5660d771


## Verification

See the general instructions on [how to verify] proposals like this. A "quick
start" guide is provided here.

[how to verify]: https://github.com/dfinity/ic/tree/86229594d61b433c39fc5331ab818ccb6c6aa6a7/rs/nervous_system/docs/proposal_verification.md


### WASM Verification

See ["Building the code"][prereqs] for prerequisites.

[prereqs]: https://github.com/dfinity/ic/tree/86229594d61b433c39fc5331ab818ccb6c6aa6a7/README.adoc#building-the-code

```
# 1. Get a copy of the code.
git clone git@github.com:dfinity/ic.git
cd ic
# Or, if you already have a copy of the ic repo,
git fetch
git checkout 86229594d61b433c39fc5331ab818ccb6c6aa6a7

# 2. Build canisters.
./ci/container/build-ic.sh -c

# 3. Fingerprint the result.
sha256sum ./artifacts/canisters/registry-canister.wasm.gz
```

This should match `wasm_module_hash` field of this proposal.


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134437)

Upgrade the Registry Canister to Commit 8622959 - Unknown - NNS Id 134437

This proposal sets the notarisation delay of the subnet to 300ms, down from 600ms. The change will increase the block rate of the subnet, aimed to reduce latency of update calls.

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/132215)

Set subnet notarisation delay to 300ms - SubnetManagement - NNS Id 132215

# Upgrade the Cycles-minting Canister to Commit cf23743

__Proposer__: daniel.wong at dfinity.org\
__Source Code__: [cf237434877b39d0a94fb5ef84b13ea576a225ac][new-commit]

[new-commit]: https://github.com/dfinity/ic/tree/cf237434877b39d0a94fb5ef84b13ea576a225ac


## Features, Fixes, and Optimizations

* Support more log visibility options.
* Initialize `average_icp_xdr_conversion_rate`
* Add support for wasm_memory_threshold.


## New Commits

```
$ git log --format="%C(auto) %h %s" 3b3ffedc6aa481fd9b92eefaf46beded9e51a344..cf237434877b39d0a94fb5ef84b13ea576a225ac --  ./rs/nns/cmc
 1fbaf34459 chore(cmc): Use the CYCLES_LEDGER_CANISTER_ID constant in ic_nns_constants (#1234)
 f040350513 feat: [EXC-1675] migrate replica to no-op LogVisibilityV2 (#768)
 ca24b5d66d chore: sort dependencies in Cargo.toml files (#828)
 94f580d004 feat(cmc): Initialize `average_icp_xdr_conversion_rate` (#803)
 4bebd6f6a8 chore: [EXC-1665] Add Wasm memory threshold field to canister settings (#475)
```


## Upgrade Arguments

```candid
()
```


## Current Version

- Current Git Hash: 3b3ffedc6aa481fd9b92eefaf46beded9e51a344
- Current Wasm Hash: f24df747ad451a9d45fe2e98aa60b82578203fb73fc24316cd33ce98307e9f0c


## WASM Verification

See ["Building the code"][prereqs] for prerequisites.

[prereqs]: https://github.com/dfinity/ic?tab=readme-ov-file#building-the-code

```
# 1. Get a copy of the code.
git clone git@github.com:dfinity/ic.git
cd ic
# Or, if you already have a copy of the ic repo,
git fetch
git checkout cf237434877b39d0a94fb5ef84b13ea576a225ac

# 2. Build canisters.
./gitlab-ci/container/build-ic.sh -c

# 3. Fingerprint the result.
sha256sum ./artifacts/canisters/cycles-minting-canister.wasm.gz
```

This should match `wasm_module` field of this proposal.


## Upgrade Arguments Verification

[`didc`][latest-didc] is required.

[latest-didc]: https://github.com/dfinity/candid/releases/latest

```
didc encode '()' | xxd -r -p | sha256sum

```

This should match the `arg_hash` field of this proposal.


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/132224)

Upgrade the Cycles-minting Canister to Commit cf23743 - NetworkCanisterManagement - NNS Id 132224

This proposal sets the notarisation delay of the subnet to 300ms, down from 600ms. The change will increase the block rate of the subnet, aimed to reduce latency of update calls.

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/132216)

Set subnet notarisation delay to 300ms - SubnetManagement - NNS Id 132216

This is Internet Identity release [release-2024-08-30](https://github.com/dfinity/internet-identity/releases/tag/release-2024-08-30) for commit [fd5486afabb4e0eead403f771d63d8752f95ab17](https://github.com/dfinity/internet-identity/commit/fd5486afabb4e0eead403f771d63d8752f95ab17).

The main change of this release is a new feature that allows dapps to streamline re-authentication: Dapps may supply a principal to Internet Identity when sending the `authorize-client` message. If that principal belongs to the last used identity on that client application origin, then the identity will be selected automatically. The user will then be presented with the passkey interaction immediately, making the actual authentication the only user interaction required to complete the re-authentication process.

The sha256 of production asset [internet_identity_production.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2024-08-30/internet_identity_production.wasm.gz) is [9ea1df5ffd63367080ee1bc342eeff47a020da280845612b47aba5afc6cb3fe1](https://github.com/dfinity/internet-identity/actions/runs/10629731060/job/29467191935#step:7:1).

## What's Changed
* Update release in README by @gix-bot in https://github.com/dfinity/internet-identity/pull/2565
* Update node version by @gix-bot in https://github.com/dfinity/internet-identity/pull/2566
* Migrate integration tests to PocketIC by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2557
* Remove obsolete IC commit file by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2568
* Simplify identity metadata repository by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2567
* fix: broken link in II spec by @jessiemongeon1 in https://github.com/dfinity/internet-identity/pull/2569
* Implement API to auto-select identity based on known principal by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2563
* Move sig-verifier-js tests out of e2e by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2571
* Bump outdated github script action by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2572
* Replace login error page with toast by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2570
* Move and fix dapps explorer by @lmuntaner in https://github.com/dfinity/internet-identity/pull/2573
* Extract error toast from authn box by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2574
* Fix errors in the alternative origins documentation by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2575
* Remove unnecessary dependency by @lmuntaner in https://github.com/dfinity/internet-identity/pull/2577
* Separate principal and origin information in IndexedDB storage by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2578
* Only allow the most recently used identity to be auto-selected by @frederikrothenberger in https://github.com/dfinity/internet-identity/pull/2579


**Full Changelog**: https://github.com/dfinity/internet-identity/compare/release-2024-08-21...release-2024-08-30
## Build flavors

For more information please see the [Build flavors](https://github.com/dfinity/internet-identity/tree/release-2024-08-30#build-features-and-flavors) section of the README.

| Filename | sha256 (links to CI Run) |
| --- | --- |
|[internet_identity_production.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2024-08-30/internet_identity_production.wasm.gz)|[`9ea1df5ffd63367080ee1bc342eeff47a020da280845612b47aba5afc6cb3fe1`](https://github.com/dfinity/internet-identity/actions/runs/10629731060/job/29467191935#step:7:1)|
|[internet_identity_dev.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2024-08-30/internet_identity_dev.wasm.gz)|[`5b40d36e886f57d033850cae79040bbccc7ffc884163cf7298b40528ebd071e4`](https://github.com/dfinity/internet-identity/actions/runs/10629731060/job/29467192394#step:7:1)|
|[internet_identity_test.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2024-08-30/internet_identity_test.wasm.gz)|[`fcfa5fe585ac01690e4081dde281c619e0176df77db731d02dc4d053bacd2f50`](https://github.com/dfinity/internet-identity/actions/runs/10629731060/job/29467192159#step:7:1)|
|[archive.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2024-08-30/archive.wasm.gz)|[`7ac9c94fd2f18b4b09b8758d6e51a85d0197bbf2fc53d0cef60a88a089831a7d`](https://github.com/dfinity/internet-identity/actions/runs/10629731060/job/29467191696#step:6:1)|
|[vc_demo_issuer.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2024-08-30/vc_demo_issuer.wasm.gz)|[`abf52e1eedbcf8d594f4ab54370fc69665bf64341a5e9137eee5b990c2b4ee83`](https://github.com/dfinity/internet-identity/actions/runs/10629731060/job/29467185204#step:8:1)|

## Wasm Verification

To build the wasm modules yourself and verify their hashes, run the following commands from the root of the [Internet Identity repository](https://github.com/dfinity/internet-identity):
```
git pull # to ensure you have the latest changes.
git checkout fd5486afabb4e0eead403f771d63d8752f95ab17
./scripts/verify-hash --ii-hash 9ea1df5ffd63367080ee1bc342eeff47a020da280845612b47aba5afc6cb3fe1
```

Make sure to compare the hashes also with the proposal payload when verifying canister upgrade proposals.


## Argument Verification

Run the follwing command to verify the upgrade argument hash:
```
didc encode '(null)' | xxd -r -p | sha256sum
```



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/132221)

Upgrade NNS Canister: rdmx6-jaaaa-aaaaa-aaadq-cai to wasm with hash: 9ea1df5ffd63367080ee1bc342eeff47a020da280845612b47aba5afc6cb3fe1 - NetworkCanisterManagement - NNS Id 132221

# Upgrade the Genesis-token Canister to Commit cf23743

__Proposer__: daniel.wong at dfinity.org\
__Source Code__: [cf237434877b39d0a94fb5ef84b13ea576a225ac][new-commit]

[new-commit]: https://github.com/dfinity/ic/tree/cf237434877b39d0a94fb5ef84b13ea576a225ac


## Features, Fixes, and Optimizations

None. This is just to avoid a large amount of unreleased changes piling up.


## New Commits

```
$ git log --format="%C(auto) %h %s" ad5629caa17ac8a4545bc2e3cf0ecc990c9f681e..cf237434877b39d0a94fb5ef84b13ea576a225ac --  ./rs/nns/gtc
 a3129e0d7c test(nns): Stop generating .did files. (#1114)
 c6e64a7e3e chore(crypto): CRP-2567 Rename ic_crypto_ecdsa_secp256k1 crate (#999)
 12e89bb818 refactor: Migrate more type dependencies to use ic_nns_governance_api (#628)
 b4be567dc0 chore: Bump rust version to 1.80 (#642)
 5cfaea5eaa chore: upgrade external crates and use workspace version
 c4563f8781 chore(crypto): CRP-1667 replace outdated libsecp256k1 dependency
 576bb8d173 chore: add buildifier sort comment to Bazel files
```


## Current Version

- Current Git Hash: ad5629caa17ac8a4545bc2e3cf0ecc990c9f681e
- Current Wasm Hash: a403f573c4426065b1a9b7b5b1a7f95c04534c6d79a06be71f1d04212b40e9de


## WASM Verification

See ["Building the code"][prereqs] for prerequisites.

[prereqs]: https://github.com/dfinity/ic?tab=readme-ov-file#building-the-code

```
# 1. Get a copy of the code.
git clone git@github.com:dfinity/ic.git
cd ic
# Or, if you already have a copy of the ic repo,
git fetch
git checkout cf237434877b39d0a94fb5ef84b13ea576a225ac

# 2. Build canisters.
./gitlab-ci/container/build-ic.sh -c

# 3. Fingerprint the result.
sha256sum ./artifacts/canisters/genesis-token-canister.wasm.gz
```

This should match `wasm_module` field of this proposal.


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/132227)

Upgrade the Genesis-token Canister to Commit cf23743 - NetworkCanisterManagement - NNS Id 132227

This proposal sets the notarisation delay of the subnet to 300ms, down from 600ms. The change will increase the block rate of the subnet, aimed to reduce latency of update calls.

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/132217)

Set subnet notarisation delay to 300ms - SubnetManagement - NNS Id 132217

Node provider 'Protocol16' is creating a new Node Operator id
for adding 28 nodes in the sg3 data center.

Protocol16 is taking over operation of the sg3 data center and
all of its Gen1 nodes, as the current node provider 162 Digital Capital is divesting
all but 42 nodes in line with the motion proposal 132553 for node rewards after 
48 months.

This proposal is clarified in this forum post: https://forum.dfinity.org/t/new-node-provider-proposals/16643/581
and this wiki link: https://wiki.internetcomputer.org/wiki/162dc_statement

The signed handover document available at the Wiki link above has the following checksum:

```
e19ca68c4a4ffa377efd8a2fecdeabdb0e1ad0dc64dd2b39388fadee1a6426dc  Signed_node_hand_over_statement.pdf
```


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134501)

Add vicvb as a Node Operator of Node Provider: x7uok - NodeAdmin - NNS Id 134501

Release Notes for [**release\-2024\-12\-06\_03\-16\-sandboxes7k**](https://github.com/dfinity/ic/tree/release-2024-12-06_03-16-sandboxes7k) (3e24396441e4c7380928d4e8b4ccff7de77d0e7e)
======================================================================================================================================================================================

This release is based on changes since [release\-2024\-12\-06\_03\-16\-base](https://dashboard.internetcomputer.org/release/d9fe2076f677a08734bed90c67b1c3f4056ed621) (d9fe2076f677a08734bed90c67b1c3f4056ed621\).

Please note that some commits may be excluded from this release if they're not relevant, or not modifying the GuestOS image. Additionally, descriptions of some changes might have been slightly modified to fit the release notes format.

To see a full list of commits added since last release, compare the revisions on [GitHub](https://github.com/dfinity/ic/compare/release-2024-12-06_03-16-base...release-2024-12-06_03-16-sandboxes7k).

Chores:
-------

* [`3e2439644`](https://github.com/dfinity/ic/commit/3e2439644) Execution,Interface,Networking: Increase max number of sandboxes to 7k ([\#3164](https://github.com/dfinity/ic/pull/3164))

# IC-OS Verification

To build and verify the IC-OS disk image, run:

```
# From https://github.com/dfinity/ic#verifying-releases
sudo apt-get install -y curl && curl --proto '=https' --tlsv1.2 -sSLO https://raw.githubusercontent.com/dfinity/ic/3e24396441e4c7380928d4e8b4ccff7de77d0e7e/ci/tools/repro-check.sh && chmod +x repro-check.sh && ./repro-check.sh -c 3e24396441e4c7380928d4e8b4ccff7de77d0e7e --guestos
```

The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal.

While not required for this NNS proposal, as we are only electing a new GuestOS version here, you have the option to verify the build reproducibility of the HostOS by passing `--hostos` to the script above instead of `--guestos`, or the SetupOS by passing `--setupos`.


Link to the forum post: https://forum.dfinity.org/t/proposal-to-elect-new-release-rc-2024-12-06-03-16/38494/11

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134497)

Elect new IC/Replica revision (commit 3e24396) - IcOsVersionElection - NNS Id 134497

Allow a principal controlled by the boundary node team to deploy canisters on the uzr34 subnet, which is required to install the rate-limiting and salt sharing canister.

For more information check [the forum thread](https://forum.dfinity.org/t/incident-handling-with-the-new-boundary-node-architecture/36390)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134256)

Authorize principal 2igsz to install canisters on subnet uzr34 - SubnetManagement - NNS Id 134256

# Replace a node in subnet w4asl

Motivation: 
 - replacing dead node quca2-52yr6-7fsih-4hv4j-d5uaw-xd25f-smuez-qs4j5-bluui-5jza5-7qe

Calculated potential impact on subnet decentralization if replacing:

- 1 additional node would result in: equal decentralization across all features

Based on the calculated potential impact, not replacing additional nodes to improve optimization.

Note: the information below is provided for your convenience. Please independently verify the decentralization changes rather than relying solely on this summary.
Here is [an explaination of how decentralization is currently calculated](https://dfinity.github.io/dre/decentralization.html), 
and there are also [instructions for performing what-if analysis](https://dfinity.github.io/dre/subnet-decentralization-whatif.html) if you are wondering if another node would have improved decentralization more.



Decentralization Nakamoto coefficient changes for subnet `w4asl-4nmyj-qnr7c-6cqq4-tkwmt-o26di-iupkq-vx4kt-asbrx-jzuxh-4ae`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 5.00 -> 5.00    (+0%)
```

**Mean Nakamoto comparison:** 5.00 -> 5.00  (+0%)

Overall replacement impact: equal decentralization across all features


# Details

Nodes removed:
- `quca2-52yr6-7fsih-4hv4j-d5uaw-xd25f-smuez-qs4j5-bluui-5jza5-7qe` [health: dead]

Nodes added:
- `qvskl-y3tsp-bnmtl-k4duq-vdcnn-zb4f2-vea23-x2vz2-jpv5d-jzwzx-eqe` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner            area                        country   
    -------------                                                              -----------            -----------------            ----                        -------   
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae  0 -> 1    bn1               1    AtlasEdge               1    Brussels Capital       1    BE       1
    64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe  1 -> 0    br2               1    Cyxtera                 1    Gauteng                1    CA       1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    ch2               1    Digital Realty          1    Geneva                 1    CH       1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    ge2               1    Equinix                 1    HongKong               1    CZ       1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    hk1               1    Gasan              1 -> 0    Illinois               1    HK       1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    jb1               1    Master Internet         1    Ljubljana              1    IN       1
    efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe       1    kr2          1 -> 0    Megazone Cloud     0 -> 1    Ontario                1    JP       1
    g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe       1    lj1               1    Posita.si               1    Panvel                 1    KR       1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    pl2               1    SafeHost                1    Seoul                  1    SE       1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sg2               1    Telin                   1    Singapore              1    SG       1
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe       1    sh1               1    Teraco                  1    South Moravian Region  1    SI       1
    unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe       1    sl1          0 -> 1    Tierpoint               1    Stockholm              1    US       1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    to2               1    Unicom                  1    Tokyo                  1    ZA       1
    zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae       1    ty1               1    Yotta                   1                                          
```


Forum post link: https://forum.dfinity.org/t/subnet-management-w4asl-application/33660/9


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134488)

Replace a node in subnet w4asl - SubnetManagement - NNS Id 134488

# Replace a node in subnet pzp6e

Motivation: The following nodes in subnet `pzp6e` have been cordoned and need to be removed from the subnet:
- sua4d: offboarding CH3 DC after 48 months; https://forum.dfinity.org/t/proposal-update-interim-gen-1-node-provider-remuneration-after-48-months/35001/16

Decentralization Nakamoto coefficient changes for subnet `pzp6e-ekpqk-3c5x7-2h6so-njoeq-mt45d-h3h6c-q3mxf-vpeq5-fk5o7-yae`:
```
  node_provider: 12.00 -> 12.00    (+0%)
    data_center: 12.00 -> 12.00    (+0%)
data_center_owner: 12.00 -> 12.00    (+0%)
           area: 10.00 -> 10.00    (+0%)
          country: 5.00 -> 6.00   (+20%)
```

**Mean Nakamoto comparison:** 10.20 -> 10.40  (+2%)

Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 3.2797 to 3.3324


# Details

Nodes removed:
- `sua4d-2yomd-7lnkd-6kumk-tzsqm-mv5dm-prpte-zjtqr-x3d63-bapf4-6ae` [health: healthy]

Nodes added:
- `5resh-f6n7z-xxkbq-7lpod-spptk-nyt7n-tcvf6-f5ecb-ixxwc-6k5ai-rqe` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner                                    area                             country        
    -------------                                                              -----------            -----------------                                    ----                             -------        
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae       1    ar1          0 -> 1    Adam                                            1    Barcelona                   1    AR       0 -> 1
    4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae       1    ba1               1    Africa Data Centres                             1    Barreiro                    1    AU            2
    4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae       1    bg1               1    Anonstake                                       1    Bogota                      1    BE            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    bn1               1    AtlasEdge                                       1    Brussels Capital            1    CA            1
    6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe       1    br2               1    Baltneta                                        1    Bucuresti                   1    CH            2
    6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe       1    bt1               1    Cloud9                                          1    CABA                   0 -> 1    CO            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    bu1               1    CyrusOne                                   1 -> 0    Cape Town                   1    CR            1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    ch3          1 -> 0    Cyxtera                                         1    Colombo                     1    CZ            1
    7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe       1    cm1               1    DEAC                                            1    Florida                     1    ES            1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    cr1               1    Datasite                                        1    Gauteng                     1    GE            1
    cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe       1    ct2               1    Digital Realty                                  1    Geneva                      1    HK            2
    cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe       1    es1               1    Dotsi                                           1    Greater Noida               1    HR            1
    diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe       1    ge2               1    EdgeUno                                         1    HongKong                    2    IN            3
    efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe       1    gn1               1    Equinix                                         1    Illinois               1 -> 0    JP            1
    eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe       1    hk3               1    Green.ch                                        1    Lisbon                      1    KR            2
    i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe       1    hk4               1    KT                                              1    Ljubljana                   1    LK            1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    jb2               1    Latitude.sh                                     1    Navi Mumbai                 1    LT            1
    ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae       1    kr1               1    M247                                            1    New Delhi                   1    LV            1
    izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe  1 -> 0    li1               1    Marvelous Web3 DC                               1    New South Wales             1    PT            2
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    lj1               1    Master Internet                                 1    New York                    1    RO            1
    mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe       1    nd1               1    Megazone Cloud                                  1    Ontario                     1    SE            1
    nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae       1    nm1               1    NEXTDC                                          1    Queensland                  1    SG            1
    otzuu-dldzs-avvu2-qwowd-hdj73-aocy7-lacgi-carzj-m6f2r-ffluy-fae       1    ns1               1    Navegalo                                        1    Riga                        1    SI            1
    py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe       1    ny1               1    Online                                          1    San Jose                    1    US       3 -> 2
    qsdw4-ao5ye-6rtq4-y3zhm-icjbj-lutd2-sbejz-4ajqz-pcflr-xrhsg-jae       1    or1               1    OrionStellar                                    1    Seoul                       2    ZA            2
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae       1    rg1               1    Posita.si                                       1    Singapore                   1                   
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    sc1               1    Rivram                                          1    South Moravian Region       1                   
    s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae  0 -> 1    sg1               1    SafeHost                                        1    Stockholm                   1                   
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    sh1               1    SyT - Servicios y Telecomunicaciones S.A.  0 -> 1    Tbilisi                     1                   
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe       1    sl1               1    Telin                                           1    Tokyo                       1                   
    ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae       1    tb1               1    Teraco                                          1    Vilnius                     1                   
    unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe       1    to2               1    Tierpoint                                       1    Zagreb                      1                   
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    ty2               1    Yotta                                           1    Zurich                      1                   
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    zg1               1    hkcolo                                          1                                                    
    wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae       1    zh6               1    hkntt                                           1                                                    
```


Forum post link: https://forum.dfinity.org/t/subnet-management-pzp6e-fiduciary/33664/59


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134490)

Replace a node in subnet pzp6e - SubnetManagement - NNS Id 134490

# Replace nodes in subnet nl6hn

Motivation: 
 - replacing dead node nebck-zsvl3-ihtov-dgrji-q7xly-qhbwu-53rao-7ysgi-x7aof-wgvna-eae
 - replacing node ptxxp-fechw-m6taf-lrkaj-hwtas-rxq6p-o6tko-yho6t-cjfzc-zkgdd-sae to optimize network topology

Calculated potential impact on subnet decentralization if replacing:

- 1 additional node would result in: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.2575 to 2.3219

Based on the calculated potential impact, replacing 1 additional nodes to improve optimization

Note: the heuristic for node replacement relies not only on the Nakamoto coefficient but also on other factors that iteratively optimize network topology.
Due to this, Nakamoto coefficients may not directly increase in every node replacement proposal.
Code for comparing decentralization of two candidate subnet topologies is at:
https://github.com/dfinity/dre/blob/79066127f58c852eaf4adda11610e815a426878c/rs/decentralization/src/nakamoto/mod.rs#L342

Note: the information below is provided for your convenience. Please independently verify the decentralization changes rather than relying solely on this summary.
Here is [an explaination of how decentralization is currently calculated](https://dfinity.github.io/dre/decentralization.html), 
and there are also [instructions for performing what-if analysis](https://dfinity.github.io/dre/subnet-decentralization-whatif.html) if you are wondering if another node would have improved decentralization more.



Decentralization Nakamoto coefficient changes for subnet `nl6hn-ja4yw-wvmpy-3z2jx-ymc34-pisx3-3cp5z-3oj4a-qzzny-jbsv3-4qe`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 4.00 -> 5.00   (+25%)
```

**Mean Nakamoto comparison:** 4.80 -> 5.00  (+4%)

Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.2575 to 2.3219


# Details

Nodes removed:
- `nebck-zsvl3-ihtov-dgrji-q7xly-qhbwu-53rao-7ysgi-x7aof-wgvna-eae` [health: dead]
- `ptxxp-fechw-m6taf-lrkaj-hwtas-rxq6p-o6tko-yho6t-cjfzc-zkgdd-sae` [health: healthy]

Nodes added:
- `lz3ap-rjo2a-ilqjt-jkyhb-t4ewt-b37eu-gl246-ltnyu-jrkec-6bi5m-cqe` [health: healthy]
- `fwpkp-tbgp3-rhl4h-njm2i-ebtn2-5susq-o765o-hjop2-qktc7-uo2kf-xae` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner            area                     country        
    -------------                                                              -----------            -----------------            ----                     -------        
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae  0 -> 1    an1               1    Cloud9             0 -> 1    Flanders            1    AU            1
    64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe  1 -> 0    fr2               1    Cyxtera                 1    Florida             1    BE            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    ge2               1    Datacenter United       1    Geneva              1    CA            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    gn1               1    Digital Realty          1    Greater Noida       1    CH       2 -> 1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe       1    hk4               1    Equinix                 1    Hesse               1    DE            1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    jv1               1    Gasan              1 -> 0    HongKong            1    GE       0 -> 1
    cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe       1    kr2          1 -> 0    Megazone Cloud     0 -> 1    Ljubljana           1    HK            1
    cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe       1    lj1               1    NEXTDC                  1    Melbourne           1    IN            1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    mn2               1    Nine.Ch            1 -> 0    Ontario             1    KR            1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    sg1               1    Posita.si               1    Seoul               1    SE            1
    spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe       1    sh1               1    SafeHost                1    Singapore           1    SG            1
    ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae  1 -> 0    sl1          0 -> 1    Telin                   1    Stockholm           1    SI            1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe  0 -> 1    tb1          0 -> 1    Tierpoint               1    Tbilisi        0 -> 1    US            1
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    to1               1    Yotta                   1    Zurich         1 -> 0                   
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae       1    zh4          1 -> 0    hkntt                   1                                            
```


Forum post link: https://forum.dfinity.org/t/subnet-management-nl6hn-application/33659/13


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134487)

Replace nodes in subnet nl6hn - SubnetManagement - NNS Id 134487

# Upgrade the Cycles-minting Canister to Commit ee52ab3

__Proposer__: jason.zhu at dfinity.org

__Source code__: [ee52ab3056cf5f39b09b08de70bdd20485c8b2dc][new-commit]

[new-commit]: https://github.com/dfinity/ic/tree/ee52ab3056cf5f39b09b08de70bdd20485c8b2dc

## Summary

Increase the cycles limit by 3x and add metrics for the limiter.

## New Commits

```
$ git log --format="%C(auto) %h %s" ca8847547d327ce8a3bd81d25a590e01da1a3af5..ee52ab3056cf5f39b09b08de70bdd20485c8b2dc --  ./rs/nns/cmc
 c89c23e5e5 feat(cmc): Increase cycles_limit by 3x. (#3093)
 7b5227e9dd feat(cmc): Limiter metrics. (#3118)
```


## Upgrade Arguments

```candid
()
```


## Current Version

__Current git hash__: ca8847547d327ce8a3bd81d25a590e01da1a3af5

__Current wasm hash__: 57f2cbbdbc2d8943173acc6ebd55aca9b9c12e2140b38ff5f20aea7b101ea570


## Verification

See the general instructions on [how to verify] proposals like this. A "quick
start" guide is provided here.

[how to verify]: https://github.com/dfinity/ic/tree/ee52ab3056cf5f39b09b08de70bdd20485c8b2dc/rs/nervous_system/docs/proposal_verification.md


### WASM Verification

See ["Building the code"][prereqs] for prerequisites.

[prereqs]: https://github.com/dfinity/ic/tree/ee52ab3056cf5f39b09b08de70bdd20485c8b2dc/README.adoc#building-the-code

```
# 1. Get a copy of the code.
git clone git@github.com:dfinity/ic.git
cd ic
# Or, if you already have a copy of the ic repo,
git fetch
git checkout ee52ab3056cf5f39b09b08de70bdd20485c8b2dc

# 2. Build canisters.
./ci/container/build-ic.sh -c

# 3. Fingerprint the result.
sha256sum ./artifacts/canisters/cycles-minting-canister.wasm.gz
```

This should match `wasm_module_hash` field of this proposal.


### Upgrade Arguments Verification

[`didc`][latest-didc] is required.

[latest-didc]: https://github.com/dfinity/candid/releases/latest

```
didc encode '()' | xxd -r -p | sha256sum

```

This should match the `arg_hash` field of this proposal.


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134500)

Upgrade the Cycles-minting Canister to Commit ee52ab3 - Unknown - NNS Id 134500

# Replace nodes in subnet gmq5v

Motivation: 
 - replacing dead node g46et-p24p2-vxbkf-woqqn-edgld-z4iif-5fcd6-a2beb-puqvu-l3wpq-sqe
 - replacing node jlb2x-vto3e-r2yf4-adrqu-3gult-4fpun-besaz-4nynm-gcmht-nziru-lae to optimize network topology

Calculated potential impact on subnet decentralization if replacing:

- 1 additional node would result in: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.2575 to 2.3219

Based on the calculated potential impact, replacing 1 additional nodes to improve optimization

Note: the heuristic for node replacement relies not only on the Nakamoto coefficient but also on other factors that iteratively optimize network topology.
Due to this, Nakamoto coefficients may not directly increase in every node replacement proposal.
Code for comparing decentralization of two candidate subnet topologies is at:
https://github.com/dfinity/dre/blob/79066127f58c852eaf4adda11610e815a426878c/rs/decentralization/src/nakamoto/mod.rs#L342

Note: the information below is provided for your convenience. Please independently verify the decentralization changes rather than relying solely on this summary.
Here is [an explaination of how decentralization is currently calculated](https://dfinity.github.io/dre/decentralization.html), 
and there are also [instructions for performing what-if analysis](https://dfinity.github.io/dre/subnet-decentralization-whatif.html) if you are wondering if another node would have improved decentralization more.



Decentralization Nakamoto coefficient changes for subnet `gmq5v-hbozq-uui6y-o55wc-ihop3-562wb-3qspg-nnijg-npqp5-he3cj-3ae`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 4.00 -> 5.00   (+25%)
```

**Mean Nakamoto comparison:** 4.80 -> 5.00  (+4%)

Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.2575 to 2.3219


# Details

Nodes removed:
- `g46et-p24p2-vxbkf-woqqn-edgld-z4iif-5fcd6-a2beb-puqvu-l3wpq-sqe` [health: dead]
- `jlb2x-vto3e-r2yf4-adrqu-3gult-4fpun-besaz-4nynm-gcmht-nziru-lae` [health: healthy]

Nodes added:
- `sjtwn-kupfb-fmu5p-twem2-vl6zm-uhqim-ahuup-pcwvi-g6v6g-qyybo-tae` [health: healthy]
- `jbgo7-cqnq6-mkd2d-fnqf2-6neke-h5zep-jtcmr-ahpnz-5vxox-z7saa-rae` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner            area                        country        
    -------------                                                              -----------            -----------------            ----                        -------        
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae  0 -> 1    aw1               1    Baltneta                1    Brussels Capital       1    AU       0 -> 1
    4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae       1    br1               1    Cloud9                  1    Bucuresti              1    BE            1
    64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe  1 -> 0    bt1               1    Cyxtera                 1    Geneva            1 -> 0    CA            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    bu1               1    Digital Realty          1    HongKong               1    CH       2 -> 1
    7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe       1    ge1          1 -> 0    Equinix                 1    Ljubljana              1    GE            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    hk1               1    Everyware               1    Melbourne         0 -> 1    HK            1
    7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe  1 -> 0    kr2          1 -> 0    Gasan              1 -> 0    Ontario                1    JP            1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    lj1               1    HighDC             1 -> 0    Pennsylvania           1    KR            1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    mn2          0 -> 1    M247                    1    Seoul                  1    LT            1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe  0 -> 1    sg3               1    Megazone Cloud     0 -> 1    Singapore              1    RO            1
    r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae       1    sl1          0 -> 1    NEXTDC             0 -> 1    Tbilisi                1    SG            1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    tb1               1    Posita.si               1    Tokyo                  1    SI            1
    sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae       1    to1               1    Racks Central           1    Vilnius                1    US            1
    vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe       1    ty3               1    Tierpoint               1    Zurich                 1                   
    wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae       1    zh2               1    Unicom                  1                                               
```


Forum post link: https://forum.dfinity.org/t/subnet-management-gmq5v-application/33764/16


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134486)

Replace nodes in subnet gmq5v - SubnetManagement - NNS Id 134486

Update subnet io67a-2jmkw-zup3h-snbwi-g6a5n-rm5dn-b6png-lvdpl-nqnto-yih6l-gqe to replica version [b0ade55f7e8999e2842fe3f49df163ba224b71a2](https://dashboard.internetcomputer.org/release/b0ade55f7e8999e2842fe3f49df163ba224b71a2)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/132166)

Update subnet io67a to replica version b0ade55 - IcOsVersionDeployment - NNS Id 132166

Update subnet eq6en-6jqla-fbu5s-daskr-h6hx2-376n5-iqabl-qgrng-gfqmv-n3yjr-mqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134229)

Update subnet eq6en to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134229

Update subnet lhg73-sax6z-2zank-6oer2-575lz-zgbxx-ptudx-5korm-fy7we-kh4hl-pqe to replica version [34e659ec3272fa2d884f48cb8229140e512f7f5e](https://dashboard.internetcomputer.org/release/34e659ec3272fa2d884f48cb8229140e512f7f5e)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134227)

Update subnet lhg73 to replica version 34e659e - IcOsVersionDeployment - NNS Id 134227



Suggested Governance Parameters Update:
 - Reward Rate: Maintain at 3% annually from .24%.
 - Maximum Age Bonus: Set to 100%, encouraging long-term staking from 25%.
 - Maximum Dissolve Delay Bonus: Set to 100%, promoting extended commitment from 50%.

Motivation: incentivize participation and align with long-term network growth goals.
            

Update SNS Parameters

Update subnet brlsh-zidhj-3yy3e-6vqbz-7xnih-xeq2l-as5oc-g32c4-i5pdn-2wwof-oae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134228)

Update subnet brlsh to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134228

Update subnet k44fs-gm4pv-afozh-rs7zw-cg32n-u7xov-xqyx3-2pw5q-eucnu-cosd4-uqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134230)

Update subnet k44fs to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134230

Update subnet cv73p-6v7zi-u67oy-7jc3h-qspsz-g5lrj-4fn7k-xrax3-thek2-sl46v-jae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134231)

Update subnet cv73p to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134231

Update subnet pzp6e-ekpqk-3c5x7-2h6so-njoeq-mt45d-h3h6c-q3mxf-vpeq5-fk5o7-yae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134247)

Update subnet pzp6e to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134247

Update subnet opn46-zyspe-hhmyp-4zu6u-7sbrh-dok77-m7dch-im62f-vyimr-a3n2c-4ae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134234)

Update subnet opn46 to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134234

Update subnet yinp6-35cfo-wgcd2-oc4ty-2kqpf-t4dul-rfk33-fsq3r-mfmua-m2ngh-jqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134241)

Update subnet yinp6 to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134241

Update subnet jtdsg-3h6gi-hs7o5-z2soi-43w3z-soyl3-ajnp3-ekni5-sw553-5kw67-nqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134239)

Update subnet jtdsg to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134239

Update subnet 5kdm2-62fc6-fwnja-hutkz-ycsnm-4z33i-woh43-4cenu-ev7mi-gii6t-4ae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134225)

Update subnet 5kdm2 to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134225

Update subnet 6pbhf-qzpdk-kuqbr-pklfa-5ehhf-jfjps-zsj6q-57nrl-kzhpd-mu7hc-vae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134238)

Update subnet 6pbhf to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134238

Update subnet io67a-2jmkw-zup3h-snbwi-g6a5n-rm5dn-b6png-lvdpl-nqnto-yih6l-gqe to replica version [34e659ec3272fa2d884f48cb8229140e512f7f5e](https://dashboard.internetcomputer.org/release/34e659ec3272fa2d884f48cb8229140e512f7f5e)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134199)

Update subnet io67a to replica version 34e659e - IcOsVersionDeployment - NNS Id 134199

Update subnet pae4o-o6dxf-xki7q-ezclx-znyd6-fnk6w-vkv5z-5lfwh-xym2i-otrrw-fqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134224)

Update subnet pae4o to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134224

# Replace a node in subnet 3hhby

Motivation: The following nodes in subnet `3hhby` have been cordoned and will be removed:
- tav5h: offboarding CH3 DC after 48 months; https://forum.dfinity.org/t/proposal-update-interim-gen-1-node-provider-remuneration-after-48-months/35001/16

Decentralization Nakamoto coefficient changes for subnet `3hhby-wmtmw-umt4t-7ieyg-bbiig-xiylg-sblrt-voxgt-bqckd-a75bf-rqe`:
```
    node_provider: 5.00 -> 5.00    (+0%)
      data_center: 5.00 -> 5.00    (+0%)
data_center_owner: 5.00 -> 5.00    (+0%)
             area: 5.00 -> 5.00    (+0%)
          country: 4.00 -> 5.00   (+25%)
```

**Mean Nakamoto comparison:** 4.80 -> 5.00  (+4%)

Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 2.2575 to 2.3219


# Details

Nodes removed:
- `tav5h-wv4rc-ty5vk-jgfh2-vm4uv-rtcm6-vasc2-acr5w-vop75-sjvut-gqe` [health: healthy]

Nodes added:
- `er26s-4rg3l-4pfha-wjj6n-a6zcm-x6hhu-kbmtm-xyhxt-yuqhx-hob4k-bqe` [health: healthy]


```
    node_provider                                                              data_center            data_center_owner            area                     country        
    -------------                                                              -----------            -----------------            ----                     -------        
    4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae  0 -> 1    an1               1    Anonstake               1    Bucuresti           1    AU            1
    4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae       1    bt1               1    Baltneta                1    California          1    BE            1
    6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe       1    bu1               1    CyrusOne           1 -> 0    Flanders            1    CA            1
    7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae       1    ch3          1 -> 0    Cyxtera                 1    Greater Noida       1    CH            1
    bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe       1    fr2               1    DEAC                    1    Hesse               1    DE            1
    cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe       1    gn1               1    Datacenter United       1    Illinois       1 -> 0    IN            1
    diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe       1    lj2               1    Digital Realty          1    Ljubljana           1    KR       0 -> 1
    i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae       1    mn2               1    Equinix                 1    Melbourne           1    LT            1
    ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe       1    rg1               1    Everyware               1    Ontario             1    LV            1
    izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe  1 -> 0    sg1               1    M247                    1    Riga                1    RO            1
    kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae       1    sj2               1    Megazone Cloud     0 -> 1    Seoul          0 -> 1    SG            1
    ks7ow-zvs7i-ratdk-azq34-zio2b-gbekj-qjicg-pfhp3-ovhgu-k5qql-dae       1    sl1          0 -> 1    NEXTDC                  1    Singapore           1    SI            1
    rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae       1    to2               1    Telin                   1    Vilnius             1    US       2 -> 1
    wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae       1    zh2               1    Yotta                   1    Zurich              1                   
```


Forum post link: https://forum.dfinity.org/t/subnet-management-3hhby-application/33657/17


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134485)

Replace a node in subnet 3hhby - SubnetManagement - NNS Id 134485

Update subnet e66qm-3cydn-nkf4i-ml4rb-4ro6o-srm5s-x5hwq-hnprz-3meqp-s7vks-5qe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134236)

Update subnet e66qm to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134236

Update subnet snjp4-xlbw4-mnbog-ddwy6-6ckfd-2w5a2-eipqo-7l436-pxqkh-l6fuv-vae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134207)

Update subnet snjp4 to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134207

Update subnet fuqsr-in2lc-zbcjj-ydmcw-pzq7h-4xm2z-pto4i-dcyee-5z4rz-x63ji-nae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134201)

Update subnet fuqsr to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134201

Update subnet 4zbus-z2bmt-ilreg-xakz4-6tyre-hsqj4-slb4g-zjwqo-snjcc-iqphi-3qe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134210)

Update subnet 4zbus to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134210

Update the unassigned nodes to the latest rolled-out version

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134198)

Update all unassigned nodes - IcOsVersionDeployment - NNS Id 134198

Update subnet nl6hn-ja4yw-wvmpy-3z2jx-ymc34-pisx3-3cp5z-3oj4a-qzzny-jbsv3-4qe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134246)

Update subnet nl6hn to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134246

Update subnet shefu-t3kr5-t5q3w-mqmdq-jabyv-vyvtf-cyyey-3kmo4-toyln-emubw-4qe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134200)

Update subnet shefu to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134200

Update subnet 4ecnw-byqwz-dtgss-ua2mh-pfvs7-c3lct-gtf4e-hnu75-j7eek-iifqm-sqe to replica version [cb3cb61009d904bcb726781ad379de10e1b745ff](https://dashboard.internetcomputer.org/release/cb3cb61009d904bcb726781ad379de10e1b745ff)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134232)

Update subnet 4ecnw to replica version cb3cb61 - IcOsVersionDeployment - NNS Id 134232

Update subnet csyj4-zmann-ys6ge-3kzi6-onexi-obayx-2fvak-zersm-euci4-6pslt-lae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134226)

Update subnet csyj4 to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134226

Update subnet lspz2-jx4pu-k3e7p-znm7j-q4yum-ork6e-6w4q6-pijwq-znehu-4jabe-kqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134233)

Update subnet lspz2 to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134233

Update subnet uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134211)

Update subnet uzr34 to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134211

Update subnet bkfrj-6k62g-dycql-7h53p-atvkj-zg4to-gaogh-netha-ptybj-ntsgw-rqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134240)

Update subnet bkfrj to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134240

Update subnet w4rem-dv5e3-widiz-wbpea-kbttk-mnzfm-tzrc7-svcj3-kbxyb-zamch-hqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134237)

Update subnet w4rem to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134237

Update subnet qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134209)

Update subnet qxesv to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134209

Update subnet 3hhby-wmtmw-umt4t-7ieyg-bbiig-xiylg-sblrt-voxgt-bqckd-a75bf-rqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134245)

Update subnet 3hhby to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134245

Update subnet w4asl-4nmyj-qnr7c-6cqq4-tkwmt-o26di-iupkq-vx4kt-asbrx-jzuxh-4ae to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134208)

Update subnet w4asl to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134208

Update subnet ejbmu-grnam-gk6ol-6irwa-htwoj-7ihfl-goimw-hlnvh-abms4-47v2e-zqe to replica version [e1e8a810e3d8646097459726ce3ab0bd8c0dff96](https://dashboard.internetcomputer.org/release/e1e8a810e3d8646097459726ce3ab0bd8c0dff96)

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134212)

Update subnet ejbmu to replica version e1e8a81 - IcOsVersionDeployment - NNS Id 134212

Updating the list of authorized subnets to:

| Subnet id | Subnet Type | Public | Description |
| --------- | ----------- | ------ | ----------- |
| 2fq7c-slacv-26cgz-vzbx2-2jrcs-5edph-i5s2j-tck77-c3rlz-iobzx-mqe | Application | false | Subnet has more than 60000 canisters |
| 3hhby-wmtmw-umt4t-7ieyg-bbiig-xiylg-sblrt-voxgt-bqckd-a75bf-rqe | Application | false | Subnet has more than 300 GiB state size |
| 4ecnw-byqwz-dtgss-ua2mh-pfvs7-c3lct-gtf4e-hnu75-j7eek-iifqm-sqe | Application | true |  |
| 4zbus-z2bmt-ilreg-xakz4-6tyre-hsqj4-slb4g-zjwqo-snjcc-iqphi-3qe | Verified Application | true |  |
| 5kdm2-62fc6-fwnja-hutkz-ycsnm-4z33i-woh43-4cenu-ev7mi-gii6t-4ae | Verified Application | false | Other verified subnets opened up in this run |
| 6pbhf-qzpdk-kuqbr-pklfa-5ehhf-jfjps-zsj6q-57nrl-kzhpd-mu7hc-vae | Application | false | Subnet has more than 300 GiB state size |
| bkfrj-6k62g-dycql-7h53p-atvkj-zg4to-gaogh-netha-ptybj-ntsgw-rqe | Application | false | Explicitly marked as non-public (European subnet) |
| brlsh-zidhj-3yy3e-6vqbz-7xnih-xeq2l-as5oc-g32c4-i5pdn-2wwof-oae | Application | true |  |
| csyj4-zmann-ys6ge-3kzi6-onexi-obayx-2fvak-zersm-euci4-6pslt-lae | Verified Application | false | Other verified subnets opened up in this run |
| cv73p-6v7zi-u67oy-7jc3h-qspsz-g5lrj-4fn7k-xrax3-thek2-sl46v-jae | Application | true |  |
| e66qm-3cydn-nkf4i-ml4rb-4ro6o-srm5s-x5hwq-hnprz-3meqp-s7vks-5qe | Application | true |  |
| ejbmu-grnam-gk6ol-6irwa-htwoj-7ihfl-goimw-hlnvh-abms4-47v2e-zqe | Verified Application | false | Other verified subnets opened up in this run |
| eq6en-6jqla-fbu5s-daskr-h6hx2-376n5-iqabl-qgrng-gfqmv-n3yjr-mqe | Verified Application | false | Subnet has more than 60000 canisters |
| fuqsr-in2lc-zbcjj-ydmcw-pzq7h-4xm2z-pto4i-dcyee-5z4rz-x63ji-nae | Application | true |  |
| gmq5v-hbozq-uui6y-o55wc-ihop3-562wb-3qspg-nnijg-npqp5-he3cj-3ae | Application | true |  |
| io67a-2jmkw-zup3h-snbwi-g6a5n-rm5dn-b6png-lvdpl-nqnto-yih6l-gqe | Verified Application | ~~false~~ ⇒ true |  |
| jtdsg-3h6gi-hs7o5-z2soi-43w3z-soyl3-ajnp3-ekni5-sw553-5kw67-nqe | Application | true |  |
| k44fs-gm4pv-afozh-rs7zw-cg32n-u7xov-xqyx3-2pw5q-eucnu-cosd4-uqe | Application | false | Subnet has more than 300 GiB state size |
| lhg73-sax6z-2zank-6oer2-575lz-zgbxx-ptudx-5korm-fy7we-kh4hl-pqe | Application | false | Subnet has more than 300 GiB state size |
| lspz2-jx4pu-k3e7p-znm7j-q4yum-ork6e-6w4q6-pijwq-znehu-4jabe-kqe | Application | true |  |
| mpubz-g52jc-grhjo-5oze5-qcj74-sex34-omprz-ivnsm-qvvhr-rfzpv-vae | Application | ~~true~~ ⇒ false | Subnet has more than 300 GiB state size |
| nl6hn-ja4yw-wvmpy-3z2jx-ymc34-pisx3-3cp5z-3oj4a-qzzny-jbsv3-4qe | Application | ~~true~~ ⇒ false | Subnet has more than 300 GiB state size |
| o3ow2-2ipam-6fcjo-3j5vt-fzbge-2g7my-5fz2m-p4o2t-dwlc4-gt2q7-5ae | Application | ~~true~~ ⇒ false | Subnet has more than 300 GiB state size |
| opn46-zyspe-hhmyp-4zu6u-7sbrh-dok77-m7dch-im62f-vyimr-a3n2c-4ae | Application | ~~true~~ ⇒ false | Subnet has more than 300 GiB state size |
| pae4o-o6dxf-xki7q-ezclx-znyd6-fnk6w-vkv5z-5lfwh-xym2i-otrrw-fqe | Verified Application | false | Other verified subnets opened up in this run |
| pjljw-kztyl-46ud4-ofrj6-nzkhm-3n4nt-wi3jt-ypmav-ijqkt-gjf66-uae | Application | true |  |
| pzp6e-ekpqk-3c5x7-2h6so-njoeq-mt45d-h3h6c-q3mxf-vpeq5-fk5o7-yae | Application | false | Explicitly marked as non-public (Fiduciary subnet) |
| qdvhd-os4o2-zzrdw-xrcv4-gljou-eztdp-bj326-e6jgr-tkhuc-ql6v2-yqe | Application | true |  |
| qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae | Verified Application | false | Other verified subnets opened up in this run |
| shefu-t3kr5-t5q3w-mqmdq-jabyv-vyvtf-cyyey-3kmo4-toyln-emubw-4qe | Verified Application | false | Explicitly marked as non-public (Distrikt subnet cannot be public before migrating away from ICQC) |
| snjp4-xlbw4-mnbog-ddwy6-6ckfd-2w5a2-eipqo-7l436-pxqkh-l6fuv-vae | Verified Application | false | Other verified subnets opened up in this run |
| tdb26-jop6k-aogll-7ltgs-eruif-6kk7m-qpktf-gdiqx-mxtrf-vb5e6-eqe | System | false | System subnets should not have public access |
| uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe | System | false | System subnets should not have public access |
| w4asl-4nmyj-qnr7c-6cqq4-tkwmt-o26di-iupkq-vx4kt-asbrx-jzuxh-4ae | Verified Application | false | Other verified subnets opened up in this run |
| w4rem-dv5e3-widiz-wbpea-kbttk-mnzfm-tzrc7-svcj3-kbxyb-zamch-hqe | System | false | System subnets should not have public access |
| x33ed-h457x-bsgyx-oqxqf-6pzwv-wkhzr-rm2j3-npodi-purzm-n66cg-gae | Application | false | Explicitly marked as non-public (SNS subnet) |
| yinp6-35cfo-wgcd2-oc4ty-2kqpf-t4dul-rfk33-fsq3r-mfmua-m2ngh-jqe | Application | false | Subnet has more than 300 GiB state size |



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134498)

Updating the list of public subnets - SubnetManagement - NNS Id 134498

This proposal updates the configuration of the NNS subnet to increase the maximum amount of ingress messages allowed in a block to 1000, and increases the DKG interval length to 499 (meaning a DKG interval and state checkpoint takes place every 500 rounds). The main goal of this proposal is to minimize configuration differences between subnets.

 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131699)

Update configuration of subnet: tdb26 - SubnetManagement - NNS Id 131699

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
IC OS Version Election, Protocol Canister Management

## Is this a team grant application?
 yes 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/82)
Hi @lara and Everyone,

I am Manvick, founder of Zenith Code LLC, and my team are excited to apply for the “IC OS Version Election” grant. We have been actively involved in the IC community since mid 2022. We have in-depth knowledge of creating dapps on ICP including but not limited to writing smart contracts in Motoko and architecting/designing multi canister apps on ICP. We are also a node provider on the ICP network.

Node Provider: https://dashboard.internetcomputer.org/provider/pa5mu-yxsey-b4yrk-bodka-dhjnm-a3nx4-w2grw-3b766-ddr6e-nupu4-pqe

### About Zenith Code and Our Team

Team Members and relevant experience:

* Manvick
  * Software Engineer by background with over 8+ years of experience in large scale Distributed systems and applications with 5+ years of experience in blockchain technologies.
  * Actively worked on Nutanix distributed software defined storage and I was responsible for designing and developing the service which provided deduplication, data resilience, and fault tolerance in the node cluster.
  * Education: Master’s in Computer Science from Texas State University, USA
  * LinkedIn: https://www.linkedin.com/in/manvick-paliwal-67441676/

* Ipsita Parida
  * 7+ years of experience in designing and implementing distributed systems including cryptography while at RSA, and AI/ML based projects..
  * Education: Master’s in System design engineering from University of Waterloo, Canada
  * LinkedIn: https://www.linkedin.com/in/ipsitaparida/
  * Github: https://github.com/ipsitaparida?tab=repositories
* Harsh Patni (Ex Microsoft Software Engineer)
  * 8+ years of experience in software engineering
  * Education: Master’s in Computer Science from Texas State University, USA
  * LinkedIn: https://www.linkedin.com/in/hpatni/
* Yuvika Khardenavis
  * Software Engineer, University of Waterloo graduate
  * 4+ years of experience in Firmware and OS level design and development.
  * LinkedIn: https://www.linkedin.com/in/ykharden/
* Vishal Kumar
  * 8+ years of experience leading software development teams in agile frameworks over various technology stacks.
  * Education: Master’s in Computer Science from Texas State University, USA
  * LinkedIn: https://www.linkedin.com/in/vishalkumarmg/

* Yamini K
  * 5+ years of hands-on experience in full stack software development in technologies like ReactJS, GraphQL.
  * LinkedIn: https://www.linkedin.com/in/yaminichowdary/

Application Details

Topic(s) we Apply For:

1. IC OS Version Election
2. Protocol Canister Management

Team Grant:
Yes

Size of our Team:
6 members

### Relevant Experience and Technical Knowledge

* Operating nodes for several months on ICP (Zenith Code LLC).
* Relevant experience in installing IC OS and monitoring nodes.
* Strong understanding of the ICP infrastructure layer.
* As a development shop in the ecosystem, we have assisted various projects in setting up their proof of concept and MVP.
* Actively contributed to writing dapps in Motoko for in-house purposes.
* Over 7 years of experience in web3 and large-scale distributed systems.
* ICP enthusiast with a deep understanding of its core technology and architecture.
* Experience in designing large-scale distributed systems for storing user data across multiple nodes in RF-2 and RF-3 production clusters.
* Worked on the design and development of NDFS (Nutanix Distributed File Storage), similar to Google File System and blockchain data storage.

### Why we Want to Be a Voting Neuron

* By becoming a voting neuron we want to contribute towards decentralization of the ICP network.
* We believe we have the right skill set to evaluate the proposals and vote on them.
* We want to become a leading voting neuron with the capability of reviewing other governance proposals in the future.

### Why We Need the Grant

We have been working full-time jobs and working part time on IC, and the grant will help us get one step closer to contributing full-time to the IC community. With Zenith Code, We plan to expand, add more nodes, develop large-scale distributed DAO products, and add significant value to the IC community.

### Long-Term Interest in ICP

We are fascinated by ICP technology and its long-term goals of creating a community cloud infrastructure. This vision, if realized, will add immense value globally and reduce dependence on major cloud players like AWS and GCP in the market. Zenith Code is also a stakeholder and long term node provider in the IC ecosystem.

### Interest in the Topics Applied For

We are interested in applying for
1. IC OS Version Election.
2. Protocol Canister Management.

We have expertise in large scale distributed systems, particularly distributed software-defined storage, cryptography, and web3.

### Long-Term Commitment as a Voting Neuron

As an existing node provider in the IC ecosystem, we are committed to the long-term growth of the IC network. This commitment is driven by both personal interests and a broader vision of making the world a better place by contributing in the development of public cloud infrastructure.

### Voting Principles

Core Principle: Decentralization

* Definition and Relevance: The Nakamoto Coefficient measures the number of entities that must collude to control a system. A higher coefficient signifies greater decentralization and, consequently, a more secure and resilient network.
* Application to Voting: Applying this principle to voting within the IC ecosystem, we emphasize the need for a diverse and decentralized set of voters to prevent centralization and ensure fair representation of the community’s interests.

Ensuring Robust Decentralization

* Diverse Voting Participation: By adhering to decentralization principles, our voting approach aligns with the IC community and foundation. This means advocating for broad participation across various stakeholders to avoid power concentration.

Evolving with Community Decisions

* Adaptive Voting Strategy: Our commitment to evolving voting strategies based on community discussions reflects a dynamic approach to maintaining and enhancing decentralization. We plan to formalize a process in which we will actively listen to community inputs and adapt our voting accordingly.
* Continuous Improvement: By aligning future voting with community conclusions on decentralization, our approach ensures that the network remains resilient to centralization risks, analogous to maintaining a high Nakamoto Coefficient.

We are eager to contribute to the ICP community in a structured and impactful way. Thank you for considering our application. 🙏



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131785)

Voting grant application of Zenith Code LLC for topic Protocol Canister Management - Governance - NNS Id 131785

Node provider '162 Digital Capital' is creating a new Node Operator id
for adding 14 nodes in the sg2 data center. This new Node Operator
ID will be used to redeploy the existing nodes in the data center under the
recommended non-HSM deployment model.

Once the nodes are redeployed under the new Node Operator ID, 162 Digital Capital will
submit additional proposals to remove the old Node Operator record and change the reward
type for the nodes (once applicable).

This proposal is in
line with motion proposal 132553 for node rewards after 48 months, the proposal
is clarified in this forum post: https://forum.dfinity.org/t/proposal-update-interim-gen-1-node-provider-remuneration-after-48-months/35001/6 and this wiki link https://wiki.internetcomputer.org/wiki/OneSixtyTwo_Digital_Capital


 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/134483)

Add qxonx as a Node Operator of Node Provider: 6nbcy - NodeAdmin - NNS Id 134483

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Protocol Canister Management

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/85)
### Applicant Information

* **Name**: Behrad
* **Topic(s) Applying For**: Protocol Canister Management proposals
* **Application Type**: Individual

### Presentation of Who We Are

**B3Pay Team**:
- **Behrad (Manager and Founder)**:
  - [LinkedIn](https://www.linkedin.com/in/b3hr4d)
  - [GitHub](https://github.com/b3hr4d)
  - [X](https://x.com/b3hr4d_dev)
- **Ali (AI and Machine Learning Developer)**:
  - [LinkedIn](https://www.linkedin.com/in/alifarahmandfar)
  - [GitHub](https://github.com/alifrmf)
- **Bahamin (Junior Motoko Developer)**:
  - [LinkedIn](https://www.linkedin.com/in/bahamin-dehpour-deylami)
  - [GitHub](https://github.com/bahamin1)
- **Neuron ID:** [16122208542864232355](https://dashboard.internetcomputer.org/neuron/16122208542864232355)

### Team Size and Composition

Our team, "[B3Pay](https://github.com/B3Pay)":

1. **Behrad (Manager and Founder)**
   - 12 years of web development experience
   - 4 years of Ethereum development
   - 2 years of ICP development
   - Role: Strategic direction, project management, and senior development

2. **Ali (AI and Machine Learning Developer)**
   - Expert in Machine Learning and Deep Learning
   - Focus: Integrating AI-driven solutions into ICP projects

3. **Bahamin (Junior Motoko Developer)**
   - Specializes in Motoko (the native language of the Internet Computer)
   - Focus: Decentralized application development on ICP

### Team Vision

B3Pay is dedicated to advancing the Internet Computer ecosystem through innovative development, thoughtful governance, and community engagement. We aim to bridge the gap between cutting-edge technology and practical, user-centric applications on the ICP platform.


### Relevant Experience

1. **[B3Forge (Candid UI)](https://sehgq-cqaaa-aaaap-ahc4q-cai.icp0.io/)**
   - Description: An enhanced Candid UI for seamless interaction with ICP canisters
   - Key Features: Improved user interface, advanced debugging tools

2. **[B3Wallet](https://mnrs5-4qaaa-aaaap-abc5a-cai.icp0.io/)**
   - Description: A secure and user-friendly wallet for ICP assets
   - Key Features: Multi-signature and Multi-chain support

3. **[B3Note](https://4lidq-zqaaa-aaaap-abkbq-cai.icp0.io/)**
   - Description: Decentralized note-taking application on ICP
   - Key Features: End-to-end encryption

4. **[ic-reactor](https://b3pay.github.io/ic-reactor/) (Frontend Library)**
   - Description: A frontend library for building ICP DApps
   - Key Features: Modular components, optimized for ICP integration

### Technical Contributions

- [B3Forge Repository](https://github.com/B3Pay/b3forge)
- [B3Wallet Repository](https://github.com/B3Pay/B3Wallet)
- [B3Note Repository](https://github.com/B3Pay/b3note)
- [ic-reactor Repository](https://github.com/B3Pay/ic-reactor)
- [B3Utils Repository](https://github.com/B3Pay/b3_utils)

### Educational Contributions

- [ETH Payment Tutorial](https://forum.dfinity.org/t/building-a-cross-chain-eth-payment-and-e-commerce-platform-on-the-internet-computer-a-step-by-step-tutorial/23938)
  - Comprehensive guide on integrating Ethereum payments with ICP
  - [Tutorial Repository](https://github.com/b3hr4d/eth_payment_tutorial)

### Motivation for Becoming a Voting Neuron

We want to be a voting neuron to:
1. Actively shape the future of the ICP ecosystem.
2. Ensure technical decisions align with community interests.
3. Stay informed about protocol changes to keep our contributions relevant and impactful.

### Need for the Grant

The grant will enable us to:
1. Dedicate more resources to understanding and contributing to Protocol Canister Management.
2. Offer our services at affordable rates, making quality decentralized solutions accessible.
3. Invest time in research and development of innovative ICP-based solutions.

### Long-Term Interest in ICP

We are committed to ICP's long-term success because:
1. We believe in ICP's potential to revolutionize decentralized computing.
2. Our team has invested significant time and resources in building on the ICP platform.
3. We see ICP as the future of blockchain technology and want to be at the forefront of its development.

### Interest in Protocol Canister Management

We are particularly interested in this topic because:
1. It's critical for maintaining the security and functionality of ICP.
2. Our technical expertise aligns well with the requirements of managing and reviewing protocol canisters.
3. We see it as an opportunity to contribute significantly to the core infrastructure of ICP.

### Long-Term Commitment as a Voting Neuron

We plan to remain a voting neuron in the long term because:
1. Our business strategy is closely tied to the success of the ICP ecosystem.
2. We are committed to ongoing learning and adaptation in the rapidly evolving blockchain space.
3. We believe in the importance of consistent, informed governance for the long-term stability of ICP.

### Voting Principles

Our voting will be guided by the following principles:
1. **Security**: Prioritizing proposals that enhance overall ecosystem security.
2. **Scalability**: Supporting initiatives that improve network capacity and efficiency.
3. **Innovation**: Favoring proposals that drive technological advancements on ICP.
4. **Community Benefit**: Backing ideas that bring tangible benefits to developers and users.
5. **Transparency**: Committing to clear communication of our voting rationale.

We believe our team's diverse skills, proven track record, and unwavering commitment to the ICP ecosystem make us ideal candidates for this grant and role as voting neurons. Thank you for considering our application.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131764)

Voting grant application of B3Pay for topic Protocol Canister Management - Governance - NNS Id 131764


This proposal transfers max weekly amount of ICP to stake with WaterNeuron.
            

Stake Maximum Weekly ICP with WaterNeuron

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Protocol Canister Management, IC OS Version Election, Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 yes 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/78)
Hi @lara and ICP community,

My name is Wenzel Bartlett, founder of **CodeGov**.  This is our formal application for the Grants for Voting Neurons program offered by DFINITY.  

### TL;DR
We have decided to apply for all four team grant opportunities, which includes [IC-OS Version Election](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/78010556105983937984590438937075688039/?ref=ffpc5-aiaaa-aaaaf-aacva-cai), [Protocol Canister Management](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/168083459961697538699863191526193241390/?ref=ffpc5-aiaaa-aaaaf-aacva-cai), [Subnet Management](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/19625648570830622662772248501612437419/?ref=ffpc5-aiaaa-aaaaf-aacva-cai), and [Participant Management](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/324352774006988329354260824487234716358/?ref=ffpc5-aiaaa-aaaaf-aacva-cai) & [Node Admin](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/261185533762247244401204502467932456179/?ref=ffpc5-aiaaa-aaaaf-aacva-cai).  The CodeGov team has been reviewing and voting independently on technical NNS proposals for over a year.  We hope to continue making an impact on the decentralization of NNS governance through funding from this program.  We are a larger team of developers from the ICP community who have the skills to provide an educated evaluation of proposal details, document their findings, and a willingness to vote reliably on every proposal.  There are 8 reviewers on our team along with a marketing manager and a project manager.

### CodeGov
Details about the CodeGov organization including our [manifesto](https://www.codegov.org/manifesto), [team members, and known neuron configuration](https://www.codegov.org/neuron) can always be found on our website at [codegov.org](https://www.codegov.org/).  The configuration of the CodeGov known neuron is actively managed to ensure that Followees for each proposal topic are selected who are fully committed and available to perform detailed reviews within 48 hours proposal creation.  The CodeGov known neuron vote is cast automatically by consensus of our reviewers who are configured as Followees for the topics in which we specialize.  In the rare event that we cannot reach consensus automatically due to unforeseen circumstances, then vote for the CodeGov neuron is cast manually based on feedback from the reviewers who have been able to complete their review the proposal within this timeframe.  Hence, we always strive to complete our reviews as soon as possible and well before DFINITY votes.  

The CodeGov neuron owns the minimal amount of voting power required to participate in NNS governance, but we trigger 5-6% total voting power in the NNS for the topics that we cover.  Hence, the voting power that we trigger is 100% provided by other neurons who have chosen to follow us on these topics.  This is a great honor and a heavy responsibility that we take very seriously.  It inspires us to perform our due diligence on every proposal and reminds us that our work has been making a difference to the NNS governance community.

In addition to participation in NNS voting, we also have a [CodeGov WTN neuron](https://oc.app/community/3fudd-diaaa-aaaar-bgmca-cai/channel/139936864411093443261235657527242394420/0/1?open=true) that votes on WaterNeuron proposals.  [WaterNeuron](https://docs.waterneuron.fi/) is a liquid staking protocol built on ICP that owns very large 6 month and 8 year neurons and enables WTN token owners to cast the votes for these large NNS neurons.  CodeGov participates in the WTN governance process because it is open to the community and has a growing influence on NNS governance.  We have built a vote relay canister that automatically casts the same vote on WTN NNS proposals that CodeGov already casts on NNS proposals.  The WaterNeuron team recently [announced](https://x.com/WaterNeuron/status/1816905884423065740) that it is following the CodeGov WTN neuron on the WTN proposal topic called “Vote on NNS Proposals”.  This is another honor, privilege, and responsibility that demonstrates the positive impact that CodeGov has been making on the ICP community.

### IC-OS Version Election
CodeGov reviewers have over a year of experience reviewing IC-OS Version Election proposals and we have 6 reviewers who are dedicated to continuing that effort if we are awarded the grant for this topic.  These reviewers include @Lorimer @ZackDS @Zane @cyberowl @hpeebles @ilbert.  There are many examples of prior reports that our reviewers have posted that can be found in our [IC-OS Version Election channel](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/78010556105983937984590438937075688039/?ref=ffpc5-aiaaa-aaaaf-aacva-cai) in our CodeGov community on OpenChat, which is a strong demonstration of our qualifications on this topic.

### Protocol Canister Management
We have 2 months of experience reviewing System Canister Management proposals, which includes all canisters that are included in the new topic titled Protocol Canister Management.  We have 5 reviewers who are dedicated to continuing that effort if we are awarded the grant for this topic.  These reviewers include @ZackDS @Zane @cyberowl @LaCosta @timk11.  There are many examples of prior reports that our reviewers have posted that can be found in our [System Canister Management channel](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/168083459961697538699863191526193241390/?ref=ffpc5-aiaaa-aaaaf-aacva-cai) in our CodeGov community on OpenChat, which is a strong demonstration of our qualifications on this topic.

### Participant Management & Node Admin
We have decided to apply for the Participant Management & Node Admin grant because we have 4 reviewers who are willing to review these topics if we are awarded the grant.  They are already gaining experience on these proposal topics by performing reviews on a few past proposals and all current proposals.  Based on this experience and our evaluation of the difficulty / effort required to perform these reviews, we believe we have the skill and capacity required.  Our reviewers will include @ZackDS @LaCosta @timk11 @Cris.MntYetti.  You can see the reports of our reviewers in our [Participant Management channel](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/324352774006988329354260824487234716358/?ref=ffpc5-aiaaa-aaaaf-aacva-cai) and our [Node Admin channel](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/261185533762247244401204502467932456179/?ref=ffpc5-aiaaa-aaaaf-aacva-cai) in our CodeGov community on OpenChat, which we offer as evidence of our qualifications on this topic.

### Subnet Management
We have decided to apply for the Subnet Management grant because we have 3 reviewers who are willing to review this topic if we are awarded the grant.  They are already gaining experience on this proposal topic by performing reviews on a few past proposals and all current proposals.  Based on this experience and our evaluation of the difficulty / effort required to perform these reviews, we believe we have the skill and capacity required.  Our reviewers will include @ZackDS @LaCosta @timk11.  You can see the reports of our reviewers in our [Subnet Management channel](https://oc.app/community/32l35-yaaaa-aaaar-aw57q-cai/channel/19625648570830622662772248501612437419/?ref=ffpc5-aiaaa-aaaaf-aacva-cai) in our CodeGov community on OpenChat, which we offer as evidence of our qualifications on this topic.

One of our team members and regular IC-OS Version Election reviewers, @Lorimer, is keen to maximize the funded time that he can allocate to Subnet Management proposals.  Therefore, he is planning to submit a separate application for this topic as an individual reviewer. He will provide more context in his application, but please note that he has the full support of the CodeGov project to pursue the grant for this topic on his own.  He is a very strong candidate for this grant.

### Voting Principles
While the teams listed above is our current plan to staff these reviews for any proposal topic where we are awarded a grant, we reserve the right to change these teams and our known neuron Followee configuration as needed.  We will actively manage our team membership in a way that ensures we have skilled reviewers dedicated to each topic who can make the time and resource commitment to these reviews for the duration of the grant program.  Hence, if anyone needs to drop out for personal reasons or because they are not in compliance with the grant requirements or our CodeGov team standards, then we will recruit and train others to fill their spots.  We also may add additional team members as needed to ensure that we are able to fulfill our commitment to these proposal topics in the most reliable way possible.  Performing technical reviews of NNS proposals is real work that requires skilled developers who are dedicated to the task every week.  It can only be accomplished reliably with adequate funding that developers are willing to accept.  Our reviewers are asked to review each proposal for technical correctness and compliance with established work processes defined by the NNS community and/or DFINITY and to vote on each proposal with their own convictions.  They are expected to explain and defend their vote, but to always remain diplomatic and civilized in how they make their case.  The fact that we have a larger team provides a safety in numbers where individual reviewers can have an opinion that differs from the rest of the reviewers, which provides an opportunity to raise awareness of differing opinions.  Having a larger team enables us to be flexible in our organizational structure and work processes to ensure we are a reliable known neuron to follow on any proposal topic.  We have spent a lot of time trying to gain experience and credibility as reviewers of technical NNS proposals and one of our goals is continuous improvement.

### Final Remarks
Thank you for the opportunity to apply for these grants.  Whether or not we get some or all the grants, CodeGov will remain committed to supporting decentralization of the NNS through active participation in governance.  Our neuron will always be configured to follow people and organizations in the ICP community who have publicly announced that they are committed to being reliable and educated Followees on any proposal topic.  We will not follow anyone who pencil whips their vote or casts automatic yes or no votes without first making a concerted effort to review technical details and vote with an educated opinion.  If we cannot find suitable Followees for a specific topic, then of course we will follow DFINITY on that topic.  DFINITY is an appropriate Followee for any topic because they offer an educated and active voice on all NNS changes.  However, if decentralization is our goal, then CodeGov is here as an option to help enable the ICP community to move in that direction.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131765)

Voting grant application of CodeGov for topic Protocol Canister Management - Governance - NNS Id 131765

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Protocol Canister Management, Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/46)
Hey @lara and ICP community members. 

I would like to be considered for the **Protocol Canister Management** grant, the **Participant Management & Node Admin** grant, and the **Subnet management** grant. I've engaged with many of you within the ICP community over the years, but for those of you whom I've yet to meet: 

**My name is *Jesse D. Williams Jr.*** The neuron ID that I will be voting with on behalf of Personal DAO is:  `6459874325470209959`

I'm an ICP developer building [Personal DAO](https://forum.dfinity.org/t/personal-dao-a-commoditized-dao-that-functions-as-a-icp-neuron-pool-for-now-more-features-on-the-way/29958?u=jesse) which, in short, is a commoditized application that functions as a turn key DAO that communities can use to pool their neuron stakes, lend to earn interest, leverage their neuron stakes to borrow liquid ICP, fund community initiatives and more. 

My X account can be found here: https://x.com/JesseThaGreat_
The Personal DAO X account can be found here: https://x.com/Personal_DAO

My LinkdIn account can be found here: https://www.linkedin.com/in/jesse-williams-m-s-8369601ab

**My team consists of 2 developers** (myself and [Samuel Atwebembeire](https://x.com/samthetutor2))

My **relevant experience** consists of:

* 10+ years of quantitative reasoning background that includes combinatorics, optimization of algorithms for space and time complexity and teaching/training students of computer science
* 5+ years of industry experience as a software engineer
* 3+ years of experience developing on the Internet Computer
* 3+ years participating in NNS governance as an active voter on the Internet Computer
* 5+ years of rigorous independent study within the field of economics, economic history, monetary policy and capital markets

**Relevant Technical Knowledge** includes:

* Familiarity with NNS architecture and functionality
* Familiarity with the DFX SDK for building, verifying and deploying ICP canisters
* Proficiency with Motoko, Rust, Typescript and Javascript development
* Proficiency with Optimization of algorithmic functions with respect to space and time complexity

For those of you who would like to see a reference to my work, the best showcase would be the [Personal DAO Decentralized Web Application](https://unl3b-waaaa-aaaam-ach6a-cai.icp0.io/)

note: *(The github repo to this project is still private pending a code audit. The link above takes you to the live instance of the first Personal DAO deployed to the internet computer. To access it, click the *login* button and then authenticate your internet identity. Doing so automatically submits a request for access to the DAO. Once you've done so, reach out to me with your principal ID and I will approve you for access to the DAO. From there, you'll be able to participate as any other DAO member.)*

My **motivation for becoming a voting neuron** is that I've invested several years of time and resources developing a digital business on top of the internet computer protocol as well as a positive working relationship with the community. I have every interest in seeing to it that the IC is properly governed so that I may continue to carry out my mission of onboarding participants of the TradFi economy to the DeFi space. 

My **reason for needing grant funding** is that I work full time towards contributing to the internet computer ecosystem as a builder, which limits the time that I have available for pursuing other sources of income. In order to continue to contribute to this ecosystem and sustain myself, it will require some form of basic funding that allows me to meet my financial obligations in the real world. 

I am **acting in the long-term interest of the ICP ecosystem** because this is the ecosystem that I've chosen to host the technical foundation of my web3 business (Personal DAO). I benefit in no way, shape or form from voting in a way that is counterproductive to the Internet Computer's security, operations, and/or community. To do so would render my own efforts and resources over the past several years unfruitful.

I am **interested in the topics for which I am applying** because I understand the implications that these topics have for the development and security of the ICP ecosystem. Additionally, these are the topics that I feel confident voting on as I believe I have the technical background and experience needed in order to make an informed decision on these topics. 

**I will remain a voting neuron in the long term, even after the grant program has ended** because, as the founder and lead developer of an ICP project, I have a vested interest in helping ensure that the network's security and integrity is maintained for the sake of the business that I operate. Furthermore, Personal DAO requires that the DAO's neurons select a delegate for their vote, I will be the default delegate for all Personal DAOs deployed to the Internet Computer. This means that in order to service my own community of supporters, I am required to maintain an active role as a voting neuron- independently of this grant. 

My **voting principles** derive from a commitment to decentralization and sovereignty for users and builders- no introduction of any centralized points of failure that could be manipulated to the detriment of end-users. My conviction for this principle is demonstrated by the architecture that I've chosen for Personal DAO in which no entity outside of each respective Personal DAO (not even myself as the developer) may interfere with the DAO's canister's WASM modules nor their internal governance.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131782)

Voting grant application of Personal DAO for topic Subnet management - Governance - NNS Id 131782

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/79)
Greetings @lara and ICP community members.

We are interested in being considered for 1. **Participant Management & Node Admin** ii. **Subnet Management** neuron grants as **ICP Hub South Africa.**

We are NOT applying for a “Team Grant”

ICP Hub South Africa Socials

[Website](https://mw3.io) | [Twitter](https://x.com/icphub_ZA) | [LinkedIn](https://www.linkedin.com/company/mzansiweb3) | [Telegram](https://t.me/mzansiweb3icp) | [Github](https://github.com/mzansiweb3-icp-hub)

**Team**

* Shaheer Karrim (Co-Founder of ICP Hub South Africa)

  [Twitter](https://x.com/icphub_ZA) | [LinkedIn](http://linkedin.com/in/shaheer-karrim-2252882b)

  Voting Neuron Members

 * Confidence Nyirenda: (DevRel, Instructor and Software Developer)

   [Twitter](https://x.com/crnyirenda) | [LinkedIn](https://www.linkedin.com/in/confidencenyirenda/) | [Github](https://github.com/renegadec)

* Enoch Chirima: (DevRel, Instructor, Software Developer, Motoko Coach)

  [Twitter](https://twitter.com/iamenochchirima) | [LinkedIn](https://www.linkedin.com/in/iamenochchirima/) | [Github ](https://github.com/iamenochchirima)

### Relevant Experience

Confidence Nyirenda is a dedicated software developer and entrepreneur who has been actively involved with the Internet Computer. As the founder of [Tswaanda Africa](https://tswaanda.com/), a project that has received a grant from Dfinity, he is committed to driving the adoption and understanding of Internet Computer technology in southern Africa. His role as an educator has been crucial in expanding the reach and impact of this innovative technology across the region. With more than six years of experience in the blockchain space, Confidence has developed a deep understanding of the technology and its applications. He has been instrumental in building and nurturing communities around blockchain, fostering collaboration and growth. In addition to his development work, Confidence also holds an active voting neuron on the NNS

Myself, Enoch Chirima, I am a Software Developer with four years of experience and 2 years of experience developing on the Internet Computer. Also a DevRel and Lead Bootcamp and Hackathons Instructor at ICP Hub South Africa and has experience in Motoko, Rust, TypeScript, Python, Solidity, and other languages. I have worked and consulted on multiple projects on the Internet Computer including Tswaanda Africa, agriiDao, and ICPuzzles . I also contributed to the IC WebSockets by creating the Motoko implementation examples.

### Technical Knowledge

1. Confidence and I are developers and have been deeply involved in ICP for about 2 years, we have built and contributed to multiple projects on the Internet Computer.

2. We have run successful boot camps and hackathons in South Africa, Zimbabwe, and Zambia. We are currently incubating six projects being built on the Internet Computer that originated from the hackathons we conducted.

### Motivation for Becoming a Voting Neuron

1. As an ICP Hub we feel it’s very important for us to contribute in as much as we can to the decentralization and progression of ICP, joining the governance process as a voting neuron enables us to achieve that.
2. The goals of the ICP align closely with our mission as an ICP Hub. We are dedicated to supporting and initiating projects that bolster the ICP ecosystem, ensuring that our objectives and efforts contribute to the protocol's strength and sustainability.

**Why do we need the grant funding**

* Grant funding is essential for us to allocate more time and resources to the review process and voting. With this support, we can increase our team's capacity, dedicate more hours to these crucial tasks, and potentially expand our team by bringing in additional reviewers. This will enhance the quality and efficiency of our work.

**Our Long-Term Interest in ICP:**

* As a hub, all our activities are deeply involved and align with ICP's goals. We are dedicated to expanding ICP in Africa. Our long-term goals depend on the success of the ICP ecosystem because we help startups and companies build on ICP. The growth and success of ICP directly impact our mission and vision for the future.

**Interest in Participant Management & Node Admin and Subnet Management:**

* We have decided to apply for the Participant Management & Node Admin and the Subnet Management grants because we have the relevant experience to review these topics effectively. This involvement will also help us gain more knowledge about the protocol's architecture.
* Since our team is not very large, we are looking to start with something that won't require too much time but still allows us to contribute meaningfully.

**Long-term participation as a neuron**

* At ICP Hub South Africa, our long-term interest is rooted in our commitment to advancing ICP. Our activities, including boot camps, hackathons, start-up incubations and community building, are aligned with ICP's goals. We believe that the growth and success of the ICP ecosystem directly impact our mission to support projects/startups and companies building on ICP, driving innovation and economic development in the region so we are certain our contributions as a hub will continue even after the grants.

### Voting Principles for Our Hub

* Our commitment includes voting on at least 90% of proposals, providing clear explanations for our decisions, and sharing detailed reports and evidence on the forum.
* We  ensure each team member has fully understood and is in sync with the final decisions and critically analyzing and addressing all different opinions.
* We ensure that each proposal is reviewed for technical correctness and compliance by skilled team members who are committed to the task for when we consider adding additional reviewers.
Thank you  :pray:t5:



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131778)

Voting grant application of ICP Hub South Africa for topic Subnet management - Governance - NNS Id 131778

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 yes 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/88)
Hi everyone,

I’m [**Javier Arroyo Ferrer**](https://www.linkedin.com/in/javier-arroyo-ferrer-%E2%99%BE-94546a50?originalSubdomain=ca), Co-Founder and leader of the [**ICP HUB Canada & US**](https://x.com/icphub_CA) and Partner at [**Quantum Leap Labs Inc.**](https://quantumleaplabs.ca/) As a dedicated team of over 5 members focusing on the Internet Computer Protocol, we ensure sufficient redundancy to have at least 3 reviewers per proposal. We are interested in applying for a team grant and respectfully seek consideration for the following segments:

1, Participant Management & Node Admin
2. Subnet Management grants

While we have collaborated with many esteemed members of the ICP community since Genesis, we are eager to connect with those we have yet to meet. We are the team behind ICP HUB Canada & US and its official incubator, Quantum Leap Labs.

**Team:**

Our team comprises professionals with backgrounds in finance, computer science, and software development:

- [**Javier Arroyo Ferrer**](https://www.linkedin.com/in/javier-arroyo-ferrer-%E2%99%BE-94546a50?originalSubdomain=ca) (Partner at Quantum Leap Labs Inc/Leader of ICP HUB Canada & US)
- [**Athika Fatima**](https://www.linkedin.com/in/athika-fatima/) (Technical Program and Incubation Manager at Quantum Leap Labs, Community Manager at ICP HUB Canada & US)
- **Anjali Singla** (Technical Mentor at Quantum Leap Labs Inc, Developer Relations Manager at ICP HUB Canada & US)
[**Chetan Mittal**](https://www.linkedin.com/in/ichetanmittal/) (Developer Relations at ICP HUB Canada & US, ICP Master Instructor)
- [**Fawaz Malik**](https://www.linkedin.com/in/fawaz-i-malik/) (ICP Master Instructor)


**About Us:**

**Quantum Leap Labs Inc:**
As the official accelerator of ICP HUB Canada & US, we guide projects from inception to DAO on ICP. We provide strategic Internet Computer expertise to align project goals with DAO objectives, enabling informed decision-making and successful launches in the Web 3 space. Our full support includes tokenomics, canister design, legal setup, marketing, community building, SNS DAO, and grant applications. More info: **[Website](https://quantumleaplabs.ca/) | [Twitter](https://x.com/quantumleaplab) | [LinkedIn](https://www.linkedin.com/company/quantum-leap-labs/)**

**Team Members Involved in Voting Neurons:**

**Javier Arroyo Ferrer:** **[Twitter](https://x.com/quantumleaplab) | [LinkedIn](https://www.linkedin.com/company/quantum-leap-labs/)**
Javier is a prominent economist and entrepreneur driving blockchain innovation in North America. With over a decade of experience in banking and finance at leading institutions, he plays a crucial role in advancing the Internet Computer Blockchain across Canada and the United States. He is the Founder and Leader of the ICP HUB Canada & US AND PARTNER AT Quantum Leap Labs Inc.also a founding member of FUEL DAO, focusing on car renting and sharing, underscoring his commitment to pioneering real-world blockchain applications.

**Athika Fatima:** **[Twitter](https://twitter.com/athikafz) | [LinkedIn](https://www.linkedin.com/in/athika-fatima?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app) | [Github](https://github.com/athikaf)**
Athika is a Computer Engineer specializing in Blockchain Development. She has worked with over 120 startups as a Technical Product Manager, gaining extensive experience in various industries. Currently, she is a Technical Program and Incubation Manager at Quantum Leap Labs and a Blockchain Product Engineer at Bitcoin Bay Corp. Her expertise spans multiple programming languages and blockchain technologies.

**Anjali Singla:** **[Twitter](https://twitter.com/singlanjali3091) | [LinkedIn](https://www.linkedin.com/in/anjali-singla-02086649?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app) | [Github](https://github.com/angie3019)**
Anjali is a Software Developer and Technologist with a background in Computer Science. She has over a decade of experience in software development and has engaged with blockchain projects on Ethereum and Polygon since 2021. Her current role as Developer Relations Manager at ICP HUB Canada & US focuses on bridging the gap between developers and the community.

**Chetan Mittal:** **[Twitter](https://twitter.com/ichetanmittal) | [LinkedIn](https://www.linkedin.com/in/ichetanmittal?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app) | [Github](https://github.com/ichetanmittal)**
Chetan is a junior in Computer Science with diverse tech industry experience. He works as Developer Relations at ICP HUB Canada & US and as a Software Engineer at Flicfit in Japan. His technical skills include proficiency in Solidity, Motoko, Python, and TypeScript. He is also well-versed in canister management essential for developing scalable applications on the ICP platform.

**Fawaz Malik:** **[Twitter](https://twitter.com/fawazmalik95?lang=en) | [LinkedIn](https://www.linkedin.com/in/fawaz-i-malik?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app) | [Github](https://github.com/FawazMalik-jjj)**
Fawaz is an ambassador for Internet Computer Protocol (ICP) in the education sector. With a postgraduate degree in blockchain development, he has demonstrated keen interest and dedication to the intersection of technology and innovation. He actively engages in roles at an AI/blockchain startup and serves as a Motoko developer.

**Relevant Experience:**

Our team consists of Computer Scientists and Software Developer Engineers with expertise in WebAssembly, Rust, TypeScript, Motoko, and Python. We have accelerated numerous projects to successful DAO status on ICP and are significant contributors to the Internet Computer Blockchain in North America. We regularly conduct Motoko and other ICP courses, teach tech workshops, and organize hackathons at leading universities across North America.

**Technical Knowledge:**

Our technical team members possess strong backgrounds in Computer Science and have extensive experience building projects on the Internet Computer. We have analyzed and reviewed hundreds of projects for Quantum Leap Labs and have participated as judges in several hackathons.

Projects incubating on the ICP or participating on their development: 
1. [Fantasy Extreme](https://fantasyextreme.org/) 
2. [BlockBolt](https://blockbolt.io/) 
3. [Rubaru](https://rubaru.app/) 
4. [BIP Quantum](https://bipquantum.com/) 
5. [Pixel Paddle](https://www.pixelpaddle.com/)
6. [Mesias Brand Intelligence Spain](https://mesias.org.es/) 

**Motivation for Becoming a Voting Neuron:**

As early contributors to the Internet Computer Blockchain, we aim to leverage our expertise to improve the protocol and contribute to its decentralization. Our vision includes expanding the ICP community and ensuring the success of numerous projects as DAOs.

**Need for Grant Funding:**

Grant funding will help us achieve two key objectives:

Expand our incubation operations to support more ICP projects.
Onboard new technical talent to assist with proposal reviews and voting, enhancing our team's ability to manage proposals effectively.
Long-term Interest in ICP:

We plan to maintain a long-term presence in the ICP ecosystem, participating in conferences and incubating 10-30% of all successful SNS projects over the next four years.

**Voting Principles:**

We are committed to community engagement, delivering monthly reports, voting on at least 90% of proposals, and providing transparent explanations for our decisions. We will host AMAs and Tech Talks to review our decisions and ensure alignment with the community.

**Grant Scope:**

We plan to apply for grants in the following areas:

1. Participant Management & Node Admin
7. Subnet Management



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131772)

Voting grant application of ICP Hub Canada & US for topic Subnet management - Governance - NNS Id 131772

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Subnet management, Participant Management & Node Admin

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/86)
Greetings ALL community members!

We are interested in being considered for **Subnet Management**, and **Participant Management & Node Admin** neuron grants as **ICP Hub Poland.**

ICP Hub Poland:

[Twitter](https://x.com/ICPHUB_PL)
[LinkedIn](https://www.linkedin.com/company/icphub-pl)
[Telegram](https://t.me/ICP_PL)
[OpenChat](https://oc.app/community/qyqpi-viaaa-aaaar-bihgq-cai)

**Team**

* [Maciej Orłowski](https://www.linkedin.com/in/orlowski-maciej) (ICP Hub Poland Lead)

Voting Neuron Members:
* [Krzysztof Żelazko](https://x.com/kc_zelazko): (ICP Hub Poland Governance Lead, Lifeguard, Music Producer)
* [CryptoDEVence](https://oc.app/user/zhs7r-qqaaa-aaaar-a6bsq-cai): (Founder of ICP Polska, Software Developer, Motoko)

*Relevant Experience*

CryptoDEVence is a dedicated software developer who has been actively involved with the Internet Computer. As the founder of [ICP Polska](https://6ec2p-paaaa-aaaal-ai45q-cai.icp0.io), he is committed to driving the adoption and understanding of Internet Computer technology in Poland. His role as an educator has been crucial in expanding the reach and impact of this innovative technology across the region. He is a “old school” programmer who, as part of his Motoko education, created and is developing an app that will (we hope) be useful to the Polish crypto community someday. He tests various ICP solutions and shares his experiences. He plans to start publishing his first educational materials in September. At NNS, he votes every day with his morning coffee.

Myself, Krzysztof Żelazko. I am a Music Producer with ten years of experience and 2 years of experience developing on the Internet Computer. I have worked and consulted on multiple projects on the Internet Computer like [ICode DAO](https://x.com/ICodeDA0), [Rakeoff](https://rakeoff.io) or [8YearGangDAO](https://oc.app/community/6efj4-vqaaa-aaaar-ar2ia-cai/channel/69530127954244796840303922258183167660). Recently I also contributed to the ICP Hub Poland neuron by creating it and its decentralized voting framework. In addition to my development work, I also hold an active voting known neuron on the NNS.

*Motivation for Becoming a Voting Neuron*

* As an ICP Hub we feel it’s very important for us to contribute as much as we can to the decentralization and progression of ICP, joining the governance process as a responsibly voting neuron enables us to achieve that.
* The goals of the ICP align closely with our mission as an ICP Hub. We are dedicated to supporting and initiating projects that bolster the ICP ecosystem, ensuring that our objectives and efforts contribute to the protocol’s strength and sustainability.

**Why do we need the grant funding?**

* Grant funding is essential for us to allocate more time and resources to the review process and voting. With this support, we can increase our team’s capacity, dedicate more hours to these crucial tasks, and potentially expand our team by bringing in additional reviewers. This will enhance the quality and efficiency of our work and help us better communicate the governance activities with community.

**Why did we choose Subnet Management, and Participant Management & Node Admin?**

* We have decided to apply for the Subnet Management, and Participant Management & Node Admin grants because these topics are more flexible in terms of time for us, and we have the experience to effectively analyze these topics, as we do this now regularly anyway,
* Since our team is not very large, we are looking to start with something that won’t require too much time but still allows us to contribute meaningfully.

**Our Long-Term Interest in ICP**

* At ICP Hub Poland, our long-term interest is rooted in our commitment to advancing ICP. Our activities, including boot camps, hackathons, start-up incubations and community building, are aligned with ICP’s long-term growth.
* As a hub, all our activities are deeply involved and align with ICP's long-term growth goals. We are dedicated to expanding ICP in Poland. Our long-term goals depend on the success of the ICP ecosystem because we help startups and companies build on ICP. The growth and success of ICP directly impact our mission and vision for the future.
* As of now, part of advancing the ecosystem is to create and expand the governance structures for the Internet Computer. These activities include creating named neuron, promote governance among local communities, create space for active participation in governance of Internet Computer DAO and to help to improve the governing quality by actively participate in voting, reviewing & explaining proposals to the community.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131776)

Voting grant application of ICP Hub Poland for topic Subnet management - Governance - NNS Id 131776

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 yes 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/88)
Hi everyone,

I’m [**Javier Arroyo Ferrer**](https://www.linkedin.com/in/javier-arroyo-ferrer-%E2%99%BE-94546a50?originalSubdomain=ca), Co-Founder and leader of the [**ICP HUB Canada & US**](https://x.com/icphub_CA) and Partner at [**Quantum Leap Labs Inc.**](https://quantumleaplabs.ca/) As a dedicated team of over 5 members focusing on the Internet Computer Protocol, we ensure sufficient redundancy to have at least 3 reviewers per proposal. We are interested in applying for a team grant and respectfully seek consideration for the following segments:

1, Participant Management & Node Admin
2. Subnet Management grants

While we have collaborated with many esteemed members of the ICP community since Genesis, we are eager to connect with those we have yet to meet. We are the team behind ICP HUB Canada & US and its official incubator, Quantum Leap Labs.

**Team:**

Our team comprises professionals with backgrounds in finance, computer science, and software development:

- [**Javier Arroyo Ferrer**](https://www.linkedin.com/in/javier-arroyo-ferrer-%E2%99%BE-94546a50?originalSubdomain=ca) (Partner at Quantum Leap Labs Inc/Leader of ICP HUB Canada & US)
- [**Athika Fatima**](https://www.linkedin.com/in/athika-fatima/) (Technical Program and Incubation Manager at Quantum Leap Labs, Community Manager at ICP HUB Canada & US)
- **Anjali Singla** (Technical Mentor at Quantum Leap Labs Inc, Developer Relations Manager at ICP HUB Canada & US)
[**Chetan Mittal**](https://www.linkedin.com/in/ichetanmittal/) (Developer Relations at ICP HUB Canada & US, ICP Master Instructor)
- [**Fawaz Malik**](https://www.linkedin.com/in/fawaz-i-malik/) (ICP Master Instructor)


**About Us:**

**Quantum Leap Labs Inc:**
As the official accelerator of ICP HUB Canada & US, we guide projects from inception to DAO on ICP. We provide strategic Internet Computer expertise to align project goals with DAO objectives, enabling informed decision-making and successful launches in the Web 3 space. Our full support includes tokenomics, canister design, legal setup, marketing, community building, SNS DAO, and grant applications. More info: **[Website](https://quantumleaplabs.ca/) | [Twitter](https://x.com/quantumleaplab) | [LinkedIn](https://www.linkedin.com/company/quantum-leap-labs/)**

**Team Members Involved in Voting Neurons:**

**Javier Arroyo Ferrer:** **[Twitter](https://x.com/quantumleaplab) | [LinkedIn](https://www.linkedin.com/company/quantum-leap-labs/)**
Javier is a prominent economist and entrepreneur driving blockchain innovation in North America. With over a decade of experience in banking and finance at leading institutions, he plays a crucial role in advancing the Internet Computer Blockchain across Canada and the United States. He is the Founder and Leader of the ICP HUB Canada & US AND PARTNER AT Quantum Leap Labs Inc.also a founding member of FUEL DAO, focusing on car renting and sharing, underscoring his commitment to pioneering real-world blockchain applications.

**Athika Fatima:** **[Twitter](https://twitter.com/athikafz) | [LinkedIn](https://www.linkedin.com/in/athika-fatima?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app) | [Github](https://github.com/athikaf)**
Athika is a Computer Engineer specializing in Blockchain Development. She has worked with over 120 startups as a Technical Product Manager, gaining extensive experience in various industries. Currently, she is a Technical Program and Incubation Manager at Quantum Leap Labs and a Blockchain Product Engineer at Bitcoin Bay Corp. Her expertise spans multiple programming languages and blockchain technologies.

**Anjali Singla:** **[Twitter](https://twitter.com/singlanjali3091) | [LinkedIn](https://www.linkedin.com/in/anjali-singla-02086649?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app) | [Github](https://github.com/angie3019)**
Anjali is a Software Developer and Technologist with a background in Computer Science. She has over a decade of experience in software development and has engaged with blockchain projects on Ethereum and Polygon since 2021. Her current role as Developer Relations Manager at ICP HUB Canada & US focuses on bridging the gap between developers and the community.

**Chetan Mittal:** **[Twitter](https://twitter.com/ichetanmittal) | [LinkedIn](https://www.linkedin.com/in/ichetanmittal?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app) | [Github](https://github.com/ichetanmittal)**
Chetan is a junior in Computer Science with diverse tech industry experience. He works as Developer Relations at ICP HUB Canada & US and as a Software Engineer at Flicfit in Japan. His technical skills include proficiency in Solidity, Motoko, Python, and TypeScript. He is also well-versed in canister management essential for developing scalable applications on the ICP platform.

**Fawaz Malik:** **[Twitter](https://twitter.com/fawazmalik95?lang=en) | [LinkedIn](https://www.linkedin.com/in/fawaz-i-malik?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=ios_app) | [Github](https://github.com/FawazMalik-jjj)**
Fawaz is an ambassador for Internet Computer Protocol (ICP) in the education sector. With a postgraduate degree in blockchain development, he has demonstrated keen interest and dedication to the intersection of technology and innovation. He actively engages in roles at an AI/blockchain startup and serves as a Motoko developer.

**Relevant Experience:**

Our team consists of Computer Scientists and Software Developer Engineers with expertise in WebAssembly, Rust, TypeScript, Motoko, and Python. We have accelerated numerous projects to successful DAO status on ICP and are significant contributors to the Internet Computer Blockchain in North America. We regularly conduct Motoko and other ICP courses, teach tech workshops, and organize hackathons at leading universities across North America.

**Technical Knowledge:**

Our technical team members possess strong backgrounds in Computer Science and have extensive experience building projects on the Internet Computer. We have analyzed and reviewed hundreds of projects for Quantum Leap Labs and have participated as judges in several hackathons.

Projects incubating on the ICP or participating on their development: 
1. [Fantasy Extreme](https://fantasyextreme.org/) 
2. [BlockBolt](https://blockbolt.io/) 
3. [Rubaru](https://rubaru.app/) 
4. [BIP Quantum](https://bipquantum.com/) 
5. [Pixel Paddle](https://www.pixelpaddle.com/)
6. [Mesias Brand Intelligence Spain](https://mesias.org.es/) 

**Motivation for Becoming a Voting Neuron:**

As early contributors to the Internet Computer Blockchain, we aim to leverage our expertise to improve the protocol and contribute to its decentralization. Our vision includes expanding the ICP community and ensuring the success of numerous projects as DAOs.

**Need for Grant Funding:**

Grant funding will help us achieve two key objectives:

Expand our incubation operations to support more ICP projects.
Onboard new technical talent to assist with proposal reviews and voting, enhancing our team's ability to manage proposals effectively.
Long-term Interest in ICP:

We plan to maintain a long-term presence in the ICP ecosystem, participating in conferences and incubating 10-30% of all successful SNS projects over the next four years.

**Voting Principles:**

We are committed to community engagement, delivering monthly reports, voting on at least 90% of proposals, and providing transparent explanations for our decisions. We will host AMAs and Tech Talks to review our decisions and ensure alignment with the community.

**Grant Scope:**

We plan to apply for grants in the following areas:

1. Participant Management & Node Admin
7. Subnet Management



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131771)

Voting grant application of ICP Hub Canada & US for topic Participant Management & Node Admin - Governance - NNS Id 131771

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Protocol Canister Management, Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/46)
Hey @lara and ICP community members. 

I would like to be considered for the **Protocol Canister Management** grant, the **Participant Management & Node Admin** grant, and the **Subnet management** grant. I've engaged with many of you within the ICP community over the years, but for those of you whom I've yet to meet: 

**My name is *Jesse D. Williams Jr.*** The neuron ID that I will be voting with on behalf of Personal DAO is:  `6459874325470209959`

I'm an ICP developer building [Personal DAO](https://forum.dfinity.org/t/personal-dao-a-commoditized-dao-that-functions-as-a-icp-neuron-pool-for-now-more-features-on-the-way/29958?u=jesse) which, in short, is a commoditized application that functions as a turn key DAO that communities can use to pool their neuron stakes, lend to earn interest, leverage their neuron stakes to borrow liquid ICP, fund community initiatives and more. 

My X account can be found here: https://x.com/JesseThaGreat_
The Personal DAO X account can be found here: https://x.com/Personal_DAO

My LinkdIn account can be found here: https://www.linkedin.com/in/jesse-williams-m-s-8369601ab

**My team consists of 2 developers** (myself and [Samuel Atwebembeire](https://x.com/samthetutor2))

My **relevant experience** consists of:

* 10+ years of quantitative reasoning background that includes combinatorics, optimization of algorithms for space and time complexity and teaching/training students of computer science
* 5+ years of industry experience as a software engineer
* 3+ years of experience developing on the Internet Computer
* 3+ years participating in NNS governance as an active voter on the Internet Computer
* 5+ years of rigorous independent study within the field of economics, economic history, monetary policy and capital markets

**Relevant Technical Knowledge** includes:

* Familiarity with NNS architecture and functionality
* Familiarity with the DFX SDK for building, verifying and deploying ICP canisters
* Proficiency with Motoko, Rust, Typescript and Javascript development
* Proficiency with Optimization of algorithmic functions with respect to space and time complexity

For those of you who would like to see a reference to my work, the best showcase would be the [Personal DAO Decentralized Web Application](https://unl3b-waaaa-aaaam-ach6a-cai.icp0.io/)

note: *(The github repo to this project is still private pending a code audit. The link above takes you to the live instance of the first Personal DAO deployed to the internet computer. To access it, click the *login* button and then authenticate your internet identity. Doing so automatically submits a request for access to the DAO. Once you've done so, reach out to me with your principal ID and I will approve you for access to the DAO. From there, you'll be able to participate as any other DAO member.)*

My **motivation for becoming a voting neuron** is that I've invested several years of time and resources developing a digital business on top of the internet computer protocol as well as a positive working relationship with the community. I have every interest in seeing to it that the IC is properly governed so that I may continue to carry out my mission of onboarding participants of the TradFi economy to the DeFi space. 

My **reason for needing grant funding** is that I work full time towards contributing to the internet computer ecosystem as a builder, which limits the time that I have available for pursuing other sources of income. In order to continue to contribute to this ecosystem and sustain myself, it will require some form of basic funding that allows me to meet my financial obligations in the real world. 

I am **acting in the long-term interest of the ICP ecosystem** because this is the ecosystem that I've chosen to host the technical foundation of my web3 business (Personal DAO). I benefit in no way, shape or form from voting in a way that is counterproductive to the Internet Computer's security, operations, and/or community. To do so would render my own efforts and resources over the past several years unfruitful.

I am **interested in the topics for which I am applying** because I understand the implications that these topics have for the development and security of the ICP ecosystem. Additionally, these are the topics that I feel confident voting on as I believe I have the technical background and experience needed in order to make an informed decision on these topics. 

**I will remain a voting neuron in the long term, even after the grant program has ended** because, as the founder and lead developer of an ICP project, I have a vested interest in helping ensure that the network's security and integrity is maintained for the sake of the business that I operate. Furthermore, Personal DAO requires that the DAO's neurons select a delegate for their vote, I will be the default delegate for all Personal DAOs deployed to the Internet Computer. This means that in order to service my own community of supporters, I am required to maintain an active role as a voting neuron- independently of this grant. 

My **voting principles** derive from a commitment to decentralization and sovereignty for users and builders- no introduction of any centralized points of failure that could be manipulated to the detriment of end-users. My conviction for this principle is demonstrated by the architecture that I've chosen for Personal DAO in which no entity outside of each respective Personal DAO (not even myself as the developer) may interfere with the DAO's canister's WASM modules nor their internal governance.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131780)

Voting grant application of Personal DAO for topic Protocol Canister Management - Governance - NNS Id 131780

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Protocol Canister Management, Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/77)
Hello, IC Community. I hope everyone had a restful and enjoyable weekend.

* We want to apply for the Protocol Canister Management, Participant Management & Node Admin, and Subnet Management topics.

* Not applying for a team grant.
* My name is Zohaib from Aegis Finance. My accounts are [GitHub](https://github.com/mzurs), [LinkedIn](https://www.linkedin.com/in/muhammad-z-33002a1b5/), and [X](https://x.com/zohaib__29).
* Our team consists of two devs (me and [Kashif](https://forum.dfinity.org/u/0x4d5a/summary)).
* I have done my Bachelors in Computer Science. I have 4 years of experience as a Software Engineer and 2 years of experience as a Blockchain Analyst.
* To demonstrate our technical expertise in Internet Computer (IC) development, we present [InheritX](https://kii7z-gaaaa-aaaal-adhwa-cai.icp0.io/), an application built under the AegisFinance umbrella. Currently live on the IC Mainnet, InheritX serves as a testament to our capabilities. Our team is actively developing additional features for AegisFinance, including an Insurance Contract (anticipated mid-August), an Options Contract, and a ready-to-deploy Staking module. We are committed to expanding the platform’s functionality.
* As a software developer with years of experience building on the Internet Computer, I am eager to contribute to governance discussions and initiatives. I aspire to become a Known Neuron named Aegis Finance.
* Evaluation of governance proposals necessitates substantial time and resources to ensure informed decision-making. Securing the grant would enable us to allocate additional hours exclusively to governance matters.
* Based on my experience as a Blockchain Analyst, ICP demonstrates significant potential to rival traditional infrastructures. As such, I advocate for the utilization of ICP as the foundational platform for developing decentralized, sustainable businesses and real-world applications.
* I am keen to contribute to these topics due to their critical role in shaping the ICP ecosystem’s growth and security. My experience directly aligns with these areas, enabling me to make informed and responsible voting decisions.
* I have expressed my intention to persist in governance-related activities post-grant. My decision to participate in the voting process is directly influenced by the interests of our followers.
* My voting principles emphasize transparency where all governance processes and decision-making within the DAO are transparent and inclusivity by encouraging active participation from all members of the DAO, ensuring that every voice is heard and every vote counts.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131759)

Voting grant application of Aegis Finance for topic Protocol Canister Management - Governance - NNS Id 131759

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Protocol Canister Management, Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/77)
Hello, IC Community. I hope everyone had a restful and enjoyable weekend.

* We want to apply for the Protocol Canister Management, Participant Management & Node Admin, and Subnet Management topics.

* Not applying for a team grant.
* My name is Zohaib from Aegis Finance. My accounts are [GitHub](https://github.com/mzurs), [LinkedIn](https://www.linkedin.com/in/muhammad-z-33002a1b5/), and [X](https://x.com/zohaib__29).
* Our team consists of two devs (me and [Kashif](https://forum.dfinity.org/u/0x4d5a/summary)).
* I have done my Bachelors in Computer Science. I have 4 years of experience as a Software Engineer and 2 years of experience as a Blockchain Analyst.
* To demonstrate our technical expertise in Internet Computer (IC) development, we present [InheritX](https://kii7z-gaaaa-aaaal-adhwa-cai.icp0.io/), an application built under the AegisFinance umbrella. Currently live on the IC Mainnet, InheritX serves as a testament to our capabilities. Our team is actively developing additional features for AegisFinance, including an Insurance Contract (anticipated mid-August), an Options Contract, and a ready-to-deploy Staking module. We are committed to expanding the platform’s functionality.
* As a software developer with years of experience building on the Internet Computer, I am eager to contribute to governance discussions and initiatives. I aspire to become a Known Neuron named Aegis Finance.
* Evaluation of governance proposals necessitates substantial time and resources to ensure informed decision-making. Securing the grant would enable us to allocate additional hours exclusively to governance matters.
* Based on my experience as a Blockchain Analyst, ICP demonstrates significant potential to rival traditional infrastructures. As such, I advocate for the utilization of ICP as the foundational platform for developing decentralized, sustainable businesses and real-world applications.
* I am keen to contribute to these topics due to their critical role in shaping the ICP ecosystem’s growth and security. My experience directly aligns with these areas, enabling me to make informed and responsible voting decisions.
* I have expressed my intention to persist in governance-related activities post-grant. My decision to participate in the voting process is directly influenced by the interests of our followers.
* My voting principles emphasize transparency where all governance processes and decision-making within the DAO are transparent and inclusivity by encouraging active participation from all members of the DAO, ensuring that every voice is heard and every vote counts.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131761)

Voting grant application of Aegis Finance for topic Participant Management & Node Admin - Governance - NNS Id 131761

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Protocol Canister Management, Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/87)
Hi **ICP Community members**

As a dedicated team committed to advancing the adoption and development of the Internet Computer Protocol (ICP), we are confident that we have the needed skills and resources to advance ICP’s core mission. Since our inception, [ICP Hub Kenya](https://icphubkenya.io/) has focused on building a robust community of ICP enthusiasts, developers, and stakeholders by fostering education, collaboration, and innovation.


As part of our ongoing commitment to the ICP community, we seek consideration for three proposal topics: Protocol Canister Management, Participant Management & Node Administration, and Subnet Management. By securing this grant, we aim to implement rigorous protocols that will ensure the integrity, reliability, and security of the ICP ecosystem.
**We are not applying for a team grant.**
We believe that our efforts will significantly contribute to the security and stability of the ICP network, and are excited about the potential impact of this opportunity. We look forward to connecting and working closely with the ICP community to achieve our shared vision of a secure and decentralized future.

About the team

Our team consists of 5 dedicated members, each possessing unique skill sets encompassing software development, developer relations, project management, and more. Our diverse range of expertise has, over time, proven fruitful as it allows us to approach challenges from multiple angles, ensuring comprehensive and innovative solutions. In addition, one of our team members, Tevin, has been actively participating in voting on the Network Nervous System (NNS) and staking ICP, which provides valuable experience and insight as we embark on becoming a voting neuron. His involvement will be beneficial in ensuring informed and effective participation in the governance of the ICP ecosystem, leveraging their firsthand knowledge and commitment to the platform's growth and stability. Additionally, we have trained numerous local developers who are ready to provide assistance in need arises.

We seek to apply for a group grant to focus on the three key areas: Protocol Canister Management, Participant Management & Node Administration, and Subnet Management. Our team's combined skills will enable us to develop robust protocols for canister management, optimize participant management and node administration, and implement effective subnet management strategies.

Team members:

1. Yvonne Kagondu (Team Lead) [LinkedIn](https://www.linkedin.com/in/yvonne-kagondu/) | [Twitter](https://x.com/kagondu_yvonne)

Yvonne Kagondu is a Blockchain and Web3 expert specializing in empowering the Kenyan youth and fostering Blockchain adoption. She is currently the cofounder of ICP Hub Kenya and has been at the forefront of developing initiatives aimed at

empowering Web3 developers and fostering ICP adoption in East Africa. With her extensive leadership experience and background in finance and cryptocurrencies, Yvonne possesses the needed capabilities to oversee the implementation of key initiatives centering on the proposed three topics.

2. Tevin Isaac (Developer) [LinkedIn](https://www.linkedin.com/in/tevin-isaac/?originalSubdomain=ke) | [Twitter](https://x.com/isaactevin) | Neuron ID - 47310282765699638696

Tevin is a blockchain developer and software engineer with 4 years of working experience. Throughout his career, he has interacted with various programming languages before specializing in JavaScript and its associated frameworks – Solidity and Rust. In addition, Tevin actively participates in voting on the Network Nervous System (NNS) daily when there are active proposals and stakes ICP monthly, which provides valuable experience and insight as we embark on becoming a voting neuron. His participation in the governance of the ICP ecosystem will be beneficial if our team is granted this opportunity.

Currently, Tevin is the lead developer at ICP Hub Kenya. One of his key achievements while working with the Hub is being part of the team spearheading the Olympus Accelerator Program in Kenya, as well as organising Ideathons and Hackathons, where he actively empowers and motivates participants to transform their innovative and disruptive ideas into reality. Aside from making big strides in his career path, Tevin also enjoys engaging and educating aspiring and upcoming tech enthusiasts and developers on blockchain, with a keen focus on the Internet Computer.

3. Mary Usaji (Project Manager) [LinkedIn](https://www.linkedin.com/in/mary-usaji/?originalSubdomain=ke) | [Twitter](https://x.com/usajimary)

Mary is an experienced and result-driven Web3 front-end developer with a background in business development. With over five years of experience in Business Management and a 2-year experience as a front-end developer, she has worked with various firms, honing her skills in orchestrating projects and driving business growth. Her unique blend of technical and business acumen sets her apart in the fast-evolving world of blockchain technology. Some key skills she has acquired throughout her business management career include leadership, strategic planning, market research, and customer relationship management. Currently, Mary works at ICP Hub Kenya as a Project Manager, where she orchestrates projects and events aimed at championing the increased adoption of the Internet Computer in the East African region.

4. Stephen Kimoi (Project Manager & Dev Rel) [LinkedIn](https://www.linkedin.com/in/stephen-kimoi/?original_referer=https%3A%2F%2Fwww%2Egoogle%2Ecom%2F&originalSubdomain=ke) | [Twitter](https://x.com/stevekimoi)

Stephen is a Blockchain Developer, Technical Web3 Writer, and Web3 Strategist with a solid foundation in software development spanning three years. His keen interest in Blockchain motivated him to delve into the world of Blockchain development for the past two years and actively contribute to the evolution of decentralized technologies. Steve is a Project Manager and DevRel at ICP Hub Kenya, an initiative dedicated to democratizing Blockchain technology through accessible education and empowering developers to create real decentralized applications on the Internet Computer platform. As the Project Manager, he leads and manages projects focused on driving positive change and innovation in the East African region, with a particular focus on strategic partnerships, incubation programs, hackathons, and community events.

5. Dedan Okware (Developer) [LinkedIn](https://www.linkedin.com/in/softcysec-dedan-okware/) | [Twitter](https://x.com/Dedan_O_Okware)

Dedan Okware is a multifaceted Web2 and Web3 Software Engineer, Data Scientist, and Linux Package Builder. With a robust background in technology, Dedan is passionately committed to continuous learning and professional growth. He thrives on embracing new challenges to advance his skills and deepen his knowledge in Software Development, Machine Learning, and Data Science. Dedan is currently one of the distinguished beneficiaries of the Olympus Accelerator program, an initiative that equips him with invaluable resources and mentorship to transform his disruptive ideas into groundbreaking realities. Dedan's expertise spans the evolving landscapes of Web2 and Web3, underscoring his adaptability and forward-thinking approach. His proficiency in data science and machine learning allows him to harness the power of data to drive meaningful insights and solutions. Additionally, his skills as a Linux Package Builder highlight his versatility and technical prowess.

Relevant experience

Since our inception, the team has made significant strides in promoting and advancing the Internet Computer Protocol (ICP) across East Africa. Hence, we possess several key relevant experiences that make us an ideal candidate for this grant:

1. We actively support multiple developer communities in Kenya, actively guiding and motivating the next generation of developers to build on ICP to benefit from the revolutionary potential of this platform.
2. We have, so far, trained and mentored 50+ developers who can provide technical support for this project. The opportunity presented by this task will not only help them practice their acquired skills but also continue contributing to the ICP ecosystem.
3. Recently, we joined the first cohort of Olympus and have incubated five products, each being built on ICP.
4. Our team comprises professionals with significant industry experience in key areas, such as software engineering, project management, and financial economics, giving us a unique advantage when tackling the responsibilities that will be assigned to us once granted this opportunity.

Technical knowledge

Our team possesses a diverse range of technical expertise, essential for advancing the security and development of the Internet Computer Protocol (ICP).

1. Our members are proficient in full-stack development, blockchain development, and both web3 frontend and backend development.
2. We have a deep understanding of the Network Nervous System (NNS) architecture and functionality, enabling us to effectively manage and secure the network.
3. Our technical skills extend to programming languages such as Typescript, Motoko, Rust, and Javascript, allowing us to develop robust and scalable applications on the ICP platform.
4. Deployed nearly 200 canisters from our hub activities, demonstrating our technical expertise and commitment to the platform's growth.
5. Established a series of strategic partnerships that are beneficial to ICP's bottom line, including collaborations with local government entities and industry leaders.

This comprehensive technical knowledge positions us uniquely to contribute meaningfully to the ICP ecosystem, driving innovation, and ensuring its security and stability.

Why you want to be a voting neuron

We would like to be a voting neuron as it offers us a unique opportunity to engage directly in the governance of the ICP network. The voting power associated with being a neuron will enable us to influence important decisions and proposals that shape the future of ICP, ensuring that our perspectives and priorities are considered in the network’s evolution. This role not only enhances our ability to contribute to the development and security of the ICP ecosystem but also aligns with our commitment to fostering a robust and dynamic decentralized community. Being a voting neuron represents a significant opportunity for us to play an active part in steering ICP toward its full potential.

Why you need the grants to do so

We are fully dedicated to the advancement of ICP, and securing this funding is crucial for us to execute the necessary tasks effectively. The funds will facilitate our team's operations, enabling us to focus entirely on enhancing ICP's security through our proposed initiatives in Protocol Canister Management, Participant Management & Node Administration, and Subnet Management. A key strength of our team is our ability to achieve targets at a low cost, ensuring that every cent is spent efficiently and yields maximum impact. This funding will empower us to continue our work with the same level of dedication and efficiency, driving significant progress within the ICP ecosystem.

Why you are acting in the long-term interest of ICP

We are committed to the long-term success and sustainability of the Internet Computer Protocol (ICP) because we believe in its potential to revolutionize the digital landscape by enabling truly decentralized applications and services. Our efforts are not just about immediate gains but about laying a solid foundation for future growth and innovation. By focusing on critical areas such as security, developer engagement, and community building, we aim to create a robust and resilient ecosystem that can withstand challenges and thrive over time. Our long-term vision aligns with ICP's goals of providing a secure, scalable, and decentralized internet, ensuring that our work benefits the entire ICP community for years to come.

Why you are interested in the topics you apply for

We are particularly interested in focusing on Protocol Canister Management, Participant Management & Node Administration, and Subnet Management because these areas are critical to ensuring the security, efficiency, and scalability of the ICP network. By concentrating our efforts on these key areas, we aim to fortify the ICP infrastructure, enhance its overall security, and support its continued growth and adoption.

Why you remain a voting neuron in the long term, even after the grant is over

We intend to remain a voting neuron in the long term, even after the grant period concludes, as this commitment aligns with our dedication to promoting ICP’s integrity and security. By maintaining our role as a voting neuron, we will continue to actively contribute to the governance and development of the ICP network, ensuring that our efforts to enhance the ecosystem extend beyond the immediate term and support the network’s ongoing growth and stability.

Whether you have some voting principles

In our role as a voting neuron, we will adhere to several key voting principles to guide our decisions and contributions.

1. We will prioritize transparency, ensuring that our voting actions and rationale are clear and accessible to the community.
2. We will emphasize fairness and impartiality, carefully evaluating proposals based on their merits and impact rather than personal or external biases.
3. We will commit to thorough deliberation, taking the time to understand the potential implications of each proposal before casting our vote.
4. We will align our voting decisions with the long-term goals of the ICP network, focusing on initiatives that promote decentralization, security, and sustainable growth for the entire ecosystem.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131774)

Voting grant application of ICP Hub Kenya for topic Protocol Canister Management - Governance - NNS Id 131774

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Subnet management, Participant Management & Node Admin

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/86)
Greetings ALL community members!

We are interested in being considered for **Subnet Management**, and **Participant Management & Node Admin** neuron grants as **ICP Hub Poland.**

ICP Hub Poland:

[Twitter](https://x.com/ICPHUB_PL)
[LinkedIn](https://www.linkedin.com/company/icphub-pl)
[Telegram](https://t.me/ICP_PL)
[OpenChat](https://oc.app/community/qyqpi-viaaa-aaaar-bihgq-cai)

**Team**

* [Maciej Orłowski](https://www.linkedin.com/in/orlowski-maciej) (ICP Hub Poland Lead)

Voting Neuron Members:
* [Krzysztof Żelazko](https://x.com/kc_zelazko): (ICP Hub Poland Governance Lead, Lifeguard, Music Producer)
* [CryptoDEVence](https://oc.app/user/zhs7r-qqaaa-aaaar-a6bsq-cai): (Founder of ICP Polska, Software Developer, Motoko)

*Relevant Experience*

CryptoDEVence is a dedicated software developer who has been actively involved with the Internet Computer. As the founder of [ICP Polska](https://6ec2p-paaaa-aaaal-ai45q-cai.icp0.io), he is committed to driving the adoption and understanding of Internet Computer technology in Poland. His role as an educator has been crucial in expanding the reach and impact of this innovative technology across the region. He is a “old school” programmer who, as part of his Motoko education, created and is developing an app that will (we hope) be useful to the Polish crypto community someday. He tests various ICP solutions and shares his experiences. He plans to start publishing his first educational materials in September. At NNS, he votes every day with his morning coffee.

Myself, Krzysztof Żelazko. I am a Music Producer with ten years of experience and 2 years of experience developing on the Internet Computer. I have worked and consulted on multiple projects on the Internet Computer like [ICode DAO](https://x.com/ICodeDA0), [Rakeoff](https://rakeoff.io) or [8YearGangDAO](https://oc.app/community/6efj4-vqaaa-aaaar-ar2ia-cai/channel/69530127954244796840303922258183167660). Recently I also contributed to the ICP Hub Poland neuron by creating it and its decentralized voting framework. In addition to my development work, I also hold an active voting known neuron on the NNS.

*Motivation for Becoming a Voting Neuron*

* As an ICP Hub we feel it’s very important for us to contribute as much as we can to the decentralization and progression of ICP, joining the governance process as a responsibly voting neuron enables us to achieve that.
* The goals of the ICP align closely with our mission as an ICP Hub. We are dedicated to supporting and initiating projects that bolster the ICP ecosystem, ensuring that our objectives and efforts contribute to the protocol’s strength and sustainability.

**Why do we need the grant funding?**

* Grant funding is essential for us to allocate more time and resources to the review process and voting. With this support, we can increase our team’s capacity, dedicate more hours to these crucial tasks, and potentially expand our team by bringing in additional reviewers. This will enhance the quality and efficiency of our work and help us better communicate the governance activities with community.

**Why did we choose Subnet Management, and Participant Management & Node Admin?**

* We have decided to apply for the Subnet Management, and Participant Management & Node Admin grants because these topics are more flexible in terms of time for us, and we have the experience to effectively analyze these topics, as we do this now regularly anyway,
* Since our team is not very large, we are looking to start with something that won’t require too much time but still allows us to contribute meaningfully.

**Our Long-Term Interest in ICP**

* At ICP Hub Poland, our long-term interest is rooted in our commitment to advancing ICP. Our activities, including boot camps, hackathons, start-up incubations and community building, are aligned with ICP’s long-term growth.
* As a hub, all our activities are deeply involved and align with ICP's long-term growth goals. We are dedicated to expanding ICP in Poland. Our long-term goals depend on the success of the ICP ecosystem because we help startups and companies build on ICP. The growth and success of ICP directly impact our mission and vision for the future.
* As of now, part of advancing the ecosystem is to create and expand the governance structures for the Internet Computer. These activities include creating named neuron, promote governance among local communities, create space for active participation in governance of Internet Computer DAO and to help to improve the governing quality by actively participate in voting, reviewing & explaining proposals to the community.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131777)

Voting grant application of ICP Hub Poland for topic Participant Management & Node Admin - Governance - NNS Id 131777

## Background 
As part of an ongoing effort to to incentivise neurons to verify proposals in depth, voting grants will be provided for candidates selected by the community. Overall, 2 candidates are selected for each of 4 proposal topics.
**This is one of multiple motion proposals submitted today to select these candidates**:  
- one NNS motion proposal is submitted for each candidate and topic for which the candidate applied  
- for each proposal, the result is computed as the number of YES minus the number of no votes (#YES-#NO) 
- for each topic, the 2 candidates with the highest results get the grants  

You can read more about the motivation and the process [here](https://forum.dfinity.org/t/grants-for-voting-neurons/32721).

## Proposal Topic
Protocol Canister Management, Participant Management & Node Admin, Subnet management

## Is this a team grant application?
 no 

## [Application Text](https://forum.dfinity.org/t/grants-for-voting-neurons/32721/87)
Hi **ICP Community members**

As a dedicated team committed to advancing the adoption and development of the Internet Computer Protocol (ICP), we are confident that we have the needed skills and resources to advance ICP’s core mission. Since our inception, [ICP Hub Kenya](https://icphubkenya.io/) has focused on building a robust community of ICP enthusiasts, developers, and stakeholders by fostering education, collaboration, and innovation.


As part of our ongoing commitment to the ICP community, we seek consideration for three proposal topics: Protocol Canister Management, Participant Management & Node Administration, and Subnet Management. By securing this grant, we aim to implement rigorous protocols that will ensure the integrity, reliability, and security of the ICP ecosystem.
**We are not applying for a team grant.**
We believe that our efforts will significantly contribute to the security and stability of the ICP network, and are excited about the potential impact of this opportunity. We look forward to connecting and working closely with the ICP community to achieve our shared vision of a secure and decentralized future.

About the team

Our team consists of 5 dedicated members, each possessing unique skill sets encompassing software development, developer relations, project management, and more. Our diverse range of expertise has, over time, proven fruitful as it allows us to approach challenges from multiple angles, ensuring comprehensive and innovative solutions. In addition, one of our team members, Tevin, has been actively participating in voting on the Network Nervous System (NNS) and staking ICP, which provides valuable experience and insight as we embark on becoming a voting neuron. His involvement will be beneficial in ensuring informed and effective participation in the governance of the ICP ecosystem, leveraging their firsthand knowledge and commitment to the platform's growth and stability. Additionally, we have trained numerous local developers who are ready to provide assistance in need arises.

We seek to apply for a group grant to focus on the three key areas: Protocol Canister Management, Participant Management & Node Administration, and Subnet Management. Our team's combined skills will enable us to develop robust protocols for canister management, optimize participant management and node administration, and implement effective subnet management strategies.

Team members:

1. Yvonne Kagondu (Team Lead) [LinkedIn](https://www.linkedin.com/in/yvonne-kagondu/) | [Twitter](https://x.com/kagondu_yvonne)

Yvonne Kagondu is a Blockchain and Web3 expert specializing in empowering the Kenyan youth and fostering Blockchain adoption. She is currently the cofounder of ICP Hub Kenya and has been at the forefront of developing initiatives aimed at

empowering Web3 developers and fostering ICP adoption in East Africa. With her extensive leadership experience and background in finance and cryptocurrencies, Yvonne possesses the needed capabilities to oversee the implementation of key initiatives centering on the proposed three topics.

2. Tevin Isaac (Developer) [LinkedIn](https://www.linkedin.com/in/tevin-isaac/?originalSubdomain=ke) | [Twitter](https://x.com/isaactevin) | Neuron ID - 47310282765699638696

Tevin is a blockchain developer and software engineer with 4 years of working experience. Throughout his career, he has interacted with various programming languages before specializing in JavaScript and its associated frameworks – Solidity and Rust. In addition, Tevin actively participates in voting on the Network Nervous System (NNS) daily when there are active proposals and stakes ICP monthly, which provides valuable experience and insight as we embark on becoming a voting neuron. His participation in the governance of the ICP ecosystem will be beneficial if our team is granted this opportunity.

Currently, Tevin is the lead developer at ICP Hub Kenya. One of his key achievements while working with the Hub is being part of the team spearheading the Olympus Accelerator Program in Kenya, as well as organising Ideathons and Hackathons, where he actively empowers and motivates participants to transform their innovative and disruptive ideas into reality. Aside from making big strides in his career path, Tevin also enjoys engaging and educating aspiring and upcoming tech enthusiasts and developers on blockchain, with a keen focus on the Internet Computer.

3. Mary Usaji (Project Manager) [LinkedIn](https://www.linkedin.com/in/mary-usaji/?originalSubdomain=ke) | [Twitter](https://x.com/usajimary)

Mary is an experienced and result-driven Web3 front-end developer with a background in business development. With over five years of experience in Business Management and a 2-year experience as a front-end developer, she has worked with various firms, honing her skills in orchestrating projects and driving business growth. Her unique blend of technical and business acumen sets her apart in the fast-evolving world of blockchain technology. Some key skills she has acquired throughout her business management career include leadership, strategic planning, market research, and customer relationship management. Currently, Mary works at ICP Hub Kenya as a Project Manager, where she orchestrates projects and events aimed at championing the increased adoption of the Internet Computer in the East African region.

4. Stephen Kimoi (Project Manager & Dev Rel) [LinkedIn](https://www.linkedin.com/in/stephen-kimoi/?original_referer=https%3A%2F%2Fwww%2Egoogle%2Ecom%2F&originalSubdomain=ke) | [Twitter](https://x.com/stevekimoi)

Stephen is a Blockchain Developer, Technical Web3 Writer, and Web3 Strategist with a solid foundation in software development spanning three years. His keen interest in Blockchain motivated him to delve into the world of Blockchain development for the past two years and actively contribute to the evolution of decentralized technologies. Steve is a Project Manager and DevRel at ICP Hub Kenya, an initiative dedicated to democratizing Blockchain technology through accessible education and empowering developers to create real decentralized applications on the Internet Computer platform. As the Project Manager, he leads and manages projects focused on driving positive change and innovation in the East African region, with a particular focus on strategic partnerships, incubation programs, hackathons, and community events.

5. Dedan Okware (Developer) [LinkedIn](https://www.linkedin.com/in/softcysec-dedan-okware/) | [Twitter](https://x.com/Dedan_O_Okware)

Dedan Okware is a multifaceted Web2 and Web3 Software Engineer, Data Scientist, and Linux Package Builder. With a robust background in technology, Dedan is passionately committed to continuous learning and professional growth. He thrives on embracing new challenges to advance his skills and deepen his knowledge in Software Development, Machine Learning, and Data Science. Dedan is currently one of the distinguished beneficiaries of the Olympus Accelerator program, an initiative that equips him with invaluable resources and mentorship to transform his disruptive ideas into groundbreaking realities. Dedan's expertise spans the evolving landscapes of Web2 and Web3, underscoring his adaptability and forward-thinking approach. His proficiency in data science and machine learning allows him to harness the power of data to drive meaningful insights and solutions. Additionally, his skills as a Linux Package Builder highlight his versatility and technical prowess.

Relevant experience

Since our inception, the team has made significant strides in promoting and advancing the Internet Computer Protocol (ICP) across East Africa. Hence, we possess several key relevant experiences that make us an ideal candidate for this grant:

1. We actively support multiple developer communities in Kenya, actively guiding and motivating the next generation of developers to build on ICP to benefit from the revolutionary potential of this platform.
2. We have, so far, trained and mentored 50+ developers who can provide technical support for this project. The opportunity presented by this task will not only help them practice their acquired skills but also continue contributing to the ICP ecosystem.
3. Recently, we joined the first cohort of Olympus and have incubated five products, each being built on ICP.
4. Our team comprises professionals with significant industry experience in key areas, such as software engineering, project management, and financial economics, giving us a unique advantage when tackling the responsibilities that will be assigned to us once granted this opportunity.

Technical knowledge

Our team possesses a diverse range of technical expertise, essential for advancing the security and development of the Internet Computer Protocol (ICP).

1. Our members are proficient in full-stack development, blockchain development, and both web3 frontend and backend development.
2. We have a deep understanding of the Network Nervous System (NNS) architecture and functionality, enabling us to effectively manage and secure the network.
3. Our technical skills extend to programming languages such as Typescript, Motoko, Rust, and Javascript, allowing us to develop robust and scalable applications on the ICP platform.
4. Deployed nearly 200 canisters from our hub activities, demonstrating our technical expertise and commitment to the platform's growth.
5. Established a series of strategic partnerships that are beneficial to ICP's bottom line, including collaborations with local government entities and industry leaders.

This comprehensive technical knowledge positions us uniquely to contribute meaningfully to the ICP ecosystem, driving innovation, and ensuring its security and stability.

Why you want to be a voting neuron

We would like to be a voting neuron as it offers us a unique opportunity to engage directly in the governance of the ICP network. The voting power associated with being a neuron will enable us to influence important decisions and proposals that shape the future of ICP, ensuring that our perspectives and priorities are considered in the network’s evolution. This role not only enhances our ability to contribute to the development and security of the ICP ecosystem but also aligns with our commitment to fostering a robust and dynamic decentralized community. Being a voting neuron represents a significant opportunity for us to play an active part in steering ICP toward its full potential.

Why you need the grants to do so

We are fully dedicated to the advancement of ICP, and securing this funding is crucial for us to execute the necessary tasks effectively. The funds will facilitate our team's operations, enabling us to focus entirely on enhancing ICP's security through our proposed initiatives in Protocol Canister Management, Participant Management & Node Administration, and Subnet Management. A key strength of our team is our ability to achieve targets at a low cost, ensuring that every cent is spent efficiently and yields maximum impact. This funding will empower us to continue our work with the same level of dedication and efficiency, driving significant progress within the ICP ecosystem.

Why you are acting in the long-term interest of ICP

We are committed to the long-term success and sustainability of the Internet Computer Protocol (ICP) because we believe in its potential to revolutionize the digital landscape by enabling truly decentralized applications and services. Our efforts are not just about immediate gains but about laying a solid foundation for future growth and innovation. By focusing on critical areas such as security, developer engagement, and community building, we aim to create a robust and resilient ecosystem that can withstand challenges and thrive over time. Our long-term vision aligns with ICP's goals of providing a secure, scalable, and decentralized internet, ensuring that our work benefits the entire ICP community for years to come.

Why you are interested in the topics you apply for

We are particularly interested in focusing on Protocol Canister Management, Participant Management & Node Administration, and Subnet Management because these areas are critical to ensuring the security, efficiency, and scalability of the ICP network. By concentrating our efforts on these key areas, we aim to fortify the ICP infrastructure, enhance its overall security, and support its continued growth and adoption.

Why you remain a voting neuron in the long term, even after the grant is over

We intend to remain a voting neuron in the long term, even after the grant period concludes, as this commitment aligns with our dedication to promoting ICP’s integrity and security. By maintaining our role as a voting neuron, we will continue to actively contribute to the governance and development of the ICP network, ensuring that our efforts to enhance the ecosystem extend beyond the immediate term and support the network’s ongoing growth and stability.

Whether you have some voting principles

In our role as a voting neuron, we will adhere to several key voting principles to guide our decisions and contributions.

1. We will prioritize transparency, ensuring that our voting actions and rationale are clear and accessible to the community.
2. We will emphasize fairness and impartiality, carefully evaluating proposals based on their merits and impact rather than personal or external biases.
3. We will commit to thorough deliberation, taking the time to understand the potential implications of each proposal before casting our vote.
4. We will align our voting decisions with the long-term goals of the ICP network, focusing on initiatives that promote decentralization, security, and sustainable growth for the entire ecosystem.



 [Original NNS proposal](https://dashboard.internetcomputer.org/proposal/131775)