Can we get methods off this to get all parts of tx data - this encode function gives you the data param, but would be nice to get everything including nonce, value, gasLimit, etc. all in one structure from a function (similar to how fractal needs it). This would actually let us create this generic contract encoder interface for every function call.

Here's an example of what the structure looks like: https://buildthirdweb.slack.com/archives/C03GRV58Y13/p1658382917

And implementation in Go: https://buildthirdweb.slack.com/archives/C03GRV58Y13/p165844326355217

But maybe most convenient is just to have a single function that returns the entire tx object, however ethers expects it, so people can do signing themselves as well (or at least for now to access the data).

yeah that's interesting basically make this one encodeFunctionData() and add another encodeTransaction() or something like that

Should we add docs on this interface as well (like on submit vs execute)

yep definitely, adding it now

Would it be beneficial to use/at least support the argument object pattern which tends to be common in JS vs the builder pattern. We had builder before with claim conditions and moved away from it - these two aren't as complex (this comment applies to both TransactionTaskBuilder and TransactionTask) but could be more convenient

I see what you mean - I kinda gravitated towards a builder pattern mainly coz im used to it. Might not be the JS way. I'll play with an object as argument, prob less code too

nitpick would be more concise with object params pattern instead of factory/builder and (imo but maybe wrong) more idiomatic for JS

Also, instead of passing this.contractWrapper here, could we add a function called buildTransaction to contractWrapper that lets us do this.contractWrapper.buildTransaction with the exact same API we've been using before for sendTransaction