How Do Rotating Channels Work in Live-Camera Betting?
Rotating channels on Lukk, by Adkuu, are synchronized broadcasts: everyone watches the same scene, a strict majority can skip early, and bets settle on their own scene.
Rotating channels are how Lukk, by Adkuu, decides what players watch: players watch channels, not cameras. A channel is a synchronized, rotating broadcast in a category such as Streets, Crossings, Nature, Water, Ports or Wildlife; everyone on it sees the same scene at the same time, nobody can camp a camera or pick the next scene, and there is always a round in play. Viewers can vote to skip a scene, which a strict majority of current viewers wins, and a bet placed before a cut settles normally on the scene it was placed on.
Channels, not cameras
A camera-picker would turn a live-camera product into a catalogue: players would choose a feed, wait for something to happen, and spread thinly across many scenes. Lukk's design choice is the opposite. The schedule chooses the scene, the channel carries it to everyone at once, and the AI writes a market on whatever that scene offers. The player's decision is which channel to watch and which outcome to back, never which camera to watch. This is a different route to the same goal that 155.io's Rush Hour reaches by selecting its locations automatically by time of day and traffic patterns: in both products the operator's players are not the ones choosing the camera.
The categories group the kinds of public live cameras Lukk uses: street crossings, junctions, harbours, canal bridges, container ports, bird feeders, wildlife pools and ski slopes. Scenes shown on Lukk's marketing pages are illustrations; the schedule on a channel is set by Lukk.
Synchronized broadcasts
Synchronization means that one market is live on a channel at a time and every viewer is looking at the same frames. A new market opens every minute or two and a round runs about 90 seconds, so a channel is never idle: when one window closes and settles, the next question is already being written. For the operator this is what makes the product behave like a broadcast rather than a lobby. A widget on the casino floor shows the same scene to every player who opens it, and a feed integration can show the same channel on a sportsbook page with the same timing. The B2B feed carries the market's timing and status so that a player on the operator's own front end sees the window open and close in step with the stream.
Skip votes: a strict majority moves the cut forward
On a rotating channel viewers can vote to skip the current scene. The rules are narrow by design:
- A skip passes only with a strict majority of the viewers present at that moment.
- A successful skip cuts early to the same next scene the schedule would have picked anyway.
- A skip can bring the cut forward; it can never choose where the cut lands.
The last point is the one that matters for integrity. If a vote could steer the channel to a chosen camera, a coordinated group could pick a scene they had prepared. Because the destination is fixed by the schedule and the vote only shortens the current scene, there is nothing to gain from organising one beyond a faster rotation.
What happens to a bet when the scene changes
A bet riding through a cut settles normally on the scene it was placed on. The deciding frames come from that scene, the frozen rule_hash on the ticket names that market, and the signed evidence frames and replay are published for it as usual. A skip never voids a market and never refunds it; a void happens only when the camera cannot tell, and then every stake is refunded in full. The operator sees the outcome as won, lost or refunded through the settlement webhook or the pull endpoint exactly as for any other market; the channel's next scene is a new market with its own hash.
Why rotation is an anti-camping defence
"Camping" is the risk the trade press raises when it asks whether someone could influence the scene: a player who stands at a known camera, or who watches a chosen feed for hours, waiting for a moment they can exploit. Rotation removes the precondition.
| Risk | What rotation does about it |
|---|---|
| A player prepares a specific camera | Players cannot choose the camera; the schedule does, and a skip cannot redirect it |
| A player at the scene acts on what they see | Bets close before the window begins, so even someone standing at the camera has not seen the outcome when acceptance stops |
| A group waits for a favourable scene | Short windows and a rotating schedule leave nothing to plan for |
| A delayed stream is used to bet late | Oracle-lag measurement refuses the ticket; it is never filled stale |
| A large position on one outcome | Per-bet stake and payout limits in the operator's currency, per-outcome liability caps, circuit breakers and kill switches cap the economics |
Rotation is one layer. The acceptance pipeline (a one-to-three-second acceptance delay, an in-flight veto from the deterministic tracker, price protection and a quote TTL), stake caps that make rigging uneconomic, and resolutions that are logged and replayable sit underneath it. The settlement side is described in How are live-camera betting markets settled?.
What operators control, and what is on the roadmap
An operator launches a channel inside the widget or renders it from the feed, themes the widget with its own colours and typography, and sets stake presets and limits. Which scenes a channel carries is Lukk's schedule as of October 2026. Operator-owned cameras, exclusive low-latency streams and partner scene packs are on the roadmap, which would let an operator bring its own public scenes into the rotation. The player-facing explanation of channels is on How it works, with common questions answered in the Lukk FAQ.
Sources
- CCTV betting: Accessible innovation or an integrity nightmare waiting to happen?
- What Is Betting on Traffic and Where to Gamble on CCTV Traffic Footage?
- Hub88 chosen as exclusive aggregation partner for 155.io's breakthrough CCTV game Rush Hour
Last verified: October 10, 2026.