TL;DR: 

• Toccata feature freeze reached; TN12 relaunched: Michael Sutton confirmed the consensus feature freeze and TN12 restart with finalized updates, marking the transition from development to testing ahead of mainnet activation.

• Node upgrade path improved ahead of fork: PR #956 introduced backward compatibility for existing node data, reducing the need for full resyncs during Toccata upgrades.

• ZK and cross-chain primitives demonstrated on testnet: KasSigner executed ZK-based transactions and added SHA-256 hash lock support, enabling early experimentation with on-chain verification and atomic swaps.

• Kaskad advances toward mainnet with audit and open-source oracle: The protocol completed its Sherlock audit and open-sourced its “Nuntius” oracle system for multi-source, TEE-secured price delivery.

• Execution-layer and tooling development expands: Igra published documentation outlining its MEV mitigation model, while new tools like go-kaspabook and MyKAI integrations aim to simplify development and node operation.

Toccata Testnet Freeze Initiated 

On April 30, 2026, Michael Sutton submitted a series of commits ahead of the Testnet 12 (TN12) feature freeze for the Toccata hard fork, including updates to txscript limits, TN12 genesis configuration, and script pricing. He shared: 

“Toccata consensus feature freeze is finally here after a heroic last-mile push by kas core devs.”

The freeze marks the cutoff point for new consensus-level changes ahead of the planned mainnet activation window, shifting focus toward stabilization and testing.

On May 1, 2026, TN12 was relaunched to incorporate the finalized Toccata features. Sutton outlined the update set:

“• KIP-21 sequence commitment support

• Updated script pricing

• Script engine additions and improvements, including OpCheckSigFromStack and non-minimal encoding support

• Additional consensus and node improvements from the Toccata development branch.“

Existing TN12 node operators can update in place by pulling the latest code from the tn12 branch, with no local data directory reset required. Miners should update to at least cpuminer v0.2.7, which Sutton listed as the minimum supported version for TN12.

Toccata Preparation: Database (DB) Compatibility Added for Node Upgrades

PR #956 (“aDBptation”) was merged into the Toccata development branch of Rusty Kaspa, introducing backward compatibility for previously stored node data, a key step in preparing for the Toccata hard fork.

The update allows post-Toccata nodes to read data written by pre-Toccata nodes, enabling compatibility between legacy and updated data formats and reducing the need for disruptive database resets during upgrades. In practice, this means node operators can upgrade without needing to delete and rebuild their local data from scratch.

This change is part of ongoing preparation for the Toccata activation, focusing on smoother node transitions and minimizing friction for operators as consensus and data structures evolve.

KasSigner Demonstrates ZK Transactions and Atomic Swap Primitives on TN12

KasSigner, an open-source, air-gapped hardware signing device for Kaspa, reported multiple testnet demonstrations on Testnet 12 (TN12), including what it described as the first zero-knowledge (ZK) proof-based transaction executed on the Kaspa network.

The initial test used a Groth16 verifier, where funds are locked behind a condition that can only be satisfied by proving knowledge of a secret without revealing it. Groth16 proofs are compact and efficient, but require the computation to be expressed as a predefined circuit. Verification was performed on-chain via the OP_ZK_PRECOMPILE opcode, with proof generation occurring client-side and signing handled through an air-gapped device.

In a follow-up test, the project demonstrated a second ZK verification flow using RISC0 Succinct, a STARK-based system capable of proving execution of general-purpose programs compiled to RISC-V, rather than fixed circuits. This expands the scope of what can be verified on-chain from specific logic to arbitrary program execution.

Separately, the project reported support for cross-chain atomic swap primitives:

“KasSigner now supports SHA-256 hash locks — the same standard used by Bitcoin, Ethereum, Litecoin, and many other chains.”

This enables transactions where assets can be exchanged across different blockchains without intermediaries, using a shared cryptographic condition enforced on both sides of the swap.

Both implementations use air-gapped signing and are fully open source, with no reliance on external servers.

The demonstrations are experimental and were conducted on testnet using Toccata features not yet active on mainnet.

Together, they highlight early experimentation with programmable transactions, zero-knowledge verification, and cross-chain coordination on Kaspa.

Igra Publishes MEV Model Documentation for Integrators

Igra Labs released a new documentation page outlining its approach to mitigating maximal extractable value (MEV), aimed at developers, exchanges, and infrastructure partners. They shared:

“Igra has structural properties that make the most common MEV attacks (sandwiching, front-running, oracle manipulation) significantly harder than on Ethereum or single-sequencer L2s.”

The design relies on Kaspa L1 for transaction ordering, where no single actor can deterministically control sequencing without majority hashrate. Unlike Ethereum-style systems, Igra does not use a centralized sequencer or a persistent public mempool, reducing the effectiveness of timing-based attacks.

Under this model, MEV extraction becomes probabilistic rather than guaranteed, with outcomes dependent on network conditions rather than privileged access to ordering. This positions Igra’s approach as a shift from deterministic, operator-controlled MEV toward a more distributed and less predictable extraction environment.

Kaskad Open-Sources “Nuntius” Oracle Design Ahead of Mainnet

Kaskad introduced “Nuntius” (Latin for “messenger”), an oracle system created by Eliott Mea, with its oracle codebase now open-sourced ahead of mainnet.

Designed as a permissionless, TEE-secured system for delivering verifiable price data on-chain, Nuntius acts as a trusted bridge between off-chain market data and on-chain applications.

The system aggregates price data across multiple trading venues to derive a consolidated value, aiming to reflect broader market conditions rather than relying on a single source. This increases the cost of manipulation, as influencing the oracle would require coordinated activity across multiple markets.

Price computation is executed inside a Trusted Execution Environment (TEE), where outputs are generated and signed in an isolated environment that prevents operator tampering.

The system is designed to be permissionless and extensible, allowing anyone to run a node or integrate the oracle with custom data sources.

It supports both push-based updates and pull-based access, enabling different integration models depending on application requirements.

SEC Chair’s Remarks focus on Crypto

SEC Chairman Paul S. Atkins used keynote remarks at the Economic Club of Washington (a nonprofit organization of government officials, economists, Fortune 500 leaders created to further the collaboration amongst global leaders) to highlight a shift in U.S. regulatory posture toward digital assets, framing crypto as a priority area for modernization:

“As I have stated, to advance our regulatory posture is to bring it into honest alignment with the world as it is, rather than as it was when many of our rules were first written. After all, innovation rarely pauses for regulation. And perhaps nowhere has the cost of failing to keep up been more apparent than in the agency’s treatment of crypto assets.”

He highlighted the progress the agency has made in regards to crypto, from creating the Crypto Task Force, Project Crypto, and creating a five level crypto taxonomy. He also flagged the imminent release of an “innovation exemption” for market participants  

The remarks positioned crypto within a wider regulatory overhaul focused on reducing friction, clarifying jurisdiction with the CFTC, and reversing what Atkins described as prior enforcement-driven oversight that pushed innovation offshore.

In a separate op-ed in the Washington Examiner, Atkins reflected on his first year as Chairman, describing a move away from prior enforcement-led approaches toward rulemaking and regulatory clarity. 

He stated that the SEC, in coordination with the Commodity Futures Trading Commission through Project Crypto, is working to align regulatory frameworks, reduce overlapping requirements, and define clearer jurisdictional boundaries.

He closed the essay with : “America’s capital markets must continue to mirror the character of our nation — dynamic, deep, and unrivaled in their ability to convert innovation into opportunity. That has long been their promise. And in this new day at the SEC, it is a promise that they will continue to keep.”

Kaskad Completes External Audit Ahead of Release

Kaskad, a lending protocol under development on Kaspa’s Igra L2 network, reported that its external audit with Sherlock has been completed, covering its custom incentive and governance code. Sherlock has previously audited crypto protocols such as Aave and Maple.

The audit identified 9 high, 8 medium, and 4 low/informational issues, all of which are reported in the audit as either fixed or acknowledged, with no outstanding unaddressed items.

The audited codebase has been made publicly available, marking a step toward deployment readiness and external review as the project progresses toward mainnet.

go-kaspabook Introduces Indexed Data Layer for Kaspa Integration

A new project, go-kaspabook, was introduced as a lightweight data access layer for Kaspa, providing a REST API designed for backend services, exchanges, and application infrastructure.

The system indexes chain data locally using RocksDB, with support for pruning, reorg handling, and query paths for blocks, transactions, and addresses, while also exposing select passthrough endpoints to kaspad for real-time data.

For context, tools like this simplify how applications interact with blockchain data, enabling structured queries for wallets, dashboards, and exchange systems without requiring direct parsing of raw node data. This lowers the complexity and infrastructure requirements for teams building applications on Kaspa.

The project is in early development, with the author noting it has been under active work for approximately 10 days and is not yet production-tested. It is intended for backend use and not as a public browser-facing API.

KasMap Integrates MyKAI for One-Click Node Setup

KasMap introduced a new integration with MyKAI aimed at simplifying node deployment and monitoring for non-technical users. Users can add a node in these simple steps: 

The integration links a user’s node to their KasMap profile through a token-based setup process between the two applications, enabling basic configuration without manual node management.

MyKAI provides a one-click installer (currently Windows) that automatically sets up and runs a full Kaspa node in the background, with initial sync taking several hours. Once connected via token, users can track node status directly through KasMap, with future plans to visualize nodes geographically.

The integration focuses on reducing the complexity of running a node, highlighting ease of deployment as a factor in broader network participation.

Kii Signals Completion of L1-Native Project Suite Ahead of Deployment

Kaspa Industrial Initiative Foundation, Kii, a Kaspa-focused development team, reported that its primary development efforts are nearing completion, with multiple flagship projects built to run directly on Kaspa Layer 1.

Remaining work is focused on security hardening and migration to enterprise infrastructure, indicating the projects are moving toward a deployment phase.

While specific details have not been disclosed, the emphasis on L1 execution aligns with broader ecosystem efforts to build directly on Kaspa’s base layer as programmability features advance. No formal launch timeline has been announced.

Parker Schmidt Launches “Kaspa Explained” as Structured Research Reference

Parker Schmidt (@parker2017) introduced kaspaexplained.com, an independent resource aimed at improving how Kaspa is understood by both humans and LLMs.  Schmidt shared: 

“This is a first step toward a cleaner, more level-headed public reference that Google and LLMs can hopefully start picking up over time.”

The site organizes Kaspa into clearly separated layers including live features, near-term upgrades, roadmap, and research, while emphasizing a non-hype framing of the protocol as a Proof-of-Work blockDAG evolving toward verification-based programmability. It also highlights gaps in current public information, particularly where LLM outputs flatten technical distinctions or rely on low-quality sources.

The project is presented as an open, early-stage reference resource rather than a protocol or development initiative.

KBeam Demonstrates AI + NFC Payment Flow on Kaspa

The KBeam application, a messaging platform incorporating file sharing and payments, shared details on its architecture and ongoing feature development:

“Kaspa is used as a sequencer and as a central security layer. Some parts are on-chain. Other parts are securely encrypted and stored on servers. You can configure that yourself in the app. You can also use your own servers. It’s like a decentralized WhatsApp with voice messages, videos, photos, files, and I’m currently integrating NFC payments.”

Community testing also highlighted an early payment flow that converts standard PDF invoices into Kaspa transactions:

“I simply threw a normal PDF invoice into my test POS system… The AI pulled all the data, recognized everything perfectly, and turned it into a Kaspa payment via NFC in seconds!

Contactless, straight on the phone — and it works with every invoice.

No more filling out bank transfer forms. Never again.”

The system uses AI to extract invoice data and initiate contactless payments via NFC, with the stated goal of supporting full merchant workflows including invoicing, exchange rate handling, and reporting.

The implementation remains in early-stage testing and reflects ongoing experimentation with user-facing payment infrastructure on Kaspa. 

Zealous Swap Executes First ZEAL Burn, Initiates Monthly Cycle

Zealous Swap reported its first ZEAL token burn on May 2, 2026, removing 699,813 ZEAL from circulation and marking the start of its recurring buyback-and-burn mechanism.

The model, outlined ahead of IGRA mainnet launch, uses two revenue streams to fund the mechanism. A portion of DEX activity across Kasplex and IGRA L2s is allocated toward ZEAL buybacks, while 100% of revenue from Zealous Memberships is burned directly. All burns are executed on IGRA regardless of where the revenue originates. As shared by the Zealous team:

“The logic is straightforward: as Zealous Swap usage grows and more users adopt memberships, more ZEAL gets removed from supply. Protocol success directly impacts circulating supply.”

The team indicated this will now continue on a monthly cadence, positioning supply reduction as a function of actual protocol usage rather than fixed emissions or incentives.

Community Resources: Visual Guides Simplify Kaspa Concepts

A community-created visual guide titled “Kaspa Whitepaper for Kids,” shared by Travladd (@OfficialTravlad), offers a simplified, illustrated breakdown of Kaspa’s core concepts, including BlockDAG structure, GHOSTDAG ordering, and scaling design.

A separate community contribution by @Ashishrathodind presents an interactive explainer video focused on the Toccata hard fork, outlining expected network changes in a beginner-friendly format.

Together, these resources reflect ongoing community efforts to make Kaspa’s architecture and upcoming upgrades more accessible to non-technical users.

Third-Party Essay Explores Kaspa’s BlockDAG Design

A long-form post by BankQuote offers a narrative overview of Kaspa’s design and evolution, from early GHOST-based research through to its current BlockDAG architecture. He shared:

“The core idea was not to abandon Proof-of-Work, but to stop forcing it into a narrow linear pipe. If honest miners produce valid blocks in parallel, those blocks should not become waste. They should be included, ordered, and converted into ledger progression.”

He also emphasized the broader implications of this design approach:

“That is why Kaspa is misunderstood when viewed only through TPS. The deeper point is not capacity alone. Kaspa reduces the impedance between distributed mining and ledger finality. It lets Proof-of-Work breathe across parallel topology instead of forcing every miner through a single-file checkpoint.”

The piece presents a high-level interpretation of Kaspa’s approach to parallel block production and is best read as a conceptual overview rather than an official or developer-sourced specification.

Stablecoin Payment Infrastructure Expands Across Platforms and Legacy Rails

Meta and Stripe introduced USDC payout support, enabling stablecoin-based payments for users and creators, while Western Union unveiled USDPT, a new digital settlement rail for cross-border transfers.

Together, the developments reflect continued movement toward stablecoin-based payment and settlement systems across both consumer platforms and traditional financial infrastructure, with major firms testing blockchain-based alternatives to existing payout and cross-border rails.