Guardians

Veax has a protocol's stop procedure.

If Veax starts operating poorly—for example, malicious attempts, performance-related problems, or bugs—Veax has a plan that reduces the risks of being hacked and the negative impact of such issues, including the possible loss of investors' assets.

To resolve maintenance issues and process any other administration tasks with the smart contract, Veax uses a guards approach.

There's always at least one guard—a smart contract owner. The smart contract has API to add and remove additional guards. Guards as well as an owner account are additional accounts allowed to suspend and resume payable API. The owner account is the only account that may add and remove additional guards.

The main idea of suspending payable API is to prevent critical damage during maintenance or to suspend a working smart contract when a critical issue is detected, and the bug fix is in progress.

For more information about the guards and suspend and resume API, see Guards API.