Bug: Only Engine API server modules are initialized in the Binary

[0xOsiris]

The only RPC methods actually initialized in rollup-boost is from the Engine API server here.

I noticed this while testing #61 on a local Devnet.

On main this means eth_sendRawTransaction is not a registered RPC method on the Server.

[0xKitsune]

For visibility, I am currently working on a fix that merges and initializes all RPC modules and will open a PR once I have finished writing additional tests.

[avalonche]

EthApiServer and EngineApiServer are both implemented for EthEngineApi though, how did you test this?

[0xOsiris]

EthApiServer and EngineApiServer are both implemented for EthEngineApi though, how did you test this?

@avalonche You can verify this by simply logging

module.method_names().for_each(|name| {
    info!("Registered Method {}", name);
})

In the binary. The rpc proc macro implements into_rpc on the EthEngineApi 2 times, but it's only pulling from a single implementation (Engine API) when calling into_rpc. The modules need to be merged into a single module. We will have a PR open today that resolves this.