Skip to content

Conversation

arnetheduck
Copy link
Member

Blocks are getting stored both in BlockRef and in TxFrame - this is the less invasive change that delays storing block contents in TxFrame until it's time to update the base - the better option for the future is likely to not store the full block in BlockRef (and instead load it from TxFrame on demand)

@arnetheduck arnetheduck force-pushed the fc-half branch 4 times, most recently from 1c26462 to dffaf55 Compare September 8, 2025 15:39
@arnetheduck arnetheduck force-pushed the fc-half branch 2 times, most recently from a627026 to 95e3e1d Compare September 15, 2025 07:42
@arnetheduck arnetheduck force-pushed the fc-half branch 5 times, most recently from 5bf134c to 4cfa1d8 Compare September 25, 2025 10:05
Making the two projects more similar makes it easier to maintain a
cohesive user experience over time:

* remove metrics logging - this is not viable for the amount of metrics
that we have (no other project has this either)
* remove `EthContext` - looks like a refactoring leftover
* reuse more `nimbus_binary_common` utilities instead of homegrown
versions
* bump eth2
Blocks are getting stored both in BlockRef and in TxFrame - this is the
less invasive change that delays storing block contents in TxFrame until
it's time to update the base - the better option for the future is
likely to not store the full block in BlockRef (and instead load it from
TxFrame on demand)
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.

1 participant