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
Since migrating my go-etherum from v1.10.22 to v1.13.15 my smart contracts started firing
abi: attempting to unmarshal an empty string while arguments are expected.
Which i didn't expect to be.
I have been testing multiple versions of go-etherum. I was succesfully able to migrate on v1.11.6 but moving forward with v1.13.0 started to introduce issues.
Steps to reproduce the behaviour
I have tried to regenerate go smartcontract with abi and bin but still running with same issue.
contact is build on solidity ^0.5.0;
The text was updated successfully, but these errors were encountered:
System information
Geth version:
v1.13.15
CL client & version: e.g. lighthouse/nimbus/[email protected]
OS & Version: OSX 14.4.1 (23E224)
Commit hash : (if
develop
)Expected behaviour
Since migrating my go-etherum from v1.10.22 to v1.13.15 my smart contracts started firing
abi: attempting to unmarshal an empty string while arguments are expected.
Which i didn't expect to be.
I have been testing multiple versions of go-etherum. I was succesfully able to migrate on v1.11.6 but moving forward with v1.13.0 started to introduce issues.
Steps to reproduce the behaviour
I have tried to regenerate go smartcontract with abi and bin but still running with same issue.
contact is build on solidity ^0.5.0;
The text was updated successfully, but these errors were encountered: