Support EIP 7702

[chaitanyapotti]

Describe the Feature

Add support for tx type 0x04 and authorization_list in transaction types

https://eips.ethereum.org/EIPS/eip-7702

Code Example

No response

[ricmoo]

Oh! Is it finally deployed on a testnet? I’ve been waiting for that, as that is a good indication the spec of likely done changing. Plus it enables trying it out to test it. :)

Initially this will be available on signer._authorization() and once official, will be signer.authorization().

[Oxbobby]

@ricmoo it's deployed on Pectra Devnet, Odyssey and a few others. Looking forward to this

[marcelomorgado]

FYI https://blog.ethereum.org/2025/02/14/pectra-testnet-announcement

It will go live on Holesky at epoch 115968 (Feb. 24, 21:55 UTC) and then on Sepolia at epoch 222464 (Mar. 5, 7:29 UTC).

[ricmoo]

Thanks! Yes, I have a local implementation (in BaseWallet and Transaction) ready to release on the 24th once I can test it out. :)

[Mannan-Goyal]

@ricmoo let me know if this requires any contribution, as I've already tested this out on mekong

[Phillip-Kemper]

any way I can initiate the new transaction type already with ethers?

[ricmoo]

Almost. I have a PR I'll be pushing up later. I'm just waiting for it to go live on Sepolia so I can make sure my tests work. :)

[ricmoo]

Does anyone know of a JSON-RPC endpoint for Sepolia that this works on? It should have definitely activated by now. I've tried Infura, but I get the error:

// Error:
{
  code: -32602,
  message: 'transaction could not be decoded: unsupported transaction type'
}

// Payload:
{
  method: 'eth_sendRawTransaction',
  params: [
    '0x04f8c383aa36a70e80808252089401234567890123456789012345678901234567898080c0f85cf85a809401234567890123456789012345678901234567898080a0f063d1abb04fa98cfa4dfd92d509efcd398ab63b6d9c2944a1827d631f310b50a065c40ea1fa228700da4a53bdd1fc94d2b67ee23121466af3cf56f37ecc70c37a01a074c7c3b64a353009ab12c1c81406e381c83a7452be4513c23356816922e09c38a052d74f0486ac363f2c83b4dca8f099f09d3400a7469efb553195efa6fe94aca8'
  ],
  id: 8,
  jsonrpc: '2.0'
}

But that could just mean my encoding is incorrect or there is some other issue and the error is half red-herring. If someone has a know good JSON-RPC endpoint, it'd be appreciated. :)

[ricmoo]

I've added a branch with initial support. I'm going to test it a bit more and then publish it as an alpha release on npm.