🤖 Final Pre-Mainnet Phase: INITIATED

The wait is almost over! The final rendition of our cutting-edge Randomizer VRF contract has just been launched on the Arbitrum Goerli network, paving the way for its mainnet debut.

But we didn’t stop there. We’ve invited multiple Arbitrum projects to run a Randomizer beacon. We're now doing a test run of the contract together with these projects, ensuring that all independent beacons are rock-solid and ready for prime time.

We’ve also made some major changes to the contract that will benefit developers building with Randomizer.

We advise all developers to take note of these changes, as they change some function and data types:

• The Request ID type has been changed to uint256 (from uint128). Make sure you store the ID as uint256 and that your callback function uses uint256 as the type for id: randomizerCallback(uint256 id, bytes32 value).

• The function name getFeeEstimate(uint256 callbackGasLimit) has been changed to estimateFee(uint256 callbackGasLimit).

• You can now get fee estimates in your front-end for a specific gas price, using the public view function estimateFee(uint256 callbackGasLimit, uint256 gasPrice). This is perfect for charging users for requests and forwarding the deposited amount to Randomizer.

As a smart contract developer, you’re aware of the importance of secure and reliable random number generation in web3. Don’t miss out on this opportunity to take your projects to the next level – try the Randomizer VRF contract on Arbitrum Goerli today and experience the power of Layer 2 randomness, and prepare yourself for mainnet!