> For the complete documentation index, see [llms.txt](https://docs.naoxprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.naoxprotocol.com/introduction/post-quantum-depin-testnet-growth.md).
# 🚀 Post-Quantum DePIN Testnet Growth
A New Benchmark in Decentralized Security
### A Quantum-Ready Testnet, Live and Scaling
On January 31, 2025, NaoX Protocol launched the world’s first Post-Quantum DePIN Testnet — a live, production-grade infrastructure designed to secure the digital world at scale. Built from the ground up with quantum-resilient architecture, the testnet serves as a real-world validation of NaoX Protocol’s SubZero Layer and Proof of Security consensus — each contributing to its security mesh’s self-healing, real-time cyber defense model.
The testnet isn’t theoretical. It’s operational, and its numbers reflect unprecedented traction across security, decentralization, and performance.
### Testnet Stats after 30 Days
In one month, the testnet achieved:
* **14M+ Post-Quantum Transactions Processed**\
– NaoX is the first blockchain to process PQ transactions at scale.
* **1.1M+ Wallets Created**\
– A rate outpacing what most major chains achieved in their first year.
* **440K+ Security Nodes Activated**\
– The largest decentralized security mesh launched to date.
* **133M+ \*Threats Mitigated**\
– Outpacing traditional centralized cybersecurity providers in detection volume.\
\
*\*Decentralized Browser Security Node Use Case - Malware, Ads, Trackers, Browser Threats & Vulnerabilities*
These results are not simulations. They are on-chain, measurable, and reflect operational resilience under real-world conditions.
### A First-Mover Advantage
Compared to traditional Web3 and cybersecurity players, NaoX Protocol is demonstrating production-level performance with an architecture fundamentally different from legacy models. For instance, while Microsoft mitigated \~90M threats in the same timeframe, NaoX more than doubled that — all through decentralized mechanisms.
No other blockchain currently processes post-quantum transactions, giving NaoX Protocol a clear lead in post-quantum readiness ahead of Q-Day.
### How the Protocol Enables Scale
These performance benchmarks are enabled by NaoX Protocol’s native innovations:
* [SubZero Layer](https://knowledgebase.naorisprotocol.com/naoris-protocol/introduction/what-is-a-post-quantum-sub-zero-blockchain): A foundational layer below L0 for real-time, cross-infrastructure trust.
* [Proof of Security consensus](https://knowledgebase.naorisprotocol.com/naoris-protocol/technical-guide/dposec-consensus-mechanism): Every node must prove its own integrity — not just validate blocks.
This architecture is designed not only for blockchain compatibility, but also to integrate with enterprise Web2 infrastructure — forming a single mesh of decentralized trust.
### Why This Matters
As quantum computing advances and centralized systems continue to fail at scale, NaoX Protocol’s testnet demonstrates a viable, production-grade alternative. It offers enterprise-ready, blockchain-native cybersecurity that works now — with no need for hard forks, wallet migrations, or degraded performance.
### Explore the Testnet
* [View Testnet Website](https://naorisprotocol.network/testnet)
* [View Testnet Explorer](https://naorisprotocol.network/explorer/)
* [Visit NaorisProtocol.com](https://www.naorisprotocol.com/)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.naoxprotocol.com/introduction/post-quantum-depin-testnet-growth.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.