# CCIP & PNS

<figure><img src="https://3277765323-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FStOwhwvhAvs3L45w42Xw%2Fuploads%2FpFE49Dczdn36PHhCC2SM%2FPNS_CCIP.png?alt=media&#x26;token=1aba0fd5-6b75-4f77-9522-c61f080ef18d" alt=""><figcaption></figcaption></figure>

The PulseChain Name System (PNS) has integrated **CCIP Read** from the Ethereum Name Service (ENS), bringing cross-chain name resolution and significantly expanding the usability of `.pls` names across the broader Web3 ecosystem. It’s the first occurrence in Web3 history that a non-Ethereum domain name service employs CCIP in such a manner, underlining a significant leap in interoperability. With a single integration, `.pls` names are now compatible in over 500+ dApps, websites, and wallets that already support ENS lookups—without those dApps needing to natively integrate PNS.

#### What does this mean for `.pls` name holders?

* **ENS Compatibility:** A name like `alex.pls` can now be looked up via ENS by entering `alex.pls.eth`.
* **Wider Adoption:** Any service, wallet, or site that supports ENS name resolution can now recognize and use `.pls` domains e.g. MetaMask, EtherScan, Revoke Cash & more.
* **Native vs. CCIP Integrations:**
  * **Native Integrations** offer full PNS support and seamless integration.
  * **CCIP Integrations** offer full to partial support of the PNS system, depending on the dApp, site or wallet and their configuration of the ENS system.

A full list of dApps, wallets & sites that are now compatible via CCIP can be viewed [here](https://www.pulse.domains/#Ecosystem).

<figure><img src="https://3277765323-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FStOwhwvhAvs3L45w42Xw%2Fuploads%2FKiKQVNv3uw5ja4uIZhPg%2FPNS_CCIP2.png?alt=media&#x26;token=8e0ccc31-5866-4b16-b404-3be3d74310bf" alt=""><figcaption></figcaption></figure>

### What is CCIP?

CCIP stands for **Cross-Chain Interoperability Protocol**, a middleware solution developed by [Chainlink](https://chain.link/) that enables data and asset transfers between different blockchains. Its goal is to provide a secure, flexible framework so that organizations don’t have to develop one-off solutions every time they need to connect to a new chain.

#### CCIP Read

**CCIP Read** is an extension of the Chainlink CCIP specifically adapted and implemented by ENS. It allows off-chain lookups and on-chain verification of data, enabling ENS to resolve domains on Ethereum even if some domain data (records, resolvers, etc.) is stored on a different chain (e.g., Layer 2 or any off-chain environment).&#x20;


---

# 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.pulse.domains/guides/ccip-and-pns.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.