[Followup] Trait for relationships between receipts, logs, and log contents

[prestwich]

We need trait bounds for specifying when the contents of a receipt log vector can be interpreted as logs. I.e. a trait-based definition for what a log is, including encoded, decoded, rpc, consensus, etc.

This means that they contain a consensus::Log object (either consensus Log or RPC Log containing an inner consensus log) and that the data type consensus::Log<T> can be infallibly converted into LogData

          it's a bit more complicated and we will need more work here. Because `Log` is actually `Log<T = LogData>` we want to be able to implement generically across a wide variety of types, and may need to introduce a `trait Log` in order to do it

          For now, this is an improvement over the existing state of things so we might as well

Originally posted by @prestwich in #617 (comment)

[prestwich]

See also:
#512 (comment)

[prestwich]

How i'm currently thinking about this:

• some types (like SolEvent) can be infallibly converted into LogData

  • this is currently captured as a messy for<'a> bound
  • should probably be an IntoLogData trait?

• Log objects contain either LogData or some type that can be converted into it Log<T: IntoLogData>

• some types contain log vectors trait HasLogs<T: IntoLogData>: AsRef<Log<T>> { }

  • This is partially captured by trait TxReceipt in alloy-consensus
  • ReceiptEnvelope AND RpcReceipt AND consensus::Receipt should implement HasLogs<T>

• N::ReceiptEnvelope and N::ReceiptResponse types contain log vectors

  • new bound on those assoc types

• N::ReceiptResponse should always contain a ReceiptEnvelope

  • new bound no that assoc type AsRef<Self::ReceiptEnvelope>

• All <N as Network>::ReceiptResponse types contain a ReceiptEnvelope

  • new bound ReceiptResponse: AsRef<ReceiptEnvelope> + TxReceipt
  • as a result, we can also bound + TxReceipt