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
The answer here is, that the contract was deployed, but empty!
Section 7.1 of the yellow paper it states that "while the initialisation code is executing, the newly created address exists but with no intrinsic body code. For a normal STOP code, or if the code returned is otherwise empty, then the state is left with a zombie account, and any remaining balance will be locked into the account forever"
The thing that was confusing me was that Parity could do queries on it, even though it returned 0x000 values (web3 didn't return anything but errors). So I thought the contract wasn't empty!
Maybe web3 can give a better error message like: contract is empty or function doesn't exist
I am querying a mapping via a web3 call like this:
If
orderValue
is > 15 then I get the following error:If
orderValue
is <= 15 (e.g. 10) then I get the following error:the mapping in the smart contract looks as follows:
The text was updated successfully, but these errors were encountered: