feat: L2ToL2CDM SentMessage originContext#15844
Conversation
l2tol2cdm.sentmessage.ctx
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #15844 +/- ##
===========================================
- Coverage 46.86% 45.99% -0.87%
===========================================
Files 1338 1283 -55
Lines 108127 103891 -4236
===========================================
- Hits 50672 47788 -2884
+ Misses 53847 52630 -1217
+ Partials 3608 3473 -135
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
| bytes32 internal constant CROSS_DOMAIN_MESSAGE_SOURCE_SLOT = | ||
| 0x711dfa3259c842fffc17d6e1f1e0fc5927756133a2345ca56b4cb8178589fee7; | ||
|
|
||
| /// @notice Event selector for the SentMessage event. Will be removed in favor of reading |
There was a problem hiding this comment.
no longer needed with the merged bugfix
| address _target, | ||
| bytes memory _message | ||
| bytes memory _message, | ||
| bytes memory _context |
There was a problem hiding this comment.
critical to include here so that resendMessage works as intended
| @@ -16,7 +16,7 @@ import { ISuperchainTokenBridge } from "interfaces/L2/ISuperchainTokenBridge.sol | |||
| /// @notice Integration test that checks that the `ExecutingMessage` event is emitted on crosschain mints. | |||
| contract ExecutingMessageEmittedTest is CommonTest { | |||
| bytes32 internal constant SENT_MESSAGE_EVENT_SELECTOR = | |||
There was a problem hiding this comment.
Can we use the selector property on the event itself rather than hardcoding it and needing it to change?
| if (_target == Predeploys.L2_TO_L2_CROSS_DOMAIN_MESSENGER) revert MessageTargetL2ToL2CrossDomainMessenger(); | ||
|
|
||
| uint256 nonce = messageNonce(); | ||
| bytes memory context = ""; |
There was a problem hiding this comment.
I am confused, should there be a sendMessage(uint,address,bytes,bytes) in addition where the context can be set?
|
Can you link the specs PR to this PR? edit: I see ethereum-optimism/specs#700 |
|
This pr has been automatically marked as stale and will be closed in 5 days if no updates |
|
Closing in favor of #16150 |

Implementation of Design Doc.