Reference
Every request and response of the wallet protocol and the launch API, generated from their OpenAPI documents.
The pages in this section are generated from two OpenAPI 3.1 documents. They are the contract; the guides explain how to use it. Each document is a verbatim copy of the one kept beside the RGS code, so the pages, the downloads below and the RGS describe the same thing.
Wallet protocol
The casino implements it; the RGS calls it. Balance, debit, credit and rollback move a player's money for a round; operations exports what the wallet applied, for reconciliation. Every request and response is signed.
- The rules for every operation: Wallet protocol.
- Pages: Current balance, Charge a bet, Pay out and close the round, Cancel a named debit, Export the applied operations.
- Guide: Wallet (seamless).
- Download: wallet.yaml
Launch API
The casino calls it; the RGS answers. It starts a game session for a player, issues a new launch URL for a session, and lists the games of a market. Every request is signed with the casino's Ed25519 key.
- The rules for every operation (signing, keys, errors): Launch API.
- Pages: Start a game session, Get a new launch URL for a session, List a market's games.
- Guides: Authentication and signing, Launching a game.
- Download: launch.yaml
The server addresses in both documents are examples. The wallet's address is the casino's own; the launch API's address for each environment is given with the keys.