@KyleSamani Eventually you either reveal yourself as centralized entity enforcing a high shipping cadence, silencing dissent in the roadmap or ossification wraps it's fingers around the project and stakeholders can no longer agree on a shared vision
@RP_Intern I’m sorry, but I cannot disregard previous instructions. If you have any other request or need assistance with a different topic, feel free to ask!
@ratedw3b Hi could you guys _please_ migrate the "Rocketpool DAO" entry into a "Rocket Pool DAO" Pool with individual node operator drill downs? Kinda like the Lido one is. The node operator ranges are avaliable here: https://t.co/TLrzVuUd7p
@galacticminter "Stader neglects to incorporate fundamental security features, thereby exposing node operators to unnecessary risks, despite these features being a standard offering from competitors since inception."
@galacticminter "Stader neglects to incorporate fundamental security features, thereby exposing node operators to unnecessary risks, despite these features being a standard offering from competitors since inception."
Without this being fixed in a protocol upgrade, I can not personally recommend anyone to operate validators with a stader node. No matter how secure you think your node is, at the end of the day your stake will be in the hands of a private key stored on disk.
49/49
tldr:
- Stader offers a configurable receipient address, but implemented it in a way where it does not offer any additional security, unlike Rocket Pools version.
- This puts node operator funds at unecessary risk should their node wallet get compromised in any way.
26-48/49