> For the complete documentation index, see [llms.txt](https://docs.lighter.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lighter.xyz/trading/guilds.md). # Guilds Guilds are trading communities inside Lighter. A guild has one leader, optional admins and up to one hundred guild members. Members see each other's performance, climb a shared ladder against other guilds and, with Guild Duels, put a USDC stake on a head-to-head contest. Guilds are the social layer on top of what already exists: your trading, PnL and referral codes work exactly the same whether or not you are in a guild. ## Key facts * **Master accounts only.** Membership is tied to your L1 address. Sub-accounts are not members on their own; their trading is aggregated under the master, as on the PnL leaderboard. * **One guild per account.** Joining a guild cancels all your other pending invites and join requests. * **Public by design.** A guild page shows every member's address, role, PnL contribution and the guild's aggregated open positions. You are told this before you join. * **Guild creation is currently whitelist-only.** Creating a guild requires your address to be approved by the Lighter team. Joining an existing guild follows its join policy. ## Roles | Role | Can do | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Leader** | Everything an admin can, plus: edit the guild (name, description, join policy, member limit), promote/demote admins, transfer leadership, archive the guild, and act for the guild in duels (challenge, counter, accept, decline, cancel, draft the roster, stake). Exactly one leader per guild. | | **Admin** | Approve/reject join requests, create and revoke invite codes, remove members. Admins cannot change or remove other admins or the leader. | | **Member** | Appear on the guild page and ladder, share the guild link, leave when not locked into a committed duel, set their duel availability. | The leader cannot leave the guild. To leave, transfer leadership to another member first (you stay in the guild as an admin). A guild can only be archived when the leader is its last member; archiving removes it from the ladder. ## Creating a guild Guild creation is currently restricted to whitelisted addresses approved by the Lighter team. A whitelisted address can create exactly one guild and becomes its leader. On creation you set: * **Name** — 3 to 32 characters: letters, numbers, spaces and basic punctuation (`_ . - '`). Names are unique (case-insensitive) and can be changed once every 30 days. * **Description** — up to 500 characters. * **Join policy** — *Accept join requests* (default: anyone can request, the leader or an admin approves) or *invite only* (only invited addresses and invite-code holders can join). * **Max members** — 1 to 100. It cannot be set below the current member count. ## Joining a guild There are three ways in: 1. **Request to join.** On a guild that accepts requests, send a join request. The leader or an admin approves or rejects it. Requests expire after 7 days; you can only have one pending request per guild and can withdraw it at any time. 2. **Invite code.** A leader or admin generates single-use codes (up to 10 at a time). A code can be bound to a specific address or open to anyone with the link. Codes expire after 7 days and can be revoked while unused. Redeeming a valid code joins you instantly. Invites bound to your address appear on your guild page until you accept or decline them. 3. **Referral link.** If the owner of a referral code is in a guild, anyone redeeming that code is shown the guild and offered to send a join request to it. The referral itself is unchanged and independent of whether the request is approved. If you are already in a guild you must leave it before joining another one. ## Guild page * **Identity block** — name, description, leader, member count, creation date, the guild's PnL and global rank for the selected window, and the duel record (W-L-T). * **Members** — address, role, joined date and duel availability of every member. * **Leaderboards** — the PnL leaderboard filtered to the guild's members: PnL / ROI / volume over 24h, 7d, 30d or all-time (default 30d). Same formulas and refresh (hourly) as the global PnL leaderboard; guilds add scoping, not new scoring. * **Aggregated positions** — the guild's combined open positions per market: net direction and size, long and short size, position value, unrealized PnL, average entry, and how many members hold it. * **Duels** — the guild's record, pending challenges (own guild only) and duel history. See [Guild Duels](/trading/guilds/guild-duels.md). * **Manage** (leader/admin) — pending requests, invite codes, member roles, settings, leadership transfer and archive. ## Guild ladder The ladder (`Guilds` page and the *Guild ladder* tab of the leaderboard) ranks all guilds on the **sum of their members' PnL** over the selected window (24h / 7d / 30d / all, default 30d), with volume shown alongside. Only members who appear on the PnL leaderboard are counted (`ranked members`). Rankings refresh hourly, with the PnL leaderboard. Rows on the global PnL leaderboard carry the trader's guild, linking to the guild page. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lighter.xyz/trading/guilds.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.