Skip to content

Conversation

@lexnv
Copy link
Contributor

@lexnv lexnv commented Oct 31, 2025

Argument

Over the recent months, I have focused my efforts on the Ethereum Block Storage implementation in Substrate's Pallet Revive. This is part of a company-wide effort to bring EVM smart contract support to Substrate. At the same time, I continued to offer support for litep2p, pending fixes and reviews on the WebRTC work.

Ethereum Block Storage

I implemented an Ethereum-compatible block within pallet-revive (the Substrate EVM pallet) to enable full Ethereum block reconstruction, including block hashes, transaction roots, and receipt roots, directly within the Substrate runtime.

The #PR 9418 introduces a memory-efficient Ethereum block builder that constructs a full Ethereum block on-chain using only Substrate runtime data.

The implementation achieves a low memory footprint, avoiding pallet storage bloat and consuming up to 90% less memory and storage. This utilizes low-level semantics of RLP encoding to incrementally build the transaction and receipt roots, while keeping a maximum of 3 in-flight transactions.

The RPC layer has also been adjusted by Lukas and me to utilize the pallet changes.

For more details, the workload was monitored weekly in the following public document:
Weekly Progress Tracking

Litep2p Network Backend

I continued to monitor and support the litep2p crate. In doing so, I created a new release, litep2p v0.11.1, which mitigates an edge case that causes nodes to panic on unexpected rust-yamux inbound connections — addressed in PR #445. I also submitted a fix in the upstream rust-yamux crate to ensure poisoned states are no longer polled: rust-yamux #211.

During this period, I’ve also been in contact with Tim from ChainSafe to provide feedback on their WebRTC work, which is progressing in the right direction: litep2p WebRTC PR #441.

cc @skunert @sandreim 🙏

Signed-off-by: Alexandru Vasile <[email protected]>
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.

3 participants