VRF: Difference between revisions
From Chainlink Community Wiki
No edit summary |
No edit summary |
||
Line 6: | Line 6: | ||
__TOC__ | __TOC__ | ||
<br> | <br> | ||
<h2>The problem</h2> | |||
<h2>The solution</h2> | |||
<h2>The details</h2> | |||
<h2>Overview</h2> | <h2>Overview</h2> | ||
<big>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. | <big>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 08:08, 19 March 2022
Quick take - VRF (Verifiable random function)
- Provably fair > Probably fair
- Provides a transparent source of randomness to the blockchain space.
The problem
The solution
The details
Overview
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.
Use cases
Release info
- VRF v2. Chainlink VRF v2 offers a new and improved version of the industry-standard on-chain RNG solution, making it easier to configure and scale randomness requests at a significantly reduced cost.
For v2 highlights check out the following blog. https://www.bnbchain.world/en/blog/chainlink-vrf-v2-is-live-on-bnbchain/
Relevant quotes
VRF resources