Skip to content
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

fix(traverse): don't mess with Byron update epoch #566

Merged
merged 1 commit into from
Dec 22, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions pallas-traverse/src/block.rs
Original file line number Diff line number Diff line change
Expand Up @@ -183,9 +183,7 @@ impl<'b> MultiEraBlock<'b> {
match self {
MultiEraBlock::Byron(x) => {
if let Some(up) = x.body.upd_payload.proposal.deref() {
// TODO: this might be horribly wrong, I'm assuming that the activation epoch
// for a Byron upgrade proposal is always current epoch + 1.
let epoch = x.header.consensus_data.0.epoch + 1;
let epoch = x.header.consensus_data.0.epoch;
Some(MultiEraUpdate::Byron(
epoch,
Box::new(Cow::Owned(up.clone())),
Expand Down
Loading