• (a) full names,
• (b) official titles,
• (c) and prior experience of key team members.

For any non-existent entity, explicitly mention it does not exist. External links may be included but they will not factor into the score.

• (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 (e.g., multisig pause), governance-executor authorities, and the method of authority for each (e.g., veto, majority, super-majority).
• (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 the current governance rights of tokenholders and any 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 (e.g., on-chain vote threshold, board resolution of a legal wrapper).

• (a) Entity — Type and jurisdiction.
• (b) IP ownership & control — What IP the entity owns/controls (repos/code, trademarks/brand; license optional)
• (c) Powers over DAO, treasury, protocol-controlled resources, and token administration — If any, describe the current powers over DAO governance, treasury actions, protocol-controlled resources (e.g. revenue), 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 DevCo.
• (e) Contract/admin powers — Pause/upgrade/governance-executor authorities, and the method/threshold for each (e.g., veto/majority/super-majority).
• (f) Current economic arrangements and distribution policies — Describe any current governance-approved, contractual, or programmatic mechanisms, if any, by which protocol-controlled resources, treasury assets, fees, revenue, rewards, or token distributions may be directed to this entity, its equityholders, contributors, or other participants. If no such mechanism currently exists, state that explicitly.

• (a) Entity — Type and jurisdiction.
• (b) IP ownership & control — What IP the entity owns/controls (repos/code, trademarks/brand; license optional)
• (c) Powers over DAO, treasury, protocol-controlled resources, and token administration — If any, describe the current powers over DAO governance, treasury actions, protocol-controlled resources (e.g. revenue), token administration, or reward parameters, and the method/threshold for each.
• (d) Powers over Foundation — Explain whether the DevCo 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 (e.g., veto/majority/super-majority; "3/5 multisig").
• (f) Current economic arrangements and distribution policies — Describe any current governance-approved, contractual, or programmatic mechanisms, if any, by which protocol-controlled resources, treasury assets, fees, revenue, rewards, or token distributions may be directed to this entity, its equityholders, contributors, or other participants. If no such mechanism currently exists, state that explicitly. Do not discuss hypothetical future dividends, repurchases, or distributions unless formally adopted.

• (a) Identity & role — Legal name, entity type, jurisdiction, and role (e.g., core development, security, infrastructure, market making, operations).
• (b) Parameter control & scope — For each existing APC, if any, what major protocol parameters the APC controls; include the method of authority (e.g., veto, majority, super-majority). If none, say so.
• (c) Contract/admin powers — For each existing APC, if any, provide the pause/upgrade powers (e.g., multisig pause), governance-executor authorities and limitations; include the method of authority for each (e.g. veto, majority, super-majority). If none, say so.
• (d) Compensation and material economic arrangements — For each existing APC, if protocol-generated resources or economic value is dynamically routed to the APC, describe the arrangement. If applicable, include the resource sources, routing mechanism, payment frequency, and duration. If no protocol resources or resources-linked economics are routed to the APC, state that explicitly.

• (a) Post-TGE employee lock as % of total supply — State the current total amount of tokens locked attributable to post-TGE employees, expressed as a percentage of total supply.
• (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.

• (a) Existence — Whether any such token-based payments or advisory commitments exist (or explicitly state that no token-based compensation for advisory commitments exist).
• (b) Total token allocation — For all existing token-based advisors, disclose the total token allocation across all advisory services.
• (c) Payer entity — For each existing token-based advisor, share the payer entity (e.g., Foundation, Labs/DevCo, DAO/treasury).
• (d) Description of advisory/services — For each existing token-based advisor, provide a brief description of the advisory/services (e.g., "legal and regulatory advisory," "growth and BD support," "security advisory").

• (a) Existence & scope — State plainly whether KOLs receive tokens for payment.
• (b) Usernames & roles — List usernames/handles (with platforms) for KOLs that received token-based compensation and describe the nature of their activities. Legal names are not required.
• (c) Token allocation & vesting/locks — Provide the aggregate token amount across all such arrangements and summarize vesting, lock, or release terms.

• (a) A category label explaining the wallet's primary function.
• (b) chain the wallet is on.
• (c) The unique address of the wallet.
• (d) The mechanism of control (e.g., DAO, multisig).
• (e) One verification link to a blockchain 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.

• (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).

If no native tokens were loaned or allocated to market makers, state that explicitly; cash/fiat retainers or fees are not required for (b).

• (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; cash/fiat fee amounts are not required for this item.

• (a) Token repurchases or secondary-market accumulations (if any) — Source of funds, treatment (burn, treasury retention, POL, redistribution, or other), policy controller (who can change the secondary-market accumulation strategy), and whether those tokens may be re-used, re-issued, or permanently removed from circulation.
• (b) Protocol-owned liquidity (POL) (if any) — Where deployed, total token or dollar size across deployments, policy controller (who can change the POL strategy), and unwind/exit policy.
• (c) Liquidity deals / purchased TVL (if any) — The total size across all deals, and where the capital participates - no counterparty names needed.
• (d) Token-secured loans/lines (incl. against unissued tokens) (if any) — Principal, gross position size, collateral, counterparties, and unwind/exit policy.

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

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

• (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).
• (c) Operational use of resources — For each existing entity, briefly describe how those resources are generally used (e.g., development, operations, security, ecosystem support, grants, liquidity support).
• (d) Onchain Resource Usage — For each existing entity, 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.

• (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 — Link(s) to post-mortem/advisory/PR.