You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UNKNOWN_STATUS is extremely vague and is certain to cause a lot of turmoil in the minds of new stakers when we go live. Showing that an Eth1 deposit has been received before the validator is pending inclusion will enhance the quality of the product in the minds of end users. There may be other appropriate status updates that could be included.
The text was updated successfully, but these errors were encountered:
Good point that UNKNOWN is a bit concerning. It simply means that the status was not set.
We should look into adding or fixing eth1 deposit received. We should be returning a status to indicate that the beacon node has seen the eth1 deposit.
We could also display "Awaiting deposit" or something along those lines if the deposit has not been observed in eth1 deposit contract.
I intend to make some larger scale logging improvements for validator status after #5396 is merged. Have you tried a new validator deposit within the last few days @superphiz ?
I intend to make some larger scale logging improvements for validator status after #5396 is merged. Have you tried a new validator deposit within the last few days @superphiz ?
I intend to make some larger scale logging improvements for validator status after #5396 is merged. Some improvements were already made in #5389. @superphiz would you mind letting me know if the experience has improved when we restart our testnet?
UNKNOWN_STATUS is extremely vague and is certain to cause a lot of turmoil in the minds of new stakers when we go live. Showing that an Eth1 deposit has been received before the validator is pending inclusion will enhance the quality of the product in the minds of end users. There may be other appropriate status updates that could be included.
The text was updated successfully, but these errors were encountered: