Gaming infrastructure
JERDOG’s infrastructure separates player access, game information, game rules, and settlement. Each game defines its own rules. RUFF supplies verifiable randomness as a separate service.
The platform’s layers
Section titled “The platform’s layers”| Layer | Responsibility |
|---|---|
| Games | The play format, accepted actions, outcome rules, and rewards for each game. |
| Game contracts | The planned authority for paid rounds, settlement, and prize claims on Arc. |
| RUFF | A random result and the evidence needed to verify its derivation. |
| Application services | Player access, indexed game activity, history, and information presented to players. |
| Game interface | The scene, controls, animations, and wallet prompts. |
The public Feed JerDog preview runs its rounds locally. Live game contracts and their supporting services belong to the planned rollout; they do not settle the preview’s credits.
Rules belong to the game
Section titled “Rules belong to the game”Feed JerDog uses packs, outcome tables, and Bark Time. PvP and weekly lotteries are separate formats with their own rules to be defined. Reusing platform infrastructure does not make their reward systems identical.
The existing feeding engine versions its rules and saves an accepted round before revealing its result. The live design puts accepted round parameters and prize accounting in contracts, while the website displays the result. An animation is a presentation of the round, not the authority that awards a prize.
Randomness through RUFF
Section titled “Randomness through RUFF”RUFF (Randomness Utility & Fulfillment Framework) is JERDOG’s separate randomness product. A consumer contract requests a number. The hub checks the delivered evidence, stores the result, and calls the consumer back. The consumer applies its own game rules to that number.
The same interface can serve applications outside JERDOG. Integrating RUFF does not require adopting the feeding game, its payout tables, or the $JERDOG token. Its contract API and trust model describe the current implementation.
Wallets and supporting services
Section titled “Wallets and supporting services”The current application uses Reown for embedded and external wallet connections, LI.FI for swap routes, and JERDOG’s own application API for campaign records. Live game indexing and history are part of the planned game services.
Wallet connection identifies the account used in an action. The relevant contract or server then verifies that action before recording it. The browser’s displayed balance or success state is not a substitute for the underlying record.
Integration paths
Section titled “Integration paths”- Players: explore the game catalogue and wallet guide.
- Game developers: use the RUFF quickstart to request and verify a mainnet result.
- Platform partners: see the developer overview for the current integration surface.
RUFF has its own release and deployment lifecycle. Its deployment reference identifies the network and contract configuration for an integration. The JERDOG roadmap covers the platform’s game releases.