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

# Registry

## Introduction

The Registry contract contains mapping with all pToken addresses, it allows get the pToken address by the underlying asset address. The Registry also contains the address of the current implementation of the pToken, which is used by all proxy pools.

## Get pToken address

The Registry contract has a mapping called `pTokens`. It maps underlying asset addresses to pToken addresses.

#### Registry

```
mapping (address => address) public pTokens;
```

#### **Solidity**

```
Registry registry = Registry(0x123...);
address asset = 0xabc...;
address pool = registry.pTokens(asset);
```

#### **Web3 1.0**

```
const asset = '0xabc...';
const registry = new web3.eth.Contract(registryAbi, registryAddress);
const pool = await registry.methods.pTokens(asset).call();
```


---

# 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://doc.defipie.com/registry.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.