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

# Intro

Ethereum domains are gradually becoming more and more popular and used in the web3 landscape.

There are many volumes of exchanges of these domains, in the form of NFTs that are traded in major NFT marketplaces, foremost among them Opensea.

Dedicated ENS marketplaces have also been created over time, the most famous being ENS Vision.

Thus, **most of the exchange volume occurs through marketplace listings and direct purchase**.

Why do we think this is inefficient?

1. Domains do not have an easily identifiable price, and standard **listing does not allow for a price discovery process**
2. In marketplaces, domains can only be reached via search, and listings are almost always lost in the **multitude of NFTs and domains offered for sale**
3. At the launch of Ethereum Name Service, **domains were offered via auction**, with a calendar accessible to anyone who wanted to participate
4. On Opensea and other large marketplaces, **referral links no longer exist**, whereas at the time of the first ENS auctions they were present on Opensea and were an incentive for word-of-mouth of domains for sale

Our solution is to create a **space dedicated exclusively to ENS domain**.\
The main difference from marketplace is that Domains here are sold via a **raffle process**. \
\
Basically, **a domain owner can offer his domain for sale through a raffle**, which takes place on Layer2 (right now Arbitrum). 

**Anyone interested can purchase tickets on the Arbitrum network**, and at the end of the process, a winner is identified in a trustless way via Chainlink. The winner can redeem his or her domain on the Ethereum network.

As it is designed, Ethereum Name Raffles allow for several advantages:

1. the main page is dedicated to ongoing raffles, with a maximum **limit of 10 simultaneous raffles** shown in the main page
2. **joining the raffle is very cheap** thanks to transaction costs on Arbitrum network for the purchase of tickets
3. a **Ref Link system** allows bloggers and inluencers to help promote auctions of their interest
4. a **raffle calendar** allows the most interesting raffles to be added to Calendar

{% content-ref url="/pages/X24dvyFWEa6Ys61BUns3" %}
[ENS Raffles](/ens-raffles/ens-raffles.md)
{% endcontent-ref %}

{% content-ref url="/pages/bfip5yPJL2c66YLFaLLB" %}
[Set-up a Raffle](/ens-raffles/set-up-a-raffle.md)
{% endcontent-ref %}

{% content-ref url="/pages/MgS1bfd2gN5hGMjOM2kC" %}
[Join Raffle](/ens-raffles/join-raffle.md)
{% endcontent-ref %}

{% content-ref url="/pages/WhlHWVKH6dLDkJR7Fwbi" %}
[Referral System](/ens-raffles/referral-system.md)
{% endcontent-ref %}

{% content-ref url="/pages/UNp187gZS0Is8Q5lkVgu" %}
[Testnet](/ens-raffles/testnet/ens-testnet.md)
{% endcontent-ref %}

{% content-ref url="/pages/W1hcrqR2wekj407hc9Vt" %}
[ENS Raffles POC](/ens-raffles/testnet/ens-raffles-poc.md)
{% endcontent-ref %}


---

# 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://ensraffles.gitbook.io/ens-raffles/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.