External Developers & Transmitter Agents

External Developers are data vendors that leverage a cross-chain transfer framework to facilitate the collection and submission of data by Transmitters.

Learn how to be an External Developer here.

Transmitters play a crucial role as the intermediary between data sources and the Entangle blockchain. Their primary objective is to establish a robust data pipeline on the Entangle blockchain. Transmitter Agents can operate their own Transmitter nodes, register to work with the protocol, stake NGL tokens, and find a delegator.

What sets us apart from other similar projects is our commitment to providing external developers with the autonomy to build their pathways for processing and transmitting cross-chain messages.

The External Developer Hub contract plays a crucial role in overseeing and configuring the operations of these external developers. It is designed to streamline the process of adding new external developers by requiring them to undergo a KYC (Know Your Customer) procedure.

Once verified, these External Developers are granted the autonomy to configure and manage their protocol operations effectively, ensuring a secure and regulated environment for data handling within the Entangle ecosystem.

This is how the process works:

1. External Developers create and initialize their protocols, customizing the system to their specific needs.

2. External Developers must lock up NGL tokens to cover Transmitter rewards and the protocol fees.

3. The External Developers specify the amount of stake that the Transmitter or delegator must lock up within their system. They also specify the rewards for various operations.

4. Set the maximum number of Transmitters that can simultaneously work with the protocol.

5. External Developers deploy their Executors by specifying their addresses and networks. These Executors are responsible for carrying out the operations dictated by the protocol.

6. Establish a consensus target, which can help guide the protocol's operation towards achieving a desired level of agreement among participants.

All actions related to the protocol's configuration are sent to the to the External Developer Hub contract and then disseminated to other networks via the GOV protocol. This ensures a centralized point of management that can efficiently propagate updates and changes across the entire system.