# 2.2 Target Customer Segments

#### Segment 1: Zero-Knowledge (ZK) Protocols

ZK-rollups (zkSync, StarkNet, Polygon zkEVM, Scroll) require verifiable entropy for proof generation, trusted setup, and random challenge sampling. Existing solutions—software-based PRNGs or centralized entropy providers (e.g., drand)—introduce trust assumptions that weaken ZK security guarantees. QuantaRail provides hardware-attested, quantum-sourced entropy with on-chain verifiability.

#### Segment 2: Cross-Chain Bridges

Bridge protocols (LayerZero, Wormhole, Axelar) represent the highest-value attack surface in Web3, with over $2.5 billion in cumulative losses since 2020. Quantum-resistant signatures for bridge validators constitute a critical security upgrade. QuantaRail’s PQC signatures enable operators to future-proof validator key infrastructure against HNDL threats.

#### Segment 3: Institutional Custody

Institutional custodians (Fireblocks, Copper, Anchorage) face increasing client demand and regulatory pressure (NIST, CNSA 2.0, DORA) for quantum-resistant key management. QuantaRail’s HSM-based PQC signatures provide an auditable, standards-compliant solution.

#### Segment 4: Oracle Networks

Oracle networks (Chainlink, Pyth, API3) transmit price feeds securing billions in DeFi collateral. PQC signatures for oracle attestations prevent future retroactive manipulation of historical data.

#### Segment 5: Enterprise Regulatory Compliance

Financial institutions and government contractors subject to CNSA 2.0 (mandated by 2035), NIS2, and DORA require compliant entropy and signature infrastructure. QuantaRail’s NIST SP 800-90B-compliant QRNG and FIPS 204/205 signatures address this compliance gap.


---

# 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://railquant.gitbook.io/quantarail/2.-market-opportunity-and-demand-validation/2.2-target-customer-segments.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.