-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Presigned Exit Messages #560
Comments
I don't see presigned exit messages as enabling trustless marriages yet, so this is not a high priority, though I do believe it's a good feature to keep on the backlog. Without a SC acting as the node wallet, there's no way to ensure the operator of the node, be they the RPL provider or the ETH provider, will actually use the bls key that they sent the presigned exit message for. A NO taking on someone else's RPL can simply launch additional minipools to keep the RPL unwithdrawable, and a NO taking on someone else's ETH can grief them by staking under a totally different pubkey from the one they used to sign the exit message. It's feasible two highly technical people may do this with a gnosis safe, but being that they must be highly technical, I am willing to let them cope with the signing process themselves, for now. |
With Houston's new core protocol features to separate node operators from ETH / RPL providers, it makes a lot of sense to share presigned exit messages in such an arrangement to enable full trustlessness. It would be great if Smart Node could do this natively with
rocketpool minipool presign-exit
or a similar command with a different name.The text was updated successfully, but these errors were encountered: