Introduction

If you are following "Modular Deployment" approach for node installation, you can skip this EI setup, since it is covered in the Modular deployment script itself.

External initiators can listen to event and run for any webhook job that it has been linked to, so it is highly critical unit for Node to bridge with External-initiator and it can listen to events from client contract that uses the oracle.

External initiators allow jobs in a node to be initiated depending on some external condition. The ability to create and add external initiators to Plugin nodes enables blockchain agnostic cross-chain compatibility.

External initiators are disabled on nodes by default. Set the FEATURE_EXTERNAL_INITIATORS=true configuration variable to enable this feature.

Initiator Bridges handle the authentication to and from the External Initiator and where to send the messages. When creating a Bridge two parameters are required:

Only the webhook job type can be initiated using an External Initiator.

The external initiator must be created before the webhook job, and must be referenced by name (whitelisted) in order for that external initiator to be allowed to trigger the given webhook job.

When the External Initiator is created it generates two pairs of credentials: Outgoing and Incoming. The Outgoing Access Key and Secret are used to authenticate messages sent from the Core to the External Initiator. The Incoming Access Key and Secret are used to authenticate messages sent from the External Initiator to the Core.

Then, once you've created the name, bridge, and have the correct access keys for the URL, you can proceed to use the external initiator as if it's a regular initiator in future job specs.