-
-
Notifications
You must be signed in to change notification settings - Fork 405
Description
Something to note, we apply the same validation on the api as we do on gossip
export async function validateApiVoluntaryExit( |
this is due to the fact that we publish it to the network immediately
await network.publishVoluntaryExit(signedVoluntaryExit); |
but something we could consider is that we separate out some transient checks which would become valid eventually, there are like 3-4 of them and post-electra we add another one which checks that there are no pending withdrawals. Meaning we would keep the volunary exit in the cache and publish it to the network only after those conditions are met.
As this has worked like this since phase0 it seems like no issue but something to consider to improve UX, on the other hand I can also see that accepting the voluntary exit but not publishing it immediately might be confusing as well.
Originally posted by @nflaig in #7379 (comment)