Frequently Asked Questions

An ownership token is a token whose holders have enforceable, onchain rights--directly or via tokenholder-governed execution--over the assets and value flows that determine economic outcomes.

The framework is intended for reviewing and verifying the programmatic economic rights associated with a token using primary evidence. It evaluates both onchain mechanisms and relevant offchain dependencies that may reinforce or undermine expectations of ownership rights.

The Ownership Token Framework is not an endorsement of any project and is not investment advice. The Framework evaluates tokenholder rights and related dependencies, not whether a project generates value. It provides structure and primary evidence that can inform fundamental analysis and help market participants reach their own conclusions, but it is not sufficient on its own.

Our token reports include metrics, criteria, and evidence.

Each of our four metrics contain a checklist of criteria. For each criteria we provide primary evidence, including:
Onchain: active deployments, permissions/roles, parameters, execution history.
Offchain (where relevant): public filings/registrations, published legal terms, and other public documentation.

You can read the full metric definitions and methodology here.

All evidence used by the Framework is public and linked in the findings. For onchain criteria, we use active deployments and execution history. For offchain criteria, we use public registrations and legal disclaimers (where available).

Initial research and sourcing is done by the Aragon team. Protocol teams, investors, and community members can also submit public primary evidence to support, correct, or challenge specific findings.

You can learn more about the methodology here.

We started with a set of established projects to validate the framework. Ongoing inclusion is request-driven: anyone can request a token be reviewed for possible inclusion.

Submit a request (or refer a token) using this here.

If you want to provide feedback, propose improvements, or explore collaboration, reach out here.