> ***It’s very likely you’ve been HimFested, whether you like it or not — but that’s just the way it is.***
Welcome to the HimFestation.
**HimFest** is our way of rewarding on-chain behaviour with a healthy dose of HIM.\
It’s part growth tactic, part chaos. Here’s how it works:
🪙 1. **Standard Token Transfers** — *6.9 HIM*
Think of this as the casual drive-by of infestations.
* You receive any token transfer.
* You’re holding at least **0.2 BERA/WBERA**. (Respect.)
* You’ve never held HIM before. (Purity is important.)
* You’re not a contract address.
**Result:** You are HimFested with 6.9 $HIM.
***
#### 🔠 2. **ENS Name Registration** — *420 HIM*
You wanted a sick name on-chain.\
You got a surprise HIM shower with it.
* Just register any ENS name.
* We see you. The **`NameRegistered`** event tells us.
* Contract being watched: `0xf0fb7ba7d6D18AdC32298d2Ff452f448F90255dC`
* Each address can only score this once, so make it count.
**Result:** You are HimFested with 420 $HIM.
***
#### 🌉 3. **OFT Token Receipt** — *69 HIM*
Bridged some tokens using LayerZero? Congrats — you just caught a HIM infection.
* We detect the **`OFTReceived`** event on-chain.
* Watched over by contract: `0x45f1A95A4D3f3836523F5c83673c797f4d4d263B`
* One-time drop per address. Make it memorable.
**Result:** You are HimFested with 6.9 $HIM.
***
#### ⚙️ How It All Goes Down
All HimFestations are curated and processed via a custom **disperser contract**, which:
* Runs every **5 minutes** *or*
* Waits until there are **50 unsuspecting addresses** lined up for $HIM
and then... well you have become $HIM.
***
This is **HimFest** — infestation as a service.
---
# 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://him.gitbook.io/honey-is-money/himfestation/the-himfestor.md?ask=
```
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.