User Tools
future_modifications
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| future_modifications [12/02/2021 17:58] – gfactor | future_modifications [12/02/2021 18:01] – [Solution] gfactor | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| This measures how long it took to compute a nonce at difficulty level 15. If those numbers are consistently higher than one or two minutes, it could be a problem (because it could mean that the node's online accounts would miss out on being included in some blocks, due to taking a long time to compute the proof of work). We’ll need to arrive at the correct difficulty and time limits to use. | This measures how long it took to compute a nonce at difficulty level 15. If those numbers are consistently higher than one or two minutes, it could be a problem (because it could mean that the node's online accounts would miss out on being included in some blocks, due to taking a long time to compute the proof of work). We’ll need to arrive at the correct difficulty and time limits to use. | ||
| - | 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 spec 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 @qortallogs and Discord channel # | We have a Telegram channel @qortallogs and Discord channel # | ||
future_modifications.txt · Last modified: 12/05/2021 08:29 by gfactor