...
This is how triggers are described in the whitepaper:
Triggers can be either based on time or on a confirmed transaction (event)are Iroha Special Instructions that may be invoked based on condition. This is very powerful feature and enables Turing complete computation for Iroha's smart contractsSpecial Instructions.
- Trigger at timestamp (every 5 minutes or after one hour)
- Trigger at blockchain (new block, reach of some height, etc.)
- Trigger at condition (new account, transfer of an asset, etc.)
Representation
- Trigger at condition
Representation
As you can see in the quote from the whitepaper the Triggers were initially planned to be represented as ISI. But with With the recent decision to introduce WASM. It , it is suggested to use it for Triggers. So that Triggers can be written in Rust* and compiled into WASM.
This way Triggers will benefit from a high level language features of an already established language and will be able to solve all the listed use cases with ease.
As discussed previously, solving listed use cases with ISI was impossible or very difficult and needed significant work on the language design side.
...