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

# Base Sepolia

The current controlled pilot runs on **Base Sepolia**, chain ID `84532` — a public Ethereum Layer-2 test network. It is not Base mainnet, and it is not any production network.

## Why a public testnet, not a private/local chain

Running on a real public network — rather than a private or local test chain — means the deployment is independently inspectable and reproducible by anyone, using ordinary public block-explorer and RPC tooling, not a tool ADCP itself controls.

## Test assets only

Every asset used in the current pilot — the USDC and BTC representations included — is a dedicated test asset with no real-world value, distinct from real USDC or real BTC on any production network. **No real value is at risk anywhere in this deployment.**

## Explorer

Deployed contracts are viewable on the public Base Sepolia block explorer at [sepolia.basescan.org](https://sepolia.basescan.org). See [Deployment Reference](/network/deployment-reference.md) for the current pilot's exact contract addresses.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adcpcapital.com/network/base-sepolia.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.