Skip to content

Conversation

@ahshum
Copy link
Contributor

@ahshum ahshum commented Nov 21, 2025

No description provided.

@github-actions
Copy link

github-actions bot commented Nov 21, 2025

Unit Test Results

       12 files  ±0    2 432 suites  ±0   44m 16s ⏱️ - 1m 54s
12 672 tests ±0  12 107 ✔️ ±0  565 💤 ±0  0 ±0 
63 692 runs  ±0  62 964 ✔️ ±0  728 💤 ±0  0 ±0 

Results for commit b1ad20e. ± Comparison against base commit 0edc9d5.

♻️ This comment has been updated with latest results.

const consensusFork = typeof(blck).kind
static: doAssert consensusFork >= ConsensusFork.Deneb

template forkyTransactions: untyped =
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typically when Nimbus uses forkyFoo, it means the actual Foo (Transaction, say) are different. It seems like in this case the transactions themselves are the same, just housed differently?

else:
blck.body.execution_payload.transactions
template forkyCommitments: untyped =
when consensusFork >= ConsensusFork.Gloas:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar point here -- are the commitments any different, or just in a different part of the block/envelope?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants