You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A smart contract by any project that's interacting with (tx_from / tr_from) the L2ToL2CrossDomainMessenger: 0x4200000000000000000000000000000000000023, and any other smart contracts that builds on top of the smart contract aforementioned (e.g. DEX built on top of cross-chain liquidity layer that sends cross-chain messages to the L2ToL2CrossDomainMessenger)
Any smart contract that validates a cross chain message on the destination chain and emits an ExecutingMessage event. (Note that the ExecutingMessage itself doesn't emit the sender address but we can get it from validateMessage in traces
The text was updated successfully, but these errors were encountered:
chuxinh
changed the title
Interop Enabled App Definiton
[Exploratory] Interop Enabled App Definiton
Mar 1, 2025
Adding SuperchainTokenBridge so that you can capture who is sending/receiving tokens. Otherwise tx_from/to for the perspective of the L2ToL2CrossDomainMessenger is just the SuperchainTokenBridge
Proposed Definition
tx_from
/tr_from
) theL2ToL2CrossDomainMessenger
:0x4200000000000000000000000000000000000023
, and any other smart contracts that builds on top of the smart contract aforementioned (e.g. DEX built on top of cross-chain liquidity layer that sends cross-chain messages to theL2ToL2CrossDomainMessenger
)ExecutingMessage
event. (Note that theExecutingMessage
itself doesn't emit the sender address but we can get it fromvalidateMessage
in tracesThe text was updated successfully, but these errors were encountered: