The Oracle problem: Difference between revisions
From Chainlink Community Wiki
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
---- | ---- | ||
Blockchain nodes are designed to perform standardized and uniform operations to generate consensus on a set of transactions (solving the double-spend problem). However, they are not suited to answer subjective questions about probabilistic real-world data, as blockchain nodes do not always have access to the same information, making generating consensus on even the most basic data requests challenging and source quality enforcement impossible. | Blockchain nodes are designed to perform standardized and uniform operations to generate consensus on a set of transactions (solving the double-spend problem). However, they are not suited to answer subjective questions about probabilistic real-world data, as blockchain nodes do not always have access to the same information, making generating consensus on even the most basic data requests challenging and source quality enforcement impossible. | ||
<ref | <ref name"FAQ" /> [[User:Reggie|Reggie]] ([[User talk:Reggie|talk]]) 04:40, 22 June 2022 (UTC) | ||
---- | ---- | ||
Revision as of 04:44, 22 June 2022
The Oracle Problem Discussion Page
 |
Welcome to the talk page for discussing improvements to the Oracle Problem 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. |
n order to create a bridge between the blockchain (on-chain) and the outside world (off-chain), an additional and separate piece of infrastructure known as an “oracle” is required.[1]
Blockchain nodes are designed to perform standardized and uniform operations to generate consensus on a set of transactions (solving the double-spend problem). However, they are not suited to answer subjective questions about probabilistic real-world data, as blockchain nodes do not always have access to the same information, making generating consensus on even the most basic data requests challenging and source quality enforcement impossible.
Cite error: The opening <ref> tag is malformed or has a bad name Reggie (talk) 04:40, 22 June 2022 (UTC)