Talk:Market & data feeds
From Chainlink Community Wiki
This Article Needs Your Help!
 |
Anyone— INCLUDING YOU—can become a contributor to the Chainlink Community Wiki. Our contributors perform a wide variety of tasks, from fixing typos to perfecting content, but all are united in a desire to make Chainlink knowledge available to everyone.
Interested?
But first, make sure to check out each article's subject-specific discussion page. Discussion pages are used for communicating with other contributors in order to help better build the wiki article. Talk pages can be accessed by clicking the "discussion" tab from within the actions menu. |
We might want to dicuss Proxy addresses for Aggregators.
"Updates to proxy and aggregator contracts Aggregator contracts must be updated from time to time to add additional capabilities to data feeds. These updates include changes to the aggregator configuration or a complete replacement of the aggregator that the proxy uses. If you consume data feeds through the proxy, your applications can continue to operate during these changes.
Proxy and aggregator contracts all have an owner address that has permission to change variables and functions. For example, if you read the BTC/USD proxy contract in Etherscan, you can see the owner address. This address is a multi-signature safe (multisig) that you can also inspect.
If you view the multisig contract in Etherscan using the Read as Proxy feature, you can see the full details of the multisig including the list of addresses that can sign and the number of signers required for the multisig to approve actions on any contracts that it owns."
Some details to consider add.
- Each data feed is updated by a decentralized oracle network.
- Each oracle operator is rewarded for publishing data.
- The number of oracles contributing to each feed varies
Source: https://docs.chain.link/docs/architecture-decentralized-model/