Natalia Kulesha
https://dashboard.internetcomputer.org/provider/6ryfx-xszlo-xpvyj-b7vx6-m4erk-zwdkc-5lzfwfty7k-arl66-uc3jk-nae
Forum Handle: kulesha_natalia
Date Joined Forums: 29 Jan 2024
Date Made Proposal: 08 Feb 2024
Proposal: https://dashboard.internetcomputer.org/proposal/127688
Number of Days: 10
UBO: Unknown
ID Proof: an invoice for a roll of DISPOSABLE FLOOR SHEETING that comes in 60x50 tear
off sections from an online shopping site
Background: Unknown, possibly a sales manager - https://www.linkedin.com/in/nataliakulesha-016a33233/?originalSubdomain=pl
ExCentral seems to be headquartered in Cyprus and is a forex and crypto brokerage?
https://b2bhint.com/en/company/cy/mount-nico-corp-ltd--ÎÎ%20307717
Principal: 6ryfx-xszlo-xpvyj-b7vx6-m4erk-zwdkc-5lzfw-fty7k-arl66-uc3jk-nae
Account: 3a2ec378efa8ffb869e505e64a29bdab7665b49a277d1aa84337fd55421bf543
Transactions: minted zero ICP
Every time we remove a node provider I have to listen to âAnother One Bites the Dustâ by queen and drink a beer.
Still recovering from the 32 node provider nightâŚ
LGTM, I voted to adopt. Proposal: 136021 - ICP Dashboard
Node Provider: Natalia Kulesha - ICP Dashboard
Interestingly this same proposal was rejected recently - Proposal: 135778 - ICP Dashboard
The reason it was rejected is because
âthe rules set in place by the community (even though nobody was even paying attention at the time)â
trumps common sense.
Please let me do my administrative job of removing defunct node providers.
Proposal #136013
Vote: Adopted
Reason
NP Serenity Lotus Limited currently has 0 nodes.
Proposal #136021
Vote: Adopted
Reason
NP Natalia Kulesha currently has 0 nodes.
I had previously voted to reject these proposals when they were first submitted, as at the time they had met the minimum requirementsâthough, admittedly, the standards were either low or not well-defined.
Iâd now like to tag @ArtUi , who submitted the proposal to register NP Serenity Lotus Limited, and @Kulesha_Natalia , who submitted the proposal to register NP Natalia Kulesha, to give them both the opportunity to clarify their position as a Node Provider and make any corrections. If thereâs no response within 48 hours, I will proceed to vote to adopt these proposals.
Should @ArtUi and @Kulesha_Natalia only see this after the 48-hour window, please know that you are still welcome to resubmit a new proposal to register as a Node Provider. This is possible even if the target topology is currently met. Provided the required documentation aligns with the community standards, I would vote to adopt it.
Hi, all new to the space. A couple of weeks back I saw there was a good amount of votes to remove node providers but I didnât understand at the time why this was put up to a vote, so i did not vote.
Is there a place someone can direct me to so I can learn about what the node requirements are and why I would choose to reject or accept these proposals in the future? Really would love to be more active with voting when I can.
Hey person whoâs new to the space - would like to welcome you to our community!
If youâre looking for the node requirements, well theyâre a complete shambles right now. I suggest you check back in a few weeks when theyâve all been rewritten.
Very interesting Borovan.
I appreciate the links Zack. I checked them briefly found the hardware and node provider onboarding requirements and thought âthis is above my current knowledge poolâ. lol
The majority of proposals came down to Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #5 by katiep and the rest of removing Node Providers was an initiative started by Adam and his team backed by Dfinity, so as long as you follow Dfinity you should be ok, by that I mean voting the right way.
Yesss! Ok whoâs next
Hello!
TLDR> DFINITY voted to approve the removal of those node providers because they were part of a program that had ceased to be active as of November 30. They simply hadnât been removed yet, as of the time that the other user. A few of those proposals were also for accounts that had been set up for testing purposes. DFINITY does not approve of removing NPs who are actively hosting nodes. Such action would have to be more involved and follow approved processes. We voted to reject the proposals that were for active NPs.
Proposal 136021 â Louise | Aviate Labs
Vote: ADOPT
Review:
- This NP has 0 nodes active on the network
- No response after being tagged
Although this Node Provider did follow the correct processes and standards in place at the time, if this proposal were submitted today with the active community reviews in place, it likely would not have been accepted without further discussion. Questions would have been raised around whether the documentation provided is sufficient proof of identity.
As the community continues to improve and formalize these processes, I would like to invite @Kulesha_Natalia to consider submitting a new proposal if there is still interest in becoming a node provider, once the updated standards are in place.
Proposal 136013 â Louise | Aviate Labs
Vote: ADOPT
Review:
- This NP has 0 nodes active on the network
- No response after being tagged
I have tried to look up this entity on the British Virgin Islands Financial Services Commission website - this seems to be the registry for companies in the BVI. I could not find âSerenity Lotus Limitedâ. If this NP submitted their registration proposal today, it would have likely been rejected due to this.
About Aviate Labs
Aviate Labs is a team dedicated to supporting node providers since 2020. Our mission is to make high-performance infrastructure management on the Internet Computer (ICP) as seamless as possible, while adhering to the principles of decentralization.
We are known for our contributions to the ecosystem, including the go-agent and developer work packages on GitHub, as well as the Node Monitor tool, which alerts Node Providers as soon as any of their nodes go down.
In the NNS, Louise reviews and votes independently on âNode Adminâ and âParticipant Managementâ proposals on behalf of the Aviate Labs Neuron.
The Aviate Labs known neuron is configured to follow Louise for these topics and other trusted entities for broader proposals. We strive to be a credible and reliable Followee, committed to voting on every proposal and supporting decentralization within the ICP ecosystem.