1

I created EOS mainnet account and I tested some transfer commands.

Each time when I typed transfer commands, my CPU usage increased about 2ms.

So I staked EOS to my CPU constantly, and I think there's no difference with "Fee"!

In my thought, after a few times ago, I will be decreasing little by little, but after a few hours later, It didn't changed.

In another steemit post (https://steemit.com/eos/@leordev/eos-ram-and-bandwith-analysis-airdropping-steps-on-junglenet), in reply, dan says that

"Once people claim their tokens you get the ram back" (It's not for CPU's, but... anyway!)

So, my questions is,

Q1. Can my CPU usage shrinks when I executed transfer commands? If can, how can I know when is that time?

Q2. What "claim their tokens" means in dan says?

2

Q1. Can my CPU usage shrinks when I executed transfer commands? If can, how can I know when is that time?

Your CPU usage resets after an average of 24 hours.

How long is the reset period of the cpu bandwith?

Q2. What "claim their tokens" means in dan says?

Dan means that once people move their tokens, they'll become the payer of the account balance row in the smart contract. Because they are the new payer, the old payer is no longer a payer and his RAM staked is now unstaked.

CPU and bandwidth comes back easy enough, so you can get pretty wild with it, RAM however is a different story, you cannot unstake RAM at anytime like you can CPU and bandwidth. This is because RAM can become commited to records in smart contracts, e.g. the eosio.token contract where a piece of RAM is used for every account balance. Until that record is destroyed or someone else is paying for the RAM, that RAM cannot be unstaked.

| improve this answer | |
  • 1
    What do you mean 1100 EOS is gone, did it go out through a transfer? You should retain a staked balance of X amount of EOS. Send me your account name if you like and I'll check it out. – John Williamson Jun 29 '18 at 7:19
  • False alarm, solved the issue. There had to be a transaction done first for CPU to restart. – Damir Olejar Jun 29 '18 at 16:03
0

Copying the comment from @nat as an actual answer.

Your CPU/NET recharges over 24 hours:

static const uint32_t account_cpu_usage_average_window_ms = 24*60*60*1000l;
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.