we noticed that small fraction of nodes are not voting consistently with consensus results, due to missing blocks data from the period when they were offline. smeshers are recommended to upgrade when they are not eligible for rewards.
we noticed that small fraction of nodes are not voting consistently with consensus results, due to missing blocks data from the period when they were offline. smeshers are recommended to upgrade when they are not eligible for rewards.
v1.0.15
⚠️ Critical fix ⚠️
We discovered the bug:
The value responsible for regulating the number of proposals in each layer has been omitted and therefore each smesher will only be eligible for a single block proposal in the entire epoch.
all ballots in layers <= 8180 will use 0 layer size for eligibility, so each smesher is eligible for only a single ballot per epoch
after layer 8180 they will start using 50 (the correct value), so each smesher will be eligible for many ballots per epoch as intended
This means that smeshers that haven't been eligible for a block proposal yet will now calculate their number of eligibilities correctly. To prevent smeshers that were already eligible from accidentally misbehaving and adding additional eligibilities, we're going to introduce a mechanism for respecting any previous claim to the number of eligibilities. If a smesher was already eligible and published a block proposal, this means they already received their full reward for the epoch for that one block proposal, so they don't need to be eligible again. Smeshers that were not eligible yet, will now have multiple eligibilities and their rewards will be spread out, as originally planned.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps github.com/spacemeshos/go-spacemesh from 1.0.2 to 1.0.17.
Release notes
Sourced from github.com/spacemeshos/go-spacemesh's releases.
... (truncated)
Commits
437777a
tortoise: cap ballot layer by current according to the clock7668357
sync, blocks: request blocks when tortoise crossed local threshold (#4826)85b1ea9
extend update1705d98
find first non-empty blockac66267
invalid miner cache3de23ea
extend time for updateb4f342f
stop atx grading at layer N57041b1
separate layer average size before some point and after2b1ad2a
beacon: add public metrics for current and next epoch (#4813)b74d266
parametrize inbound/outbound fractions for experiments (#4787)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show