QDay, Then and Now

We just switched on the Aevum Testnet, and within hours the same question showed up in every channel, every DM, and every reply: what actually changed? It's a fair question, and it deserves a precise answer rather than a marketing one. Here is what is different, what is genuinely preserved, and why Aevum is best understood as the testnet for the upgraded QDay network rather than a standalone payment chain bolted onto QDay.

The Promise That Never Moved

Start with what has not changed, because it's easy to lose in a story about upgraded architecture: QDay's core thesis is still to be a quantum-resistant, EVM-compatible network. That objective has not shifted, and it isn't a one-time claim you either satisfy or don't. It is a direction QDay has committed to for the long run, guiding a deliberate migration path from classical cryptography today toward hybrid and eventually native post-quantum mechanisms. The upgraded QDay architecture, now live on Aevum Testnet, exists to carry that objective forward, not to replace it.

What the Original QDay Design Proved

The original QDay design did real work establishing that this thesis was buildable. It ran a customized implementation of Polygon's ZK Rollup technology, adapted to operate alongside Abelian, a Layer 1 network built around quantum-resistant, lattice-based cryptography—specifically the Learning-With-Errors and Ring-LWE problems. That original design also described a PoS-over-PoW security and consensus model inherited from its underlying ecosystem, as well as a governance-controlled emergency-response capability intended to let the network act if a security incident occurred. These were the load-bearing ideas that proved the broader concept was technically sound: a quantum-resistant foundation could support a fully EVM-compatible execution environment without giving up either property.

It's worth being precise about Abelian's role in that picture, because it is easy to overstate. Abelian is best described as part of QDay's quantum-resistant security and data-state foundation, not simply as "the settlement chain." The more accurate relationship is layered: applications run on the execution layer, ZK proofs establish verifiability, state and data publication mechanisms record the relevant information, and Abelian's quantum-resistant properties underpin that stack rather than acting as a single settlement destination for every transaction.

Aevum Testnet: A New Generation of QDay

This is the most important clarification in this piece. Aevum is not a payment testnet, and it is not simply a new layer sitting on top of QDay. The Aevum Testnet represents a new generation of the QDay Network — a new execution architecture that becomes the foundation for QDAY's payment, smart-wallet, AI-agent, and future post-quantum capabilities. Payment is one of the key capabilities this new QDay architecture makes possible; it is not the sole definition of what QDay is.

Architecturally, this upgrade means moving QDay from a single customized rollup implementation to a modular, CDK-based stack. QDay retains its native token and governance model, while the execution environment itself is rebuilt around distinct, purpose-built components—sequencing, proving, aggregation, verification, and state and data publication—connected to Polygon's AggLayer for broader interoperability. The ZK-rollup principle carries over from the original design, but the underlying network architecture has been substantially redesigned rather than lightly patched.

What Changed Under the Hood

Concretely, the components that produce a confirmed transaction on QDay are now separated into specialized roles rather than bundled into one framework. A sequencer orders transactions; a prover generates the zero-knowledge proofs that establish their validity; an aggregator batches this activity efficiently; verification contracts check the proofs; and state and data publication mechanisms make the relevant information available. That modularity is what unlocks throughput and cost improvements for QDay: the design targets 4,000+ transactions per second, with a path toward much higher TPS on optimized infrastructure, and average fees at the sub-cent level.

It's worth separating two things that are easy to conflate: how quickly a transaction is confirmed, and how its long-term security is finalized. Transactions can achieve rapid confirmation within the QDay execution environment, but that confirmation is distinct from the ZK proof generation, verification, and subsequent state and data publication that form QDay's broader security and finality process. Fast timing describes the first step; the second step is what ultimately anchors the network's quantum-resistant guarantees.

What the New Architecture Adds to QDay

With this upgraded architecture in place, QDay is building a payment-oriented execution environment designed for stablecoin payments, smart-wallet automation, and autonomous AI-agent transactions. That is a deliberate response to three converging trends: AI systems increasingly acting as economic agents rather than passive tools, the global rise of regulated USD-pegged stablecoins, and the emergence of agent-native payment protocols such as x402.

Concretely, the capabilities coming to QDay include a native, USD-pegged stablecoin as the primary payment unit; gas abstraction, so fees can be paid in that stablecoin rather than requiring a separate gas token; ERC-4337-compatible smart wallets that provide session-scoped authorization, allowing an AI agent to operate within defined spending limits, permissions, and expiry windows instead of receiving unrestricted access to a balance; onchain agent identity through the ERC-8004 standard, so an agent can build a portable, verifiable reputation; and native support for the x402 protocol itself, letting an agent pay for an API call or inference request in the same exchange that asks for it. These payment and agent capabilities are on the way to Aevum and are not live yet.

Why Quantum Resistance Matters for Agents

This is also where quantum resistance stops being a purely defensive line item and becomes a genuine differentiator for QDay. A sufficiently powerful quantum computer could undermine widely used elliptic-curve cryptography, creating a long-term risk for any account whose security depends on classical signatures. That risk becomes particularly important once autonomous agents are holding balances and initiating transfers without a human approving every action, as there is simply less opportunity to catch a problem after the fact.

QDay's response is a progressive migration path rather than a single cutover: from classical ECDSA today, to a hybrid model combining ECDSA with ML-DSA-65, and eventually to native post-quantum signing. Quantum resistance remains a foundational design objective across that path, and the upgraded architecture is the infrastructure on which QDay can carry out that migration incrementally, rather than needing to redesign accounts from scratch once native post-quantum accounts arrive.

Original QDay vs. Upgraded QDay, at a Glance

The table below summarizes the comparison between the original QDay design and the upgraded QDay architecture now running on Aevum Testnet.

What Stayed the Same

None of this is a rebrand, and it's worth restating plainly what is actually preserved. The core thesis—a quantum-resistant, EVM-compatible network—is unchanged. Full EVM compatibility is unchanged. The commitment to quantum resistance as a long-term design objective is unchanged, even as the specific cryptography evolves along its planned path. Abelian's role as part of QDay's quantum-resistant foundation is preserved, even though its relationship to execution is more accurately described as layered than as a single settlement layer. Finally, QDay retains a governance-controlled emergency-response capability intended to pause relevant execution or restrict affected accounts during a security incident, subject to defined governance and authorization rules. This is the same protective instinct behind the original design, described here with the scope it actually carries rather than an unconditional claim.

What Comes Next

Aevum Testnet is live today, giving builders a working environment for QDay's new execution architecture, with the payment infrastructure, smart wallets, and agent-facing capabilities described above coming next. From here, the path runs toward QDay Mainnet, alongside continued work on the progressive PQC migration that eventually leads to native post-quantum account infrastructure at the execution layer. Specific target dates will be shared as they're confirmed against the current build, rather than restated from an earlier roadmap that predates this architecture upgrade.

If you're building on QDay, or deciding whether to, Aevum Testnet is the place to see the throughline in one environment: the same quantum-resistant, EVM-compatible thesis QDay started with, while substantially redesigning the execution and ZK infrastructure underneath it, with payment, account-abstraction, AI-agent, and x402 capabilities being added on top.

Aevum Testnet is LIVE now. Go build, break things, and tell us what you find.