slot-vrng

Verifiable randomness for on-chain games is generated atomically within a single transaction using Cartridge's VRF. You call request_random as the first entry in a multicall, then retrieve the value via consume_random in your game logic to ensure trust-minimized outcomes.

Atomic verifiable RNG prevents race conditions by generating and verifying the random number within a single transaction. This removes reliance on off-chain oracles or external delays, ensuring the random value is settled before the transaction completes.

Yes, Cartridge session keys support verifiable RNG for dice rolls and loot drops. You must configure the VRF provider address in your Controller policies for allowed methods, enabling seamless atomic random number generation in your game contracts.

The best way to structure a multicall for on-chain randomness is to place request_random as the very first call, followed by your game entrypoint. You must match the source values, such as nonces or salts, between request_random and consume_random.

Your consume_random call fails if the source values do not match the request_random call. You must ensure the per-address nonces or explicit salts provided in the initial request_random entry are identical when consuming the verifiable random value.

Yes, you need to configure Controller policies to use verifiable randomness. You must add the VRF provider address to your allowed methods list, granting the session key permission to execute the request_random and consume_random calls.