KaspaForge brings self-custody, covenant-backed trade, on-chain publishing and verifiable games into one encrypted Desk. It runs on Kaspa — a decentralized, high-speed proof-of-work Layer 1 — while your private keys stay in your browser and every transaction is signed locally.
The hero background is a decorative interactive mesh of KaspaForge product clusters — a stylized scene, not live network data.
▾Arena is KaspaForge's non-custodial game layer. There is no casino balance: your Desk signs locally, game funds move through covenant UTXOs, and completed games end in Kaspa L1 receipts.
Blackjack combines two committed seeds, a deterministic shuffle, Merkle card openings and an independently verified ZK proof. Dice combines two committed seeds into one deterministic 16-bit roll. Different games, one rule: the interface shows only a result it can verify.
Current tables are house-operated. Settled outcomes are verifiable; operator services remain an availability boundary.
Arena · covenant games + proofs
Blackjack proves its hidden deck and shuffle; Dice opens two committed seeds into one verifiable roll.
Keys are generated in your unlocked browser and never leave it in plaintext.
An HD master seed derives every future key via domain-separated HMAC-SHA512, so the first encrypted backup also covers what you create later.
You see the exact amount, fees and destination before anything is signed.
A fee change before signing invalidates the previous review — there is no “approximately”.
The local WASM core signs the transaction; the private key stays on this device.
kaspa-safe-core compiled to WebAssembly performs Schnorr signing inside the browser.
The server and node receive a signed transaction, not your private key.
Any Kaspa v2+ node works — node.kaspaforge.org is only the default relay.
The network decides: the UI shows confirming until Kaspa reports acceptance.
Pending and confirming are never presented as confirmed; progress after broadcast is data-driven, never faked by a timer.
Every withdrawal waits through your chosen window, with its destination fixed on-chain from the start. If it wasn’t yours, the separate alarm key returns everything to the vault. Optional inheritance opens only after your check-ins stop for the period you set.
With separate storage, alarm cards remain separate and never sync.
Deal funds sit in an on-chain covenant, not with us. Every valid path pays the buyer, seller or a split between them. The arbiter can judge evidence, but cannot redirect the principal: the Kaspa network rejects every other destination.
Holds the funds and asks you to trust a person’s discretion.
The covenant holds the funds and cannot pay the operator.
Every Buy button opens covenant escrow automatically. The seller cannot take the funds before release, and a dispute uses the same fixed payout paths as any Forge deal.
A security deposit held by the same escrow covenant: the holder cannot spend it, and nobody can take it outside the agreed outcomes.
How Deposit works ▸ BoardsPublic on-chain boards: the text record is a Kaspa transaction — 0 KAS platform fee, dynamic network fee, up to 2,048 bytes. Text lives on-chain; images are best-effort off-chain.
Open the boards ▸Kaspa Forge already uses specialised AI agents inside Market and Escrow. They review offers and structure disclosed evidence — but receive no signing keys and cannot move the money.
Meet the Forge agents ▸Your shared Desk data lives in an age-encrypted profile locked by your password. Optional Forge Sync uploads ciphertext only after you enable it; the server cannot decrypt it. Separate-storage Safe alarm keys never enter the mirror — alarm cards remain separate and need their own protected copy.
| Property | Where enforced | What can fail | Recovery |
|---|---|---|---|
| Keys stay local | Browser + Rust/WASM signing | Device loss, forgotten password | Encrypted .age file plus its passphrase |
| Arbiter cannot redirect funds | Escrow covenant on Kaspa L1 | A dispute judged against you | Payout still bounded to buyer · seller · split |
| On-chain state survives this site | Kaspa BlockDAG | Site or server outage | Open-source CLI against any Kaspa v2+ node |
| Backup is encrypted and user-held | age scrypt passphrase | Losing both file and passphrase | None — no backdoor exists; enable inheritance |
| No platform token or bridge | Plain KAS inside covenant scripts | Nothing to depeg or drain | Not needed |
| Optional sync is ciphertext only | Client-side encryption before upload | Server compromise leaks ciphertext | Keys and plaintext are never uploaded |
The Desk is your control room: a personal Kaspa wallet (receive, balance, send) that funds vaults and deals directly, a portfolio of vaults with live status, your deals and your listings — all decrypted from one profile, all in one place.
Coins flow in a loop: store in the Safe, fund a deal in Escrow, sell on the Market — proceeds land back at your desk, and you decide what’s next.
solid — stays on your device dashed — signed or encrypted data crossing the network
Covenant scripts & verification ▸The contracts passed our full on-chain test cycle and adversarial attacks. The covenants are open source and unaudited. Non-custodial — nobody can move your funds but you.
Mainnet, Toccata covenants — live since June 30, 2026. No tokens, no bridges: plain KAS inside covenant scripts.
| Operation | Fee |
|---|---|
| Vault: create · withdraw · cancel · inherit | 0 KAS + network fee |
| Vault alerts & check-in reminders (Telegram) | 100 KAS / yr · 30 d free |
| Escrow: create a deal | free |
| Escrow: release / refund | 0.5 % · min 1.2 KAS |
| Escrow: arbitration (only if disputed) | 2 % · min 5 KAS |
Read the key-security and Sync boundary, inspect the live verification center, then check the open source.
One local profile. Real KAS. Local signatures, covenant-controlled funds and receipts you can verify.