Closed gbotrel closed 2 months ago
I kinda feel like we can abstract things better if there's literally no change other than chain spec. But at the same time we also want to keep the ELF files minimal (e.g. it would be a waste to build Linea spec into the Ethereum ELF).
An alternative would be making the chain spec part of the client input.. but that increases runtime costs (slightly?). It does give us the benefit of using the exact same ELF for every single Ethereum equivalents that only differ in spec though.
@jtguibas wdyt?
In any case I think we should just merge first and deal with extra abstraction later. Will take a look soon.
I may have missed something since the host always complains about a state root mismatch (didn't find a single block on which it didn't complain).
Do you have a Linea RPC node that can be used for testing this?
Can you ping me on Telegram? (@gbotrel) I have a partially sync archive node but need to whitelist your IP to access it
Ugh I pushed the wrong commit to your main
branch, and the PR got closed, so I lost access to push to your main.
Could you please just push anything to main
so I can reopen this? @gbotrel
Ugh I pushed the wrong commit to your
main
branch, and the PR got closed, so I lost access to push to your main.Could you please just push anything to
main
so I can reopen this? @gbotrel
done --> https://github.com/gbotrel/rsp/commit/acdc1c0afcc3905d57431cb26b558bca50fb35ef 👍
This PR adds the Linea variant, which is mostly copy pasted from the default Ethereum one + adds the corresponding LineaVariant and chainspec objects.
Example output for
cargo run --bin rsp --release -- --block-number 279107 --rpc-url ...
: