Skip to content
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

Enforced Mesage Ordering #5354

Open
nambrot opened this issue Jan 31, 2025 · 0 comments
Open

Enforced Mesage Ordering #5354

nambrot opened this issue Jan 31, 2025 · 0 comments
Labels

Comments

@nambrot
Copy link
Contributor

nambrot commented Jan 31, 2025

Current Behavior:

Message senders currently do not get any ordering guarantees from the protocol.

Related issue: #5352

Expected Behavior:

Message senders can get ordering guarantees from the protocol.

Open thoughts

Would an ordering hook and ism work? I.e. you allow message senders to specify an ordering hook (maybe with a nonce/salt in the hook metadata). The ordering hook would send a message to the ordering ISM with a commitment to the original message ID and nonce. The ordering ISM can then be enforcing explicit ordering of the messages. Nice thing here is that senders have the ability to opt-in. They also can have different ordering per application logic.

@nambrot nambrot changed the title Enforced Ordering Enforced Mesage Ordering Jan 31, 2025
@yorhodes yorhodes moved this to Backlog in Hyperlane Tasks Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

No branches or pull requests

1 participant