# What is Proven Network?

Proven Network is a companion network for the Radix DLT which provides an ergonomic suite of services to complement and extend the existing ledger capabilities. Our goal is to enable a next-generation of Web3 dApps which are experientially competitive with Web2 applications.

Broadly, the three main categories of services provided are:

* Off-ledger **auditable/verifiable compute** with capabilities-based permissions which can run private serverless workloads extremely cheaply (pay only for usage/scale to zero). This compute layer uses a WASM-based VM executing inside a globally distributed network of trusted-execution environments to ensure complete privacy and inability for tampering - even from the operator of the hardware on which the computation is occurring.
* Off-ledger **encrypted storage** keyed by Radix ledger identity primitives creating an environment where data can truly be "owned" by end-users while also being mutated through the business-rules of the application.
* A global **messaging** bus that ties together the TEE-based compute and encrypted storage together with Radix-native on-ledger events. Making the above resources available, over cryptographically-authenticated channels, to the edge (IE user devices) and enabling real-time trust-minimised compute and collaboration between users.

## What use-cases can Proven Network help solve?

Application developers can use these compute, storage, and messaging primitives to create modern Web3 applications that tackle new use-cases not possible with a ledger alone. Examples of what developers might build using Proven in conjunction with Radix DLT include:

* Multiplayer game servers with complicated rule-sets computed in real-time off-ledger but with assets managed on-ledger. Enabling GameFi which requires imperfect information between players - or simply those whose rule-sets are too expansive to compute with consensus-based means.
* Long-tail oracles that can bridge between on and off-ledger environments by leveraging the existing PKI infrastructures of the internet. Oracles which pull information securely (with full audit logs) from web-based APIs can be created - enabling prediction markets and similar applications. By utilising hardware-based trust-models, these oracles can be run an order-of-magnitude more cheaply than their crypto-economic based counterparts.
* Enabling access-control to storage and messaging channels based on ledger-state. Applications can make content like songs or videos, or private messaging, to be only accessible to holders of particular assets.
* Programmatically triggering on-ledger transactions based on a timer or cron schedule.
* Applications which want to be extremely compliant with global data regulations - ensuring that legal requirements like the "Right to be Forgotten" are enshrined in auditable code.
* Creating trust-minimised DID issuers/verifiers that can act as integration points for legacy (or Web2) identity providers.
* DAOs with private voting capabilities which can enact the results of their voting on-ledger. This might include deploying new smart-contracts which allows true decentralisation of the locus of control over dApps.
* Creating trading bots or other autonomous agents which can act and react based on events occurring on-ledger. Everything from simple tools for DCA purchasing of ledger assets to advanced real-time DeFi strategies can be codified.
* Using the network as a secure platform to compute ZK proofs for under-powered platforms (mobile, etc.) which can be verified on-ledger.


---

# 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.proven.network/what-is-proven-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.