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.

Sign up for GitHub

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

Jump to bottom

L1MessageTx Considerations #15

Open
frisitano opened this issue Oct 7, 2024 · 0 comments
Open

L1MessageTx Considerations #15

frisitano opened this issue Oct 7, 2024 · 0 comments

Comments

@frisitano
Copy link
Collaborator

Overview

L1MessageTx transactions are unsigned objects and as such can not be authenticated. Therefore we should not allow for these transactions to be consumed from the transaction pool. Instead we should modify the payload attributes on the engine api to support for a trusted entity to inject these transactions as they are read from L1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Reth
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@frisitano