
Kasmos
12 posts


We said the oracle explanation was coming in a follow-up. Apparently that already counts as "long awaited."
So — our sincere apologies for the long-awaited explanation. Here it is.
On oracles: if a chain truly wants to maximize its DeFi safety, the gold standard is paying @chainlink a few million to integrate. Or, for the budget-conscious: a "single TEE-attested node" — the kind already running in a bolt-on L2 lending protocol — for a few hundred dollars a month in server fees. (Just maybe don't run it in us-east-1. It goes down a little too often.)
But here's the thing, and it's common sense to anyone who's actually built one: a binary market needs no price data from an oracle at all. It needs a single bit — did YES happen, or NO. That bit comes from an LP multisig, or a user-bond vote. No feed, no 30-second refresh, no "fair price" to defend. One bit, once, done.
So even in that exact same worst case — a single node:
• Lending reads the price LIVE, on every interaction, with leverage, and the result is irreversible. One bad price mints bad debt and drains the pool. No undo button.
• A binary market touches the oracle ONCE, at a challengeable moment, capped at a single market's open interest — and anyone can merge YES + NO back into collateral and walk away before resolution.
A single point of trust is one thing we will never adopt. The full oracle design is coming with our third product — Touchstone, an optimistic oracle for feeding data to covenants.
English

How Kasmos builds a prediction market on Toccata hard fork
It's not a server, database, or custodial wallet.
It's a set of SilverScript covenants that your own wallet co-spends — rules enforced by every Kaspa node on every transaction.
• CtfVault escrows KAS and splits it into YES + NO tokens. Only the winner redeems.
•YES/NO shares are bound to their own covenant ID.
•Orders + permissionless matching, all fully on-chain.
The real trick: Toccata's covenants (KIP-17 + KIP-20) let a script enforce where funds go and bind tokens to unbreakable rules — all enforced by consensus, with no operator.
A prediction market is just those rules, running on-chain.

English

@brt2412 @mrZeku2000x @Kaspa_Girl @Chris_Hutch7 @realvijayk @kaspador_ @qu1ck_crypt0 Yes, it will be open-sourced this month.
English

@KasmosLabs @mrZeku2000x @Kaspa_Girl @Chris_Hutch7 @realvijayk @kaspador_ @qu1ck_crypt0 Is Kasmos Wallet open source?
English

We're releasing a series of products for Kaspa's Toccata Era.
First Up: Kasmos Wallet — a Covenant++ native wallet.
The uncomfortable truth about Kaspa wallets today — they're one of two things:
• P2PK wallets: send KAS, receive KAS
• EVM wallets: bolted on for an L2
Not one of them can construct a covenant transaction. That's fine today.
After June 30 it's a wall.
Using a covenant app means a wallet has to construct the transaction. Input selection, sighash modes, co-spend, carriers, change, utxo continuation. A different discipline entirely.
We've spent years on application-layer development in the Bitcoin. That's the experience that went into Kasmos Wallet. And we're putting the pattern in working code as a reference, so the whole ecosystem has something to build toward.
It runs on testnet today. The day Toccata activates covenants on mainnet, it's ready.

English

@Kaspacryptoking already building:
x.com/KasmosLabs/sta…
Kasmos@KasmosLabs
Product Two. We’re building a full suite of covenant-native products on Kaspa. This one is a proven category. Will $KAS hit $0.2 this year? You can bet on it. Meet Auspice — a native prediction market based on Kaspa Toccata covenant. No custodians. No bridges. No L2. No extra token. Collateral sits in the market’s own covenant. Payouts are enforced by consensus, not promises. You trust code and covenants. Not us. Live end-to-end on TN10 today. Mainnet the moment covenants land. Read the signs. Trade the morrow.
English

kaspa:native The Toccata hard fork is officially scheduled for mainnet activation on June 30th.
Most people still think Kaspa is just a fast proof-of-work payment network. This is going to completely change that narrative. With native Layer 1 covenant support, we are bringing programmable smart contract functionality directly into the base layer. This isnt just an upgrade, its a fundamental shift in what Kaspa can do. The narrative is about to flip. Study #Kaspa #CryptoMarket #Crypto #Cryptonews

English

Product Two.
We’re building a full suite of covenant-native products on Kaspa. This one is a proven category.
Will $KAS hit $0.2 this year? You can bet on it.
Meet Auspice — a native prediction market based on Kaspa Toccata covenant. No custodians. No bridges. No L2. No extra token.
Collateral sits in the market’s own covenant. Payouts are enforced by consensus, not promises.
You trust code and covenants. Not us.
Live end-to-end on TN10 today. Mainnet the moment covenants land.
Read the signs. Trade the morrow.
English
Kasmos retweetet

Kaspa Toccata mainnet process update:
Today we plan to publish the v1.3.0 mainnet pre-release, without activation, for 1–2 days of broader network sanity testing.
Assuming everything looks good, the following release will be v2.0.0, with activation planned for June 30, 4 weeks from today
Michael Sutton@michaelsuttonil
👀
English

@michaelsuttonil @OriNewman @Max143672 @IzioDev @coderofstuff_ @hus_qy @manyfest_ @asaefstroem @Tiram_88 @smartgoo_ Congrats 👏
English


In just days, Kaspa flips the switch on Toccata — native covenants (KIP-17/20), ZK verification opcodes (KIP-16), sequencing commitments (KIP-21), and the SilverScript compiler. World-class engineering. Real programmable Proof-of-Work. But let me ruin the party real quick
Covenants aren’t new. Bitcoin has been arguing about them for years — OP_CAT, every proposal imaginable. The outcome? Still zero Ethereum-sized ecosystem. A more powerful primitive doesn’t magically create a stronger ecosystem.
Here’s what the countdown won’t tell you: Toccata ships the engine. It does not ship the car, the roads, or the drivers. Opcodes are ~10% of the work. The remaining 90% — indexers, wallets, UTXO co-spend, tooling, docs — is still 100% on the community.
Native ZK at L1 is genuinely incredible. But verifier opcodes don’t write circuits for you. Who’s building the proving systems? With what tooling? For which users? Power that nobody can actually use is just a fancy press release.
The uncomfortable truth: Kaspa still has very few real ecosystem developers. What currently gets called “the ecosystem” is mostly chat apps stuffing data into OP_RETURN-style payloads. That’s not a dApp. Toccata raises the ceiling. It doesn’t raise the floor.
So here’s what will happen in the next few weeks: The fork activates perfectly.The chart might pump.And then most people will realize… there’s still almost nothing to actually use. Because building anything meaningful is still brutally difficult. The hard fork isn’t the finish line.
It’s the starting line.
The real question was never “Does Kaspa have covenants?” It’s: Can a normal developer ship a real app in a weekend without building everything from scratch first? Answer that question correctly → Kaspa wins.
Fail to answer it → Toccata becomes a beautiful engine sitting in an empty garage. June 20 is the beginning, not the end. #Kaspa $KAS
English


