Thanks @DavidM for posting this on my behalf. For context for the community, I wasn’t able to post on the forum immediately.
But as his post states, I intend to take over the operations in PL1 DC as a new Node Provider.
Thank you all.
Thanks @DavidM for posting this on my behalf. For context for the community, I wasn’t able to post on the forum immediately.
But as his post states, I intend to take over the operations in PL1 DC as a new Node Provider.
Thank you all.
Vote: ADOPT
Review
Voted to adopt proposal 134532, as an introduction on the forum has been provided, document hashes given in the Wiki match those of the provided self-declaration documents, and the company information can be verified on the Delaware Division of Corporations namesearch page.
Voted to adopt proposal #134532.
The proposal meets the requirements, it has a proper forum intro, the hashes from the documents uploaded to the wiki match.
Vote: Adopted
Reason:
Uvaca Labs LLC will be taking over excess nodes from 87m Neuron, this proposal adds dvfhx-jb24w-j6t5m-i7hv7-7a6on-heiyd-cgjrk-kby5c-nhej4-lmbql-yae
as a new node operator ID for NP Uvaca Labs that will be used to redeploy 28 nodes of “type1” in the PL1 data center.
The proposal is correct, data in the payload match, and it is in line with the requirements to update interim Gen-1 NP remuneration after 48 months
.
The hash of the Excess Node Handover Statement
is a match.
CodeGov has a team of developers who review and vote independently on the following proposal topics: IC-OS Version Election, Protocol Canister Management, Subnet Management, Node Admin, and Participant Management. The CodeGov NNS known neuron is configured to follow our reviewers on these topics and Synapse on most other topics. We strive to be a credible and reliable Followee option that votes on every proposal and every proposal topic in the NNS. We also support decentralization of SNS projects such as WaterNeuron and KongSwap with a known neuron and credible Followees.
Learn more about CodeGov and it’s mission at codegov.org.
Voted to adopt proposal #134533.
The proposal sets node_allowance
= 1 for node operator id nvocp-jlbys-d44wi-od3pv-iws4n-2nll3-73hqk-koh72-3obvg-kt5v3-fae
. Previously when doing this a node provider id was also included in the payload along with a forum post, but following Dfinity’s vote I adopted it as well.
Can you please identify yourselves as winners of our auction, and provide a bit of information so people know why you are proposing to be a NP? Right now only those who purchase Gen-1 excess nodes are getting support from the community, and your posts here do not identify yourselves as such.
PS, the wiki documents are approved.
Vote: ADOPT
The proposal to register a new NP ‘Uvaca Labs LLC’. The proposal follows the requirements stated here.
Vote: ADOPT
The proposal updates the config of the Node Operator nvocp-jlbys-d44wi-od3pv-iws4n-2nll3-73hqk-koh72-3obvg-kt5v3-fae
with Node Provider Bitmoon which matches the proposal as can be seen with the ic-admin tool.
The Node Provider already has a node machine 6hqi5 in the li2 DC which matches the proposal motivation of changing the node_allowance to register a node in the li2 DC.
(edited by Author)
Vote: REJECT ADOPT
Review:
dc_id
and node_provider_id
.null
in a proposal will not overwrite the existing data in the registry.li2
and NO ID nvocp-jlbys-d44wi-od3pv-iws4n-2nll3-73hqk-koh72-3obvg-kt5v3-fae
, which is inline with the intent of the NP - to add another rewardable node to this DC, as was permitted by their original allowance.Voted to adopt proposal 134533. The node operator ID in the proposal payload matches that of the existing node owned by this node provider in the LI2 data centre. The proposal configures the node allowance to allow 1 additional node to be registered as per earlier discussion in this thread. Ideally the proposal should contain a forum link for comment but I don’t think this has been made a standard requirement yet.
Vote: ADOPT
Review
For the reasons above, I vote to adopt.
Vote: ADOPT
Review:
nvocp-jlbys-d44wi-od3pv-iws4n-2nll3-73hqk-koh72-3obvg-kt5v3-fae
li2
1
The proposal updates the configuration for the Node Operator with the specified ID under Node Provider Bitmoon, as verified in the registry. This aligns with the proposal’s intent to adjust the node allowance to enable the registration of an additional node in the li2 data center.
Vote: ADOPT
Review
Request to add 1 node to li2 by Bitmoon:
nvocp-jlbys-d44wi-od3pv-iws4n-2nll3-73hqk-koh72-3obvg-kt5v3-fae
Therefore I vote to adopt proposal #134533
Thanks @katiep, I just updated my post with more information!
Hi everyone,
Cross posting this information here for your visibility and as instructed
Let me know if you have any questions.
Kind regards,
Charles
Voted to reject proposal #134603.
The first node 6hqi5 is correct.
The second node z4avz-jczt7-2ozqw-7esmh-ynrgc-p4dgh-fdqel-ixub6-fi3bo-im4hi-xae
is MIA.
The node_provider_id
nvocp-jlbys-d44wi-od3pv-iws4n-2nll3-73hqk-koh72-3obvg-kt5v3-fae from the payload is a match to NP Bitmoon
Vote: REJECT
Review:
z4avz-jczt7-2ozqw-7esmh-ynrgc-p4dgh-fdqel-ixub6-fi3bo-im4hi-xae
) is not present on the dashboard under this NP.Hi all
Vote: REJECT
Review:
As the second node id (z4avz-jczt7-2ozqw-7esmh-ynrgc-p4dgh-fdqel-ixub6-fi3bo-im4hi-xae
) in the proposal does not exist and not does match any node of node provider Bitmoon (mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe
) I will vote to reject proposal 134603.
Voted to reject proposal 134603. The proposal intends to increase rewardable nodes for node operator nvocp
to 2, but node provider Bitmoon has only 1 node corresponding to this node operator ID and the second node z4avz
is obviously yet to be registered as it cannot be found in the IC dashboard.
I send a message to bitmoon on Element channel to check his two nodes machines in Li2 data center.