guidiaz

> But the witnet-toolkit seems to use a different percentage, right @guidiaz ? Indeed. Witnet-toolkit solved successfully a 7-source pf, when 2 of them were emitting errors. That is, a...

https://github.com/witnet/WIPs/pull/99

On StringParseJsonArray, StringParseJsonMap and StringParseXmlMap, I would suggest to: - serialize big integers (>64 bits) to RadonFloats, so "absolute", "greaterThan", "lessThan", "modulo", "multiply", "negate" and "power" math operators could still...

> In that case the data request resolves with 0 commits, because it is not possible to serialize the result. Sheikah doesn't detect that error when using "try data request",...

Would it make sense to rephrase the log error message to "Couldn't encode value from < whatever > into < RadonType >: {}" ?

Some package deps were deleted and the rest upgraded to latest versions. Solidity contracts and test support now any compiler compliant w/ `pragma solidity ^0.8.0^`, which was the goal of...

Rebasing from 0.7.x branch...

Unfortunately, interception of `eth_getTransactionReceipt` on the gateway is returning null, although txs seem to get mined. This issue wont be feasible until a further assessment on whether reef's graphql schema...

Perhaps not when encoding errored results. For sure it would make life easier for WitnetParserLib, as it could assume (as it currently does) that parameterized errors would always be encoded...

In such case, +1 to force the node to encode error parameters as array of unsigned integers.