Flux monitor: Difference between revisions
From Chainlink Community Wiki
No edit summary |
No edit summary |
||
| Line 36: | Line 36: | ||
<h2>Price Feeds: Limitations of FluxMonitor</h2> | <h2>Price Feeds: Limitations of FluxMonitor</h2> | ||
<h3>Issues with Scaling</h3> | <h3>Issues with Scaling</h3> | ||
<p>While FluxMonitor | <p>While FluxMonitor provided a <i>major</i> increase in efficiency over the previous generation Runlog contracts, it was not efficient enough to accommodate for the increasing number of transactions on the Ethereum network.</p> | ||
<p>With the rapid adoption of DeFi in the summer of 2021, the blocks were filling up rapidly and the efficiency of FluxMonitor was not enough to keep up.</p> | <p>With the rapid adoption of DeFi in the summer of 2021, the blocks were filling up rapidly and the efficiency of FluxMonitor was not enough to keep up.</p> | ||
<p>Each new round for each Price Feed still required on-chain transactions from each Node Operator. This meant that at times of high market volatility, each Price Feed was adding 9+ transactions to the mempool for each Price Feed.</p> | <p>Each new round, for each Price Feed still required on-chain transactions from each Node Operator. This meant that at times of high market volatility, each Price Feed was adding 9+ transactions to the mempool for each Price Feed.</p> | ||
<p>As new DeFi protocols | <p>As new DeFi protocols launched with a desire to support new tokens, more price feeds were needed. FluxMonitor was not enough to meet the demand that Chainlink was experiencing.</p> | ||
<p>If only there were a way to reach consensus off-chain, without risk to the security of the Price | <p>If only there were a way to reach consensus off-chain, without risk to the security of the Price Feeds. Offchain reporting.</p> | ||
{{:flux_monitor_resources}} | {{:flux_monitor_resources}} | ||
<references /> | <references /> | ||
Revision as of 05:57, 11 April 2022
Price Feeds: FluxMonitor (FM)
The deployment and migration from Runlog to FluxMonitor was a major milestone.
The migration removed the high risks from the Price Feeds' dependence on the Deviator / Utility Node, while also significantly reducing operation costs.
Migration to FluxMonitor: ETH / USD
06 Aug 20: The ETH / USD FluxAggregator.sol contract was deployed at address
- AccessControlledAggregator: 0x00c7A37B03690fb9f41b5C5AF8131735C7275446
- EACAggregatorProxy: 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419
and at transaction hash 0x1697d1bd5ab87a246571186262cf5111cb469b60b9798d70a1fe307d3252c76c
06 Apr 21: The ETH / USD price feed was formally migrated from Runlog to FluxMonitor contracts.
As Chainlink is extremely risk-averse, they did not want to migrate all of their Price Feed contracts to the new FluxMonitor contracts without a backup plan.
If anything were to happen, the proxy contracts were each pointed at their respective FluxMonitor aggregator contracts. If anything were to happen, the Chainlink team could fall back to the Runlog contracts in a matter of moments.
FluxMonitor Operation
The operation of FluxMonitor feeds and all related contracts is rather complex, and outside the scope (Price Feed History) of this page. Please refer to Chainlink Contract Details for more information.
The important changes from migrating to FM contracts, were:
- The Deviator / Utility Node was no longer necessary.
- Monitoring data sources for deviation was pushed out to each Node Operator.
- If a single Node Operator detected deviation beyond the set threshold, a new round would be fired.
- The Deviator / Utility Node was no longer a single point of failure.
- The Deviator / Utility Node no longer sent transactions to each Node Opertor for every price update
- This resulted in significantly reducing the cost of operating multiple Price Feeds
- Monitoring data sources for deviation was pushed out to each Node Operator.
Price Feeds: Limitations of FluxMonitor
Issues with Scaling
While FluxMonitor provided a major increase in efficiency over the previous generation Runlog contracts, it was not efficient enough to accommodate for the increasing number of transactions on the Ethereum network.
With the rapid adoption of DeFi in the summer of 2021, the blocks were filling up rapidly and the efficiency of FluxMonitor was not enough to keep up.
Each new round, for each Price Feed still required on-chain transactions from each Node Operator. This meant that at times of high market volatility, each Price Feed was adding 9+ transactions to the mempool for each Price Feed.
As new DeFi protocols launched with a desire to support new tokens, more price feeds were needed. FluxMonitor was not enough to meet the demand that Chainlink was experiencing.
If only there were a way to reach consensus off-chain, without risk to the security of the Price Feeds. Offchain reporting.
Flux Monitor resources
Timeline
| Date | Media | Author | Title |
|---|---|---|---|
| XXXX | XXXX | XXXX | [] |
| XXXX | XXXX | XXXX | [] |
Educational
| Date | Media | Author | Title |
|---|---|---|---|
| N/A | Official Docs | Chainlink | Flux Monitor Jobs - Official Chainlink Documentation |
| XXXX | XXXX | XXXX | [] |
| XXXX | XXXX | XXXX | [] |
| XXXX | XXXX | XXXX | [] |