Closed mikeshultz closed 6 years ago
Simplest test case so far, seems to lay the blame with web3.js
, or how abi-decoder
is calling SolidityCoder
.
const SolidityCoder = require("./lib/solidity/coder.js");
SolidityCoder.decodeParams([ 'string' ], '000000000000000000000000f2a3047bc98fb43dd782948e88c785475609dce4000000000000000000000000b89c7bf13e8c852d29b3ce7bd1be0e6c47d81b8c000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000056c756e7972000000000000000000000000000000000000000000000000000000')
I'm not super familiar with dynamic type parsing, so I don't yet know where exactly the blame lies.
This does not look to be a parser issue, but perhaps a solidity bug, problem with the contract, or the node running the test network. The event is not what I'd expect. There's only 2 elements in topics
, when there's 3 indexed event params, which I believe should mean topics.length === 4
.
I'll look into the problem from that angle and assume it's not an abi-decoder issue for now.
I'm getting the same issue when decoding a method call. any further insights on this?
Sorry I haven't maintained this for a while, I will check the issues this week and perform some updates
Having an issue decoding an event log with
abi-decoder@1.0.9
. Perhaps the problem is with an event string argument, but the error message doesn't point out exactly what it's having an issue with. Here's a simple test case:And the resulting error:
Let me know if I can provide any more info.