Private _basePrivate _factorPrivate _internalPrivate _maxPrivate _maxPrivate _posPrivate _tokenProtected eventsProtected storesApplies the state changes of a command through the state machine.
The hook Command.execute() is triggered by a transaction identified by the module name and the command name.
Additionally, an event will be emitted that provides the information on whether a command is executed successfully or failed.
In this hook, the state can be mutated and events can be emitted.
If the command verification succeeded, but the hook execution fails, the transaction that triggered this command is still valid, however the state changes applied in this hook are reverted.
The context available in every Command.execute() hook.
The hook Command.verify() is called to perform all necessary verifications.
If the verification of the command was successful, for the next step the command can be executed.
Similar to the verifyTransaction hook, Command.verify() will be called also in the TransactionPool, and its purpose is to guarantee that the verification defined within this hook is adhered to when the transactions are incorporated into a block.
In this hook, the state cannot be mutated and events cannot be emitted.
The context available in every Command.verify() hook.
Generated using TypeDoc
The
BaseCommandrepresents Lisk commands by providing a generic interface, from which each command extends from.