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
Hi Guys, can you please check this bug report web3p/rlp#27 and explain how geth is handling RLP encoded addresses with leading 00's removed? Trying to find source of this error when dealing with 0x00 prefixed wallets.
rlp: input string too short for common.Address, decoding into (types.DynamicFeeTx).To
Seems when im signing transaction using geth it'll leave 00's in the address. Eg. destination address is
0x00f0cb2ed033f72b4a1e14948860e197aa2ee988
Geth will keep it in the transacion. PHP/RLP will convert this address to 0xf0cb2ed033f72b4a1e14948860e197aa2ee988
Thanks
The text was updated successfully, but these errors were encountered:
Hi Guys, can you please check this bug report web3p/rlp#27 and explain how geth is handling RLP encoded addresses with leading 00's removed? Trying to find source of this error when dealing with 0x00 prefixed wallets.
rlp: input string too short for common.Address, decoding into (types.DynamicFeeTx).To
Seems when im signing transaction using geth it'll leave 00's in the address. Eg. destination address is
0x00f0cb2ed033f72b4a1e14948860e197aa2ee988
Geth will keep it in the transacion. PHP/RLP will convert this address to 0xf0cb2ed033f72b4a1e14948860e197aa2ee988
Thanks
The text was updated successfully, but these errors were encountered: