Radar / Saracen AR: 100m from border — Mac 44% pass rate, Windows persistent lockout
Source. May 5, 2026 weekly sync (monthly brief) — Radar Browser-Based Solution / Saracen AR section. Full recording: BetSaracenFullTestingSession.mov (21 min, internal Drive).
What we tested
Distance-graded validation runs against Bet Saracen AR (Radar browser-based deployment) from inside the regulated jurisdiction, on Mac + Windows desktops.
What happened
- 350m+ from the state line — success rates remained high. ✓
- 100m mark — Mac devices cleared only 44% of verifications.
- Windows users — hit a persistent lockout after a single failure,
further complicated by an atypical
fraud_jumped_single_deviceflag during betting attempts.
Why it matters
100m is a city-block distance — well inside the state. A 44% pass rate at that range is direct booked-bet revenue loss for the operator. The Windows persistent-lockout behaviour is worse: a single retry triggers an account-level block with no clear self-service recovery path. Support ticket volume scales linearly.
The fraud_jumped_single_device flag is interesting — it suggests
Radar's device-fingerprint logic is misidentifying repeat verification
attempts as suspicious device-jumping behaviour. Pair with the Underdog
DFS device-counting bug (every login = new device) — same architectural
class of problem.
Radar profile → · Underdog device-counting bug → · May 5 weekly sync →