Open wu-s-john opened 5 years ago
I think this should be done along with the concurrent VRF evaluation stuff that's coming down the pipeline. We already need to build something that will evaluate VRF results in parallel in order to support nodes staking for a high number of delegators. We should roll the entire architecture for that up into a single RFC and explicitly list this as a requirement of that system.
Currently, the Proposer code only shows the next slot that will win. It would be nice to show all the possible slots that you will win for an epoch. I suspect that this may be computationally expensive and we want to compute this lazily when a client wants this info.
For the graphql schema, this new field should be under each owned account as the computation for computing the next slot requires a private key.
Also, we should do this computation for all accounts that you own. This would probably under daemon status.