This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
future_modifications [12/02/2021 18:01] – [Solution] gfactor | future_modifications [12/03/2021 04:07] – gfactor | ||
---|---|---|---|
Line 29: | Line 29: | ||
Useful info like ‘computed nonce 112021 time taken 433918’ is helpful. Cal can work out the hash rate from that alone. But if you could send over some more readings (or the whole log file if easier) that would be good too. Please also include the specs of your machine. Then he can start collating data. | Useful info like ‘computed nonce 112021 time taken 433918’ is helpful. Cal can work out the hash rate from that alone. But if you could send over some more readings (or the whole log file if easier) that would be good too. Please also include the specs of your machine. Then he can start collating data. | ||
- | We have a Telegram channel | + | We have a Telegram channel |
+ | |||
+ | ===== Additional Info ===== | ||
+ | |||
+ | The JAR makes no difference right now to any consensus or rewards if you run it. All the JAR is doing is some additional proof of work in the background (essentially wasted computations) in order to a) simulate the system load of this approach, and b) log info about the speed at which it is calculating. | ||
+ | |||
+ | If we were to switch to this approach in the future, these computations would become compulsory in order to mint. They would prevent gamers from being able to run too many minting keys on a single node. But it comes with the trade-off of a lot of extra system load, which you can simulate using the PoW JAR. | ||
+ | |||
+ | Once it's been running for at least a few hours, would be great if you could share your log file (or at least the lines that start with " | ||
+ | |||
+ | Log file is in ``%localappdata%/ | ||
+ | |||
+ | You can type `%localappdata%/ |