prepared privately · illustrative only · not affiliated with FanDuel · not indexed

FanDuel Predicts is live in all fifty states. Every eligibility call is an evidence call.

FanDuel Predicts runs event contracts nationwide. Sports contracts run in eighteen states. Tribal lands carve out. Every state that later legalizes online sports betting flips its own rule. Every deposit limit, cool-off, and self-exclusion on the sportsbook must extend to the Predicts app. Sooner or later a court, a state attorney general, the CFTC, or a tribal government will ask a specific question. For one user, in one state, at one moment, under one rule version, did the eligibility check actually run. Today that answer lives inside the same platform whose conduct is in question.

Hive comes alongside FanDuel as a sidecar. At the moment of each eligibility decision and each responsible-gaming control, it makes an independent, signed receipt that anyone can check offline. It never places a wager, sets a line, decides who may play, or drives the platform. It does not judge. The receipt proves the check ran. It does not decide legality and does not guarantee compliance. It is invisible to your users, invisible to your risk engine, and fail-open. If Hive is unreachable, FanDuel operates exactly as it does today.

FanDuel Predicts · Dec 22, 2025
FanDuel and CME Group launch FanDuel Predicts in Alabama, Alaska, South Carolina, North Dakota, and South Dakota. Event contracts on financial benchmarks, commodities, crypto, economic indicators, and sports outcomes. The regulated substrate is CFTC and NFA. The state overlay is fifty different rulebooks and every tribal government.
CME Group release, Dec 22, 2025
Nationwide rollout · Jan 2026
FanDuel Predicts goes live in all fifty US states. Sports event contracts run in eighteen states. Non-sports contracts on financial indices, commodities, and economics run in all fifty. Every state that legalizes online sports betting turns off the sports side of Predicts inside that state. Never on tribal lands.
Covers, Jan 15, 2026
RG portability commitment · Dec 22, 2025
FanDuel's own launch materials commit that deposit limits, session alerts, and self-exclusion on the sportsbook and the daily-fantasy app extend to the Predicts app. Portable RG is now a written promise. The next layer is independently checkable evidence, per user, per surface, that the exclusion or limit actually applied at the moment of the decision.
CME Group release, Dec 22, 2025
The forward posture
Foundation first. Every eligibility decision and every RG control, from day one, produces an independently verifiable, cryptographically signed receipt showing the user segment, state, tribal check, rule version, decision, and time. Anyone can check it offline, without ever entering FanDuel systems or seeing customer data. Regulators cannot argue with a proof they can verify themselves.
Concept proposal by Hive

Three simple states

Where an eligibility or RG-control record is now. Where a signed receipt takes it. What stays yours.

● today · current state

You can show your logs

When a court, an outside counsel team, or a state asks whether a specific session was screened, you look it up and explain it from your own logs. Useful, but the record is held by the same platform whose conduct is in question, so the dispute becomes he-said, she-said.

● with Hive · sidecar state

You can hand over proof

Each eligibility decision gets its own signed receipt at the moment it happens. The receipt records that a location check ran, which jurisdiction applied, which rule version and effective date governed, the allow or block result, and the timestamp. Anyone can check it offline, without touching your systems.

● travels with the record · portable

The receipt goes with the evidence

The signed receipt can travel with a discovery production, a filing, an outside-counsel packet, or an independent monitor review. The evidence is built at the moment of the decision, not reconstructed under deadline pressure weeks later.

follow one user session · synthetic data · runs in this tab

Follow one Predicts session to a signed receipt

A user opens the FanDuel Predicts app in one of several US states and tries to take a sports event contract. Watch the location signal resolve, the state check apply, the tribal-lands check apply, the sportsbook-legal check apply, the RG-portability check apply, the sports contract get blocked, and a receipt get signed. Switch the state to see the same session resolve differently. Nothing here is real FanDuel or user data. It is synthetic, made to show how the sidecar works. Hive never decides who may play.

● what a log shows today
● what a signed receipt adds
Signedanyone can check it

Press Run this session to watch the eligibility receipt get stamped at the moment of the decision.

offline verifier · runs entirely in this tab · no telemetry after page load

Check an eligibility receipt yourself. No install.

This builds a real signed receipt for a synthetic FanDuel Predicts eligibility decision, checks it in your browser, lets you break one byte and watch the check refuse it, re-checks pasted evidence, and re-verifies a published 5,000-receipt soak test. Same signing engine, same offline check, same receipt structure Hive uses across every illustrative proof page on this site.

The signing engine is bundled and served from this same site. After the page loads it makes zero outside calls except two same-site file reads it names out loud. Core verification is fully offline.

In-browser · offline The verifier never leaves this page except to read its own sample and soak-test file from this site.

Idle. Click 1 · Build & check a receipt to load the engine and run the first check. Everything runs in this tab.

Every click prints the recomputed hash next to the stored hash, one line per layer. A changed byte reads FAIL in the same output; a clean receipt reads PASS. Success is labelled, never color alone. There is no server round-trip.

rule version and effective date · runs in this tab

Which rule applied, and when it took effect

Many FanDuel disputes turn on which version of a state RG rule, a Predicts eligibility rule, or a tribal-lands carve-out governed a specific session, and when it took effect. This binds the exact rule set, its version, and its effective date into the same signed receipt as the eligibility decision. The governing rule for one session becomes a matter of independent record, not an after-the-fact account. All values are synthetic.

the session
state · NJ
rule set · fd-predicts-sports-block
version · v2026.01.15
effective · 2026-01-15
the decision
contract type · sports event
location check · performed
result · blocked
at · synthetic timestamp
what the receipt fixes
rule version bound · yes
effective date bound · yes
independently checkable · offline
raw account data · 0 bytes
Idle. Press Seal this rule-version receipt to bind the jurisdiction, rule version, and effective date into a signed receipt.

The rule version and effective date are content-addressed inside the receipt. Change either after signing and the address changes, which breaks the seal. This proves which rule governed the session. It does not judge whether that rule was correct, adequately disclosed, or lawful.

discovery evidence bundle · deterministic · runs in this tab

Group many sessions, then seal the bundle

A state AG production, a plaintiff discovery request, an NFA audit, or a settlement demand usually covers many sessions, not one. This demo takes three signed eligibility decisions from one synthetic day and rolls them into a single grouped proof vector. It folds that into one signed bundle a court, a state, or opposing counsel can check offline. Change one session after signing to watch the check refuse it. All values are synthetic.

session 1 · NJ · sports block
state · NJ resolved
contract · sports event
rule · fd-predicts-sports-block v2026.01.15
result · blocked
session 2 · AZ · tribal block
state · AZ resolved, on tribal land
contract · any Predicts
rule · fd-predicts-tribal-block v2026.01.15
result · blocked
discovery rollup
sessions sealed · 3 of 3
weakest link · none flagged
state · recoverable
raw account bytes · 0
Idle. Press Assemble and seal to roll the day's eligibility decisions into one grouped proof vector and fold it into a signed bundle.

This is a grouped proof over synthetic sessions folded into a real signed frame, not a FanDuel production and not user data. The rollup names the weakest link for review; it does not grade the underlying legal question.

responsible-gaming enforcement receipt · synthetic data · runs in this tab

A signed record that the RG control fired

FanDuel's own Predicts launch materials commit that deposit limits, session alerts, and self-exclusion on the sportsbook and daily-fantasy apps extend to Predicts. Recent complaints and state suits allege that RG controls did not consistently reach every product surface for every flagged user. The evidentiary question is narrow. For one flagged account, can FanDuel show, independently, that the exclusion or the deposit-limit check ran, against which policy version, and with what result. This demo signs that check as a receipt. All accounts and policies below are synthetic.

synthetic screen · one hour, one product surface
account SYN-4471 · active self-exclusionblock
account SYN-2093 · no flag, no limit hitallow
account SYN-8810 · daily deposit limit reachedblock
screen ran against policyfd-rg-carryover-v2026.01.15
what the receipt attests
that the RG check was performedyes
the policy versionbound
the per-account resultbound
the timestampbound
Idle. Press Sign the RG-enforcement receipt to seal a signed record that the screen ran, against which policy, with what per-account result.

This shows only that an RG control ran and what it returned. It does not diagnose problem gambling, does not define material harm, and it does not judge any account or plaintiff. FanDuel's own launch materials describe RG portability from the sportsbook and daily-fantasy apps to Predicts (CME Group release, Dec 22, 2025).

your numbers · arithmetic tool, not a forecast, quote, or ROI claim

Move the sliders. See evidence volume and time you stop reconstructing.

This is an evidence-coverage tool. It counts how many signed Predicts and RG receipts a given daily activity level produces and how much reconstruction time signed coverage can remove. Every value below is a number you set. It is not a forecast, a quote, or a dollar-savings claim, and it makes no assumption about FanDuel's real volume.

Every slider is a labelled assumption you set. This is arithmetic on numbers you enter, not a forecast, a quote, or a claim about FanDuel's real activity. No return-on-investment figure is implied.

Signed eligibility receipts / day·
Signed receipts / 30 days·
Sports-blocked-state decisions with a receipt
per day·
Reviewed or produced sessions covered by a receipt
per 30 days·
Reconstruction hours avoided
covered sessions, no manual rebuild·
Raw account data moved to Hive0 bytes

Whatever you enter, the last number is always zero. Receipts carry one-way fingerprints and commitments, never raw account or location data. Evidence volume scales with sessions; proprietary data moved to Hive does not scale at all, because it never moves.

just filed · USPTO 64/119,279 · Jul 26, 2026

Seven upstream receipts, signed before the session receipt is cut

The session-level receipt above proves the eligibility check and RG control ran for one Predicts session. The seven upstream primitives below prove that the eligibility model, its policy state, its refusal thresholds, and every egress from the risk stack were themselves signed, before that session receipt was ever cut. Live and operational today.

Environment and policy provenance
PBS™ · Provenance-Bonded SandboxThe RG-scoring and eligibility-scoring models ran in a sandbox whose kernel, model-weights hash, and firmware version were on the signed heartbeat chain at the moment they evaluated the user.PBS · Merkle heartbeat chainupstream to the eligibility decision
Refusal Ledger™FanDuel's deposit-limit and self-exclusion thresholds live on a public Merkle mutation ledger with a ZK envelope-bond, so a state regulator, tribal government, or auditor can verify the bounds without seeing the exact number.Refusal Ledger · ZK envelope-bondupstream to the RG-block decision
Interpretability and perimeter integrity
Howler™ (SAE-triggered)A signed freeze receipt fires the instant a promotional-targeting feature activates for a self-flagged or excluded user during automated VIP or offer-selection reasoning.Howler · SAE probeupstream to VIP and promo inference
Perimeter Bond™The eBPF bytecode enforcing DLP on internal user-behavior analytics is fingerprint-bound to the exact version filed with state regulators, so an egress can be verified as running under the approved rule.Perimeter Bond · eBPF hashupstream to every egress attempt
Weekend, incident, and settlement regimes
Diurnal Bond™High-impact VIP-outreach or promotional-override actions taken during evening or weekend hours require k-of-n countersign before they run, so a flagged-user override cannot happen off-hours without a signed second key.Diurnal Bond · k-of-n countersignupstream to off-hours VIP actions
Egress Bond™Caps on customer-identity egress from RG-surveillance and marketing-analytics systems are Pedersen-metered per semantic class, and a cap breach retroactively invalidates the analytics DAG.Egress Bond · Pedersen meteringupstream to the analytics DAG
Post-incident and regulator replay
Forensic Rail™Post-incident analysis of any RG or eligibility failure runs under a threshold-signed consortium credential and is deterministic-replayable by the CFTC, the NFA, a state AG, a tribal government, or an independent auditor.Forensic Rail · threshold-signed credentialupstream to incident response

These seven sit upstream of the session receipt described above. None of this decides eligibility, refuses a wager, or blocks a customer. Each one proves that the thing that made that call was itself the thing it claimed to be. Live and operational today.

Filed. July 26, 2026. USPTO application 64/119,279. See upstream group in Hive Proof Architecture → · Read the essay →

Where this fits the FanDuel surface

The same signed receipt fits eight distinct FanDuel decision surfaces. Here is where it earns its keep, in plain words, with the Hive primitive named as a small label and a candid read on whether it helps now or is a fast-follow. Public reference material used in preparing this overview is linked at the foot of the page. Hive sits alongside, never inside the decision to allow or block.

Responsible-gaming enforcement
Self-exclusion and cool-off portabilityDid the self-exclusion take effect at the moment of request, across every product surface, including Predicts. A signed receipt binds the exclusion event, the product surface, and the timestamp, so a state AG or a plaintiff sees an independent record instead of an internal dashboard export.Imprimatur · SiGRhelps now for RG-carryover, self-exclusion enforcement, and Arroyo-style complaints
Deposit and wager limitsWhich deposit limit or wager limit was live when a deposit cleared or a bet went through. Bind the effective limit and the check result into the same session receipt, so a limit dispute becomes an offline verification instead of a log-file forensics exercise.HiveBound · SiGRhelps now for deposit-limit and session-cap disputes
Promotional targeting and VIP
Was this customer excluded from the modelAfter a customer is self-flagged or excluded, promotional targeting and personalized-offer models must exclude them from the training and serving population. A signed receipt binds the exclusion tag to each model-serving decision, so an algorithmic-targeting complaint can be answered with independent proof of exclusion.MiR · SiGRhelps now for SDNY-style algorithmic-targeting suits and PHAI complaints
VIP designation and flagged-customer ruleDid the VIP-outreach policy apply the flagged-customer rule check first. A signed policy-clearance receipt at the VIP-designation step, with a k-of-n countersign for off-hours or high-impact overrides.Imprimatur · Howlerhelps now for VIP-policy enforcement and off-hours override audit
Predicts eligibility and customer support
Predicts eligibilityDid the state, tribal-lands, and contract-type exclusions all run for a Predicts session, and what did they return. Each Predicts eligibility decision is sealed with the state, the tribal-lands check, the contract type, the rule version, and the allow or block result.HiveBound · Structural Laterationhelps now for state-attorney inquiries and tribal-government relations
Customer support and chatWhat did the platform tell the customer, and when. Streaming voice and chat receipts bind the transcript, the agent instance, and the policy version to a signed record, so a customer-service dispute is anchored to what was actually said.AFiR-Streamhelps now for customer-service dispute audit
Regulator production and whole-platform record
Regulator and AG productionProduce everything for N accounts over a time window. Grouped proof vectors let a state AG, the NFA, or a tribal government receive an independently checkable stack of receipts instead of a records-custodian dump.R3Pv · Customer Consolehelps now for state-AG productions, NFA audits, and multi-state settlement demands
Whole-platform recordIs the record complete, and can a missing entry be detected. A public dashboard streams the receipt-emit rate for each surface, so the absence of an expected receipt is itself an evidentiary signal.Command Centerhelps now for internal audit posture and regulator-facing telemetry

Every primitive named here is live in the offline verifier on this page. Nothing is forced onto a use it does not fit. Hive proves conditions, never verdicts.

What supports this behind the scenes

You do not need any of this to understand the value. It is here for the people who want to look under the hood. Each row is a plain benefit first, with the Hive part named as a small label.

A single eligibility decision becomes a signed exhibit: the location check, the jurisdiction, the rule version and effective date, and the allow or block result, sealed into one receipt. SiGR patent pendingSiGR →
SiGR, the Signed Inference Guarantee Receipt, signs a decision into one receipt anchored on Base. It turns trust our logs into a signed exhibit that stands up in a filing or an independent review. See the SiGR page.
The authority or eligibility is checked before a transaction runs, and any attempt without a valid pass is blocked and recorded. Imprimatur · HiveBound patent pendingImprimatur →
Imprimatur is a pre-action attestation gate. It signs a clearance before a consequential action runs and blocks any call without a valid, unexpired pass, so the authority was in place is proved up front rather than reconstructed after the fact. HiveBound binds a decision to a jurisdiction and policy boundary. Both sit alongside the platform and never decide who may transact. See the Imprimatur page.
The exact jurisdiction rule set, its version, and its effective date are pinned to the decision, so which rule governed a session is a matter of record. Carnac™ family · Carnac Gateway™ patent pendingCarnac™ →
Carnac™ sizes how much proof a decision deserves, CarnacPrompt™ carries the human-visible context and proof demand, and Carnac Gateway™ clears an action before it runs. The rule version and effective date are carried in the signed context so a change in rule is traceable to the sessions it first affected. See the Carnac™ plane, CarnacPrompt™, and Carnac Gateway™.
Many receipts from one day, jurisdiction, or account roll into a single grouped proof vector that flags the weakest link. R3Pv · Protected Flow patent pendingR3Pv →
R3Pv, the Receipt Proof Vector, groups receipts into one signed vector: verification depth, weakest boundary, recoverability, and next action. One machine-readable summary per day, jurisdiction, or account lets a review or discovery team triage instead of re-checking everything. Protected Flow rolls many receipts into one proof-state view. See the R3Pv benchmark.
Big screening jobs and multi-step checks get proof at the piece level, and streaming inputs are signed as they flow. AFiR · SiGR patent pendingAFiR →
AFiR, Attested Fragmented Inference Routing, breaks a request into signed, routable sub-tasks and signs each fragment inside the path, so a multi-step surveillance or eligibility check is provable step by step. See the AFiR page.
The signing key is born random and lives in hardware, so a stolen key cannot forge your receipts. XCALIBUR · SPIRE patent pendingXCALIBUR →
XCALIBUR is a hardware root of trust: a signing device that keeps the key in silicon, born from quantum-grade randomness and bound to the device. SPIRE gives a service or agent instance a signed identity, so which system signed a receipt has a signed answer. See the XCALIBUR page and SPIRE in the proof architecture.
Under it all sits the evidence floor that holds a decision record still while proof is attached, so it can be rebuilt and re-checked offline. InkFrame v1 · Carnac Live Ink™ patent pendingInkFrame →
Carnac Live Ink™ writes non-mutating evidence frames. InkFrame v1 holds a proof-completion frame still using eight content-addressed roots and a hybrid Ed25519 with ML-DSA-65 signature. Change one byte and the address changes, which breaks the seal. See InkFrame v1 and Carnac Live Ink™.
Settlement receipts can be anchored and, where a partner wants it, paid and reconciled on a public rail. Hive Receipt · x402 · Base USDC patent pendingHive Receipt →
A Hive Receipt can be anchored on Base (chain 8453) and, where a counterparty wants a settled record, verified through the x402 rail with USDC settlement. This is optional infrastructure for a neutral, checkable ledger-state record, not a requirement for the offline verifier on this page. See the receipts page.

Explore Hive Proof Architecture.

The keys stay with you

In plain words: your organization holds the pen that signs. Hive never touches your proprietary account or location data, never decides who may transact, and never holds your keys.

You hold your own signing keys

You keep the private key that stamps your receipts. Nobody else can sign in your name, and the key never leaves your own hardware. The signature is yours, not Hive's.

Hive stays a non-custodial sidecar

Hive gives you the way to make and check receipts. It does not place a trade, set a price, decide eligibility, or run the platform, does not enter the decision loop, and does not move or store your raw account or location data. Each decision is recorded as a one-way fingerprint and cryptographic commitment, never the underlying data.

Turn every eligibility and RG decision into a portable trust asset

As algorithmic-targeting suits deepen and Predicts opens 50 states, a court, a state AG, outside counsel, or a tribal government will ask whether a specific control ran for a specific session. A signed, independently checkable receipt at each eligibility decision and each RG-enforcement step is how that answer stays provable. Naming FanDuel does not imply any agreement, and this page does not state or imply that FanDuel is a customer, partner, pilot, or endorser, or that FanDuel uses Hive.

Legal & enforcement Outside counsel & discovery Compliance & surveillance Engineering & platform

One line to start: [email protected]

illustrative and non-endorsement notice

This page is illustrative only. It is prepared privately by Hive Civilization Inc. and is not affiliated with, sponsored by, or endorsed by FanDuel Group, Flutter Entertainment plc, CME Group Inc., or any of their subsidiaries. It does not state or imply that FanDuel is a customer, partner, pilot, or endorser, or that FanDuel uses Hive.

Every session, account, state rule, tribal-lands designation, RG policy version, timestamp, and receipt shown in the demos is synthetic and made to illustrate how the service works. None of it is real FanDuel, user, account, deposit, or location data.

A signed receipt proves that a check ran and what it returned. It does not decide legality, does not guarantee compliance, does not resolve state or tribal preemption questions, and does not adjudicate any court matter. Every court matter named on this page is a pending allegation unless a court has finally found otherwise. Court and current facts on this page are cited to primary filings or named reporting and carry their exact status, which is preliminary, pending, interim, or final as labelled. They should be re-verified before any external use given the pace of docket activity.

Private, illustrative overview · noindex / nofollow / noarchive / nosnippet · not affiliated with FanDuel Group, Flutter Entertainment plc, or CME Group Inc.; this page does not state or imply that FanDuel is a customer, partner, pilot, or endorser, and does not imply FanDuel uses Hive · the sessions, accounts, states, tribal-lands designations, RG policies, and receipts shown are synthetic and made to illustrate how the service works; they are not FanDuel or user data · Hive is a sidecar; it does not place a wager, set a price, decide eligibility, or run the platform, does not enter the decision loop, and does not move or store raw account, deposit, or location data · a signed record that a check ran is not a statement of legality, and does not guarantee compliance · every court matter named on this page is a pending allegation unless a court has finally found otherwise · Hive never reads the underlying data; each decision is recorded as a one-way SHA-256 fingerprint and cryptographic commitment, not the raw signal · Carnac™ sizes how much proof a decision deserves. It does not judge. · verification is free, works offline, and needs no account · signatures use a hybrid of Ed25519 and ML-DSA-65 (NIST FIPS 204), a federal standard · public reference material used in preparing this overview, to be re-verified before external use: FanDuel & CME Group Predicts launch (CME Group release, Dec 22, 2025); FanDuel Predicts nationwide (Covers, Jan 15, 2026); FanDuel CLCO departure (Bloomberg Law, Apr 9, 2026; EGR North America, Apr 7, 2026); FanDuel CEO transition (CNBC, May 6, 2026) · Carnac™, CarnacPrompt™, Carnac Gateway™, and Carnac Live Ink™ are Hive marks · all Hive methods patent pending · prepared by Hive Civilization Inc. · Wyoming, USA
new in the canon · runnable on this page

Carry state checks with the wagering record

This receipt adds a defined evidence trail for state wagering gates and self exclusion screens beside the eligibility path already illustrated here. It answers in production right now, and the run below proves it end to end.

screening.attestation · Deployed in production

Record which state and self exclusion screen ran

When one Predicts session reaches a sports contract, this receipt can record the screening run that considered the applicable state rule and a named self exclusion reference. It captures the engine, rule set fingerprint, list versions, supplemental sources, screening instant, clock bound, stated verdict, and period for which that verdict may be relied on. The customer and the matching list record stay concealed behind protected references. A risk team can therefore compare an Alabama result with a later New Jersey result without treating them as the same rule. Compliance and legal receive a stable account of the actual screen rather than an informal description of what a control should have done.

What it does not do. It does not prove that every state rule, tribal restriction, or self exclusion list was complete or correctly chosen, and it does not establish that a person was actually barred from wagering. It cannot fix a false negative, expose the customer or a list match, prevent a wager, or decide whether responsible gaming or gaming law requirements were met.

Open the Screening Attestation Receipt pageCanon entrySchema
POST /verify/screening-attestation · case pass, a clean record

Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.

POST /verify/screening-attestation · case matched, a name matched the list

Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.

POST /verify/screening-attestation · case fail, a forged record

Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.

Every run above posts a verified request body from this domain to the open verify route and prints what came back. The example receipts are signed with published example keys, so verify reports key_trust example_registry. That is on purpose. Nothing on this page is a production issuance, a customer record, or an endorsement. Patent Pending.

Canon cross reference

The exact canon entries behind this page

Each link opens that entry in the canon implementation explorer, where its schema, mint route, open verify route, auth requirement and implementation state are stated. The state shown here is read from the same registry file the explorer renders from, so the two cannot drift apart. Nothing here implies a customer, a deployment or an endorsement.

Search the explorer for FanDuel proof surface