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

# Intro

### Welcome to the documentation for Prepunk ENS Domains.

This resource aims to provide comprehensive information about the Ethereum Name Service (ENS), its origins, and specifically, the historical significance of "Prepunk" domains – those registered in the very early days of ENS, between May 9, 2017, and June 23, 2017.

Whether you're an ENS enthusiast, a digital historian, an NFT collector, or new to the space, this guide will walk you through:

* **The fundamentals of ENS:** Understanding what it is and the problem it solves.
* **The history of ENS:** How it began, including the unique auction process used at launch.
* **Defining Prepunks:** What criteria make an ENS domain a Prepunk and why they are historically relevant.
* **Verification:** How to confirm if a specific ENS domain is a Prepunk using available tools and data.
* **Subcategories and nuances:** Exploring different types of Prepunks, including digits, ethmojis, blank spaces, and chaff names.
* **Trading insights:** Where to find and trade these historical assets.

Our goal is to present this information clearly and accurately, focusing on the historical context and technical details that make Prepunks a unique part of Ethereum's history. If you do find any mistake or inaccuracy or would like to contribute, reach out to [@goatbeing](https://x.co/goatbeing).

Navigate through the sections using the sidebar to explore the fascinating world of Prepunk ENS domains.


---

# 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://prepunk.gitbook.io/doc/intro.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.