acidstates
acidstates

acid//states — unique slot games, built as state machines

spinstaterepeat

A slot is a machine of states. We build the states by hand — no reskins. Idle, spin, near-miss, win, settle: the states are the product.

See the games →

// why states

// the lineup

Games as states.

Ten worlds, one machine. Each a state you can feel.

SOLVENT, an acid//states slot01state: dissolveSOLVENTPour it on. The board keeps giving until there is nothing left to take.CALL CENTER, an acid//states slot02state: holdCALL CENTEREvery call is a con. Pick up anyway.SAWBONES, an acid//states slot03state: cutSAWBONESThe doctor is in. Anaesthesia is extra.SAWBONES II, an acid//states slot04state: relapseSAWBONES IIThe cat operates now.AUTOMAT, an acid//states slot05state: serveAUTOMATCoffee, pie, and whatever is behind the little glass door.CRUSHER, an acid//states slot06state: pressCRUSHEREverything on this lot goes through the jaws eventually.SCRATCH, an acid//states slot07state: revealSCRATCHOne more card. This one feels different.SPIN CYCLE, an acid//states slot08state: launderSPIN CYCLEIn dirty, out clean. Nobody asks about the drum.PLOT, an acid//states slot09state: growPLOTSomething is coming up. Best not to ask what.CATMINT, an acid//states slot10state: familyCATMINTThe family sits. The mint moves. Nobody asks about the vacuum.
scrollswipe to explore
A hand-built acid//states engine: glass chambers of glowing fluid linked by pipes, a central valve core, an engineer sealing a joint

// the machine

We ship a machine, not a catalogue.

One engine under every title. Not a slogan — it’s how the games are built, sealed and shipped.

  1. One engine

    Every game is a repository on the same engine. A module is a deploy unit; a merge to main is a release. New title, same machine.

  2. Built for certification

    Pay paths are sealed in tests — change the math without re-sealing the pledge and the build fails. Every round replays from its log.

    2,000,000rounds simulated
    per math version

  3. One integration

    Integrate once. Every title we release reaches your lobby through the same Game Server and wallet contract — direct or through your aggregator.

Certification target: GLI-19 — in progress. We don’t say “certified” until there’s a number.

// for operators

Integrate once. Ship every state.

One engine means one integration — not one per game. The pay path is sealed and every round replays from its log, so checks stop being a debate.

Talk to us ↗direct or via your aggregator
An engineer slotting a sealed module into a single integration socket on the acid//states machine
  • 01 · integrate

    One engine, every title

    You integrate once. Every game we ship reaches your lobby through the same Game Server and wallet contract.

  • 02 · trust

    Sealed & replayable

    Pay paths are sealed in tests. A disputed round is re-run from its log — not argued over email.

  • 03 · lab

    The lab pack is assembled

    RNG assessment, round-log spec, replay-invariant, mobile FPS, simulation reports, volatility profiles.

the round protocol

loginstartsyncplayaward
  • Deterministic golden tests — same seed, same round, byte for byte.
  • 2,000,000 simbot rounds per math version, reported with a confidence interval.
  • RTP corridors checked in CI on every change.
  • One engine — QA doesn’t restart with each title.
A certification lab: an engineer at a wall of monitors showing round logs, RTP curves and waveforms

Certification target: GLI-19 — in progress. No “certified” until there’s a certificate number.