You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Filling the above. Basically, it's impossible to access the Full transaction field from the BlockTransactionHashesInner object as the only exposed API will collapse a Full transaction into its transaction hash. I would classify this as a bug and not a feature request as it is quite misleading, but happy to be corrected, mostly nomenclature to be honest. It does seem erroneous to download full payloads only to be offered access to the transaction hashes, which are returned in default mode anyways.
Obviously, something might have escaped me from the API, which might deprecate this bug report. Happy to stand corrected!
The text was updated successfully, but these errors were encountered:
okay it turns out that all the impls here are only for T = Transaction so i may need a trait abstraction for Transaction if i want to make it reusable across networks 🤔
Component
rpc
What version of Alloy are you on?
No response
Operating System
None
Describe the bug
Hello sirs.
Wonderful job!
Filling the above. Basically, it's impossible to access the Full transaction field from the BlockTransactionHashesInner object as the only exposed API will collapse a Full transaction into its transaction hash. I would classify this as a bug and not a feature request as it is quite misleading, but happy to be corrected, mostly nomenclature to be honest. It does seem erroneous to download full payloads only to be offered access to the transaction hashes, which are returned in default mode anyways.
Obviously, something might have escaped me from the API, which might deprecate this bug report. Happy to stand corrected!
The text was updated successfully, but these errors were encountered: