This article was first published on Chainlink
We are excited to announce that Chainlink VRF (Verifiable Random Function) is now live on the Ethereum mainnet, generating a highly secure and provably fair source of on-chain randomness for blockchain applications. Several projects are already using Chainlink VRF live in production to secure critical smart contract functions: PoolTogether for randomly selecting prize pool winners in its v3 release, Centaur and UniLend for fair randomized selection of public sale participants, and numerous other projects already committed to launching in the near future like Aavegotchi, Polyient, Get Protocol, and much more.
This launch of Chainlink VRF showcases the power of secure and reliable oracles as not only a means of providing accurate price feeds for the DeFi ecosystem, but generating and delivering provably fair randomness on-chain for gaming, Non-Fungible Tokens (NFTs), and various other applications requiring unpredictability. It’s yet another example of the Chainlink Network continually expanding the types of data and computation users can receive through its oracle networks, greatly increasing the number and variety of applications that smart contract developers can build.
If you are a new or existing smart contract developer and want to build with Chainlink VRF, check out our documentation to deploy a testnet contract in Remix or integrate Chainlink VRF into your dApp on mainnet. If you want to discuss the integration in greater depth, reach out to us and schedule a call.
If you want a more in-depth look into the academic research and formal proofs backing the development, refer to our Chainlink VRF blog post about on-chain verifiable randomness.
The Importance of Verifiable Randomness
Random Number Generation (RNG) is critical to the development of many software applications because it serves as a mechanism for creating unpredictability. Not only does unpredictability protect against malicious entities trying to reverse-engineer a system, but it can ...
To keep reading, please go to the original article at: