wip: native l2 bridge adapter

[0xOsiris]

Note

High Risk
Changes cross-chain state delivery and trust boundaries (dispute game + MPT on L1, rollup messenger auth on L2); misconfiguration of L1 sender/messenger or relay addresses could block or mis-route bridged state.

Overview
Adds a native OP Stack path to bridge World ID state to L2s (e.g. Base): World Chain is still proven on L1 via dispute game + MPT, then EthereumMPTGatewayAdapter.forwardToL2 re-verifies and sends the commitment delta through L1CrossDomainMessenger to a new OpStackGatewayAdapter on L2, which only trusts the messenger + configured L1 MPT adapter as xDomainMessageSender and a chainHead(bytes32) attribute.

Contracts: new OpStackGatewayAdapter, InvalidCrossDomainSender, deploy script wiring (opStackGateway config/salt, _l1GatewayAddr tracking, L1-before-L2 deploy guards), staging config for ethereum+base. Relay: op_stack_gateways config, OpStackSatellite, and L1 send_forward_to_l2_tx alongside existing satellite types. Tests: e2e + auth failure cases with MockCrossDomainMessenger.

^{Reviewed by Cursor Bugbot for commit 5a538c6. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 5a538c6. Configure here.}

[cursor]

Wrong chain_id used for OP Stack wallet metrics

Medium Severity

log_wallet_status for OP Stack satellites passes config.source.chain_id (World Chain, e.g. 480) as the chain_id metric label, but the provider is the L1 provider. Every other satellite type correctly passes the chain ID matching the provider where transactions are sent (sat_config.destination_chain_id). This causes the L1 wallet balance metric to be recorded under the World Chain chain ID, making monitoring dashboards incorrect and potentially hiding low-balance alerts for the L1 relay wallet.

 

^{Reviewed by Cursor Bugbot for commit 5a538c6. Configure here.}

[cursor]

Missing periodic wallet metrics task for OP Stack

Low Severity

The OP Stack satellite setup calls log_wallet_status but never calls spawn_wallet_metrics_task, unlike every other satellite type (permissioned and Ethereum MPT). This means the L1 relay wallet balance won't be periodically updated in metrics after the initial log, potentially hiding a depleted wallet from monitoring.

 

^{Reviewed by Cursor Bugbot for commit 5a538c6. Configure here.}