# Phase III: Testnet

The Testnet phase will take place in 2025, marking another significant preparation step for the transition to decentralized blockchain—a Testnet directly involving nodes distributed worldwide. AZC Testnet, along with accessible Node software, not only allows blockchain testing but also initiates community efforts to develop decentralized utilities using Test-AZC.

### Decentralization through Testnet Nodes

#### Node Deployment

* Global Distribution: Deploying Testnet nodes across multiple geographical locations to simulate a decentralized environment. This helps in testing the network's resilience and performance under various conditions.
* Node Software: Providing accessible Node software for community members and developers. This software enables participants to set up and run Testnet nodes, contributing to the network's decentralization and testing efforts.

#### Quorum Slices

* Configuration and Testing: Configuring quorum slices as per the EVM consensus protocol to ensure efficient and secure consensus. This involves testing various configurations to determine the optimal setup for the Mainnet.
* Trust Graph: Building a trust graph through Testnet nodes, which simulates the real-world trust relationships that will be used in the Mainnet. This helps in verifying the effectiveness of the EVM consensus protocol in maintaining network integrity.

### Growth through the AZCoiner Mobile App

#### User Engagement

* Onboarding Pioneers: Using the AZCoiner mobile app to onboard users (Pioneers) to the Testnet. This involves educating users on how to contribute to the network and rewarding them with Test-AZC tokens for their participation.
* Community Building: Leveraging the mobile app to build a strong and active community around the AZC Network. This includes organizing events, providing updates, and encouraging community-driven initiatives.

#### Security Circles

* Aggregation and Validation: Allowing Pioneers to form and aggregate Security Circles within the mobile app. These circles contribute to building a trust graph, which is essential for the EVM-based consensus mechanism.
* Feedback Loop: Collecting feedback from Pioneers on their experience with the mobile app and the Testnet. This feedback is crucial for refining the user experience and addressing any issues before the Mainnet launch.

### Connectivity, Performance, Security, and Scalability Testing

#### Connectivity

* Interoperability: Testing the connectivity between Testnet nodes and other blockchain networks. This ensures that the AZC Network can interact seamlessly with external systems and platforms.
* Node Communication: Evaluating the efficiency of node communication protocols to ensure reliable data transmission and consensus across the network.

#### Performance

* Load Testing: Conducting load tests to measure the network's ability to handle high transaction volumes. This helps in identifying bottlenecks and optimizing performance.
* Latency and Throughput: Monitoring latency and throughput metrics to ensure the network can process transactions quickly and efficiently.

#### Security:

* Penetration Testing: Performing penetration tests to identify potential security vulnerabilities. This involves simulating attacks to assess the network's defenses and implementing necessary mitigations.
* Consensus Integrity: Verifying the integrity of the EVM-based consensus mechanism under various attack scenarios. This ensures the network can maintain consensus even in the presence of malicious actors.

#### Scalability

* Sharding and Sidechains: Exploring scalability solutions such as sharding and sidechains to enhance the network's capacity. These solutions are tested on the Testnet to evaluate their effectiveness and feasibility.
* Resource Optimization: Optimizing resource usage to ensure the network can scale efficiently. This includes fine-tuning node configurations and consensus parameters.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whitepaper.azcoiner.com/viii.-roadmap/vii.1-overview-of-development-stages/phase-iii-testnet.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.