FAQ

10% of your games' GGR (stakes minus wins), unless your agreement says otherwise. Statements are made on the 1st of each month (UTC) for the month before, per game and coin, and paid in the coin the GGR was earned in, to your address for that coin, after our finance team approves the payout. Earnings in a fiat wallet currency (euros, yen…) are paid in USDT at the day's rate, which the statement shows.

Negative GGR is carried forward against the same game and coin in later months. You are never charged for it.

USDT (Tron), USDC (Ethereum), BTC, ETH and SOL. Add your addresses in Billing. A change of address is emailed to every owner of the studio.

You do. You license it to Housebets to offer to its players while it is live; you can pause it or take it down.

A game's maths is a set of weighted tables: every outcome, its weight, and what each bet pays on it. The engine computes the RTP of every bet from those tables exactly, to four decimals, before a version can be used. There is no simulation and nothing to trust: the number is the table's.

Between 90% and 99% per bet, and at most the RTP your pack declares. The store page shows the range across bets, the hit rate, the largest multiplier and the volatility.

Use the maths kit (@housegames/engine-math): describe reels, lines or ways, scatters and free spins; it lists every outcome of a round as a row (a "book") with its weight, and solves the weights to hit your RTP exactly. The lines template (reels, paylines, free spins) and the tumble template (a scatter-pays grid with tumbles and multipliers) are complete slots built this way.

Our server, from the player's provably-fair seeds. Your page receives the drawn row and shows it. A player can check any round in the fairness dialog.

Each coin has a maximum win per round. A stake whose largest possible win would pass it is refused before the round starts; it is never reduced.

Any web stack: plain JavaScript, PixiJS, Svelte, React, Phaser. The bundle is static files. The SDK gives you the connection, the bet field, money formatting in the player's coin or fiat, staged asset loading, and the engine panel.

150 MB per upload, 2,600 files. The first screen should load fast: the scan warns when the files needed for the first paint are large. Compress images to WebP and sounds to Opus or M4A.

Open the Sandbox tab of your game: pick a coin, a language and a device. Every upload is also played automatically on desktop and phone, in the site's frame and in fullscreen.

Yes. The House Engine MCP server gives an agent the same commands as the CLI: start from a template, verify the maths, check the bundle, upload, and read the checks.

Each check says why. math: a table does not verify (the line and the reason are given). scan: the bundle uses something we do not allow, such as network calls, storage, eval, or outcome logic in the browser. boot: the page did not say it was ready. bet: a round did not play through. draws: after a round the play area shows nothing (often a board with no width). fit: something is cut off or scrolls in the frame. network: the page tried to reach another server.

That the game plays as the rules say, the art and words are fit for the site, nothing in the page decides an outcome, and the store page is complete. We aim to answer within 24 hours.

Upload a new version and submit it. Players keep the live version until an owner puts the approved new one live. Rounds already open finish on the version they started on.

Yes: an owner can pause and resume it from the game's page. Housebets can also switch a game off; we tell you why.

Games that copy another studio's art or name, games aimed at children, and games whose page changes the outcome or the stake. Ask us when in doubt.