VRF: Difference between revisions
From Chainlink Community Wiki
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
</td></tr></table> | </td></tr></table> | ||
}} | }} | ||
Chainlink VRF generates both a random number and cryptographic proof, then delivers both on-chain where the cryptographic proof is verified prior to the acceptance of the random number by the consuming application.--[[User:Reggie|Reggie]] ([[User talk:Reggie|talk]]) 04:07, 22 June 2022 (UTC)<ref>https://joecontent.substack.com/p/joepegs-x-chainlink-vrf?sd=pf</ref> | |||
---- | |||
'''REVIEW''' | '''REVIEW''' | ||
Chainlink VRF works by combining block data that is still unknown when the request is made with the oracle node’s pre-committed private key to generate both a random number and a cryptographic proof. The smart contract will only accept the random number input if it has a valid cryptographic proof, and the cryptographic proof can only be generated if the VRF process is tamper-proof. This helps provide users with automated and publicly verifiable proof directly on-chain that each application using Chainlink VRF for randomness is provably fair and cannot be tampered with or predicted by the oracle, outside entities, or development teams. | Chainlink VRF works by combining block data that is still unknown when the request is made with the oracle node’s pre-committed private key to generate both a random number and a cryptographic proof. The smart contract will only accept the random number input if it has a valid cryptographic proof, and the cryptographic proof can only be generated if the VRF process is tamper-proof. This helps provide users with automated and publicly verifiable proof directly on-chain that each application using Chainlink VRF for randomness is provably fair and cannot be tampered with or predicted by the oracle, outside entities, or development teams. | ||
Revision as of 04:07, 22 June 2022
VRF Discussion Page
 |
Welcome to the talk page for discussing improvements to the VRF 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. |
Chainlink VRF generates both a random number and cryptographic proof, then delivers both on-chain where the cryptographic proof is verified prior to the acceptance of the random number by the consuming application.--Reggie (talk) 04:07, 22 June 2022 (UTC)[1]
REVIEW Chainlink VRF works by combining block data that is still unknown when the request is made with the oracle node’s pre-committed private key to generate both a random number and a cryptographic proof. The smart contract will only accept the random number input if it has a valid cryptographic proof, and the cryptographic proof can only be generated if the VRF process is tamper-proof. This helps provide users with automated and publicly verifiable proof directly on-chain that each application using Chainlink VRF for randomness is provably fair and cannot be tampered with or predicted by the oracle, outside entities, or development teams. REVIEW --Reggie (talk) 08:56, 20 June 2022 (UTC)