Skip to content

OPR Targeting Patch
Compare
Choose a tag to compare
@Emyrk Emyrk released this 18 Sep 16:48
v0.2.1
c1ae9f8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Targeting Patch

Mainly addressing this issue: #310. This change corrects a bug that enabled miners to set very low difficulties, breaking the targeting code. The result is burning more EC than necessary.

Following this patch, RecordsPerBlock should never be to set to over 50. Anything more than 50 is a complete waste in all scenarios, and this might be enforced in a future release. If you are more concerned about the costs, a cap of 25 is the most any miner would want to submit if there a majority of honest miners. So setting RecordsPerBlock to max 25 is also reasonable.

Note: If you are using the netcoordinator, only the netcoordinator needs to be updated. Not the netminers

Behavior Changes:

  • In the performance command, your total submissions might have changed. The miner when quick syncing from disk no longer keeps anything past the last graded opr. Meaning the miner cannot find submissions beyond that. In the future, we will not longer count submissions past 50 in the miner. Another daemon/tool will need to be used to get more statistics. With the growing rate of the chain, keeping all this in the miner is becoming more expensive than the miner should support.

Changelog:

  • Targeting now correctly bases it's calculation of the 50th honest opr by difficulty
  • Arm64 builds will now be created
  • More details in the logs, such as ip addresses of the clients on connect/disconnect
  • Some small bug fixes to some cli command used by developers
    • pegnet decode entry was using the wrong extid for the version number
    • Two commands were using the -o flag, that collision was fixed
Assets 8
Loading