ExEx - rollup - RPC endpoint

[adaki2004]

Hey there!

Sorry for tagging you @mattsse , but i have seen your name in some issues/PRs/discussions around the topic, but i'm not so sure i'm on the correct path, would love to have some guidance!

So currently shooting up reth in kurtosis as per reth documentation, and we have a slight modification of main branch, where we are having the exex and wants to make it a rollup. (L2 inside the L1).

Currently with hardcoded payload we are able to make blocks on L2 (coming from L1), but what we would need to do now is to interact with the "L2 exex" rpc, but even tho reth seemingly provides us with an endpoint, it seems it does not work (or we misconfugre something).

Maybe can you help us what address/flag needs to be set to (0.0.0.0) because the default (127.0.0.1) is not exposing just locally, and if i modify the code (to explicitly have 0.0.0.0 in the "logs") of this below - i still cannot see the port actually workingly exposed, even tho logs says so.. I cannot connect to it.

impl Default for RpcServerArgs {
    fn default() -> Self {
        Self {
            http: true,
            http_addr: Ipv4Addr::new(0,0,0,0).into(), //Ipv4Addr::LOCALHOST.into(),
            http_port: constants::DEFAULT_HTTP_RPC_PORT,
            ...
        }
    }
}

And my main function looking like this:

fn main() -> eyre::Result<()> {
    reth::cli::Cli::parse_args().run(|builder, _| async move {
        // Create the L2 node
        let tasks = TaskManager::current();
        let exec = tasks.executor();

        let network_config = NetworkArgs {
            discovery: DiscoveryArgs { disable_discovery: true, ..DiscoveryArgs::default() },
            ..NetworkArgs::default()
        };

        let chain_spec = ChainSpecBuilder::default()
                .chain(CHAIN_ID.into())
                .genesis(serde_json::from_str(include_str!("../../../crates/ethereum/node/tests/assets/genesis.json")).unwrap())
                .cancun_activated()
                .build();

        let node_config = NodeConfig::test()
            .with_chain(chain_spec.clone())
            .with_network(network_config.clone())
            .with_unused_ports()
            .with_rpc(RpcServerArgs::default().with_unused_ports().with_http())
            .set_dev(true);

        let NodeHandle { node, node_exit_future: _ } = NodeBuilder::new(node_config.clone())
            .testing_node(exec.clone())
            .node(Default::default())
            .launch()
            .await?;

        let node = NodeTestContext::new(node).await?;

        let handle = builder
            .node(EthereumNode::default())
            .install_exex("Rollup", move |ctx| async {
                Ok(Rollup::new(ctx, node)?.start())
            })
            .launch()
            .await?;

        handle.wait_for_node_exit().await
    })
}

It seems the ports (via docker) is not exposed, also as per Kurtosis it shall be. (?) AFAIK. Even the logs itself in reth showing me an endpoint (which shall be my exex rollup rpc endpoint i guess), but not present in the enclave.

...
2024-08-22 08:33:25 2024-08-22T06:33:25.342375Z  INFO RPC HTTP server started url=0.0.0.0:33853
...

The enclave inspect is not mentioning that port anywhere, and i can clearly see not exposed.

Name:            winter-rift
UUID:            de06f07b4669
Status:          RUNNING
Creation Time:   Thu, 22 Aug 2024 08:33:06 CEST
Flags:           

========================================= Files Artifacts =========================================
UUID           Name
8832198c5cb1   1-lighthouse-reth-0-63-0
7b0d1a9bd9fa   2-teku-reth-64-127-0
6dc63c1faf3f   el_cl_genesis_data
990c8ce4c230   final-genesis-timestamp
68a1bd0cb91c   genesis-el-cl-env-file
b448f5603219   genesis_validators_root
a52bdee13102   jwt_file
9fdcf524d517   keymanager_file
82ee2e08dca7   prysm-password
2e85f5edf7c4   validator-ranges

========================================== User Services ==========================================
UUID           Name                                             Ports                                         Status
784441feb3d6   cl-1-lighthouse-reth                             http: 4000/tcp -> http://127.0.0.1:50510      RUNNING
                                                                metrics: 5054/tcp -> http://127.0.0.1:50511   
                                                                tcp-discovery: 9000/tcp -> 127.0.0.1:50512    
                                                                udp-discovery: 9000/udp -> 127.0.0.1:61010    
d7daa5d75849   cl-2-teku-reth                                   http: 4000/tcp -> http://127.0.0.1:50514      RUNNING
                                                                metrics: 8008/tcp -> http://127.0.0.1:50515   
                                                                tcp-discovery: 9000/tcp -> 127.0.0.1:50513    
                                                                udp-discovery: 9000/udp -> 127.0.0.1:64258    
2239f2112235   el-1-reth-lighthouse                             engine-rpc: 8551/tcp -> 127.0.0.1:50503       RUNNING
                                                                metrics: 9001/tcp -> http://127.0.0.1:50504   
                                                                rpc: 8545/tcp -> 127.0.0.1:50501              
                                                                tcp-discovery: 30303/tcp -> 127.0.0.1:50500   
                                                                udp-discovery: 30303/udp -> 127.0.0.1:60710   
                                                                ws: 8546/tcp -> 127.0.0.1:50502               
24a4ed35ed62   el-2-reth-teku                                   engine-rpc: 8551/tcp -> 127.0.0.1:50508       RUNNING
                                                                metrics: 9001/tcp -> http://127.0.0.1:50509   
                                                                rpc: 8545/tcp -> 127.0.0.1:50506              
                                                                tcp-discovery: 30303/tcp -> 127.0.0.1:50505   
                                                                udp-discovery: 30303/udp -> 127.0.0.1:62648   
                                                                ws: 8546/tcp -> 127.0.0.1:50507               
da4d6ba62b17   validator-key-generation-cl-validator-keystore   <none>                                        RUNNING
bb5830cdf5f7   vc-1-reth-lighthouse                             metrics: 8080/tcp -> http://127.0.0.1:50518   RUNNING

Would love to have your thoughts as i'm a bit on hold for this. Most probably it is just a config or flag i'm not setting properly.

[mattsse]

not familiar with the enclave docker but it looks like kurtosis maps

rpc: 8545/tcp -> 127.0.0.1:50506

INFO RPC HTTP server started url=0.0.0.0:33853

this looks like a random port or port 0, likely because of .testing_node(exec.clone())

what if you configure the rpc endpoint of reth to 8545?

cc @shekhirin

[adaki2004]

Thanks for the fast reply!

i somehow assumed we need 2 ports and 50506 is the L1 rpc endpoint but i did not found anything about my exex rollup one, which (i just thought) shall be that 33853 as per the log.

8545 is the one but exposed to that 50506.
(Reason is: 8545 i cannot reach outside the container.)

[mattsse]

ah I see you're launching an entire new node as exex with its own server on a random port

.with_rpc(RpcServerArgs::default().with_unused_ports().with_http())

tbh idk how to do additional port mappings in kurtosis

[adaki2004]

Ah yes, right! I’m in Kurtosis server too, Barnabas is a great asset, he shall be able to help when he will have time i just thought i’m “attacking” on multiple front :), if it’s something you encountered with already. Thank you !

[adaki2004]

@mattsse @shekhirin
Are there any launcher flags that i can use so that i can set exex.addrs to 0.0.0.0 ?

Like here: https://github.com/ethpandaops/ethereum-package/blob/a433c50e1c61dd20a6c28dcebfde704c136ddb69/src/el/reth/reth_launcher.star#L213