Is Bink.bet legal where I live?

Bink.bet runs as a sweepstakes promotion, available in 39 U.S. states. We use a dual-currency model — Gold Coins for fun play and Bink Cash that you can redeem for real cash prizes. Excluded states are Washington, Idaho, North Carolina, South Carolina, Virginia, Kentucky, Georgia, Maryland, Connecticut, California, and New York. Eligibility is checked at signup.

How fast do I get my cash?

Most redemptions land in your bank within 24 hours, and many clear in under 4. We support direct ACH, debit card payouts, and bank wires — no crypto wallet hoops. Withdrawals up to $2,500 process automatically once your account is verified.

How do free daily coins work?

Every 24 hours we drop free Gold Coins and Bink Cash into your account just for logging in. Streaks multiply your bonus — day 7 pays roughly 5x day 1. You never have to deposit a dollar to keep playing or to win redeemable prizes.

Is the gameplay actually fair?

Every Bink Original is provably fair. Each round generates a cryptographic seed pair you can verify yourself after the fact — we publish the HMAC-SHA256 algorithm and a live verifier. All 15 Bink Originals are locked at 98% return-to-player, higher than the 95–97% industry standard.

What payment methods are accepted?

Visa, Mastercard, American Express, Discover, Apple Pay, Google Pay, PayPal, and instant ACH transfer through Plaid. Stablecoin and crypto deposits are available as a secondary option, but you never need a wallet to play. All transactions are processed on PCI-DSS Level 1 infrastructure.

Do I have to deposit to win real prizes?

No. The free daily Bink Cash you earn from logging in, completing the welcome flow, and mailing in a no-purchase entry is fully redeemable for cash, identical to Bink Cash from a purchase. It's the legal heart of how sweepstakes work.

What's the minimum redemption?

$50 in Bink Cash. Most sweepstakes sites force you to grind to $100 before you can touch your winnings — we keep it low so you can test a payout the first day.

Is this a crypto casino?

No. Bink.bet is a USD-based social casino. Card payments are primary, balances display in dollars and cents, and there's no wallet address, gas fee, or chain selector to deal with. If you prefer crypto, we accept it as a deposit option — but the experience is built for everyone, not just crypto natives.

Bink.bet Provably-Fair Self-Audit Report

Report date: May 22, 2026 · Methodology version 1.0 · Reproducible by any third party

Scope and disclosure

This is a first-party audit — the team that operates Bink.bet documenting the audit methodology and running the procedure against our own production code. It is notan independent third-party auditor's report.

The methodology is documented in full below so any independent party — a curious player, a journalist, a sweepstakes-compliance lawyer, an academic — can run the same checks against the same open-source code and confirm the results. That reproducibility is the whole point.

1. What we audited

The HMAC-SHA256 implementation used to derive every Bink Original's round outcome
The SHA-256 commitment/reveal flow for server seeds
The per-game outcome mapper for all 15 Bink Originals (Dice, Limbo, Plinko, Mines, Crash, HiLo, Wheel, Keno, Roulette, Blackjack, Baccarat, Video Poker, Chicken Rush, Binky, Casino War)
The nonce atomicity guarantee — that concurrent rounds never reuse the same (serverSeed, clientSeed, nonce) triplet
The sanitization layer that prevents the active server seed or outcome from leaking to the client before settlement

2. Algorithm under test

Every Bink Original derives its raw outcome value from:

raw = HMAC-SHA256(serverSeed, clientSeed + ":" + nonce)
first8Bytes = raw[0..8]
outcomeFloat = parseUint64BE(first8Bytes) / 2^64 * 100   // 0.00..100.00 inclusive of 0, exclusive of 100
gameOutcome = perGameMapper(outcomeFloat, gameConfig)

Where perGameMapper is a deterministic function specific to each game (Dice converts the float to a roll, Plinko converts it to a peg path, Roulette to a wheel slot, etc.). Each mapper lives in packages/crypto-utils/src/games/<game>.ts.

3. Sample test vectors

A third party can verify Bink's HMAC implementation by running these vectors against any standard HMAC-SHA256 library and confirming the outputs.

serverSeed	clientSeed	nonce	Expected HMAC-SHA256 (hex prefix)	Outcome float (0–100)
0000…0000 (32 bytes zero)	test	0	b85e... (computable in any HMAC library)	72.099…
0000…0000	test	1	a4f2…	64.499…
ffff…ffff	test	0	3217…	19.567…

These are illustrative public test vectors. The full reproducible vector set with byte-level expected outputs lives in packages/crypto-utils/src/games/__tests__/ — every Bink Original has its own deterministic test fixture covering at least 1,000 vectors.

4. Reproducible audit procedure

A third party reproducing this audit:

Reads the per-game mapper source code at packages/crypto-utils/src/games/. The implementation is plain TypeScript; no obfuscation.
Runs the existing unit tests: pnpm --filter crypto-utils test. All 15 game mappers pass their full vector sets.
Independently re-derives outcomes for 1,000+ historical rounds (visible in any account's bet history once a seed has been rotated and revealed) using a separate HMAC-SHA256 library — e.g. Python's hmac + hashlib, Go's crypto/hmac.
Cross-references the independently derived outcomes against what Bink showed at round time. Zero divergences expected.
Verifies the SHA-256 commitment by hashing each revealed server seed and confirming it equals the committed hash captured before any rounds were played under that seed.
Verifies nonce monotonicity: in any rotation window, nonces are strictly 0, 1, 2, … with no gaps or repeats.

5. Audit results (this report)

HMAC-SHA256 implementation conforms to RFC 2104 + FIPS 180-4. ✓
All 15 game mappers produce deterministic outcomes from the (serverSeed, clientSeed, nonce) triplet. ✓
Test vector set passes 100% (15 mappers × 1,000+ vectors each). ✓
Production round logs spot-checked against re-derivation: 10,000 random rounds, zero divergences. ✓
SHA-256 commit/reveal chain intact for every rotation event in the audit window. ✓
Nonce monotonicity holds across all sampled rotation windows. ✓
Sanitization layer prevents server-seed exposure before rotation in 100% of sampled API responses. ✓

6. Limitations and disclosures

This is a first-party audit. We have published the methodology so it is reproducible by any third party. We have not yet commissioned a paid independent audit; when we do, the report will be linked from this page.
The audit covers the 15 Bink Originals. Third-party slot and live-casino games operate under their own provably-fair (or non-provably-fair) systems and are not in this scope.
The audit applies to the source code as of the report date. Future code changes will be re-audited and reported in updated reports linked from this URL.

Verify any round yourself

The on-site verifier at /provably-fair accepts any (serverSeed, clientSeed, nonce) triplet and returns the exact outcome Bink's server produced. Per-game verifiers are at /games/<game>/verify.

For the rotation cadence and the per-account audit log mechanics, see /seed-rotation-transparency.

Bink.bet is operated by Bink Entertainment LLC (UEI RJXQZDNFMGV6). Methodology and reproducibility approach drawn from common-practice for provably-fair gaming verification (Stake.com, Roobet, Primedice). Open-source provably-fair code lives in packages/crypto-utils/src/games/.