Implement alloy Encodable2718 and Decodable2718 for reth transaction types

### Describe the feature

currently we use our own native functions for:

https://github.com/paradigmxyz/reth/blob/68d76f6469eac41e08f93b00a8a19a3b1e648d0b/crates/primitives/src/transaction/mod.rs#L1195-L1213

we will move more things to alloy traits and encoding is one thing so we should transition this already to alloy's traits

## TODO:
* replace reth `envelope` functions with trait impl

easiest way to update this across the codebase is to first rename the reth function, then impl the trait and remove reth function, then import trait where this is called

### Additional context

_No response_

	/// Returns the enveloped encoded transactions.
	///
	/// See also [`TransactionSigned::encode_enveloped`]
	pub fn envelope_encoded(&self) -> Bytes {
	let mut buf = Vec::new();
	self.encode_enveloped(&mut buf);
	buf.into()
	}

	/// Encodes the transaction into the "raw" format (e.g. `eth_sendRawTransaction`).
	/// This format is also referred to as "binary" encoding.
	///
	/// For legacy transactions, it encodes the RLP of the transaction into the buffer:
	/// `rlp(tx-data)`
	/// For EIP-2718 typed it encodes the type of the transaction followed by the rlp of the
	/// transaction: `tx-type \|\| rlp(tx-data)`
	pub fn encode_enveloped(&self, out: &mut dyn bytes::BufMut) {
	self.encode_inner(out, false)
	}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Implement alloy Encodable2718 and Decodable2718 for reth transaction types #11153

mattsse
openedon Sep 24, 2024

Describe the feature

TODO:

Additional context

Assignees

Labels

Type

Projects

Milestone

Relationships

Development