Q-day

Read the announcement: medium.com/qanplatform/annou…

[Announcement] On Friday, we shared the current codebase with the auditor to get a cost and time estimate. We are eager to elaborate on the features related to the audit submission. Read the full details on our blog. Link in the replies. 👇

Last week, Google shortened the timeline for quantum computers. They demonstrated that magic state cultivation works in practice on their Willow processor. Magic states are what quantum computers need to perform operations, and they've always been expensive to produce. By some estimates, they potentially consume up to 95% of a machine's capacity. The method reduced errors by about 40x compared to without cultivation, meaning that higher-quality magic states can be achieved much more efficiently. More efficient error correction means smaller machines doing bigger jobs.

September Milestones: XLINK Goes On-Chain and Deterministic QVM Metering Takes Shape September was a month of deep engineering for QANplatform. Our team turned their attention to the work that will define the production network: moving XLINK signature management on-chain, building a caching layer to speed up QVM executions, advancing our deterministic gas-metering research toward a real pricing model, and hardening the network against the subtle edge cases that only appear under sustained load. This month also brought a major strategic milestone: with the execution-layer rebase complete, our audited quantum-safe stack is ready for the final security-audit phase. Read the full technical recap on our blog (link in replies)🔗👇

[Audit status update] Based on all received feedback, we have finalized the decision on the consensus layer integration for the mainnet stack. After careful consideration, we selected Lighthouse by Sigma Prime. As discussed previously, Lighthouse is the most widely used consensus client and is considered semi-official due to its broad adoption among node operators. This choice best meets the technical and policy requirements of our strategic partners. What happens next: Step 1: We are currently preparing the official Go-Ethereum based execution client to be compatible with the modified Lighthouse consensus client. Step 2: Once these modifications are ready, we will submit the execution client to the auditors, expected by end of next week. Step 3: Once the required Lighthouse modifications are completed, we will also submit the consensus client to the auditor. Just to clarify, the above steps do not alter the mainnet launch timeline, as these processes are fully parallel.

Europol mentions QANplatform in its recently published report, “Quantum Computing and Cryptocurrencies,” as a proven example of quantum-safe blockchain technology. QAN XLINK, a cross-signer protocol that utilizes NIST’s primary-recommended post-quantum cryptography (PQC) algorithm and enables the integration of Ethereum-compatible wallets with quantum-safe, signature-capable key pairs, successfully completed a comprehensive cybersecurity audit by blockchain security firm Hacken (@hackenclub) in November 2025. The solution is already deployed on the QAN TestNet. Find the links to the report and audit in the replies. 👇

We built for a future where quantum-safety and auditability are mandatory, but public network dependency is optional. Thanks to the hybrid architecture, enterprises can keep their data private while still achieving trust by anchoring proofs to the public blockchain. On the budget side, there is one batched transaction instead of thousands. The cost model changes from per-transaction to predictable operational cost. Public-chain immutability without having to pay public-chain fees on internal operations. Both sides are quantum-safe, protected by NIST-standard post-quantum cryptography. Cost and auditability are often a tradeoff. This architecture doesn't require enterprises to choose.

[Audit status update] We know many of you are eagerly waiting for the final audit phase to begin, and we want to keep you posted. All the crucial and most challenging parts of the system have been successfully ported to Go-ethereum, the official Ethereum execution-layer client. This part is ready for auditing. Where we are now: To meet our strategic customers' requirements, we rebased our solution on top of the official Ethereum implementation and replaced all Ethereum-related components with their official counterparts. One part of the stack - the consensus layer - does not have an official Ethereum implementation. This means our customers need to align on which consensus client they are willing to accept before we submit this final component in the last audit phase. The two options are: A ) Caplin by Erigon, a Golang-based consensus implementation we currently use already deployed and tested on our testnet. B ) Lighthouse by Sigma Prime, the most widely used Rust-based consensus client, which could be considered semi-official due to its broad usage among node operators. We are working on a joint decision which is technically sound and policy-wise acceptable for all parties involved. What happens next: We expect a final decision next week, so we can move forward. Once the decision is made we will update you again.