> 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/for-event-organizers/submit-event.md). # Submit an Event Anyone with a connected wallet can add events to the Hashly calendar, and Dragon holders can publish an X Space from its link alone. *** ## 🎯 Two Ways to Add an Event | Way | Who can use it | Review | | ---------------------------------------- | ------------------------------- | ------------------------------------------ | | 🎙️ **Publish an X Space from its link** | Santuario Hedera Dragon holders | None: it goes live straight away | | 📝 **Submission form** | Any connected wallet | Admin review, unless you hold El Santuario | Both start on the [Submit Event](https://hash-ly.com/events/new) page. It's also the **Submit Event** button on the calendar when your wallet is connected. *** ## 🎙️ Publish an X Space from Its Link 1. In the **Publish an X Space instantly** panel, paste the Space link (`https://x.com/i/spaces/…`). 2. Press **Check Space** and review the preview: title, host, start time in UTC, language and notes from X. 3. Press **Publish now**. The Space is published at once, labelled **X Space** with a **Verified** badge, and you receive **100 XP**. Its details are read from X and can't be edited in the preview. Hashly refuses links that aren't Spaces, Spaces already on the calendar, Spaces without a scheduled start and Spaces that are already over. More in [Events Calendar](/hashly-docs/discover/events-calendar.md). *** ## 📝 The Submission Form Pick the **Event Type** first: **Mint Event**, **Meetup**, **Hackathon** or **Other**. Every type needs: | Field | Notes | | --------------- | ------------------------------------------------------------------------------------ | | **Title** | 3 to 100 characters. Called Project Name for mints and Hackathon Name for hackathons | | **Description** | 10 to 2,000 characters | | **Cover Image** | Upload a JPG, PNG, GIF or WebP up to 3 MB. Recommended size: 1200×630 | ### 🖼️ Mint Event | Field | Required | Notes | | ------------------------------------ | -------- | ----------------------------------------- | | **Total Supply** | ✅ | | | **Mint Phases** | ✅ | At least one. Add more with **Add Phase** | | ↳ Phase Name | ✅ | For example Whitelist or Public Sale | | ↳ Start and End (date and time, UTC) | ✅ | | | ↳ Price | ✅ | In HBAR or USDC | | ↳ Max/Wallet | ❌ | | | ↳ Whitelist Only | ❌ | Toggle | | **Website, X and Discord URLs** | ❌ | | The mint's date on the calendar is the start of its earliest phase. ### 🤝 Meetup | Field | Required | Notes | | -------------------------------------- | -------------------- | ------------------------------------------------------------------------------------------------ | | **Host** | ✅ | Use an X @handle to count toward Top hosts | | **Entry Fee** | ❌ | Leave empty for a free event | | **Language** | ❌ | English by default. Also Spanish, Portuguese, French, German, Japanese, Korean, Chinese or Other | | **Type** | ✅ | Online or In Person | | **Location** | For in-person events | For example Berlin, Germany | | **Start and End** (date and time, UTC) | ✅ | | | **Links** | ✅ | At least one and up to 10, each with a name and a URL | ### 🏗️ Hackathon The same fields as a meetup, with **Organizer** (required) in place of Host and an optional **Prizes** field. ### 📣 Other For announcements such as project news or network upgrades. **Host** is optional. The dates, type, language and links work as for a meetup. *** ## ✅ After You Submit * ⚡ **El Santuario holders** (and admins): the event is published straight away and earns **100 XP**. * 🔎 **Everyone else:** the event waits for admin review. You're taken back to the home page with an **Event submitted** notice, and the event appears on the calendar once it's approved. * ⭐ **On approval** you receive **100 XP** the first time the event is approved. Dragon Boost applies to these points. * 📋 **Track your events** on your [Profile](https://hash-ly.com/profile), grouped by type and marked **Pending**, **Approved** or **Rejected**, with shortcuts to view and edit each one. * ✏️ **Need to change something?** Use **Edit Event** on the event's page or the edit shortcut on your profile. *** ## 🏅 Mission Rewards Approved events also count toward season missions on the [Missions](https://hash-ly.com/missions) page. Published X Spaces and events published straight away count too. | Mission | Requirement | XP | | ----------------------- | ----------------------------- | ------- | | 🥇 **Event Creator** | 1 event approved this season | **100** | | 🏆 **Prolific Creator** | 5 events approved this season | **500** | *** ## 💡 Tips * 🕐 **All times are UTC.** Convert your local time before you fill in the dates. * 🎤 **Put the host as an @handle** (for example `@hashly_h`) so the event page links to it and it counts on the Top hosts board. * 🖼️ **Use the recommended 1200×630 size** for your cover image. * 🎖️ **Hosting a meetup?** You can also [issue attendance badges](/hashly-docs/for-event-organizers/host-badges.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/for-event-organizers/submit-event.md?ask=&goal= ``` `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.