staking-launchpad
staking-launchpad copied to clipboard
ethereum
Different order of steps
Please, let the user first sync the beacon-node (and connect it to its validator), and eth1 node before doing the deposit! If the user for some reason fails to set this up, it will lose ETH due to inactivity. Also, syncing an Eth1 node on the main-net can take a few hours/days.
Good points @Buttaa I transferred this issue to eth2.0-deposit repo for visibility. /cc @Battenfield
I really support this. Chose a client first, set it up, and once you are ready, come back to the launchpad!
Support this too. The user should be comfortable with a beacon node, and fully synced, before starting to deposit or validate. Before genesis this is less of a problem, but getting a beacon node running is an essential first step. And good to test those ignorant enough to not start a node or validator client at all. Deposits are part of the start process, there's more to staking, which some users seem to forget.
Maybe the beacon node should sign some message with the imported keystore acknowledging that it's fully synced and ready to use a particular validator? To then verify in the launchpad process before making the actual deposit? This can be an aggregate signature too, too keep it small and simple to copy paste. It can be bypassed if needed (i.e. can still deposit, contract doesn't change), but the user should know that they are taking on risk by doing so.
I think we need stricter checks for the eth1 node cc @protolambda , @hwwhww
https://www.reddit.com/r/ethstaker/comments/nfiuhj/made_mistake_sent_32_eth_before_gethfinished/