Is your feature request related to a problem? Please describe.
cardano-db-sync [v10-v13] does not know of active stake from last epoch, and has to wait for a while before it's able to finish calculation of active stake from 'active' epoch (new epoch - 2) prior to epoch transition. This results in active stake being reported as null for few hours post entering new epoch for any stake addresses.
One option could be to have a special condition for stake distribution cache at epoch transition to fill the data in recent_epoch_stake table.
Describe the solution you'd like
Build an active stake cache dedicated to pre-filling the information after recently finished epoch, to have the data ready to read upon next epoch transition
Describe alternatives you've considered
Wait for fixes upstream, but that will likely be deferred to v14
Additional context
With the recent changes on node post 1.35, there will be increase in reliance on query layers like Koios' gRest (remotely or as local instance), it will also prevent being able to provide leadership schedule nonce right at epoch transition easily
Is your feature request related to a problem? Please describe. cardano-db-sync [v10-v13] does not know of active stake from last epoch, and has to wait for a while before it's able to finish calculation of active stake from 'active' epoch (new epoch - 2) prior to epoch transition. This results in active stake being reported as null for few hours post entering new epoch for any stake addresses. One option could be to have a special condition for stake distribution cache at epoch transition to fill the data in recent_epoch_stake table.
Describe the solution you'd like Build an active stake cache dedicated to pre-filling the information after recently finished epoch, to have the data ready to read upon next epoch transition
Describe alternatives you've considered Wait for fixes upstream, but that will likely be deferred to v14
Additional context With the recent changes on node post 1.35, there will be increase in reliance on query layers like Koios' gRest (remotely or as local instance), it will also prevent being able to provide leadership schedule nonce right at epoch transition easily