Data Flows in IntelliX

In this section, we will delve into the detailed data flow within the IntelliX network and illustrate how this flow is orchestrated through configuration.

The above diagram illustrates the data flow and architecture of the IntelliX system for handling and validating data feeds. Here's a detailed breakdown of each component, mapped to the price feed configuration sample:

Diagram Breakdown and Mapping to Price Feed Configuration

1. Fetchers and Processors:

   • In the top section, there are multiple fetcher/processor pairs grouped together. Each fetcher is responsible for retrieving data from a specific source, while the processor handles the extraction and initial processing.

   • Mapping:

     • The fetchers correspond to the data sources in the price feed configuration:

       • Binance: https://api.binance.com/api/v3/ticker/price?symbol=BTCUSDT

       • Coinbase: https://api.exchange.coinbase.com/products/BTC-USD/ticker

       • Kraken: https://api.kraken.com/0/public/Ticker?pair=XBTUSD

       • Bitfinex: https://api-pub.bitfinex.com/v2/ticker/tBTCUSD

     • Processors use JSON paths to extract specific values from each source:

       • Binance and Coinbase: $.price

       • Kraken: $.result.XXBTZUSD.c[0]

       • Bitfinex: $[6]

   • These fetcher/processor pairs write the processed data to the IntelliX Core Chain as data feed transactions.

2. IntelliX Core Chain (Data Feed Transactions):

   • The IntelliX Core Chain serves as a central repository where data from all fetchers is stored. The processed data, once gathered from each source, is written here as data feed transactions.

3. Validators and Validation Functions:

   • In the next layer, multiple validators pick up the data feed transactions from the IntelliX Core Chain. Each validator applies specific validation functions to ensure data quality and consistency.

   • Mapping:

     • The validators correspond to the price_avg_median validation function in the configuration, which applies an average-median approach to reconcile data from multiple sources.

     • Each validator independently validates the data from the IntelliX Core Chain, and the results are then written back to the chain as aggregated data feed transactions.

4. IntelliX Core Chain (Aggregated Data Feed Transactions):

   • After validation, the aggregated/validated data is stored back on the IntelliX Core Chain as aggregated data feed transactions. This updated data represents a consensus or reconciled version of the input data, ensuring that it meets validation standards before publication.

5. Publishers and Publication Functions:

   • The bottom layer represents multiple publishers, each with publication functions. These publishers pick up the validated and aggregated data from the IntelliX Core Chain and publish it to various target chains.

   • Mapping:

     • The publishers correspond to the different blockchain targets in the configuration:

       • Bitlayer: 0x1234567890abcdef1234567890abcdef12345678

       • Ethereum (BSC): 0xabcdefabcdefabcdefabcdefabcdefabcdefabcdef

       • Merlin: 0xabcdef123456abcdef123456abcdef123456abcdef

     • Each publisher reads the validated data and publishes it to its specified smart contract address on the target chain, ensuring that the data is accessible on different blockchain networks.