IMPAKT crowdplay — integration pack
Everything a partner's engineering and security teams ask for before a pilot.
| 1. Integration overview | What the layer does, the three shapes it comes in, and which one fits you |
| 2. Protocol and API | Sockets, authentication, viewer identity, message reference |
| 3. Security and data | What crosses the wire, what is stored, what is not, and who can read it |
| 4. Readiness | What is built and running today, and what is not yet |
| 5. Pilot | What a first integration costs in engineering days, and how it is measured |
| 6. Latency and scale | Measured numbers, not estimates |
| 7. Economy and licensing | The coin, who is paid what, and the two licensing shapes |
| 8. Real money through the operator | The seamless-wallet contract for casinos and aggregators, the parimutuel round, the sandbox |
The protocol itself is specified in CROWDPLAY.md at the repository root. That document is the contract; these are the papers around it.
The short version
IMPAKT is an interaction layer, not a game and not a player. A game publishes what its audience may ask for, the audience asks, and the game receives one aggregated number per action per tick and decides what actually happens. The game stays authoritative throughout. Nothing here renders your pixels or holds your users.
Read 4. Readiness first if you are deciding whether to start. It is the honest account of what exists, and it will save a call.
Part of the IMPAKT crowdplay integration pack. All documents.