KIBL + KennelKlub Arcade
KennelKlub Arcade is a Nexa-native on‑chain arcade designed to make DeFi feel simple: play instantly, verify outcomes, and own your wallet. The brand is fun (PixelPups), but the product goal is serious: a fast, transparent, community-shaped on‑chain game hub.
Web3 games feel slow and untrusted
- Wallet friction blocks new users
- Slow settlement kills the “arcade loop”
- Opaque RNG reduces trust
Instant-feel arcade + provably fair rounds
- In‑app DApp wallet (create/import) + address linking
- Fast bet broadcasting + resilient failover
- Commit → reveal flow with round IDs for verification
Live modes
- Poker (Beta) — seasonal points, achievements, payouts
- Blackjack (Beta) — double/split, arcade win feedback
- Dice (Alpha) — risk tiers, fast loop, provably fair
KIBL Utility
KIBL is the in‑arcade utility token used for betting, rewards, and seasonal progression. The arcade is designed so users can earn and claim to their own wallet, then freely use KIBL elsewhere in the Nexa ecosystem.
- Bet loop: 100 KIBL to start a round (Poker/Blackjack/Dice)
- Rewards: daily rewards + claimable balances (hCaptcha gated)
- Wallet: send NEXA/KIBL from inside the app; move winnings to your “main” wallet
- Seasonal cosmetics: unique face cards (evolving; planned Top‑16 seasonal drops)
Note: token markets outside the arcade are not controlled by the arcade. The project focuses on building real usage and retention first.
Fairness & Transparency
We use a provably fair approach intended to be auditable:
the server commits to a seed (commit hash) before the action, and reveals after settlement.
Rounds expose identifiers like handId to make support + verification practical.
- Commit first: you see the commit before the result
- Reveal later: revealed seed material is shown after settlement
- Verify tooling: a friendlier verification page is in progress
Architecture (why it feels instant)
The bet loop is optimized to remove “handshake overhead” and keep sessions responsive: keep a single connection open, detect and repair “zombie” sockets, and use a failover path to public nodes if the private lane is unavailable.
- Cached wallet session (decrypt once per session)
- Micro‑ping health check (e.g., block tip) before broadcasting
- Failover: private node → public electrum node
Safety, Limits, and Beta Reality
Beta/alpha phases are about stability and fairness. Abuse controls (rate limits, hCaptcha gating) help protect the pool and keep the experience usable for real players. Thresholds and signals are intentionally not fully disclosed.
Community + Distribution
The primary loop is “build in public” + ship improvements suggested by players. Telegram is the home base; X is the public devlog; the product itself is the marketing.
- Owned: playpixelpup.onrender.com, Telegram, X
- Earned: Nexa ecosystem shares, dev community feedback, creator program spotlights
- On‑chain: seasonal rewards/collectibles once wallet linking is stable
Links
Play: Home · Docs · Roadmap
Telegram: t.me/NexaKennelKlub
This website litepaper is a high-level overview for community information only and is not investment advice. Token mechanics, timelines, and features are subject to change based on audits, compliance reviews, and technical feasibility.
Disclaimer
This is a beta/alpha software product. Nothing here is financial, legal, or tax advice. Use at your own risk. Features, rewards, and token utility may change as the product evolves.