STEP 1 OF 3
NEXT: How the four components divide the work →
PREREQUISITE
Bring the Chiado stack from step 03 up first (scripts/chiado-up.sh) — xchain-test.sh exits if the node container or deployments.env is missing.
ENDPOINTS · README.md · the chiado compose stack
L2 RPC
http://localhost:18688
L2 eth_*
Embedded chiado L1 RPC
http://localhost:18645
L1 eth_* (the composer's L1 view)
L1→L2 front (Inbound)
http://localhost:18999
PROXY
send L1-origin cross-chain txs here
L2→L1 front (Outbound)
http://localhost:18998
PROXY
send L2-origin cross-chain txs here
eth_sendRawTransaction
→
held, composed into the next Sync block
every other eth_*
→
forwarded to that front's source-chain RPC
The fronts are transparent proxies, not separate chains. These ports are the compose stack's; a Kurtosis devnet assigns its own — source testing/kurtosis/ports.sh.
PINNED
ROLLUP OPERATORS
How to send and test a cross-chain call
Two transparent proxy fronts sit in front of L1 and L2: sendRawTransaction is held for the next Sync block, while everything else passes straight through.
Bring the stack from step 03 up first, then drive both fronts to read the pipeline's own pass/fail numbers.
WHAT YOU'LL LEARN
- 01 · TWO FRONTS, ONE JOBsendRawTransaction is held for the next Sync block — once per L1 block, for cross-chain work.
- 02 · MIND THE BUNDLE SIZEEEZ_MAX_USER_TXS_PER_BUNDLE defaults to 3, rbuilder-chiado silently drops anything past it, and that drop is where atomicity stops.
- 03 · EXERCISE ITxchain-test.sh drives both fronts through the full matrix and prints a RESULTS block of pipeline metrics.
Verified against eez-rollup0 @ a4b9b2f — pre-mainnet; interfaces may move.