Trust & safety
Security
On this page
Real
games use wallet sign-in, a game server and USDC custody contracts on Elysium. This page describes how the release is built and its remaining limits; it is not a guarantee that bugs cannot occur.
What
holds today
- Real funds.
's vault holds deposited USDC under each player's address. Signed house stakes become locked balances. Only free balance can be withdrawn. - Server state. The server holds wallet-linked account/session records, private seed chains, game state and durable transaction journals. It reconciles confirmed chain receipts before crediting Real money moves.
- Browser data. Simulated chat and local settings are browser data, not onchain funds.
- Wallet keys.
asks for signatures or wallet transactions, never your recovery phrase or private key. - Bridge funds. The bridge page uses Elysium's canonical bridge, which
does not run and where
never holds your funds; it is separate from depositing USDC into
.
The vault pause switch does not block withdrawals of free balance. Your wallet, network and RPC still need to work. Funds in an active round must settle or recover before they become free. See Your balance and profile.
House-play session safety
The vault has an immutable session verifier. A session delegates only stakes on the house tables that verifier lists, never
Hold'em hands. The private session key stays in the browser, sealed with an encrypted key in the browser's IndexedDB storage rather than localStorage, and is never sent to
. This protects the stored copy; a script running on the page could still ask for the key, so keep your browser and extensions clean. Grant approval happens once in the player's wallet; later stakes and fresh login challenges are signed locally by that key.
Before the wallet opens, the player picks a spending limit and a length. The default is 20 USDC for 24 hours. The presets are 5, 20, 50 and 100 USDC and 1 hour, 24 hours, 3 days and 7 days. The server refuses a new approval above 500 USDC or 7 days. A stolen key could stake free USDC you have deposited, up to that limit, until the grant expires or is revoked. It cannot withdraw or transfer. Approvals made before this limit existed keep their old terms until they expire; revoke them with your wallet if you want them gone sooner.
End session, and disconnecting your wallet, stop local play and remove the browser key when storage allows it. Neither revokes the approval onchain. If deletion fails, the page warns that a reload may restore the saved approval: revoke sessions with your wallet or clear this site’s stored data. Deleting a local key does not invalidate a copy already stolen elsewhere. Wallet revocation ends every old session onchain; a replacement grant ends the previous grant once its activation confirms. Signing a replacement offline alone is insufficient. Expiry and revocation never block settlement, recovery or withdrawal of existing funds.
Session permissions are bound to the wallet, chain and vault, with spend caps, expiry, epochs, nonces and house-table restrictions checked onchain. Never share your wallet recovery phrase, wallet private key or browser session key.
Fairness you can check
For Real rounds, seed chains are committed before use. A named future drand beacon supplies a salt checked onchain. After settlement, the revealed seed and public inputs let you recompute the published outcome.
Hold'em lets you rebuild a finished deck, including cards you never saw, once its seed is published.
Seeds committed on Elysium
The release commits chains, checks salts and uses sealed outcomes before publishing settlement preimages. Recovery replays saved, exact transaction intent. These checks help prevent result replacement and duplicate custody moves. They do not make the server, operator or admin irrelevant: the contracts do not independently execute all offchain game logic. Compare proofs with the published rules.
Read How fairness works and Check a round yourself.
What the tests and reviews cover
Automated contract and server tests and an internal code and security review cover the release. An earlier test release was checked on 13 October 2026, with 104 contract tests and 306 server and game tests passing; those results do not certify the mainnet vault.
- Contract and server checks cover signed custody, duplicate and replacement receipt rejection, accounting, settlement, refunds, payout queues and recovery.
- Published desktop and mobile pages, configuration and browser connections have been checked.
- Timed concurrent-player load testing remains a separate check.
These are automated checks and internal review. They are not an independent external audit, formal verification or a guarantee against exploitation.
Usage analytics
collects first-party page visits, approximate browser sessions, referral hostnames, campaign tags and fixed error categories to improve the site. Random browser identifiers use local storage; session identifiers use session storage. Collection respects browser Do Not Track and Global Privacy Control signals. We do not collect full referring URLs, form contents, raw error messages or wallet secrets through this collector.
Signed game accounts may link browser activity to a pseudonymous wallet identifier on the server. Growth reports are private and aggregate; financial and played-wallet metrics use confirmed Elysium activity. Wallets and browser sessions do not identify unique people.
Browser event details are retained for up to 90 days, and detailed financial analytics for up to 365 days, with bounded storage. Public blockchain transactions remain publicly visible. Existing account and custody journals have their own operational persistence and are separate from this analytics retention.
Coming next Coming soon
No independent external contract audit or bug bounty is recorded for this release. Live chat moderation is also not configured; today's chat remains a browser simulation. A reviewed supply-cap implementation is required before the prepared $TILT curve can be launched.
Report a security issue Coming soon
A dedicated public security reporting address is not published yet. Do not post exploit details, keys or private transaction preimages in public chat. Nobody handling a
report should ask for your recovery phrase, private key or wallet password.
Read Risks for contract, operator, network and browser-storage limits. Real play uses real USDC, so only play with money you can afford to lose.