I'm asking this because [**no one**][1] has been able to [**give a valid answer**][2] that applies to all cases.  Also, in the EOS Devs Telegram, there are constantly people commenting that their NET/CPU hasn't come back in over 3 days.  One person today said they've been waiting a week.

This leads me to believe that the recharging process is likely more complex than we realize.

Previously, we thought it might be 24 hours because of what's in the [chain config file][3]; however, that must be a metric for something else.

    static const uint32_t account_cpu_usage_average_window_ms  = 24*60*60*1000l;
    static const uint32_t account_net_usage_average_window_ms  = 24*60*60*1000l;
    static const uint32_t block_cpu_usage_average_window_ms    = 60*1000l;
    static const uint32_t block_size_average_window_ms         = 60*1000l;

Then we decided it was 3 days because of what EOS NY has on https://www.eosrp.io/

Please post the code where you find the logic to answer this.


  [1]: https://eosio.stackexchange.com/questions/912/how-long-is-the-reset-period-of-the-cpu-bandwith
  [2]: https://eosio.stackexchange.com/questions/1220/after-48-hours-cpu-not-reset?rq=1
  [3]: https://github.com/EOSIO/eos/blob/master/libraries/chain/include/eosio/chain/config.hpp#L48