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
I think there is bug in implementation of the eth_getRawTransactionByHash RPC call.
The reason I think this is because when this is called from rbuilder, TX cannot be parsed and errors with Failed to decode transaction, error: unexpected string
Steps to Reproduce
In order to replicate the behavior, please provide a detailed list of steps:
This is output of one of the transactions: b8b702f8b40183adcb6a84773594008517bfac7c008303291894a0b86991c6218b36c1d19d4a2e9eb0ce3606eb4880b844a9059cbb0000000000000000000000003c5fd3564bbaec0fc9383b5c13a6eb20926a800000000000000000000000000000000000000000000000000000000000015752a0c080a058a58bd8771dea6375c0ad0420c5321a2e15de402044f67874ddccfefa091ee6a06cea78cba171430e4a3d051381301516105ded783fb1a156a2944666ec3facbb
I went to this website, tried to decode TX from above and also got an error (like in rbuilder), that's why I think the issue is on our side
Error: Failed to parse raw transaction hex: Unable to cast object of type 'Nethereum.RLP.RLPItem' to type 'Nethereum.RLP.RLPCollection'.
Expected behaviour
The TX shoul've been parsed, this is that very same TX: link
Additional context
As far as I can tell, t his only happens with EIP-2718 Typed TXs, the Legacy ones are OK.
Here is output of Legacy TX:
Description
I think there is bug in implementation of the
eth_getRawTransactionByHash
RPC call.The reason I think this is because when this is called from rbuilder, TX cannot be parsed and errors with
Failed to decode transaction, error: unexpected string
Steps to Reproduce
In order to replicate the behavior, please provide a detailed list of steps:
b8b702f8b40183adcb6a84773594008517bfac7c008303291894a0b86991c6218b36c1d19d4a2e9eb0ce3606eb4880b844a9059cbb0000000000000000000000003c5fd3564bbaec0fc9383b5c13a6eb20926a800000000000000000000000000000000000000000000000000000000000015752a0c080a058a58bd8771dea6375c0ad0420c5321a2e15de402044f67874ddccfefa091ee6a06cea78cba171430e4a3d051381301516105ded783fb1a156a2944666ec3facbb
rbuilder
), that's why I think the issue is on our sideExpected behaviour
The TX shoul've been parsed, this is that very same TX: link
Additional context
As far as I can tell, t his only happens with EIP-2718 Typed TXs, the Legacy ones are OK.
Here is output of Legacy TX:
This doesn't error on
rbuilder
and it is also successfully parsed by this site.I have tried playing with different
RlpBehaviors
but that didn't help :)To parse the TX
rbuilder
usesalloy-rs
here is how they parse this .Logs
Please include any relevant logs that may help identify the issue.
The text was updated successfully, but these errors were encountered: