sacha

Got it. I think it would still be useful on first launch (this is probably when you're most uncertain as to whether things are working as they should be). When...

@arnetheduck alternatively we could just have a friendly message that lets the user know this may take some time.

@arnetheduck i'm probably missing something obvious, but when i run the command as is from the nimbus guide ``` curl -d '{"jsonrpc":"2.0","method":"get_v1_beacon_states_stateId_validators","params":["finalized"],"id":1}' -H 'Content-Type: application/json' localhost:9190 -s | jq ```...

> We can potentially get a bit more decentralisation (by making secure staking more accessible) There seems to be a lot resting on this assumption. Why *a bit*, and not...

> The only consensus-layer decision is whether or not to have fraud proofs. If we have fraud proofs (which seem necessary especially since we're looking at the ethereum blockchain be...

@superphiz, while i haven't included specific instructions, I've tried to address that [here](https://github.com/ethereum/eth2.0-deposit/pull/162).

*binary executable file* sounds awfully intimidating. would replace with a friendlier term, *command line app*, or something like that (definitely a tradeoff between accuracy and friendliness here).

as it stands, it's unclear that one should expect only one keystore per validator. would add a note to help clarify. something like: > You should see that you have...

+1 :)

related https://github.com/ethereum/eth2.0-deposit/issues/41#issuecomment-626546164