...
- Limit max number of WASM instructions that can be executed per Trigger
- Take network fees for Trigger execution:
- In general case fees can be taken from the Trigger's technical account balance.
- Fees can be taken for each WASM instruction that is executed - the concept is known as `fuel` in WASM runtimes.
- If technical account does not have enough funds - changes made by Trigger are reverted.
- For Triggers called by ExecuteTrigger(_) we might consider the same approach that is used in Ethereum - take funds from the account that called it.
There is also a question of how to limit their `condition` execution if condition is also in WASM. Possibly fees will be also taken just for condition checks, but in lesser amount than for the actual execution.
Misc
It might be good to provide Triggers with a way to `Unregister` themselves. Especially for public blockchain use cases.
...