1

I'm writing an article and I'm using Chainlink VRF in one part. Theoretically, this is a two-transaction process, as it is impossible to storethe cryptographic proof on the blockchain and read the result at the same time. The estimated time to get random numbers is 30 seconds, right? For the two transactions that need to be executed. The problem is that it is taking more to return the random number. How could I justify this time?

If it were 40 seconds, maybe I could overlook it. But I just did some tests and the time was 59 seconds, so I have to justify this time. Is it only due to the Ethereum blockchain (Kovan in this case) congestion?

Improve this question
3
  • It's the first time I use VRF but it's already been almost 4 hours and my requests are still showing as pending in the Subscription Manager. I'm using Rinkeby.
    – Antao Almada
    Mar 22, 2022 at 21:25
  • @AntaoAlmada Check if all the components are OK. Does the contract have enough LINK? I´m doing some tests at this moment in Kovan and everything is perfect. It takes around 45-50 seconds.
    – Joncarre
    Mar 24, 2022 at 11:29
  • If you want a fast blockchain, do not use EVM chains. Use Near, Solana. EVM just cannot do it any faster.
    – Mikko Ohtamaa
    Mar 18 at 19:29

1 Answer 1

Reset to default
1

Your assessment is correct. The delay is due to needing multiple transactions stored on-chain. The Kovan testnet generally takes around ~1 min to return a random number.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.