MULTI-ENGINE SUITE · B2B

Physical venues

What can be done today, and what cannot. Online-first approach: venues need case-by-case discovery.

Floor machines+ CMSCMS exportJSON or SAS-like CSVFloor adapter/v1/floor/importSame proofLeafCodec + MerkleTRUVaultNeeded from the venue: CMS export with outcomeHex («cms» mode), OPERATOR_ROLE holder,raw log retention (18 days on-chain ≠ legal retention), change control.«derived» mode is a simulator for testing.
D-H · Physical venue flow with floor adapter (source: FLOOR_ADAPTER_v0.2.md)

What exists

  • Floor adapter (code in packages/floor-adapter, with tests) with «floor-batch» profile alongside «online-session»
  • Same LeafCodec, same Merkle, same TRUVault contract
  • Import from CMS export as JSON or SAS-like CSV; endpoints /v1/floor/batch/open, /events, /batch/close, /import
  • «derived» mode (simulator, /v1/floor/simulate) for testing

What we do not claim / what the venue must provide

  • No claimed compatibility with specific VLT/AWP or CMS systems
  • «cms» mode: the outcome (outcomeHex) must come from the venue system
  • Holder of the OPERATOR_ROLE on the contract
  • Raw log retention: 18 days on-chain ≠ legal retention
  • Venue change control and approvals remain unchanged

Sources: FLOOR_ADAPTER_v0.2.md; openapi-v0.2.yaml; K-TC FAQ

Physical venues: assessed case by case with the licence holder. No compatibility promised with specific systems.