Integrations

Your program asks GERO for a random value, waits for it, then uses it. Randomness comes from radioactive decay measured by the Geiger counters of GERO's node operators, and every result comes with a VDF proof that is checked on-chain before the request is fulfilled.

1. Request. Your program calls GERO's request_randomness with a seed of its own and pays the request fee in XNT (the current fee is on Oracle status). This creates a request account bound to the next grid line.
2. Fulfil. GERO fulfils the request, typically 75–80 slots (≈ 29 s) later, with a result built from the nodes' entropy and a VDF proof checked on chain. There is no fulfil deadline: a late fulfil is allowed. A request can be cancelled for a refund only after 138 slots, and only once it demonstrably cannot be served any more (its line's batch never opened, is dead with no rollover, or does not cover its nodes).
3. Use. Your program reads the result from the request account, for example to pick an NFT's traits, and finishes its own step.

Build and test on X1 testnet first. Both networks run GERO v9.1c with the same account layouts; only the request fee differs (see Oracle status on each network).