Documentation ¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Type ¶
type Type byte
Type represents trigger type used in C# reference node: https://github.com/neo-project/neo/blob/c64748ecbac3baeb8045b16af0d518398a6ced24/neo/SmartContract/TriggerType.cs#L3
const ( // The verification trigger indicates that the contract is being invoked as a verification function. // The verification function can accept multiple parameters, and should return a boolean value that indicates the validity of the transaction or block. // The entry point of the contract will be invoked if the contract is triggered by Verification: // main(...); // The entry point of the contract must be able to handle this type of invocation. Verification Type = 0x00 // The verificationR trigger indicates that the contract is being invoked as a verification function because it is specified as a target of an output of the transaction. // The verification function accepts no parameter, and should return a boolean value that indicates the validity of the transaction. // The entry point of the contract will be invoked if the contract is triggered by VerificationR: // main("receiving", new object[0]); // The receiving function should have the following signature: // public bool receiving() // The receiving function will be invoked automatically when a contract is receiving assets from a transfer. VerificationR Type = 0x01 // The application trigger indicates that the contract is being invoked as an application function. // The application function can accept multiple parameters, change the states of the blockchain, and return any type of value. // The contract can have any form of entry point, but we recommend that all contracts should have the following entry point: // public byte[] main(string operation, params object[] args) // The functions can be invoked by creating an InvocationTransaction. Application Type = 0x10 // The ApplicationR trigger indicates that the default function received of the contract is being invoked because it is specified as a target of an output of the transaction. // The received function accepts no parameter, changes the states of the blockchain, and returns any type of value. // The entry point of the contract will be invoked if the contract is triggered by ApplicationR: // main("received", new object[0]); // The received function should have the following signature: // public byte[] received() // The received function will be invoked automatically when a contract is receiving assets from a transfer. ApplicationR Type = 0x11 )
Viable list of supported trigger type constants.
Click to show internal directories.
Click to hide internal directories.