You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1444: Store pool retirement certificates + fix stake distribution fetching & combining. r=KtorZ a=KtorZ
# Issue Number
<!-- Put here a reference to the issue this PR relates to and which requirements it tackles -->
#1442
# Overview
<!-- Detail in a few bullet points the work accomplished in this PR -->
- c748037
bump versions in README compatibility matrix
- ded40cc
add Jörmungandr binary deserialisers for pool retirement certificates
- 42e387d
track 'PoolRetirementCertificate' in the stake pool worker
The corresponding database function doesn't exist _yet_, coming in the next commit.
So far, this would simply add the retirement certificates into a new table but, do
nothing with them.
- 61203d4
implement initial behavior for 'putPoolRetirement' in the database layer
Any pool that has submitted a retirement certificate will be removed
from the list, regardless of the retirement time set by the pool.
Ideally, we would prefer to only discard pool when they are actually
retired (i.e. based on the time they set).
- 7c8623a
Fetch stake distribution by epoch instead of latest one
- 9d2fd50
Ignore blocks produced by pools not in the stake distribution.
The erroring was originally a precaution.
While I haven't checked, it must be that jormungandr removes pools in
the stake-distribution... before they are retired?
This patch seems to solve the problem.
- 7f43e64
cleanup ErrMetricsInconsistency now obsolete
- 0858080
update jormungandr.nix references for 0.8.14
# Comments
<!-- Additional comments or screenshots to attach if any -->
:warning: turns out that handling de-registration certificates was kinda useless. Problem was that we were trying to merge all-time production with stake distribution of the latest epoch which.. doesn't work.
On the way fixing this, I also implemented fetching the stake distribution based on the relevant epoch number, so this is now done as part of the forward loop and should automatically make the metrics & ranking much more stable.
Also added code for managing retirement certificates. We still do nothing with that but.. it's there now :man_shrugging: ... when relevant, we can then think about notifying frontend applications about de-registered pools.
<!--
Don't forget to:
✓ Self-review your changes to make sure nothing unexpected slipped through
✓ Assign yourself to the PR
✓ Assign one or several reviewer(s)
✓ Once created, link this PR to its corresponding ticket
✓ Assign the PR to a corresponding milestone
✓ Acknowledge any changes required to the Wiki
-->
Co-authored-by: KtorZ <matthias.benkort@gmail.com>
Co-authored-by: Johannes Lund <johannes.lund@iohk.io>
0 commit comments