Should these derive the rlp encodable macro?

[0xJepsen]

alloy/crates/rpc-types/src/eth/transaction/typed.rs

Line 18 in b7a9c18

pub enum TypedTransactionRequest {

if not how should i serialize my transaction to be be signed. Working on something like thi

       let mut payload = Self::path_to_bytes(&self.derivation);

        // need to figure out how to encode the alloy TypedTransactionRequest into a Vec<u8>
        payload.extend_from_slice(tx.encode().as_slice());

        let mut signature = self.sign_payload(Instruction::Sign, &payload).await?;

[prestwich]

right now this crate has RPC type, which is actually a superset of the Transaction type that gets RLP encoded. we're still planning how to make this distinction smooth. I am skeptical of implementing rlp encodabe/decodable for types with more props than the actually encoding will represent

related conversation in #50

[prestwich]

closing this as the answer is now clearly no. this is superseded by #83 and #78