Hi community 
Proposal #134343 Review — Louise | Aviate Labs
Vote: REJECT
Review:
- The target topology has been reached.
- However, @bitmoon is allowed to onboard three nodes as this aligns with the approach agreed upon by the community - since the nodes were purchased before December 1, 2023, they may be onboarded despite the fact that the target topolgy has been reached.
- The proposal to add the node operator ID is accurate in that it matches the NP ID of Bitmoon (
mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe) and the correct DC ID (Li2). So according to this criteria, it wouldn’t be wrong to adopt this proposal. - However, adhering to convention and in an effort to maintain a standard within the registry, I believe that if the same node provider is onboarding nodes in the same data center, these nodes should fall under the same node operator ID. For this reason, I am voting to reject this proposal.
Recommendation to @bitmoon :
If the proposal does get rejected, please submit a new proposal to update the node operator configuration for the Li2 data center (node operator ID: nvocp-jlbys-d44wi-od3pv-iws4n-2nll3-73hqk-koh72-3obvg-kt5v3-fae). You can refer to a similar proposal previously submitted by @C12:
Apologies for the inconvenience. To avoid this in the future, you may also want to open a discussion with the community either via this forum, or the Matrix chat to double check your proposal before submitting.