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

Interop: update the event-index wildcard / intent feature PR #277

Open
protolambda opened this issue Jul 15, 2024 · 0 comments
Open

Interop: update the event-index wildcard / intent feature PR #277

protolambda opened this issue Jul 15, 2024 · 0 comments
Assignees

Comments

@protolambda
Copy link
Contributor

The idea of specifying a wildcard event-index, to defer the exact connection to initiating-event to the sequencer, was drafted here: #108

This needs to be updated to account for executing-messages now being declared through events, not statically in a transaction.
Likewise, the link to the initiating message, as inserted by the sequencer, may be declared through an event, to keep all message-dependency data within the log-events scope.

This enables more flexible transaction flows, by allowing users to pre-sign multiple interdependent interop txs, without pre-committing to the exact block construction (i.e. no exact event index).

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

No branches or pull requests

1 participant