Skip to main content
roll.codes runs the coordinator infrastructure for you. As an integrator, you deploy your consumer contract, send requests to the hosted coordinator for your network, and handle the randomness callback in your own contract.

​
Start here

Quickstart

See the minimal request and callback flow you need to integrate against the hosted coordinator.

Coordinator reference

Keep the request function, fee call, and callback interface beside you while implementing.

Integration pattern

Copy a fuller consumer example with request storage and settlement guards.

How roll.codes works

Understand how the hosted coordinator, request lifecycle, and callback delivery fit together.

​
What you own

  • your consumer contract
  • the application state keyed by requestId
  • the callback logic that settles the result

​
What roll.codes owns

  • the deployed coordinator contract for supported networks
  • the off-chain fulfillment pipeline
  • delivery of the random number to your callback
1

Read the quickstart

Start with the minimal hosted-coordinator integration shape.
2

Copy the integration pattern

Adapt the example consumer to your own state and game or app logic.
3

Use the coordinator reference

Check the exact request and fee interfaces while you implement.
4

Harden the callback

Review callback security and troubleshooting before you ship.
Last modified on March 6, 2026