Igra Multitude Turns Kaspa Into Sovereign EVM Infrastructure

Finance teams that want dedicated on-chain infrastructure but don't want to run their own chain stack now have a new option — and it's anchored directly to Kaspa's proof-of-work ordering. On June 30, 2026, Igra Labs announced Igra Multitude, a product designed to let applications launch their own EVM execution environments using Kaspa's BlockDAG as the sequencing layer. The announcement arrived on the same day Toccata, Kaspa's covenant-activating protocol upgrade, went live.

For Kaspa holders and PoW miners, this is worth paying attention to. It is one of the first concrete examples of Kaspa evolving from a standalone L1 into infrastructure that other chains build on top of — without handing ordering power to a centralized operator.

source

What Igra Labs Actually Built

Two years ago, according to Igra Labs, the team formed around a thesis: combine Bitcoin-style proof-of-work ordering with the programmability of modern smart-contract chains. That thesis is now running in production. Igra Network, their EVM-based rollup, has been live on mainnet for four months as of the announcement date.

The key technical claim is structural, not aspirational. Igra uses Kaspa's BlockDAG proof-of-work consensus for transaction ordering. That means:

• No provider-run sequencer. The typical L2 model hands ordering authority to a single entity — the sequencer operator — which creates a single point of trust, censorship, and MEV extraction. Igra's architecture removes this entirely.
• No global public mempool to monitor. On most chains, pending transactions sit in a publicly visible pool, giving sophisticated actors time to front-run, sandwich, or otherwise extract value from ordinary users. Igra states that its architecture eliminates this surface.
• Ultra-fast BlockDAG ordering. Kaspa's BlockDAG structure compresses the time window between transaction submission and inclusion, which in turn narrows the opportunity for MEV extraction and selective censorship.

The hashrate backing Igra's state is reported at approximately 350 PH/s — a figure drawn from Kaspa's own proof-of-work network. Fifteen community attesters provide an additional validation layer by agreeing on Igra's state transitions.

What's Already Running on Igra

Igra isn't an empty network waiting for its first app. According to Igra Labs, the following protocols are already live:

• Zealous and Kaspacom — trading applications
• Kaskad — a lending and liquidations protocol
• Other teams building on the network (not named individually in the announcement)

These are finance-native applications — trading, lending, liquidations — the exact use cases where ordering fairness matters most. A centralized sequencer operator could, in theory, reorder liquidation transactions or front-run large trades. By anchoring ordering to proof-of-work rather than an operator, Igra's existing apps inherit a stronger structural guarantee against that class of risk.

Igra Multitude: Dedicated Chains Without Running a Chain

The bigger news is Multitude. Igra Labs describes it as a way for finance applications, settlement systems, and appchain teams to launch dedicated EVM execution environments with:

• Lower setup cost compared to running independent chain infrastructure
• Dedicated throughput (not shared with other applications on the network)
• Reduced ordering and MEV capture risk, inheriting Kaspa's PoW-based sequencing

In practical terms, Multitude appears to let a team spin up its own EVM-compatible execution environment — with custom rules, custom gas economics, and custom throughput parameters — while relying on Kaspa's BlockDAG for the actual transaction ordering layer. The team gets the control of a dedicated chain without the burden of bootstrapping its own validator set or sequencer infrastructure.

This is a meaningful distinction from the standard rollup model, where a single sequencer (often run by the rollup provider) handles ordering for everyone. Multitude's pitch is that the ordering layer is not a vendor service — it's proof-of-work consensus, distributed and permissionless by design.

Why Toccata Matters Here

Igra Labs explicitly timed the Multitude announcement with the activation of Toccata, Kaspa's protocol upgrade that introduces covenants into mainnet. Covenants are a scripting primitive that lets a transaction enforce conditions on how its outputs can be spent in the future — enabling more complex on-chain contract logic without trusted intermediaries.

Igra Labs stated that Toccata "makes Kaspa an even better foundation for dedicated execution environments." The specifics of how Toccata's covenant capabilities enhance Multitude's architecture were not detailed in the announcement; Igra Labs indicated that more on Multitude's architecture and use cases will follow in upcoming posts.

For the Kaspa ecosystem, this is a significant signal. Toccata has been discussed primarily in the context of self-custody tooling — time-locked vaults, alarm keys, inheritance mechanisms. Igra's announcement broadens that picture: covenant-activated Kaspa may also serve as the settlement and ordering foundation for entire EVM chains purpose-built for finance.

What This Means for KAS Holders and PoW Miners

For miners, the calculus is straightforward in principle: every application and every dedicated chain that relies on Kaspa's proof-of-work for ordering is another source of demand for that hashrate. Igra's reported 350 PH/s is not additional hashrate — it's drawn from Kaspa's existing network. But a growing ecosystem of chains and applications anchored to that hashrate reinforces the economic case for mining and the security budget of the network.

For KAS holders who self-custody, the relevance is more architectural. The Kaspa ecosystem is beginning to show two distinct layers of value:

1. KAS as a base-layer asset — used for fees, secured by proof-of-work, governed by a transparent protocol with no central issuer. 2. Kaspa as ordering infrastructure — the BlockDAG consensus that other execution environments rely on for fair, uncensorable transaction sequencing.

Both layers benefit from increased adoption, but they carry different risk profiles. The base layer is well-understood; the infrastructure layer is newer and still proving itself in production. Igra's four months of mainnet operation is a start, but it's not a long track record. Finance teams evaluating Multitude will need to weigh the architectural advantages against the relative youth of the system.

The Honest Caveats

Igra Labs' announcement is promising from an architectural standpoint, but it is still an announcement from the project's own team. A few things worth watching:

• Auditing and verification. The claim that ordering is fully decentralized through Kaspa PoW deserves independent technical scrutiny over time.
• Multitude's specifics. The announcement does not detail pricing, throughput benchmarks, or how "dedicated throughput" is guaranteed under load. These will matter for production finance applications.
• Adoption. Naming existing apps is useful; tracking their real usage and the number of teams that adopt Multitude will be the real measure of traction.

None of these caveats diminish the significance of what's being attempted. An EVM layer that inherits proof-of-work ordering rather than relying on a sequencer-as-a-service model is an genuinely different architectural choice. Whether it holds up under real financial load is the question worth watching.

A Broader Shift

Igra's announcement is one data point in a larger pattern: Kaspa is beginning to function not just as a standalone blockchain but as infrastructure that other systems build on. The combination of BlockDAG ordering, proof-of-work security, and Toccata's covenant capabilities creates a foundation that teams can build against without vendor dependencies.

For a community that chose proof-of-work and self-custody deliberately, this is a natural evolution. The tools get more capable. The fundamental principle — that no single party should control the ordering of your transactions — remains the same.