Randomness with a record.

An independent software project

D20DAO is a contributor-led project, not an incorporated company. Contributors maintain the protocol software, SDK, website and integration examples. The public repositories and documentation describe how the system works and the assumptions an application needs to consider.

The randomness service is live on Arc and Robinhood Chain, with separate testnet deployments. Consumer contracts request a random word by paying the quoted native-token fee. Dice, selections and shuffles are deterministic mappings of that word, so an application can reproduce how a result became an outcome.

Check the result and its context

D20DAO combines the drand beacon with a verifiable random function. Arc serves requests through epochs; Robinhood Chain binds each request to a future beacon round. The Explorer and SDK expose public replay, while deployment manifests record contract addresses, code hashes and upgrade history.

A valid proof does not guarantee operator availability, honest application rules or an unbiased source. Chain confirmation, beacon assumptions and upgrade authority still matter. The verification and security guides explain these boundaries so builders can decide which checks their application requires.

For contracts and agents

The SDK provides consumer contracts, interfaces, mappings and replay helpers. The HTTP agent API accepts x402 payments and opens its randomness requests on Arc. A locally run MCP server exposes the same API as tools for agent clients; it is not a hosted MCP endpoint. These integration paths share the need to preserve request IDs, handle delivery and refunds, and verify the accepted result.