Provide a narrative description of the purpose of the project.

For each existing entity, list key team members with full name, official title, and prior experience. Explicitly mark non-existent entities.

Describe DAO governance, powers, economic rights, and control surfaces. If no DAO exists, state so and still address current tokenholder governance rights and economic arrangements.

• (a) IP ownership & control — State what IP the DAO owns or controls (e.g., codebases/repos, trademarks/brands). Note any license if relevant.
• (b) Contract/admin powers — List on-chain or administrative authorities and limits: pause/upgrade roles, governance-executor authorities, and the method of authority for each.
• (c) Locked-token rights (conditional) — If locking/staking for additional rights exists, explain the additional rights and what tokenholders can and cannot decide. If no locking mechanism exists, leave absent.
• (d) Current tokenholder governance rights and economic arrangements — If any, describe current governance rights of tokenholders and presently operative rights or arrangements relating to treasury actions, fee-routing, rewards, buybacks, or other protocol-controlled resources. If none, state that explicitly.
• (e) Control surface reliance — If any, briefly describe the anticipated or possible evolution of the protocol's governance/control model.
• (f) Dissolution authority — State who can dissolve/wind up the DAO and by what mechanism.

Describe the Primary Foundation, including entity details, IP ownership, governance or token powers, contract/admin powers, and economic arrangements. If it does not exist, state so explicitly.

• (a) Entity — Type and jurisdiction.
• (b) IP ownership & control — What IP the entity owns/controls and an explanation of any subsidiary entities.
• (c) Powers over DAO, treasury, protocol-controlled resources, and token administration — If any, describe current powers over DAO governance, treasury actions, protocol-controlled resources, token administration, or reward parameters, and the method/threshold for each.
• (d) Powers over DevCo — Explain whether the Foundation can exert direct or indirect influence over decision-making of the Developer Company.
• (e) Contract/admin powers — Pause/upgrade/governance-executor authorities and the method/threshold for each.
• (f) Current economic arrangements and distribution policies — Describe current governance-approved, contractual, or programmatic mechanisms by which protocol-controlled resources may be directed to this entity, its equityholders, contributors, or other participants. If none exist, state that explicitly.

Describe the Primary Developer Company, including entity details, IP ownership, governance or token powers, contract/admin powers, and economic arrangements. If it does not exist, state so explicitly.

• (a) Entity — Type and jurisdiction.
• (b) IP ownership & control — What IP the entity owns/controls and an explanation of any subsidiary entities.
• (c) Powers over DAO, treasury, protocol-controlled resources, and token administration — If any, describe current powers over DAO governance, treasury actions, protocol-controlled resources, token administration, or reward parameters, and the method/threshold for each.
• (d) Powers over Foundation — Explain whether the Developer Company can exert direct or indirect influence over decision-making of the Foundation.
• (e) Contract/admin powers — Pause/upgrade/governance-executor authorities and the method/threshold for each.
• (f) Current economic arrangements and distribution policies — Describe current governance-approved, contractual, or programmatic mechanisms by which protocol-controlled resources may be directed to this entity, its equityholders, contributors, or other participants. If none exist, state that explicitly.

Identify affiliated protocol contributors and explain their control, funding, or operational relationship to the project. If none exist, state so explicitly.

• (a) Identity & role — Legal name, entity type, jurisdiction, and role.
• (b) Parameter control & scope — If any, what major protocol parameters the APC controls; include the method of authority. If none, say so.
• (c) Contract/admin powers — If any, provide pause/upgrade powers, governance-executor authorities and limitations; include the method/threshold for each. If none, say so.
• (d) Compensation and material economic arrangements — If any protocol-generated resources or economic value is dynamically routed to the APC, describe the arrangement. If none, state that explicitly.

Disclose launch and initial supply details in a single initial allocation schedule covering the token's launch. Include:

• (a) Launch supply totals — The total number of tokens issued at launch, the total number of tokens locked at launch, and the total number of tokens unlocked at launch.
• (b) Recipient categories & use of funds — The recipient categories with brief explanations as to how the category will use the tokens so an auditor can distinguish each bucket.
• (c) Initial price per token — The expected initial price per token.
• (d) Ticker / market symbol — The ticker/market symbol.
• (e) Total supply & supply regime — The total supply and whether the supply is fixed (if not explain inflation rate or deflation rate).
• (f) Initial vesting / release schedules — The initial vesting/release schedules (identify which categories/recipients are subject to vesting and the high-level timing logic).

If there are not post-TGE token compensation plans state explicitly they do not exist. If there are then state the:

• A) Post-TGE employee lock as % of circulation. State the current total amount of tokens locked or unvested attributable to post-TGE employees, expressed as a percentage of current circulating supply. If circulation isn't used, an explicitly labeled equivalent (e.g., "% of total supply" or "% of FDV") is acceptable. Must include an "as of" timestamp.
• B) Typical post-TGE vesting schedule. Describe the standard vesting terms used for post-TGE grants, including: cliff length (or "no cliff"), vesting frequency (e.g., monthly/quarterly), and total duration. If variants exist (e.g., performance grants), note the typical range.

Disclose token-based compensation for external advisors and service providers (e.g., legal, marketing, technical, growth) funded from the on-chain treasury or token reserves held by the Foundation, Labs/DevCo, or similar entities. You do not need to disclose individual names, roles, salaries, or any advisors receiving fiat-only compensation.

Provide:

• (a) Whether any such token-based payments or advisory commitments exist (or explicitly state that no token-based compensation for advisory commitments exist).
• (b) The total token allocation across all advisory services (tokens paid and/or reserved in aggregate).
• (c) The payer entity (e.g., Foundation, Labs/DevCo, DAO/treasury).
• (d) A brief description of the advisory/services (e.g., "legal and regulatory advisory," "growth and BD support," "security advisory").

Disclose ongoing KOL/influencer relationships that partially or fully received tokens for payment. Do not need to disclose KOL/influencers that do not receive tokens for payment. Use lettered sub-items:

• (a) Existence & scope: State plainly whether KOLs receive tokens for payment, if none say so.
• (b) Usernames & roles: List usernames/handles (with platforms) for participating KOLs and describe their roles/activities. Legal names are not required.
• (c) Token allocation & vesting/locks: Say whether tokens were allocated to KOLs. If yes, provide the aggregate token amount across all KOLs and summarize vesting/lock terms (e.g., cliff and vest length, or "no vest/locks").

Publicly label all wallets that hold Unissued Tokens (e.g., foundation, operations, treasury, investor reserve), keep each category in distinct wallets (a unique address per category), and disclose who controls each wallet (DAO multisig, foundation, labs/devco, operations, or contract controller + admin). Include one verification link per wallet (docs or explorer).

Definition: Unissued Supply = tokens authorized by the contract but not yet issued to any party; where they sit (treasury or mint authority) does not change that they are unissued. For instance: if a token has a total supply cap of 1B, and 400M tokens have been issued to investors, the team, and users (whether vested or unlocked), then those 400M count as issued supply. The remaining 600M are authorized but unissued supply, even if they are already minted into a DAO treasury wallet.

Projects must disclose all material terms of market-making arrangements that affect token liquidity. If the project has no agreements or deals with market makers, state that explicitly; doing so earns full credit. For each market maker, include in a table:

• (a) Market maker's name — the market maker's name;
• (b) Token allocation or loaned amount — the token allocation or loaned amount as a percentage of total supply;
• (c) Duration/term of agreement — the duration/term of the agreement; and, where applicable,
• (d) Name of agreement structure — label the financial vehicle being used in the agreement (i.e. loan, option/call, retainer model) without describing trading strategy or expected outcomes.

If the project has no agreements or deals with market makers, state that explicitly; doing so earns full credit. If no native tokens were loaned or allocated to market makers, state that explicitly; cash/fiat retainers or fees are not required for this item.

Projects must disclose all material terms of centralized or decentralized exchange listings that affect token liquidity. For each listing, include in a table:

• (a) Exchange name / DEX pool — the exchange name (and, for DEX, the specific pool/pair);
• (b) Token allocation for listing — the token allocation supplied or committed for listing as a percentage of total supply;
• (c) Term Duration — the duration/term of any listing lockups, liquidity, or incentive programs; and, where applicable,
• (d) Native-token listing fees — whether any listing fees were paid in native tokens, with amounts (tokens or % of supply), recipients, and any vesting or lock terms tied to the partnership.

If the project has no agreements or deals with CEX or DEX, state that explicitly; doing so earns full credit. If no native-token listing fees were paid, state that explicitly; cash/fiat fee amounts are not required for this item.

If a category does not exist or is not applicable, make that clear in plain language (no specific wording required).

• (a) Buybacks & re-release (bought-back tokens only): source of funds (e.g., % of revenue), treatment (burn/treasury/POL), controller/approvals (DAO, multisig, or contract), and whether bought-back tokens can ever be re-released; if "never," give the mechanism (burn or irrevocable timelock); otherwise state the re-release policy.
• (b) Protocol-owned liquidity (POL): where deployed, total token or dollar size across all deployments, controller, and unwind/exit policy.
• (c) Liquidity deals / purchased TVL: the total size across all deals, and where the capital participates - no counterparty names needed.
• (d) Token-secured loans/lines (incl. against unissued tokens): principal, gross position size, collateral, counterparties, and unwind/exit policy.

Disclose all prior token sales by the Project — including fundraising rounds, any material OTC sales to investors, and any discounted market-maker sales. For each sale, provide:

• (a) Series Name / Early-Stage Investment Instrument used (i.e. SAFT, STAMP, SAFE, SAFE+Token Warrant, etc.)
• (b) Date of sale (at least month & year).
• (c) Number of tokens sold (or % of total supply)
• (d) Vesting schedule

If no prior sales occurred, state that explicitly (e.g., "No prior fundraising, OTC, or discounted MM sales have occurred.")

Provide a narrative description of the Project's material funding sources, economic flows, and operational provisioning, broken out by entity: Foundation, Lab/DevCo, and DAO. If an entity does not exist, state that explicitly. If an entity exists but does not pursue revenue-generating activity, state how it funds or provisions its operations.

• (a) Entity existence — Explicitly state whether each of Foundation, Lab/DevCo, and DAO exists.
• (b) Material sources of funding or economic inflows — For each existing entity, describe its primary sources of operational funding or economic inflows, if any (e.g., service fees, grants, donations, treasury reserves, token reserves, staking rewards, validator/sequencer income, partnership payments, retained revenue, or other protocol-related receipts). If none, state "none."
• (c) Operational use of resources — Briefly describe how those resources are generally used (e.g., development, operations, security, ecosystem support, grants, liquidity support).
• (d) Onchain Resource Usage — Provide links to public dashboards and token holder relations reports that help explain on-chain financial activity, treasury activity, fee flows, rewards, or other protocol-controlled resources. Make certain to explain what each link is for.

If any, list prior exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply. This question is not asking about general protocol, application, or smart contract exploits unless the incident directly affected the native token itself. If no prior incidents, state this explicitly (e.g., "No exploits affecting tokenholders or protocol funds as of YYYY-MM-DD").

• (a) Date & component affected — Date (YYYY-MM or YYYY-MM-DD), chain(s)/component affected.
• (b) Exploit vector summary — Plain-language summary of the exploit vector (what the hack was).
• (c) Quantified impact — Quantified impact (assets/tokens affected or a clear "no loss of funds" statement).
• (d) Remediation/response taken — Remediation/response taken (patches, upgrades, governance actions, compensation).
• (e) Current status — Current status (resolved, in litigation, under investigation, refunded, etc.).
• (f) References (optional) — Link(s) to post-mortem/advisory/PR.

Provide a single income statement, expense summary, or comparable operating statement for the primary Foundation or Developer Company. A consolidated or entity-level presentation is acceptable. Balance Sheet and Statement of Cash Flows may be included but are not required. This item is intended to provide transparency into offchain operating resources and expenditures only.

Identify to the best of your ability the token's current deployments across chains, including project-issued deployments, project-endorsed representations, and, if possible, documented third-party wrapped or bridged representations.

For each entry, provide:

• Token Contract Address or Chain-Specific Asset Identifier
• Chain
• Deployment Type: Protocol-level asset / Direct token issuance / Wrapped or bridged representation
• Project Relationship: Native-token / Project-endorsed / Endorsed third-party / Third-party, endorsement not established / Explicitly unsupported
• Supporting Source: Link to supporting source

Multiple entries on the same chain are permitted.

Definition: A protocol-level asset is an asset whose balances and transfers are handled directly by the blockchain's core rules, rather than by a token smart contract. For protocol-level assets without a token contract address, enter "No contract address" and identify the asset and chain.