Skip to content

feat: refactor sent messages mapping #16402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

hexshire
Copy link
Contributor

Description
Refactor of the L2ToL2CrossDomainMessenger::sentMessages mapping to improve traceability of message hashes and prepare the codebase for future features.

@hexshire hexshire requested a review from a team as a code owner June 12, 2025 19:19
@hexshire hexshire requested a review from mds1 June 12, 2025 19:19
/// mapping if it has been sent from this chain to a destination chain.
mapping(bytes32 => bool) public sentMessages;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nit: the successfulMessages mapping doesn't use the named key/value

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed: 919a0ba

@tynes
Copy link
Contributor

tynes commented Jun 13, 2025

This only impacts the mapping on the send side and not the receive side, looks safe to me

@tynes
Copy link
Contributor

tynes commented Jun 13, 2025

/ci authorize 919a0ba

@tynes
Copy link
Contributor

tynes commented Jun 14, 2025

/ci authorize 81ac2b1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants