-
Notifications
You must be signed in to change notification settings - Fork 45
Cleanup legacy code from thales era #2340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Test Results 3 files ± 0 52 suites ±0 10m 24s ⏱️ -13s Results for commit dac8109. ± Comparison against base commit 3f77f6b. This pull request removes 38 and adds 3 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
be7c8bb
to
f838b52
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🔥
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
Removing the need to wait for pending certificates.
…ion tests + simplify CardanoTransactions integration tests by prepending blocks to scan in init so first signature don't fail because of an empty merkle tree.
…ureMessage` All signers released since the `Pythagoras` era addition always send this metadata, allowing us to make it mandatory.
There's still some signers running a version without the backward compatibility support (v`0.2.209`, distribution `2445.0`), but they don't need it to be compatibile with aggregators that include this commit as it only means that they will send an extra field when registering signatures (those fields will be discarded by serde).
…cardano_signing_config_empty_values` As all aggregators have been updated.
…orFeaturesMessage` As signers now retrieve them using the `/epoch-settings` route instead since they can vary over epochs.
…ince Pythagoras era The transition to the Pythagoras era guarentee us that the nodes communication are using at least open api v`0.1.35`.
Resulting in a simple file. Migrations have been squashed up to `v29` as `v30` was the first included after distribution `2445.0`.
* mithril-persistence from `0.2.46` to `0.2.47` * mithril-aggregator from `0.7.6` to `0.7.7` * mithril-client-cli from `0.11.4` to `0.11.5` * mithril-client from `0.11.6` to `0.11.7` * mithril-common from `0.5.6` to `0.5.7` * mithril-relay from `0.1.35` to `0.1.36` * mithril-signer from `0.2.230` to `0.2.231` * mithril-aggregator-fake from `0.4.1` to `0.4.2` * mithril-end-to-end from `0.4.71` to `0.4.72` * openapi.yaml from `0.1.45` to `0.1.46`
1e6868d
to
dac8109
Compare
Content
Important
A backward compatibility workflow should be run after the merge of this PR.
This PR removes legacy code that was remaining to ensure backward compatibility with previous nodes from Thales era. With the transition to the Pythagoras era that code can now safely be removed because all actives nodes in the network have support for the updated code.
Context
Pythagoras era was available since
distribution 2445.0
, released Nov 7 2024, which includemithril-signer
version0.2.209
and open api version0.1.35
.Details
Remove pending certificate support
It was needed to synchronise signers when they could not compute the beacon to sign themselves (capacity added in distribution
2442
).Messages changes:
AggregatorFeaturesMessage
: removecardano_transactions_signing_config
from capabilities (superseded by epoch settings equivalent fields since distribution2442
).EpochSettingsMessage
: remove deprecatedprotocol_parameters
andnext_protocol_parameters
(superseded withsigner_registration_protocol_parameters
since distribution2445
).RegisterSignatureMessage
:signed_message
is now mandatory (always send by signers released since distribution2442
).CardanoDbBeaconMessagePart
andSignedEntityMessagePart
and use their entities instead: they were added for bacward compatibility in distribution2450
network
field in theRegisterSignatureMessage
(which will now be ignored by serde when de-serializing in said messages inmithril-aggregator
).0.1.35
.Nodes specific changes:
load-aggregator
): Refactored to send "buffer-able" single signatures messages, so it doesn't need to relies on the/certificate-pending
route for synchronisation.mithril-aggregator
: Removereplace_cardano_signing_config_empty_values
, it was used as a band-aid to add data for nodes that were running before the introduction of migration 28. All aggregators should have been updated by now.mithril-client
: Add missingSignedEntityType
from common re-export.Pre-submit checklist
Issue(s)
Relates to #2316