> For the complete documentation index, see [llms.txt](https://docs.zetrix.com/zetrix-l2-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zetrix.com/zetrix-l2-documentation/network-and-deployment/deployment-architecture.md).

# Deployment Architecture (Current Testnet)

## Overview

The current Testnet deployment prioritizes rapid iteration and cost efficiency. In practice, **most Z2 components are deployed on the same server** rather than on dedicated, isolated hosts — the node/validator processes and the supporting services (Explorer, Monitoring, Relayer, Refueler, Faucet) are consolidated together. Web apps such as the monitoring dashboard and faucet are exposed as **paths under the node host** (`z2-test-node.zetrix.com/app/...`).

This consolidated model is appropriate for Testnet. For the initial Mainnet rollout, the team intends to **follow the same consolidated approach until scalability enhancements are required**, at which point the component separation proposed in [Production Deployment Recommendation](/zetrix-l2-documentation/network-and-deployment/production-deployment.md#production-deployment-recommendation) is adopted.

## Current Component Footprint

| Component                    | Role                                                         | Current Testnet Deployment            |
| ---------------------------- | ------------------------------------------------------------ | ------------------------------------- |
| Z2 Node                      | EVM execution + QBFT consensus (go-quorum)                   | 5 go-quorum QBFT nodes                |
| Z2 Sequencer                 | Post L2 batch to L1                                          | 3 servers                             |
| Z2 Validator + Z2 Reexecutor | Committee + Aggregator (verify & sign for soft confirmation) | 5 servers                             |
| Z2 Validator + Z2 Reexecutor | Proposer + Watcher (propose & submit assertion)              | 1 server                              |
| Z2 Refueler                  | Check & top-up EOAs (Sequencer, Committee, Main Proposer)    | 1 server                              |
| Z2 Validator + Z2 Reexecutor | External Watcher (verify assertion, dispute mismatches)      | Operated by third parties             |
| Z2 Explorer                  | Layer 2 explorer                                             | Consolidated (shared server)          |
| Z2 Monitoring                | Monitor & analyse L2 network                                 | Consolidated (shared server)          |
| Z2 Relayer                   | Relay L1→L2 (native / ZTP20 deposit)                         | Consolidated (shared server)          |
| Zetrix MCP                   | Deposit/withdraw/NFT, tx status, L2 info                     | npm package                           |
| Z2 Faucet                    | Request gas for Z2                                           | Consolidated (served under node host) |

<figure><img src="/files/dNQvR8YI49ODmIMlmVzc" alt=""><figcaption></figcaption></figure>

## Advantages of the Current Approach

| Advantage              | Explanation                        |
| ---------------------- | ---------------------------------- |
| Cost efficiency        | Fewer hosts; shared resources      |
| Simplicity             | Easier to operate for a small team |
| Fast iteration         | Quick redeploys during development |
| Sufficient for Testnet | Load and stakes are low            |

## Limitations

| Limitation                      | Risk                               |
| ------------------------------- | ---------------------------------- |
| Shared infra                    | Noisy-neighbor; correlated failure |
| Single Proposer                 | Liveness single point              |
| Co-located Reexecutor/Validator | Reduced verification independence  |
| Limited isolation               | Weaker security boundaries         |
| Limited HA                      | Some services lack standby         |

> \[!WARNING] Co-locating the Reexecutor with the Validator reduces the independence of verification. For Mainnet, run **independent** Reexecutors and encourage external Watchers to strengthen the 1-of-N honest assumption.

## Future Improvements

* Dedicated hosts per component; strict network segmentation.
* Standby Proposer and Sequencer with automated failover.
* Independent Reexecutors; incentivized external Watchers.
* Full HA for Relayer, Explorer, Monitoring.

***

[← Network Endpoints](/zetrix-l2-documentation/network-and-deployment/network-endpoints.md) · [Index](/zetrix-l2-documentation/readme.md) · [Production Deployment Recommendation →](/zetrix-l2-documentation/network-and-deployment/production-deployment.md)