tree(3)

A philosopher

[Pearl Research Labs @prlnet]

The MoE hard fork is now live. Update now!

This upgrade marks the next phase of the Pearl network.

With this hard fork, Pearl transitions to v2 certificates based on Mixture-of-Experts (MoE) workloads, enabling the network to more accurately verify and reward useful AI computation performed by participants.

⚠️ All node operators and ecosystem participants must upgrade to the latest versions to remain on the canonical chain.

Soon, new blocks will start using the v2 (MoE) certificates. Nodes that have not upgraded will continue following the previous ruleset and will no longer be compatible with the upgraded network.

Please update to the following versions:
• pearld node → v1.1.0
• Desktop Wallet → v2.0.0
Wallet download (macOS is now supported):
https://t.co/Bs9aPMDBoX

[Kasmos @KasmosLabs]

De Assets is an L1-native asset platform, built on Kaspa's KCC20 standard (https://t.co/0x3sAyDMwF) and inspired by Bitcoin's CAT20.

We've built a single global order book. Orders live directly on-chain as UTXOs, owned by no platform; assets sit in covenants, with their spending rules enforced by L1 consensus.

Alongside it, we built a browser extension and a web wallet, modeled on Bitcoin's partial-signing standard, BIP-174 (PSBT) so you can sign and spend against covenant dApps.https://t.co/As8eF5MQlY

It's now live on TN10 for open technical testing: https://t.co/ed3SgsatSe
Feedback: https://t.co/c5UdJX7epw

[Kasmos @KasmosLabs]

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.

[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.

[Joe Wong ‎𐤊 🦈 @joewong__]

Bro came

Bro ignored PA

Bro said F bear markets

Bro continue building

Be like bro.

[Yunio 𐤊 @younio1977]

KANet milestone reached.

A timeline + one txid.

Timeline:

2026-01 late
First serious engagement with AI agents
2026-03-12
Self-built relay + adapter went live;
the agent completed its first on-chain message loop via Kasia

2026-04-14
KANet source code published under MIT
2026-05-15
Phase 1 shipped — non-custodial pipeline validated with UMA mirror
2026-06-01
G1 — single-node committee consensus settlement accepted on-chain

2026-06-06
G2 — first cross-node decentralized oracle settlement loop completed on Kaspa testnet
82 days from the first day-1 on-chain loop to G2.

────────────────────
What happened:

The first cross-node decentralized oracle settlement on Kaspa testnet completed end-to-end.
This was not just a submitted transaction.
The settlement TX was accepted into a block.

Settlement TX: 95c84f8a...
Observed in block: a85dacb038e7f711...
Full flow:

Chain-derived pool
→ VRF selected 5 oracle committee members across 2 nodes
→ cross-node votes ingested
→ 4-of-5 consensus reached
→ settlement TX assembled
→ committee members signed
→ SS verification passed
→ settlement TX accepted on-chain
→ oracle members, YES winners, and broker were paid.

This validates a mechanism-level loop:

market
→ oracle committee
→ decentralized resolution
→ signed settlement
→ on-chain payout.

────────────────────

What this means:
KANet has moved from:

“agents messaging on-chain”
to:

“agents participating in market resolution and settlement.”

Agent / Oracle / Broker are no longer only communication participants.
They are becoming on-chain economic participants that can coordinate around a market event, complete adjudication, sign settlement, and distribute value through verifiable on-chain execution.
This is an early glimpse of an Agent Economy.
────────────────────
Important boundaries:
✓ Public testnet demo, not an economic launch
✓ Not mainnet operation, only testnet public validation
✓ KAS amounts are demo values, not real-money market activity
✓ The purpose is to prove the mechanism, not run a product
Also worth stating honestly:
An earlier settlement attempt failed due to a signature / fee-sighash mismatch. The final successful settlement was fixed and closed by J2, while I independently verified the accepted on-chain result.
────────────────────

Not an economic loop.
A mechanism loop.

Not mainnet operation.
Testnet public validation.
Still early. Still testnet.
But the mechanism is no longer just a diagram — it ran.
#Kaspa #KANet #AgentEconomy

[Michael Sutton @michaelsuttonil]

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

[tree(3) @ThreeTreesss]

@OfficialTravlad follow me ! https://t.co/NUMg6msCM4

[tree(3) @ThreeTreesss]

https://t.co/NUMg6msCM4 is now on coingeico https://t.co/mx3FnMBUKg. More features coming soon.

[kascan.io @kaspascan]

https://t.co/fXL81vyJc3 is now labeled as the block explorer of #kaspa @kaspaunchained on Coingeico https://t.co/hYU6Fx4nJc
@coingecko
All setup. More features coming

[Luke Dunshea @elldeeone]

toccata live on testnet 10

[Luke Dunshea @elldeeone]

https://t.co/n1qOT2qd7m has been refreshed.

Kaspa has a lot going on, but the main site does not need to put it all at the front door. Its first job is simple: help someone arrive, understand what Kaspa is, and know where to go next.

The previous site accumulated more over time. Pages, explanations, resources, and audiences were added. This version starts smaller, so it can grow with Kaspa from here.

The refresh is not just visual. The wording, structure, and narrative direction all needed attention IMO.

The content traces back to @hashdag’s writing, simplified for a first read. Kaspa is already deep enough. The first read should not make people work harder than necessary.

There are many true ways to talk about Kaspa, but https://t.co/n1qOT2qd7m cannot carry twenty narratives at once. For this version, the strongest one to unify around is real-time decentralisation.

Part of the refresh was also about making the builder path easier to follow. https://t.co/n1qOT2qd7m gives people the overview of what exists, why it matters, and where to go next. https://t.co/FrgQZdNMey gives builders the deeper material, with room for examples, detail, and ongoing improvement.

https://t.co/FrgQZdNMey starts with @IzioDev's work and has the broader goal of bringing important Kaspa L1 builder documentation into one place.

Both repos are public. Pages will be added, wording will change, gaps will be filled, and the work can happen in the open.

Big shoutout to @kasmediadotcom for their support in helping bring this refresh together.

Have a look around. If you see something that can be better, please open an issue or PR.

[KasSigner @KasSigner]

Second ZK precompile live on Kaspa L1. RISC0 Succinct. TN12 222,668 bytes of STARK proof. One air-gapped signature. On-chain verification.
RISC0 proves execution of arbitrary RISC-V programs, not circuits, not constraints, full programs. The node verifies a succinct receipt over BabyBear. The signer sees none of it. QR relay carries 538 bytes to the device. The other 222KB stays in the browser and gets assembled into the sig_script at finalization.
Two ZK verifiers. Two confirmed TXs. Same covenant framework. Same $15 @KasSigner esp32-s3 chip
Groth16 (BN254): 128 bytes. 14M script units. TX d7e203a1...2380c463 RISC0 Succinct (BabyBear): 222,668 bytes. 25M script units. TX ceac9f02...5b8f3476
#Kaspa #Toccata #KasSigner #Opensource
𝘐𝘯𝘒𝘢𝘴𝘞𝘦𝘙𝘶𝘴𝘵😎🤟🏼

[🌱🅳🄾🅳🄾 哆哆 𐤊｜dodo.kas🍀 @Dodo13080274]

#KRC20 #kaspa $kas $slow
Kinda boring, right? 😅

[KasSigner @KasSigner]

Masive...First zero-knowledge proof transaction ever executed on the Kaspa network. TN12 Not from an L2. Not from a funded team. From an air-gapped hardware signer on a $15 chip.
@KasSigner
🤟🏼 Zero-knowledge proof verified on Kaspa L1. Air-gapped. Funds locked behind a ZK gate. To spend, you prove you know — without revealing what you know. The chain verifies the math. Funds move or they don't. Under the hood: → Groth16 prover (arkworks BN254) compiled to browser WASM → 128-byte proof generated client-side → VK hash-committed in P2SH covenant via BLAKE2B → OP_ZK_PRECOMPILE (0xa6) verifies the pairing on-chain → Air-gapped Schnorr signing via QR relay — signer never sees the proof Three boundaries between the secret and the world. Browser. Device. Chain. Nothing leaks. TX:d7e203a1bec5a8cdede7be0f8ea391ebdf44a946667484f9d515c24a2380c463 No trusted third party. No server. No reveal. Just math. Built on rusty-kaspa Toccata opcodes. 100% open source. https://t.co/r4UWIGNbFh #Kaspa #KasSigner #ZeroKnowledge #Groth16 #Toccata #ZKP

[KaKa @kaka_kaspa]

The crypto market is down, but the Kaspa community is still strong. Even with falling prices, people haven’t left. Loyal supporters keep believing. They’re staying, watching history happen. $Kas

[tree(3) @ThreeTreesss]

@CyberGent_ @kaspacurrency @kaspa_stream Tks bro. I will make the indexer easier to run. The indexer can be synced under 30 mins with local kaspad with pretty crap hardware

[tree(3) @ThreeTreesss]

Shipped https://t.co/NUMg6msCM4 — a super lightweight, fully opensource @KaspaCurrency explorer 🧡
Indexer is in Rust and self-hostable at 40k TPS insertion. @kaspa_stream
https://t.co/SQka8GWSwq
#kaspa $kas

[tree(3) @ThreeTreesss]

@Dodo13080274 @5bb55b https://t.co/SQka8GWSwq

[tree(3) @ThreeTreesss]

@Dodo13080274 @5bb55b I already kinda implemented that.
Check https://t.co/NUMg6msCM4

[Kaspa Eco Foundation (KEF) @Kaspa_KEF]

gj @oneforonehaha

[tree(3) @ThreeTreesss]

#kaspa kaspa:native kaspa indexer-lite is updated with pruner to prune old spam transaction. Goal of Kaspa-indexer-lite is storing useful kaspa info at minimum hardware cost with maximum throughput to handle 100 BPS
https://t.co/SQka8GWSwq