FAQ

Exclusively B2B technology for licensed operators and aggregators: a protocol that acts as a notary for gaming sessions, plus a white-label catalogue of six slot engines built to use it. Game logic runs off-chain; the session proof (Merkle root of the spins and seed hash) is anchored on-chain; the player can verify every spin.

No. True-SlotChain is today exclusively B2B technology for licensed operators and aggregators: it is not a game offered to the public, involves no real-money gaming, and the demo is for technical evaluation only (virtual credits with no value, demonstration maths). Engines are supplied only to operators and aggregators holding the licences required in their markets.

No. The TRUVault contract does not run the game: it stores the proof (Merkle root, seed hash, metadata hash) and manages the dispute window.

With HMAC-SHA256(ServerSeed, ClientSeed:Nonce). The engine consumes the byte stream deterministically; if more bytes are needed (cascades, respins) the stream is extended with new chained HMAC blocks. Same inputs, same result.

After the session closes the seed is revealed: the player recomputes the outcome, the spin's «leaf» and the Merkle proof, and compares them with the root anchored on-chain (verifySpin SDK). In the demo, verification is done with the «Attest integrity» button, directly in the browser.

After-the-fact changes to bets, wins or outcomes once the session is closed; silent seed changes after opening; fake inclusion proofs; spins recorded after closing (the API rejects them).

It does not certify the game's maths or RTP, does not prove the operator's identity or licence, and does not guarantee off-chain log retention beyond the dispute window. These remain the responsibility of the operator and the required certifications.

No. It is complementary: it adds a verifiable audit trail.

Polygon (Amoy testnet / mainnet). Contracts in Solidity 0.8.24 with Foundry. The public demo anchors on testnet; the production network and contract address are shared with the operator during integration.

The session Merkle root, the seed hash and a metadata hash (bytes32). Individual spin details stay off-chain.

Yes, 18 days on-chain from proof submission. Off-chain log retention required by the licence remains the operator's responsibility.

No.

01 Cyber Androide (5×3, 10 lines, expanding symbol), 02 Cascade Zodiaco (6×5, cluster 8+, cascades), 03 Hold & Win Motori (5×3, 25 lines, respins and 4 jackpots), 04 243 Ways Mare (243 ways, Wild x2/x3/x5), 05 Dynamic Ways Atelier (6 reels of height 2–7, tracker), 06 Both Ways Gems (10 two-way lines, sticky respins).

Today the engines run demonstration maths, configurable per market. Certification is performed by an accredited lab (e.g. GLI, BMM) before launch. No RTP or certification is claimed today.

Via a REST Operator API (open session → record spins → close and reveal → proof), documented in OpenAPI v0.2 and protected by an API key; PAM adapter via webhook or batch; verification SDK for the player. OpenAPI specs, timing and SLA: on request, under NDA.

The protocol includes a «floor» adapter that turns CMS/machine events (JSON or CSV import) into the same proof format, on the same contract. The approach is online-first; venues need case-by-case discovery.

The technical repository and API specs can be shared under NDA.

Pricing on request. Possible models: engine licence, revenue share, setup and integration fee.

Briefing (fit: licences, PAM, who runs the RNG) → S0 (technical and compliance discovery, Go/No-Go) → Pilot (sandbox/testnet, limited titles) → Production.

True-SlotChain is designed for the requirements of the jurisdictions on the Jurisdictions page; no market is declared live. Fit is checked with the operator in phase S0, market by market.