CPU issues with running TESTNET backend/scripts/nodes/n0_test

[andrewarrow]

Running this n0_test script is great. I get new blocks produced quickly, don't have to wait for a full MAINNET to sync and free money!

I'm able to use the starter-bitclout-seed words to post new messages as it has plenty of clout available. But my CPU is pegged. It makes too many blocks and gives me too much free money.

Is there anyway to run it with a max CPU setting? I don't want it to take any significant resources from my dev machine.

[andrewarrow]

oh i think I see what I want. I just removed:

  --num-mining-threads=1 \
  --miner-public-keys=BC1YLieU9Zc5goMLXg3KM7Y3v7d9KKJg9WCuBiuJcPwkbSKxBNqYzL9 \

[andrewarrow]

actually removing that doesn't seem to solve problem. Then I have no money again and can't post. Also I noticed I had to change miner-public-keys to tBCKW665XZnvVZcCfcEmyeecSZGKAdaxwV2SH9UFab6PpSRikg4EJ2 when using &testnet=true as param to identity login.

[maebeam]

Your local testnet node will mine blocks as fast as it can. Adding a configuration variable to slow this down would be a great feature