Skip to main content

Frequently-Asked Questions

Is Anyrand production-ready?​

Answer

No, Anyrand is in developer preview! While we await the release and deployment of drand v2 containing our BLS-on-BN254 scheme by the League of Entropy, Anyrand should be treated as a developer preview. We currently run all the nodes in the preview network and the current developer preview does not provide the same trust properties as the League of Entropy.

However, we welcome you to build on top of our preview contracts and build dapps that will be able to scale out to any EVM network once the League of Entropy deploys the new network. Please note that at that point, new contracts will be deployed to support the new network.

How can I get VRF on an unsupported network?​

Answer

Anyrand is completely open-source! If your network is not in our Supported Networks list, you are free to deploy our contracts which can be found on our GitHub. Alternatively, we'd be happy to provide deployment services and set your network up with our VRF keeper for a fee. Just give us a shout on Twitter @fairyrnd!

How long does it take for the randomness response to be delivered onchain?​

Answer

The response time depends on 2 things: (1) the drand beacon's period; and (2) the block time of the chain. When making an onchain request for randomness, you must specify the deadline, which determines which beacon round your randomness is derived from. The calculation for this is show below.

if (
    (deadline < genesisTimestamp) ||
    deadline < (block.timestamp + period)
) {
    revert InvalidDeadline(deadline);
}
uint256 delta = deadline - genesisTimestamp;
uint64 round = uint64((delta / period) + (delta % period));

I'm running into a problem! Where can I get support?​

Answer

If you are running into a technical issue with one of our deployed contracts, please feel free to reach out at k@fairy.dev.