> 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/discover/voting-system.md).

# Voting System

Votes on Hashly are **stars**. There are no downvotes. Every wallet has voting power, holders of two NFT collections carry more of it, and every star is recorded on the **Hedera Consensus Service (HCS)**.

***

## ⚖️ Voting Power

### 🎯 Base Vote

Every connected wallet starts with **1**.

### 🐉 Extra Weight from NFTs

| NFT                               | Token ID      | Extra weight   | Details                                    |
| --------------------------------- | ------------- | -------------- | ------------------------------------------ |
| 🐉 **Santuario Hedera (Dragons)** | `0.0.7235629` | **+1 per NFT** | Grows with your holdings: 10 Dragons = +10 |
| ⚔️ **El Santuario**               | `0.0.9954622` | **+5**         | Counts once, however many you hold         |

> **📌 Example:** a wallet with 3 Dragons and 1 El Santuario stars with a weight of:
>
> `1 (base) + 3 (Dragons) + 5 (El Santuario) = 9`

Holdings are read from the **Hedera mirror node** at the moment you vote. When you star a token or an NFT collection, the confirmation tells you the weight your star carried.

> ⚠️ **About these NFTs.** Santuario Hedera Dragons, El Santuario NFTs and any other NFT that unlocks something on Hashly are utility tokens: digital collectibles that give access to features such as extra voting power. They are not securities, shares, investment contracts or financial instruments. Holding one gives no ownership of Hashly or of any company and no right to profits, dividends or revenue. They are not offered as an investment, and nobody should acquire one expecting a profit. Their marketplace price is set by buyers and sellers, and Hashly doesn't control or guarantee it. The features they unlock can change or end. See the [Terms of Use](https://hash-ly.com/terms).

***

## 📊 Daily Vote Limit

| Account                              | Votes per day |
| ------------------------------------ | ------------- |
| 🆓 **Free**                          | **5**         |
| 💎 **Hashly Premium** (while active) | **20**        |

* 🔗 **One allowance for everything.** Events, tokens, NFT collections and ecosystem projects all draw from the same daily votes.
* 1️⃣ **One vote per star**, whatever weight the star carries.
* 🕛 **Resets at 00:00 UTC.** Unused votes don't carry over.
* 👀 **Check what's left** in the votes pill at the bottom of the sidebar. Click it to see when the limit resets.

Premium is sold per season, and its extra votes stop when that season ends.

***

## ⭐ How Stars Work

### 📅 Events

Mints, meetups, hackathons, X Spaces and other events all use stars. Open the event and press **Give a Star**.

* 🗓️ **One star per event per UTC day.** After 00:00 UTC you can star the same event again.
* ➕ **Stars add up.** Each star adds your full weight to the event's total, so events build support over time.
* 🐉 The weight of each Dragon, and the El Santuario bonus, reaches a given event at most once per UTC day.

### ♾️ Forever Mints

Forever mints on the calendar work a little differently:

* 🔁 **Your star counts once.** Starring again uses a daily vote and moves the date of your vote to today, but only adds weight for NFTs that haven't counted on that mint yet.
* 🧹 **NFT weight follows your holdings.** A daily check at 00:00 UTC removes the weight of Dragons or El Santuario NFTs your wallet no longer holds.

### 🪙 Tokens, 🎨 NFT Collections and 🏢 Ecosystem Projects

Star them from the **Vote** column on [Markets](https://hash-ly.com/markets), from a token's own page, or from the [Ecosystem](https://hash-ly.com/ecosystem) directory.

* 🗓️ **One star per wallet per item per UTC day.**
* 🔄 **Nothing accumulates.** The counter shows **today's** stars, weighted by voting power, and starts again from zero at 00:00 UTC.
* 🧠 **Stars are kept as history.** [Mindshare](/hashly-docs/markets/mindshare.md) reads them over 24-hour, 7-day and 30-day windows.

***

## 📋 Voting by Content Type

| Content                            | Where to vote       | How often                       | Counter    | HCS topic                                                     |
| ---------------------------------- | ------------------- | ------------------------------- | ---------- | ------------------------------------------------------------- |
| 🖼️ NFT mints                      | Event page          | Once per event per UTC day      | Adds up    | [Event votes](https://hashscan.io/mainnet/topic/0.0.10279947) |
| 🤝 Meetups and 🎙️ X Spaces        | Event page          | Once per event per UTC day      | Adds up    | [Event votes](https://hashscan.io/mainnet/topic/0.0.10279947) |
| 🏗️ Hackathons and 📣 other events | Event page          | Once per event per UTC day      | Adds up    | [Event votes](https://hashscan.io/mainnet/topic/0.0.10279947) |
| ♾️ Forever mints                   | Event page          | Your star counts once           | Adds up    | [Event votes](https://hashscan.io/mainnet/topic/0.0.10279947) |
| 🪙 Tokens                          | Markets, token page | Once per token per UTC day      | Today only | [Asset votes](https://hashscan.io/mainnet/topic/0.0.10279948) |
| 🎨 NFT collections                 | Markets (NFTs tab)  | Once per collection per UTC day | Today only | [Asset votes](https://hashscan.io/mainnet/topic/0.0.10279948) |
| 🏢 Ecosystem projects              | Ecosystem           | Once per project per UTC day    | Today only | [Asset votes](https://hashscan.io/mainnet/topic/0.0.10279948) |

***

## ⛓️ On-Chain Recording

Each star is saved on Hashly first and then sent to HCS, so the on-chain record can land a few seconds after you vote.

**Event star** (topic `0.0.10279947`):

```json
{
  "type": "event_vote",
  "version": 1,
  "wallet": "0.0.xxxxx",
  "event_id": "cuid123...",
  "event_type": "meetup",
  "vote": "up",
  "timestamp": 1234567890000
}
```

**Token, collection or project star** (topic `0.0.10279948`):

```json
{
  "type": "asset_vote",
  "version": 1,
  "wallet": "0.0.xxxxx",
  "target_id": "0.0.123456",
  "target_type": "token",
  "vote": "up",
  "voting_power": 9,
  "holdings": { "el_santuario": 1, "santuario_hedera": 3 },
  "timestamp": 1234567890000
}
```

This means:

* ✅ **Every vote can be checked** on-chain, by anyone
* 🔒 **Nobody**, admins included, can edit or delete a record
* 🔍 The community can **audit rankings** independently

Every field is explained in [On-Chain Records (HCS)](/hashly-docs/technical/hcs-voting.md).

***

## 💡 Tips

* 🗓️ **Spend your votes before 00:00 UTC.** They don't roll over.
* 📅 **Return to the events you back.** Stars on events add up day after day.
* 🧠 **Stars on projects, tokens and collections feed Mindshare.** Ecosystem project stars are its strongest attention signal.
* 🏅 **Voting counts toward missions.** See [Missions & XP](/hashly-docs/rewards/missions.md).


---

# 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/discover/voting-system.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.
