Developer overview
JERDOG develops games and their supporting infrastructure on Arc. The infrastructure overview describes how game rules, settlement, application services, and randomness fit together.
For smart-contract integrations, RUFF has its own contract interfaces, SDK, and mainnet quickstart. JERDOG’s live game contracts and a platform-wide partner API have not yet been released.
Product boundaries
Section titled “Product boundaries”| Component | Responsibility |
|---|---|
| Game rules | Versioned pack and outcome definitions, round transitions, and reward calculations. |
| Live game contracts | Planned authority for accepted rounds, settlement, and claims. |
| RUFF | Separate service for random results, delivery, and verification. |
| Wallet connection | Reown AppKit connects embedded and external wallets. |
| Campaign services | The application API verifies signed participation and maintains allocation records. |
| Swap | LI.FI supplies routes; the wallet authorizes on-chain transactions. |
| Game preview | Browser storage holds local credits, rounds, and reward history. |
The current feeding preview runs locally. Its results do not represent on-chain balances or rounds settled by the planned live contracts.
Networks
Section titled “Networks”| Environment | Network | Chain ID | Hex chain ID |
|---|---|---|---|
| Public JERDOG application | Arc | 5042 | 0x13b2 |
| Development environment | Arc Testnet | 5042002 | 0x4cef52 |
Treat the chain and wallet address as separate identity fields. An address on one chain is not sufficient evidence of control of a smart account on another chain.
The public application configures its supported network through the wallet connection. Development campaigns and records are isolated from production.
Current integration path
Section titled “Current integration path”For a community website or partner page, link users to the relevant application URL. For a game that needs randomness, begin with the RUFF quickstart and deployment reference.
The site’s /api/ routes support its own authenticated browser flow. They are not a stable third-party registration API. Do not collect a participant’s email, signature, or wallet credentials through a separate form to forward them into that flow.
Future contract integrations
Section titled “Future contract integrations”The token, live game, and claim system need their own published deployment addresses and versioned integration references when released. For the separate randomness framework, see RUFF, its contract API, and its deployment reference.
For an integration discussion, contact contact@jerdog.xyz with the use case and target network.