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.Documentation Index
Fetch the complete documentation index at: https://docs.roll.codes/llms.txt
Use this file to discover all available pages before exploring further.
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