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

# Attendance Badges

Attendance badges are **proof that you attended** a meetup or event in the Hedera ecosystem. Each badge adds **100 XP** to your season total and counts toward the badge missions.

***

## ⚙️ How It Works

### 🎟️ Check In at the Event

Hosts can record attendance in three ways:

| Method                   | How you check in                                                                                              |
| ------------------------ | ------------------------------------------------------------------------------------------------------------- |
| 📷 **QR code**           | Scan the QR the host shows, connect your wallet and click **Confirm Attendance**                              |
| 🔗 **Attendance link**   | Open the link the host shares (for X Spaces, Discord calls or online events), connect your wallet and confirm |
| ✍️ **Added by the host** | The host adds your wallet address by hand, for example if you couldn't scan the QR                            |

### 🔐 Why Codes Expire

* 📷 The QR carries a **12-character code that changes every 60 seconds**, and a code stops working shortly after it changes. This keeps check-ins to the people who are there. If you see **Code Expired**, scan the QR again.
* 🔗 An attendance link works for **20 minutes**. When the host creates a new link, the previous one stops working.
* 👛 Each wallet can check in to an event **once**.

### 🔒 When the Host Ends the Event

When the host clicks **End event**, attendance is locked for good:

* 🏅 **Every wallet on the check-in list gets the badge.**
* 🚫 No more check-ins are accepted, whether by QR, link or manual add.

Badges are recorded by Hashly: nothing is minted or sent to your wallet, and you don't need to associate any token.

***

## ⛓️ On-Chain Record

Every check-in is written to the **attendance topic** on the Hedera Consensus Service: [`0.0.10300837`](https://hashscan.io/mainnet/topic/0.0.10300837). When the record is written, the confirmation screen shows its number (for example, `On-chain record: HCS #65`).

**HCS message format:**

```json
{
  "type": "event_checkin",
  "version": 2,
  "wallet": "0.0.xxxxx",
  "event_id": "cuid123...",
  "event_name": "Hedera Meetup",
  "event_type": "ECOSYSTEM_MEETUP",
  "timestamp": 1234567890
}
```

Check-ins are public and permanent, together with your account ID. See the [Privacy Policy](https://hash-ly.com/privacy).

***

## 🎯 Badge XP and Missions

* ⚡ Each badge adds **100 XP** to the season in which the host **ended the event**.
* 🐉 The Dragon Boost doesn't apply to badge XP.
* 🏆 Badges also count toward these missions:

| Mission                          | Requirement                          | XP    |
| -------------------------------- | ------------------------------------ | ----- |
| 🏅 **Badge Holder**              | Earn 1 attendance badge this season  | 300   |
| 🏆 **Badge Collector**           | Earn 3 attendance badges this season | 1,000 |
| 👑 **Elite Collector** (Premium) | Earn 5 attendance badges this season | 2,000 |

> **📌 Example:** You attend 3 meetups in one month, and each host ends their event that month. You get `3 × 100 = 300` badge XP, plus **Badge Holder** (300 XP) and **Badge Collector** (1,000 XP): **1,600 XP** before any Dragon Boost on the missions.

***

## 🗂️ Older Badges

Earlier attendance badges were minted as NFTs and airdropped to attendees. Badges are now recorded by Hashly when the host ends the event, without NFTs or airdrops.

***

## 🎤 For Hosts

See [Attendance Badges for Hosts](/hashly-docs/for-event-organizers/host-badges.md) to learn how to set up check-in for your events.

***

## 💡 Tips

* 👛 **Connect your wallet before the event starts**, so checking in takes seconds.
* 📷 **Scan again if the code expired**: a fresh code appears every minute.
* 🗓️ **Mind the season**: a badge counts in the season the host ends the event, so a meetup on the last day of a month can count toward the next season.
* 🎯 **Open the Missions page afterwards** to collect the badge missions.

***

> ⚖️ **Please note:** Badges and XP exist only inside Hashly, have no monetary value and can't be sold, transferred or exchanged for money or crypto. See the [Terms of Use](https://hash-ly.com/terms).


---

# 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://hashly.gitbook.io/hashly-docs/community/badges.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.