HIGH TABLE PROTOCOLTruth Markets on Kaspa
Kaspa Testnet
Not connected
DAA: -

Create events.
Challenge lies.
Settle on the DAG.

Non-custodial prediction and skill markets enforced by covenants on Kaspa. Full exposure or built-in downside protection. Resolved by ZK proofs and bonded oracles directly on the BlockDAG.

Non-custodial
2% on winnings only
50% loss cushion
1,000 KAS bond
ZK oracles

LIVE KASPA BLOCKDAG

Block Rate 10 BPS Finality ~10s Confirmation ~1s Consensus GHOSTDAG
--
Total Pool (KAS)
--
Active Markets
--
Positions Taken
--
Avg Payout
~1s
Confirmation

Trending Markets

Highest pool volume right now.

How it works

Five steps from wallet to payout.

1

Connect

Link your Kaspa wallet. Your keys, your funds. Non-custodial from the start.

2

Choose or Create

Browse open markets or create your own with a 1,000 KAS creator bond.

3

Take a Position

Spot for full exposure. Maximizer for a built-in safety net that rebates 50% on loss.

4

Oracle Resolves

ZK proof over external feeds, or bonded human attestation with a challenge window.

5

Get Paid

Winners split the pool pro rata. 2% fee on winnings only. Settled direct to wallet.

Settlement
Kaspa L1
Consensus
GHOSTDAG / DAGKnight
Contracts
KIP-10 Covenants
Proof
Pure PoW (kHeavyHash)

Events

Parimutuel information markets and skill events on Kaspa.

Create an Event

Define your market. Set outcomes, source, timing, and upload a market image.

Select a date to see estimated DAA score
Determined by Oracle Type above

Minimum bond required. Higher bond = more trust signal. Slashed if resolution challenged and proven wrong.
Primary: resolver submits result with Groth16 proof -- covenant verifies in one tx. If unchallenged for 1 hour, outcome finalises. No human judgment needed.
20%20% cap
Maximizer cap = max(expected, actual) × cap%. Soft floor only. Once actual volume exceeds expected, the cap scales with it. Example: 10% cap, 100K expected → 10K maximizer pool. When actual reaches 200K, cap auto-grows to 20K. Set cap to 0% to fully disable maximizers.
Click or drag to upload
Click to upload your event image
Upload Your Image Replaces the default image
CUSTOMIZE YOUR EVENT

Your event question

20%
Max cap
2%
Fee
1,000
Bond
Live Covenant Preview
Every field above auto-generates the covenant code below. Edit the code and Deploy to push changes back to the form.

SilverScript Sandbox Live

Write covenant logic that compiles to Kaspa lock rules. Use examples below or write from scratch.

SilverScript Ln 1, Col 1
Compiler Output Ready
Write SilverScript and click Compile, or press Ctrl+Enter.

Skill Games

Stakes locked in a Kaspa covenant. Play. The covenant enforces the result. No arbiter. No dispute. Winner takes the pool minus 2% protocol fee.

Open Matches 0 matches
Chess

Every move validated on-chain. Full FIDE rules. Covenant enforces checkmate, stalemate, and time control. No trust required.

Covenant EnforcedTime ControlsSeries Play
Connect 4

Classic vertical drop game with on-chain stakes. Every disc verified by the covenant. Four in a row wins the escrow.

Covenant EnforcedFast Games
Checkers

On-chain checkers with full replay proof. Multi-jump captures and king promotions verified by Kaspa covenants.

Covenant EnforcedMulti-Jump
Tic-Tac-Toe

Simple, fast, provably fair. Every X and O recorded on-chain. Instant covenant settlement on three in a row.

Covenant EnforcedInstant
A♥ K♠ Q♦ J♣ 10♥
Texas Hold'em

Heads-up Texas Hold'em with covenant escrow. Hidden hands committed via hash; reveal on showdown. Winner takes pool minus 2% fee.

Covenant EnforcedHeads-UpCommit-Reveal
BLACKJACK · 21 A K 10 5 21 BUST
Blackjack

P2P heads-up. Closest to 21 without busting wins. No house, no dealer. Card draws committed on-chain via shared seed.

Covenant EnforcedNo HouseP2P

Match Lifecycle

Trustless 5-step flow: escrow lock · opponent match · on-chain play · proof verification · settlement

Create
Lock escrow on-chain
Accept
Opponent matches escrow
Play
Moves synced on-chain
Verify
Covenant verifies proof
Settle
Winner paid instantly

Bonded Oracle Network

Decentralized oracles secured by economic stake and ZK proofs. Stakers attest real-world outcomes to settle prediction markets. Honest oracles earn fees. Dishonest ones get slashed.

247
Active Oracles
1,000
Bond Required (KAS)
3-of-N
Threshold Consensus
~2 min
Avg Resolution Time

Resolution Pipeline

1
Event Created
Market opens for
bonded resolution
2
Registration
Oracles bond
1,000 KAS min
3
ZK Proof
Groth16 verifies
attestation data
4
Consensus
3-of-N oracles
must agree
5
Settlement
On-chain payout
+ fee distribution

Become an Oracle

Stake 1,000 KAS to join the oracle network. Earn 2-5% fee on every market you help resolve. Your bond proves economic alignment — if you attest honestly, you profit. If you lie, you lose your stake.

Dispute Mechanism

Any bonded oracle can challenge a resolution within a 24-hour dispute window. The challenger posts a counter-bond equal to the original oracle's stake. Both bonds are locked until the dispute is resolved by a larger oracle quorum (5-of-N). The losing party forfeits their bond — 50% to the winner, 50% burned.

Slashing Conditions

Oracles are slashed when:
• Dispute resolution rules against them
• ZK proof verification fails on-chain
• 3+ oracles attest differently (consensus failure = all slashed)
• Evidence hash mismatch detected by miner

Slashed KAS is distributed: 60% to challenger, 30% to protocol treasury, 10% burned.

Your Oracle Dashboard

0
My Bond (KAS)
0
Resolved
0
Earned (KAS)
0
Slashed
-
Accuracy

Markets Awaiting Resolution

Portfolio

Skill game matches and event market positions. Payouts settle automatically on-chain.

P&L (KAS)
0
Open Positions
0
Won
0
Lost
0
Matches
0
Claimable (KAS)
0
W/L
0/0
Earnings
0 KAS

No active matches.

Create or join a match

Wallet

Connect via extension or enter your address. Supports TN12 testnet and mainnet.

KasWare

KasWare

Kastle

Kastle

Kasanova

Kasanova

Kaspium

Kaspium

KaspaCom

KaspaCom

DEX.cc

DEX.cc

Custom Node

Connect to your own Kaspa node for dedicated access. Defaults to public resolvers if empty.

Generate Mnemonic

12 or 24-word seed. Back it up.

Click above to generate.

Connect via Mnemonic

Connect via Private Key

Import a raw 32-byte hex private key (64 hex characters). Never share your private key.

Why Kaspa

The BlockDAG that High Table Protocol settles on.

Want to run an oracle node?
Stake KAS, connect your node, and earn fees by resolving markets on-chain.
Built for Speed. Secured by Proof of Work.

Kaspa is the only Layer 1 that runs a BlockDAG consensus at 10 blocks per second while maintaining the security guarantees of Nakamoto-style proof of work. No staking. No validators. No premine. Every block counts.

LIVE KASPA BLOCKDAG

LIVE

BlockDAG Architecture

Unlike a blockchain where one miner wins per round, Kaspa allows all miners to contribute blocks simultaneously. GHOSTDAG consensus orders them into a directed acyclic graph without orphaning any honest work. More miners means more throughput, not more waste.

Sub-Second Confirmation

Transactions confirm in under 1 second. Full probabilistic finality in roughly 10 seconds. At the 100 BPS target on the roadmap, the network will process over 30,000 transactions per second while every node validates every block.

Pure Proof of Work

Kaspa uses kHeavyHash, an optical-mining-friendly algorithm. No staking, no delegation, no foundation-controlled validators. Fair launch in November 2021 with zero premine, zero allocation, and zero insider advantage.

Why High Table Needs This

Prediction markets and skill games require fast settlement, cheap transactions, and hard finality. Kaspa delivers all three without sacrificing decentralization. Covenants enable trustless escrow and automated resolution directly on the DAG.

10 BPS
Block Rate
~1s
Confirm
~10s
Finality
28.7B
Max Supply
0
Premine
PoW
Consensus

Covenants on Kaspa

Kaspa covenants are programmable spending conditions enforced at the UTXO level. They allow contracts to lock funds, define resolution rules, and release value automatically when conditions are met. High Table Protocol uses covenants to build trustless escrow for every market and every match. Funds are locked when a position is taken and released when the outcome is resolved. No intermediary holds your money at any point.

Kaspa Timeline

November 7, 2021
Mainnet launch. Fair launch, zero premine, zero ICO. Mining begins at 1 BPS on Go-based kaspad.
2022
Community dev fund launched. First exchange listings. DAGKnight research begins (Sompolinsky, Sutton). Chromatic emission decay active.
2023
Rusty Kaspa alpha released April 2023. Full rewrite from Go to Rust. Wrapped KAS (wKAS) on ETH, Polygon, BNB. Major exchange listings.
2024
TN11 running at 10 BPS since early 2024. Rust nodes integrated on mainnet. Gradual Go-to-Rust migration across the network.
May 5, 2025
Crescendo hard fork activates 10 BPS on mainnet. Complete Rust codebase live. Kaspa becomes the fastest pure PoW chain.
Late 2025
DAGKnight prototype operational on devnet. TN12 testnet launched. vProgs yellow paper published. Covenant opcodes (KIP-10) spec finalized.
2026 (Current)
Covenants hard fork targeted Q2 2026. DAGKnight mainnet activation targeted mid-2026. 25-40 BPS on roadmap for end of Q3.
2027+
100+ BPS target. Full vProgs smart contract layer. SilverScript compiler. ZK verification opcodes.

Research Papers

PHANTOM GHOSTDAG
Sompolinsky, Wyborski, Zohar. A scalable generalization of Nakamoto consensus.
DAGKnight
Sompolinsky, Sutton. A parameterless generalization of Nakamoto consensus.
vProgs Yellow Paper
Kaspa virtual programs. Covenant execution layer enabling smart contract logic on Kaspa.
SPECTRE
Sompolinsky, Lewenberg, Zohar. A fast and scalable cryptocurrency protocol using BlockDAG voting.
Kaspa Emission Schedule
Fair launch, no premine. Chromatic phase-based geometric decay to 28.7B total supply.
Bitcoin's Security Model Revisited
Sompolinsky, Zohar. Revisiting security guarantees under realistic network conditions.
Optimal Selfish Mining Strategies in Bitcoin
Sapirshtein, Sompolinsky, Zohar. Formal analysis of selfish mining attacks and profitability thresholds.
Yonatan Sompolinsky on Medium
hashdag.medium.com. Origin stories, launch plans, vision series, post-mortems, and the philosophy behind Kaspa.

Terms, Conditions & Risk Disclosure

Please read carefully before using High Table Protocol.

1. Nature of the Protocol

High Table Protocol (“HTP”) is a non-custodial, decentralized prediction market interface built on the Kaspa BlockDAG. HTP provides a front-end to interact with covenant-enforced smart contract logic deployed on Kaspa Layer 1. HTP is not a company, corporation, partnership, or legal entity. It is open-source protocol software.

2. No Custody, No Intermediary

HTP never takes custody of your funds. All positions are held in Kaspa UTXO covenants enforced at the consensus level. You connect your own wallet and sign your own transactions. There is no fiduciary relationship. The protocol is the counterparty.

3. Parimutuel Market Mechanics

All markets operate as parimutuel pools. Stakes on each outcome accumulate into a shared pool. Upon resolution, the pool (minus protocol fees) is distributed pro-rata to the winning side. Payouts depend on your stake relative to total winning-side stakes, not on fixed odds at entry. Displayed multipliers are estimates that change as new stakes enter.

4. Trading Modes

Spot Mode: Full upside, full downside. If your outcome wins, you receive your pro-rata share minus a 2% fee on profit only. If you lose, you lose your entire stake.

Maximizer Mode: Same upside as Spot. On loss, 50% of your stake is rebated. 30% of the rebate amount is charged as an insurance fee. Net loss ~65% of stake vs 100% in Spot.

5. Market Creation & Creator Bonds

Anyone can create a market by posting a 1,000 KAS creator bond locked in a covenant until resolution. If the market resolves cleanly, the bond is returned. If flagged as spam, manipulative, or unresolvable, the bond is slashed via dispute. Creators set the question, source, category, and closing time. Creators do not set odds.

6. Oracle & Resolution

ZK-Verified (Primary): ZK proofs over external data feeds verified on Kaspa. Trustless, deterministic.

Bonded (Fallback): Human attestors post bonds and submit outcomes. A challenge window (24-72h) allows disputes via counter-bonds. Incorrect attestors are slashed. Once the window closes without dispute, the outcome is final and the covenant distributes the pool.

7. Fee Structure

All fees are protocol-level, immutable, and enforced by covenant logic.

  • Spot fee: 2% on profit only. No fee if you lose.
  • Maximizer insurance fee: 30% of the 50% loss rebate (~15% of losing stake).
  • Creator bond: 1,000 KAS, refundable on clean resolution.
  • Attestor bond: Minimum 500 KAS, slashed on incorrect attestation.

No withdrawal fees, deposit fees, or hidden charges.

8. Risk Disclosure

Total loss: Spot: 100% loss possible. Maximizer: ~65% loss possible. Do not stake more than you can afford to lose.

Smart contract risk: Covenants are immutable once deployed. No admin key, no pause, no upgrade path for live markets.

Oracle risk: Bonded escalation mitigates but does not eliminate incorrect resolution.

Network risk: Congestion, forks, or consensus failures could delay settlement.

Regulatory risk: Prediction markets may be regulated in your jurisdiction. You are solely responsible for compliance.

Liquidity risk: Low participation may result in unfavorable odds.

9. User Responsibilities

  • You are solely responsible for wallet security, private keys, and seed phrases.
  • You are responsible for determining legality in your jurisdiction.
  • You understand parimutuel mechanics and the difference between Spot and Maximizer.
  • You accept that multipliers are estimates and payouts depend on final pool composition.
  • All transactions are final and irreversible once confirmed on Kaspa.

10. No Warranty

HTP is provided “AS IS” without warranty of any kind. No representations regarding accuracy, reliability, or completeness. Use at your own risk.

11. Limitation of Liability

In no event shall developers, contributors, or associated parties be liable for any direct, indirect, incidental, special, or consequential damages arising from use of HTP, including loss of funds, data, or profits.

12. Dispute Resolution

On-chain disputes are resolved through bonded escalation (Section 6). There is no customer support, refund mechanism, or appeals process beyond the on-chain challenge system.

13. Amendments

Protocol-level rules are immutable once deployed. Interface-level terms may be updated. Continued use constitutes acceptance. Deployed covenants are unaffected by interface changes.

14. Governing Framework

HTP operates as decentralized open-source software not governed by any specific jurisdiction. Users are responsible for compliance with local laws.

15. Oracle Attestation and Bonding

A minimum bond of 5,000 KAS is required to become an oracle operator. Attestations are Kaspa transactions with a signed payload containing the market ID, outcome, and evidence hash. A 24-hour dispute window follows each ZK confirmation. Bonds are slashed upon successful challenge.

The browser daemon requires the tab to remain open; a Node.js equivalent is available for persistent operation. HTP is not responsible for the accuracy of external API data; operators bear sole responsibility. Oracle earnings are distributed from a percentage of the 2% protocol fee pool.

16. Skill Game Covenants

Escrow is locked on-chain when a match is created. Both players must deposit within 24 hours or the creator is refunded. All move validation is performed client-side against deterministic rules (chess.js for chess). The covenant enforces winner payout with no human arbiter. A 2% protocol fee is deducted from the gross pot.

Timeout: if a player's clock hits zero, the opponent wins and the covenant settles immediately. Resign: treated as a loss; the opponent receives the net payout via covenant.

17. SilverScript Covenant Tool

The sandbox auto-generates covenant code from the Create Event form for transparency. Compiled code is not submitted on-chain until "Compile + Deploy" followed by "Create Event". Custom modifications are at the user's own risk; HTP makes no guarantees. The sandbox is a developer and inspection tool, not required for normal event creation.

18. Data and Privacy

Node REST URLs are stored in localStorage only and are never transmitted to HTP servers. Wallet mnemonics never leave the browser; all signing occurs in WASM via the kaspa-wasm SDK. Oracle daemon logs are in-memory only; they are not persisted or sent externally.

Firebase Realtime Database stores market metadata, positions, and match state. Private keys and seed phrases are never stored in Firebase or any external database.

Last updated: April 1, 2026. By connecting a wallet or entering a position, you acknowledge acceptance of these terms.