# White Network

WhiteRock's infrastructure for White Network will consist of four layers: the blockchain White Network with its three layers, on top of which exists the dapp layer where WhiteRock's RWA Platform will live on. WhiteBFT makes up of the consensus layer and is a HotStuff-inspired 

<figure><img src="https://2029382772-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg9K1qAI9D2Uoe5qM0X5Z%2Fuploads%2F5e7gOEjEZ2FfUNYjBmun%2FFour%20Layers%20on%20White%20Network.png?alt=media&#x26;token=92d2c0dd-9ad8-42c3-9794-31e9f74b175c" alt=""><figcaption><p>Tech stack for White Network</p></figcaption></figure>

**WhiteBFT** serves as the network’s consensus engine, pushing throughput beyond 200,000 transactions per second while sealing each block with near-instant finality. The design is inspired by the HotStuff consensus mechanism, yet adds optimizations in bandwidth usage, signature aggregation, and deep pipelining so settlements feel immediate even for institutional loads. Because every performance parameter is modular, future upgrades can raise speed without rewriting the entire protocol.

**WhiteDB** extends this speed at the execution layer through a parallel, shard-aware data model. Transactions are prescheduled into non-conflicting groups, processed simultaneously, and merged into a single canonical state by deterministic rules. Each write produces a compact Merkle proof that light clients can verify, letting applications query balances or positions like a key-value store while retaining full cryptographic integrity. Indexing, snapshotting, and archival support are built in, allowing analytics tools, risk engines, and oracle feeds to draw data directly from the chain.

**WhiteLens** combines compliance and privacy using zero-knowledge proofs and shielding techniques inspired by Railgun. Wallets may attach encrypted attestations such as KYC status or jurisdiction tags, and smart contracts read simple true-or-false flags without exposing personal details. Users decide when to transact openly or within a privacy pool, and regulators can still confirm rule enforcement by reviewing aggregated ZK outputs. This approach eliminates the usual trade-off between confidentiality and regulatory readiness while leaving space for new standards as global policies evolve.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg9K1qAI9D2Uoe5qM0X5Z%2Fuploads%2F17rKxqpewKVF6RQtqkp4%2F200k%20tps.mp4?alt=media&token=086e0b4f-13ad-44b4-8d23-5b0911eb1644>" %}
A preview of White Network's throughput
{% endembed %}

### Network Status

Note that White Network is still in active development. The first iteration of the public testnet, scheduled for Q2 2025, was launched in July 2025.


---

# 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://docs.whiterock.fi/white-network/white-network.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.