How it works

HAL 101 lexicon

During the setup phase you will define:

  • triggers → The sets of rules defining what you want to listen on Ethereum and which conditions apply to determine if the trigger fires

  • actions → What to do when a trigger fires

You can connect many actions to a single trigger

In turn, HAL will create:

  • matches → Every time a trigger fires, a match is created. A match is the description of when and why (i.e. the data context) a trigger has been triggered

  • outcomes → Every time a match is created, HAL executes the actions connected to that trigger. The result of the execution of that action is called outcome. For example, if the action is calling a webhook, the outcome contains the response status code and body of the HTTP response.

Checkpoint

Given 1 trigger (with N actions) firing M times, there will be:

  • 1 trigger

  • N actions

  • M matches

  • M*N outcomes