invokecontractverify Method
Invokes the contract method Verify
. Unlike the method invokefunction
which executes the contract by the Application trigger, invokecontractverify
executes the contract by the Verification trigger and can pass parameters as params
and signers
. Specific parameter type and number depend on the smart contract to invoke.
[!Note]
This method is used to test your VM script as if they ran on the blockchain at that point in time. This RPC call does not affect the blockchain in any way.
You must install the plugin RpcServer before you can invoke the method.
Parameter Description
scripthash: Smart contract scripthash.
params: The parameters to be passed to the smart contract operation.
signers: Optional. List of contract signature accounts.
account: signature account
scopes: signature's valid scopes, allowed values: FeeOnly, CalledByEntry, CustomContracts, CustomGroups, Global
allowedcontracts: contracts of the signature can take effect, if scopes is CustomContracts
allowedgroups: pubkeys of the signature can take effect, if scopes is CustomGroups
[!Note]
You need to use the proper byte order of the address passed according to its data type. If the data type is Hash160, use the big endian script hash; if the data type is ByteArray, use the little endian scripthash.
For example:
Example
Request body:
Response body:
Response description:
script: the invocation script of the contract. You can convert it to OpCode at Neo 3.0 data converter.
state:
HALT
means the vm executed successfully, andFAULT
means the vm exited due to an exception.gasconsumed: the system fee consumed for invocation.
stack: the contract execution result. If the value is String or ByteArray, it is encoded by Base64.