Skip to content

0x0000000000000000000000000000000000000000 is the new winner! #1518

Answered by cromewar
praxis-dev asked this question in Q&A
Discussion options

You must be logged in to vote

Hello @vaporm
This is a common error, but you don't have to worry about it, the reason is simple
As you are using VRF from chainlink, the response of the node providing the random number will take some time to gets processed, because remember fulfillRandomness is an asynchronous function.
So, you can add a lot longer time.sleep on python to get the correct winner, or you can deploy to rinkeby and after some time you can check that the winner is actually chosen, but as I said It'll take time to process.

Cheers, Vasiliy.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@praxis-dev
Comment options

Answer selected by praxis-dev
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants