I used v2 VRF today for the first time. This opens up many possibilities for gaming, but after running tests I decided to stick with v1. With an NFT project that has a limited mint, having the LINK token directly in the contract is a perfect regulator for mints, but also so buyers can audit supply easier.
There was one odd quirk of v2, and that's how fulfillRandomness (the special ad hoc function the VRF coordinator calls) is now fulfillRandomWords. Weird...especially when you are taking the VRF number and making words out of it. As a programmer it is simple to look at the variable type to see it's a uint256, but this nomenclature is too confusing for those with only a basic understanding of how to protect themselves when auditing a contract. I believe the documentation should have a few more comments added to explain this quirk.
It is great to learn new things just by trying them out. Countless people I know have made life changing money just playing around on projects (and getting airdrops or learning why a project will break out), but a few of them also saved themselves from getting hurt by seeing suboptimal things. Today I learned that VRF is going to be absolutely massive, potentially the backbone that drives other more complicated Chainlink products to adoption.
I was already a fan, but FUD and the market waning in excitement can wear you down. It's great to discover something that just allows you to shrug at all the negativity.
Log in or sign up for Devpost to join the conversation.