Roman Khimov 29ada4ca46 smartcontract: add JSON marshal/unmarshal for InteropType ... We actually have to do that in order to answer getapplicationlog requests for transactions that leave some interop items on the stack. It follows the same logic our binary serializer/deserializes does leaving the type and stripping the value (whatever that is).		2020-05-13 17:17:41 +03:00
..
context	random: make use or random package in tests	2020-03-27 10:27:46 +03:00
trigger	smartcontract: turn trigger types into Type	2020-03-02 17:25:27 +03:00
contract.go	*: move all packages from CityOfZion to nspcc-dev	2020-03-03 17:21:42 +03:00
contract_details.go	rpc, smartcontract: move contract metadata to smartcontract package	2020-04-29 13:50:05 +03:00
contract_test.go	*: move all packages from CityOfZion to nspcc-dev	2020-03-03 17:21:42 +03:00
deployment_price.go	cli: make gas parameter to deployment add gas to the base price	2020-03-11 20:34:36 +03:00
param_type.go	smartcontract: do not require pointer in MarshalYAML	2020-03-25 16:26:39 +03:00
param_type_test.go	smartcontract: always use int64 for integers	2020-03-18 11:58:17 +03:00
parameter.go	smartcontract: add JSON marshal/unmarshal for InteropType	2020-05-13 17:17:41 +03:00
parameter_test.go	smartcontract: add JSON marshal/unmarshal for InteropType	2020-05-13 17:17:41 +03:00