Talk:Market & data feeds: Difference between revisions
From Chainlink Community Wiki
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
}} | }} | ||
---- | ---- | ||
External Adapter: This component allows for additional functionality outside of what is supported by the default Chainlink adapters. Data validation and mapping are classic scenarios for external adapters. Functionally, external adapters can be seen as serverless routines that complement the core functionality of an existing Chainlink adapter. <ref>https://dyor-crypto.fandom.com/wiki/Chainlink_(LINK)#Reviewed_Node_Operators</ref>--[[User:Reggie|Reggie]] ([[User talk:Reggie|talk]]) 08:52, 27 June 2022 (UTC) | "Just like how smart contracts are secure because they're ran on multiple machines (blockchain nodes), you can secure the inputs to your smart contracts by having that input retrieved by multiple Chainlink nodes. | ||
So if you're a requester, and you want data from a particular API DPA, you define how many Chainlink nodes you want to retrieve that data. To further decentralize your inputs, and if there are additional data providers with the same topic of data, you could have additional Chainlink nodes retrieve from another API DPB to assist with validation." <ref name="FANDOM" />--[[User:Reggie|Reggie]] ([[User talk:Reggie|talk]]) 08:57, 27 June 2022 (UTC) | |||
---- | |||
External Adapter: This component allows for additional functionality outside of what is supported by the default Chainlink adapters. Data validation and mapping are classic scenarios for external adapters. Functionally, external adapters can be seen as serverless routines that complement the core functionality of an existing Chainlink adapter. <ref name="FANDOM">https://dyor-crypto.fandom.com/wiki/Chainlink_(LINK)#Reviewed_Node_Operators</ref>--[[User:Reggie|Reggie]] ([[User talk:Reggie|talk]]) 08:52, 27 June 2022 (UTC) | |||
---- | ---- | ||
We might want to dicuss Proxy addresses for Aggregators. | We might want to dicuss Proxy addresses for Aggregators. | ||
Revision as of 08:57, 27 June 2022
Market & data feeds Discussion Page
 |
Welcome to the talk page for discussing improvements to the Market & data feeds article. Talk pages (also known as discussion pages) are Wiki administration pages where editors/contributors discuss improvements that can be made to an article. NOTE: Discussion pages are not a forum for general discussion of the article's subject. When you post a message on a talk page, you should always sign and date your comment so that other editors can follow the thread of the conversation. To do this, either type four tildes (~) at the end of your comment or just click the signature button on the row of buttons above the edit box. |
"Just like how smart contracts are secure because they're ran on multiple machines (blockchain nodes), you can secure the inputs to your smart contracts by having that input retrieved by multiple Chainlink nodes. So if you're a requester, and you want data from a particular API DPA, you define how many Chainlink nodes you want to retrieve that data. To further decentralize your inputs, and if there are additional data providers with the same topic of data, you could have additional Chainlink nodes retrieve from another API DPB to assist with validation." [1]--Reggie (talk) 08:57, 27 June 2022 (UTC)
External Adapter: This component allows for additional functionality outside of what is supported by the default Chainlink adapters. Data validation and mapping are classic scenarios for external adapters. Functionally, external adapters can be seen as serverless routines that complement the core functionality of an existing Chainlink adapter. [1]--Reggie (talk) 08:52, 27 June 2022 (UTC)
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."
Source: https://docs.chain.link/docs/using-chainlink-reference-contracts/#updates-to-proxy-and-aggregator-contracts --Reggie (talk) 08:14, 20 June 2022 (UTC)
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/
--Reggie (talk) 08:14, 20 June 2022 (UTC)