Return to Question

I'm asking this because no one has been able to give a valid answer 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; 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.

https://github.com/EOSIO/eos/blob/master/libraries/chain/resource_limits.cpp https://github.com/EOSIO/eos/blob/master/libraries/chain/include/eosio/chain/resource_limits_private.hpp

I'm asking this because no one has been able to give a valid answer 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; 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;

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.

https://github.com/EOSIO/eos/blob/master/libraries/chain/resource_limits.cpp https://github.com/EOSIO/eos/blob/master/libraries/chain/include/eosio/chain/resource_limits_private.hpp

I'm asking this because no one has been able to give a valid answer 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; 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.

I'm asking this because no one has been able to give a valid answer 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; 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.

https://github.com/EOSIO/eos/blob/master/libraries/chain/resource_limits.cpp https://github.com/EOSIO/eos/blob/master/libraries/chain/include/eosio/chain/resource_limits_private.hpp

I'm asking this because no one has been able to give a valid answer 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; 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.

I'm asking this because no one has been able to give a valid answer 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; 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.