> For the complete documentation index, see [llms.txt](https://docs.zeeve.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeeve.io/rollups/polygon-cdk-zkrollup/demo-network/details.md).

# Details

Follow the steps below to access a demo Polygon CDK through the Zeeve platform:

{% hint style="warning" %}
To get a network with the custom configuration and only accessible to you, you can deploy a new Polygon CDK network.
{% endhint %}

**Step 1: Register/Login -** Create a new account or log in to an existing account on the [Zeeve Platform](https://app.zeeve.io/auth/signup).

**Step 2: Zeeve Dashboard -** On the Zeeve platform dashboard, click on the **Polygon CDK** option under the **APPCHAINS & ROLLUPS** section available in the left sideba&#x72;**.** This will show your deployed Polygon CDK network.

**Step 3: Polygon CDK -** Click on the **View** button on the DEMO card (This is a pre-deployed network that is accessible to all the users of Zeeve.)

**Step 4: Overview -** Once you click on the **View** butto&#x6E;**.** You can see the network's overview details there.&#x20;

**Step 5: Explorer -** Click on the **Explorers** button to open L1 and L2 Explorer.

**Step 6: Blockchain Configuration -** Click the Blockchain Config tab on the overview page to view blockchain configuration. On the blockchain configuration page, you can view the Ethereum Transaction Manager and CDK Chain (L2)**.** You can also download the Genesis file by clicking the **Download Genesis File i**co&#x6E;**.**

**Step 7: Bridge -** To view the bridge, click on the **Bridge** tab on the overview page. Open the bridge by clicking on the icon next to the bridge URL(Bridge URL will be clickable once the network is ready). This will open the Polygon CDK Bridge page, where you can perform bridge operations.

**Step 8: My Nodes -** Click on the **My Nodes** Tab to view nodes. To view the **Node Details Page**, click the **View Details** icon under **Actions**. To view details about other nodes, simply click on the tab for that node.

**Step 9: My Wallets -** To view wallet information, click on the **My Wallets** tab on the overview page. You can view the wallets on Explorers by clicking on the links provided against each wallet.

**Step 10: Smart Contracts -** To view smart contracts, go to the **Smart Contracts** tab on the overview page. Click the icon under the **Actions** column to view the contract on the Explorer, or click the **Docs** icon to see deployment details in the documentation.

**Step 11: Cloud Infra -** To view cloud infra, click on the **Cloud Infra** tab on the overview page.

**Step 12: Sample Apps -** To view Sample Apps, click on the Sample Apps tab on the overview page.

**Step 13: Analytics Page:** Click on the **Analytics** button. Select the item from the dropdown for which you want to view the analytics. This will open the analytics page for that option. If you want to view analytics for some other option, you can click on the drop-down available on the Analytics page and choose your option.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zeeve.io/rollups/polygon-cdk-zkrollup/demo-network/details.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
