Currently, the random value generated is provided by Quantum Blockchains: https://docs.api3.org/reference/qrng/providers.html#quantum-blockchains-random-numbers

There were two occurrences so far where there were delays for results from this provider.

API3 has recommended to try using the Quintessence provider instead: https://docs.api3.org/reference/qrng/providers.html#quintessence-quantum-random-numbers

This proposal uses the INT VRF Factory to deploy an INT Quintessence VRF provider.

Note that this only deploys the provider, a separate proposal would need to be created to configure the RewardDistributor (https://basescan.org/address/0x76BfDDf9D9aD158cc47d4abba5af7f16A922f865) to use the new provider after it has been deployed.

Parameters in this proposal used for deployment:

• salt: 0x0c5fa5513e87c393092aabcfb02bee4f499a38e1f5807436b901af19e85302ee

This is the hash of "API3-Quintessence" on https://emn178.github.io/online-tools/keccak_256.html

• vrfConsumer: 0x76BfDDf9D9aD158cc47d4abba5af7f16A922f865

This is the RewardDistributor, the current INT Api3VrfProvider (https://basescan.org/address/0x2e2e91b4dE929ef1D32425ad6A2b0c620eAb591E#readContract) has the same value for vrfConsumer

• airnodeRrp: 0xa0AD79D995DdeeB18a14eAef56A549A04e3Aa1Bd

This is the API3 airnodeRrp contract address on Base, https://docs.api3.org/reference/airnode/latest/#airnoderrpv0, the current INT Api3VrfProvider has the same value for airnodeRrp

• airnode: 0x224e030f03Cd3440D88BD78C9BF5Ed36458A1A25

This is the airnode for Quintessence https://docs.api3.org/reference/qrng/providers.html#quintessence-quantum-random-numbers

• endpointIdUint256: 0xffd1bbe880e7b2c662f6c8511b15ff22d12a4a35d5c8c17202893a5f10e25284

This is the endpointIdUint256 for Quintessence https://docs.api3.org/reference/qrng/providers.html#quintessence-quantum-random-numbers