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

EIP-7702 Support #143

Open
frisitano opened this issue Jan 22, 2025 · 0 comments · May be fixed by #158
Open

EIP-7702 Support #143

frisitano opened this issue Jan 22, 2025 · 0 comments · May be fixed by #158

Comments

@frisitano
Copy link
Collaborator

frisitano commented Jan 22, 2025

Describe the feature

We should add support for EIP-7702 transactions.

Functional support from EIP-7702 will come from merging with upstream on reth and revm. We will then add support in our node client by adding the EIP-7702 transaction type to our primitives such as here:

/// The `TypedTransaction` enum represents all Ethereum transaction request types, modified for
/// Scroll
///
/// Its variants correspond to specific allowed transactions:
/// 1. `Legacy` (pre-EIP2718) [`TxLegacy`]
/// 2. `EIP2930` (state access lists) [`TxEip2930`]
/// 3. `EIP1559` [`TxEip1559`]
/// 4. `L1Message` [`TxL1Message`]
#[derive(Debug, Clone, PartialEq, Eq, Hash)]
#[cfg_attr(feature = "arbitrary", derive(arbitrary::Arbitrary))]
#[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
#[cfg_attr(
feature = "serde",
serde(
from = "serde_from::MaybeTaggedTypedTransaction",
into = "serde_from::TaggedTypedTransaction"
)
)]
pub enum ScrollTypedTransaction {
/// Legacy transaction
Legacy(TxLegacy),
/// EIP-2930 transaction
Eip2930(TxEip2930),
/// EIP-1559 transaction
Eip1559(TxEip1559),
/// Scroll L1 message transaction
L1Message(TxL1Message),
}

@frisitano frisitano added this to Reth Jan 22, 2025
@frisitano frisitano linked a pull request Feb 18, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant