> For the complete documentation index, see [llms.txt](https://piny.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://piny.gitbook.io/doc/03-create/event.md). # Create an event Events are how you turn a single marker into something bigger: a shared space where many people can pin under the same story. This page walks you through the **Create Event** screen step by step, and then explains how people can create markers for your event. *** ## 1. Name your event and describe the story You start by giving your event a clear identity: * **Name** – the title of your event. * **Description** – a short explanation of what this event is about and why people should care. There are simple limits to keep things readable and safe: * The event name can be up to **128 characters**. * The description can be up to **1024 characters**. Just like markers, these limits are enforced on‑chain using **bytes**, not just visible characters. Some characters (for example emojis or certain non‑Latin letters) can count as more than one byte. The app checks this for you as you type and will warn you if you go over the limit. Think of this section as your event’s elevator pitch: in a few lines, people should understand what they are joining and what kind of markers they are expected to pin. *** ## 2. Set how many pins your event can have Next you define how full your event can get. * **Maximum Pin Count** – the total number of markers that can ever be minted into this event. * If you leave this empty or **0**, the event can accept **unlimited** markers. * If you set a number, minting will stop once that many markers have been created for the event. This is useful if you want to: * Keep a campaign scarce and special (for example, “first 1,000 supporters”). * Run time‑bound activations where you want a clear, finite collection of pins. *** ## 3. Choose participation rules You can control how people can participate in your event with two simple switches: ### Custom Marker Enabled * If this is **on**, attendees can pin their **own custom markers** (using the same Marker Editor they use for personal markers). * If this is **off**, attendees can only use **pre‑defined marker images** that you (the event owner) add to the event. This lets you decide whether the event should feel more like: * A curated visual language (everyone pins with your official event markers). * A creative playground (everyone designs their own marker image). ### Only one pin per address * If this is **on**, each wallet address can mint **only one** marker for the event. * If this is **off**, the same wallet can mint **multiple** markers into the event (until the maximum pin count is reached, if you set one). Use this if you want to: * Make participation feel fair and equal (one message per person). * Avoid a single wallet flooding the event with too many markers. *** ## 4. Pick the event map view Your event has its own home view on the map. On the Create Event screen you: * Move the map to the general **area** where your event makes the most sense (a city, a country, or even the whole world). * Adjust the **zoom level** so the default view feels right for your story. The **map center and zoom** you pick here define how the event will appear on its event page: * This is the initial view people see before they explore individual markers. * They can zoom and move around, but this is the “starting frame” you control. *** ## 5. Review creator, network, and payment Below the map, if your wallet is connected, you’ll see: * **Creator** – your wallet address, with a visual blockie. * **Network** – the blockchain network where the event lives (for example, Avalanche, BNB Smart Chain, Polygon, or Arbitrum). *** ## 6. Submit and create your event When everything looks good: 1. Click the **Submit** button on the page. 2. A confirmation dialog will remind you that some settings (like name, description, max pin count, and one‑pin‑per‑address) cannot be changed later and will show the amount you will pay, if any. 3. Confirm in the dialog, then confirm the transaction in your wallet. After the transaction is confirmed on‑chain: * Your event is created on the selected network. * You’ll see a success dialog and can continue directly to the **Event Management** view (where you can enable the event, fine‑tune markers, and share the event). At this stage, the event exists on the blockchain but initially it is **disabled** until you finish setting it up and choose when to open it for participation. *** ## 7. Managing your event after creation Once your event is created, you can manage it from its dedicated event management screen. Management is broadly categorized into three main sections: 1. Event general settings 2. Payment settings 3. Event markers settings ### 7.1 Event General Settings In this section, you control the basic operation of your event: * **Enable or disable** the event so people can or cannot pin markers. * Turn **Custom Marker Enabled** on or off. * Adjust the **map center and zoom** that define how the event home page looks. * **Stop** the event permanently if you want to close participation forever. When you stop an event: * No more markers can be pinned to it. * Stopping is permanent for that event, and the interface will clearly warn you. These general settings provide full control over when the event is active and how it appears on the map. ### 7.2 Payment Settings If you want **joining your event to be paid** when people mint a marker into it, this is where you set it up. If you prefer your event to be **completely free**, you generally don’t need to change anything in this section. On the payment side: * The protocol defines which **tokens are allowed** to be used with events. * For your specific event, you can **enable or disable** each allowed token and set the **amount** that should be paid in that token when someone mints a marker into your event. * In some configurations, there may also be a protocol‑level **service fee** that is automatically taken from each payment. This fee is managed by the contracts; you only choose **which tokens** are accepted for your event and **how much** participants pay. Why make participation paid? * Help reduce spam and keep the story focused on people who truly care. * Turn your event into a **funding channel** – for example, a disaster relief campaign where every pin represents a donation to support recovery. * Support a creator’s journey – for example, a traveler funding their trips where each marker is a small contribution to the next adventure. * Simply put a **symbolic value** on joining your event, turning each pin into an economic signal that this story matters. ### 7.3 Event Markers Settings Finally, you manage the visual language and markers that participants can use for your event. * In the event markers tab, you can add or remove **marker images** (image URIs) that belong to this event. * These images create the official event marker “palette” that participants can use. * If custom markers are disabled in the event settings, participants can only mint markers using this predefined palette. Even if you later remove a marker image from the event: * Any markers that were **already minted** using that image still count as valid participation. * Those pins will continue to appear under the event and in participants’ wallets. * Removing a marker image only prevents **new** participation with that marker; it does not erase past activity. When adding a new marker image: * You design or upload the marker visual using the same Marker Editor experience. * The image is uploaded to IPFS, and its **image URI** is stored on-chain for the event. This allows you to create a visually consistent event experience and clearly define which markers participants can use.