Randomness Beacon Consumer

WHAT IT DOES

Randomness Beacon Consumer provides direct, non-custodial access to randomness beacon protocols on EVM-compatible blockchains. It enables randomness requests, consumption, and reading of beacon state for applications requiring verifiable on-chain randomness. The tool reads beacon contract state, latest randomness, randomness history, request state, consumer state, block timestamp, chain ID, and gas price. It writes requestRandomness, consumeRandomness, and readRandomness. All operations are signed and broadcast through your connected wallet — giving you full control over your randomness consumption.

HOW TO USE

Connect your EVM-compatible wallet (MetaMask, WalletConnect, or similar) using the wallet bridge. Select the network that matches the randomness beacon deployment you wish to use (Ethereum Mainnet, Polygon, Arbitrum, Optimism, Avalanche, Base, or others). Paste the beacon contract address — the tool does not hardcode any address, giving you full control to use official beacon deployments or fork contracts. Choose your action from the dropdown: request randomness, consume randomness, or read randomness. For requestRandomness, enter the consumer contract address and optional callback gas limit. For consumeRandomness, enter the request ID and randomness index. For readRandomness, enter the request ID. Click Review to verify all parameters before signing. The tool shows a clear summary of the transaction, then signs and broadcasts through your wallet with progress tracking.

HOW IT WORKS UNDER THE HOOD

The tool uses a dynamic gas estimation strategy that adapts to network conditions. Before each transaction, it calls estimateGas on the chosen method with the exact parameters, then adds a 20% buffer to avoid out-of-gas failures. For requestRandomness, the tool calls the beacon contract with the consumer address and callback gas limit — this initiates the randomness request. For consumeRandomness, it provides the request ID and randomness index to retrieve the randomness value. For readRandomness, it calls the view function to fetch the randomness for a given request ID. The tool constructs the appropriate transaction data for each beacon action. After broadcasting, the tool waits for the transaction receipt using ethers.js wait() with confirmation tracking. It uses receipt.effectiveGasPrice for accurate cost reporting, not tx.gasPrice — critical for post-EIP-1559 networks.

WHAT IT CANNOT SEE

The tool cannot verify that the beacon randomness is truly unpredictable; it relies on the beacon's source of randomness. It cannot guarantee that the randomness will be available when requested; availability depends on the beacon's update schedule. It cannot detect if the beacon has been compromised; the tool only interacts with the protocol as configured. It cannot predict when the next randomness update will occur; updates depend on the beacon's internal schedule. It cannot guarantee that the beacon service will be available; the service may experience downtime. It cannot verify that the consumed randomness meets the application's requirements; the tool provides the randomness but does not validate its fitness for specific use cases.

PLEASE NOTE

This tool works exclusively with EVM-compatible blockchains where randomness beacons are deployed. It does not support non-EVM chains. Always verify the beacon contract address against official documentation before use. Using incorrect addresses may result in loss of funds or incorrect randomness. The tool is provided as-is with no warranty of any kind. Randomness consumption requires understanding of the request lifecycle and beacon update mechanisms.