feat: Add Web3Transaction

[tibor-reiss]

What was wrong?

"There should be an easy way to take a transaction directly as a JSON-RPC dict..."

Related to Issue #3534

How was it fixed?

Add Web3Transaction thin wrapper for better UX.

Todo:

• Clean up commit history
• Add or update documentation related to these changes
• Add entry to the release notes

Cute Animal Picture

[tibor-reiss]

Hi @fselmo, could you please check if this is according to your vision?
I made a single class with ValueErrors. Other option would be to have a class hierarchy with Web3DynamicFeeTransaction, Web3AccessListTransaction, ...

[BobTheBuidler]

might I recommend defining slots to make the wrapper even thinner?

[tibor-reiss]

might I recommend defining slots to make the wrapper even thinner?

Hi @BobTheBuidler, could you please provide some example? E.g. should only typed_transaction be part of slots, or all the attributes from _dict? To me, this would make sense with a class hierarchy, because some of the attributes do not exist on specific types. Let me what you think.

[BobTheBuidler]

I was just thinking about __slots__ = ("typed_transaction, "_dict"), not necessarily slots for each attr

Though that would be even thinner if you did it!

[fselmo]

Thanks for the brainstorming here @tibor-reiss 🙂 . I'd like to think on this some more and how we could maybe leverage this transaction API as more of a "first class citizen" of the library, maybe as a pydantic model for the next major version - possibly replacing TxParams altogether. That may require quite a bit of work though. This isn't a priority at the moment but I think it's good to get the conversation going on it at least, so thanks for getting it started 👍🏼