Igra had three separate updates around the Toccata window: exit limits were raised, agentic bridging was shown live, and a new architecture name, Multitude, was teased as Kaspa entered the Toccata era.
The concrete operational update came first. On June 29, Igra Labs said a DAO proposal had been accepted and that KasExitBridge limits were raised to as many as 25 exits and 1,000,000 KAS per window, with individual exits ranging from 10,000 to 250,000 KAS. (Igra Labs on X) The quoted proposal had framed the earlier limits as conservative early-launch values, so the accepted change is a capacity adjustment rather than a brand-new bridge design.
Later the same day, Igra reposted a user flow showing a MyKAI local AI assistant bridging USDC on Igra to USDC on Ethereum through a whitelisted path. Igra summarized it in three words: "Agentic bridging on Igra, live." (Igra Labs on X) That is an ecosystem signal, but it needs careful wording. The post shows a working assisted bridge flow. It does not prove that every arbitrary agent can safely move funds, and it does not remove the need to audit route permissions, address allowlists, custody assumptions, or user consent boundaries.
On June 30, Igra tied the bigger framing to Toccata itself. The team said Toccata "makes Kaspa an even better foundation for dedicated execution environments" and announced Multitude as Kaspa entered the Toccata era, with more architecture and use-case details to follow. (Igra Labs on X)
That line matters because it positions Igra as more than an EVM-compatible rollup sitting near Kaspa. The claim is that Toccata improves the base-layer foundation for dedicated execution environments. The details still need the promised architecture posts before the claim can be evaluated, but the direction is clear: Igra wants its bridge, execution layer, and agent-facing flows to be read as part of the post-Toccata application stack.
There is a second, separate hygiene point. Igra also warned about impersonator tokens on launchpads and gave one canonical contract address for IGRA, telling users to verify against its docs before buying. (Igra Labs on X) That is not the main story, but it belongs near any Igra ecosystem coverage right now because fake-token risk tends to rise when bridge and token activity gets more attention.
The publishable takeaway is narrow. Igra raised KasExitBridge capacity through an accepted proposal, showed an assisted bridge flow, and began positioning Multitude around the Toccata era. The next article should wait for the architecture details. This one can mark the operational shift: bridge limits are no longer at the earliest conservative settings, and Igra is already using the Toccata window to push execution-environment messaging.