ixje
ixje
> What do you think about something like this: It would be nice if the JSON tests actually remains usable for other implementations as well. The above (specifically): > Assert:CurrentContext.EvaluationStack[0].Count...
At first glance looks good. I can't say if the function names might need to be renamed later on though to be inline with the rest of the exposed lightweight...
Some things I believe we should do at minimum - support use of custom neoscan servers (now it's all forced to `api.neoscan.io`). This should be configurable such that people can...
I think that all we can address now is there 👍. I'm not so sure about `Address` as name, but I would have to use the script in a couple...
great! Looking forward to your PR
Note that for #1891 (which I still think is an important issue) incorrect input types can arguably be blamed on the contract consumer as he has control over it. The...
Is this described somewhere? Because if not, we better do so as the far majority of ABI consumers will not know this mapping.
> IMO ping's payload should tell everyone our current height and the other side can assume that the node has a state corresponding to that height. 👍
@shargon why do you want to remove the Pong message? It was added for a good reason; to be able to get an up to date chain state of the...