ChainLink contracts are designed in a modular manner, allowing for them to be configured or replaced by users as needed. It also feeds oracle provider metrics back into the reputation contract. The aggregating contract collects the oracle providers’ responses and calculates the final collective result of the ChainLink query. It then selects bids using the reputation contract and finalizes the oracle SLA. The order-matching smart contract takes a proposed service level agreement, logs the SLA parameters, and collects bids from oracle providers. The reputation contract keeps track of oracle-service-provider performance metrics. ChainLink’s on-chain interface to requesting contracts is itself an on-chain contract that ChainLink’s team denotes by CHAINLINK-SC.īehind CHAINLINK-SC, ChainLink has an on-chain component consisting of three main contracts: On-Chain ArchitectureĪs an oracle service, ChainLink nodes return replies to data requests or queries made by or on behalf of a user contract, which ChainLink’s team refers to as requesting contracts and denote by USER-SC. Figure 1: ChainLink workflow: 1) USER-SC makes an on-chain request 2) CHAINLINK-SC logs an event for the oracles 3) ChainLink core picks up the event and routes the assignment to an adapter 4) ChainLink adapter performs a request to an external API 5) ChainLink adapter processes the response and passes it back to the core 6) ChainLink core reports the data to CHAINLINK-SC 7) CHAINLINK-SC aggregates responses and passes them back as a single response to USER-SC.
0 Comments
Leave a Reply. |