# Planck₀

#### Overview

Planck₀ is the world’s first Layer-0 protocol designed specifically for AI and DePIN ecosystems. It forms the foundation of the Planck stack, sitting beneath Planck₁ and any future AI-native chains launched in our ecosystem. Unlike a Layer-1, Planck₀ does not execute workloads itself. Instead, it provides the connective fabric: shared security, instant token interoperability, and — uniquely — compute interoperability.

#### Vision

The vision of Planck₀ is to create a base layer where chains are not isolated silos but part of a shared compute economy. By making compute interoperable across chains, Planck₀ allows resources to flow freely: if one chain has excess GPU capacity, another can tap into it in seconds. This transforms compute into a composable, on-demand resource, creating a foundation that is decentralized yet enterprise-grade.

#### Architecture

| Component                    | Description                                                                                                                     |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Shared Security**          | Planck₀ provides a validator set that secures all connected Layer-1s, reducing the cost and complexity of launching new chains. |
| **Token Interoperability**   | Instant movement of tokens across chains, eliminating the need for fragile custom bridges.                                      |
| **Compute Interoperability** | Native support for pooling GPU power across chains; workloads can shift to where capacity is available.                         |
| **Interchain Messaging**     | Secure communication and coordination between Planck₁ and other appchains in the ecosystem.                                     |

#### Core Capabilities

* **Cross-Chain Compute**: Excess GPU resources from one chain can be instantly reallocated to another.
* **Composable Ecosystem**: Developers can launch their own AI-native Layer-1s without needing to build validators, bridges, or compute infrastructure from scratch.
* **Seamless Scaling**: As demand grows, chains can scale horizontally by leveraging resources from across the network.
* **DePIN Integration**: Planck₀ is built to natively support decentralized infrastructure networks, extending beyond compute into storage, robotics, IoT, and more.

#### Relationship with Planck₁

Planck₀ and Planck₁ form a two-layer stack. Planck₁ is the execution environment where workloads are run, GPUs are rented, and inference and training happen. Planck₀ provides the coordination beneath it — securing Planck₁ and any other AI chains that join the ecosystem. Together, they make compute both **decentralized and interoperable**, something centralized clouds like AWS or Azure cannot achieve.

#### Token Utility

* **Staking & Governance**: Validators stake $PLANCK to secure the Layer-0 and govern protocol upgrades.
* **Bonding for Appchains**: New AI chains bond $PLANCK to inherit security and gain access to interoperability.
* **Compute Marketplace**: $PLANCK underpins the movement of compute across chains, making GPU capacity a tokenized and tradeable resource.

#### Why Planck₀ Matters

Planck₀ is more than just a Layer-0. It is the backbone of a compute-native ecosystem where resources are shared, tokenized, and accessible across chains. By combining security, interoperability, and compute, Planck₀ enables AI and DePIN projects to launch faster, scale globally, and operate at costs traditional hyperscalers cannot match. It is the invisible infrastructure layer that makes the open AI future possible.


---

# 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://resources.plancknetwork.com/learn-more/white-paper/web3-protocols/planck-1.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.