For those who this may apply to, Happy Thanksgiving!
Don’t have much time today but I wanted to quickly jump this growing discussion.
[Disclaimer - I LOVE GUIs and LOVE Docker]
Really impressive products. I’ll dive into them deeper a bit later, but the documentation is very impressive.
Yes. NP is intentionally designed to allow nodes to be portable. You can easily move a validator that was started in NP to your own Docker instance. There is zero platform lock-in and our deployment engine ensures everything is transparent. Our file structure and configs are easily understandable and designed for portability.
We do not manage the relationship between delegators and validators. Delegators should choose wisely who they want to delegate with… we have no involvement. We just make tools that streamlines how node runners can deploy and interface with their validator, but the responsibility of being a good validator to their delegators is still their responsibility.
What I have seen in most networks is eventually the majority of validators are run by custodial services. There are always a portion that are independent node runners, but most networks have the majority of validators centralized into only a few providers. The worry is then “well how do we break up the providers?”. By then you are most likely too late.
Node Launcher is ultimately the middle ground, because it enables anyone to make validator deployment applications seamlessly through JS. Node Pilot acts as the first use-case of it, but we ultimately want others to build their own and democratize node running with many options.
Yeah, that is the risk with custodial services. NP is self-hosting, the polar opposite.
We plan to do with Harmony what we’ve already proven with POKT. Once you deploy a POKT node and you have met the threshold to be a validator (have enough POKT, connected chains, etc) then we have a “Stake Validate” which does the validator process automatically once clicked. We are planning to have the same UX for Harmony validators.
I may have under-represented Node Launcher and its importance in all of this. Node Launcher is the secret sauce and the real tech we are pushing… as it enables programmatic deployment/management of Harmony containers through JS. We originally launched NP back in April where we did just hard-code docker files for nodes. We quickly realized once we started stacking different types of nodes that we wanted to standardize how nodes can be deployed and updated. So instead of managing hard-coded docker files, we have a programmatic platform that we just add integrations into.
I’d encourage the more tech-inclined to check out the Github for Node Launcher and perhaps our 7min introduction video: Node Launcher - A TypeScript Library Introduction (POKT Community Call) - YouTube
Feel free to check out the documentation for deploying a POKT node the traditional way. For the IT inclined, it’s absolutely doable without NP, but the Pocket community kicked off this project because custodial service providers were becoming the norm and majority of the network.
I may have missed some important points, but I tried to get in as many comments from as many individuals as I could before focusing on the holiday. Feel free to keep the convo going and high-light areas I can provide better clarity