How to assess a crypto project’s team and governance
Assess a crypto team by verifying identities, tracing past projects, and mapping who controls votes and treasury keys. Then record findings and set alerts for changes.
Vahe HakobyanEditor-in-chief
Updated Oct 6, 20263 min readFact-checked
On this page
- Check if names are public and match work history.
- Trace past projects for exits and disputes.
- Find who can move treasury funds and cancel votes.
A strong audit does not replace knowing who decides and who holds the keys. Collect records, then verify each claim.
What should you gather before you start?
Collect the project's core documents first. Gather the governance docs, token contract address, team profiles, governance forum, and audit reports.
How do you assess team and governance?
Work through the team first, then the rules that control money and upgrades. A public team is one whose real identities are known. A multisig wallet needs several keys to move funds.
- 1Verify team identitiesCheck names, photos, and work history on LinkedIn, GitHub, or conference records.
- 2Trace past projectsSearch each member's earlier crypto projects, token launches, and exit events.
- 3Map governance controlRead the docs to see who can propose votes, cancel them, and how voting power is counted. Check who holds the final say over the treasury.
- 4Read timelocksLook for a timelock. A timelock is a delay between a decision and its execution, giving users time to react.
- 5Check regulatory filingsIf the project ties to a US public company, read its filings on the SEC's EDGAR system.
What should you do after you assess?
Write down what you found and where you found it, because rules change. Keep a dated record of the contract address, the people with control, and the documents.
Frequently asked questions
An audit reviews code for bugs, not team conduct or governance. You can still check who controls keys and how votes work, but anonymous teams give you fewer ways to verify claims.
Read the docs to see whether the result automatically changes the protocol or only signals intent. If a multisig or admin key can ignore the vote, it is not binding.
A timelock is a waiting period between a passed decision and its execution. It gives holders time to review the change before it takes effect.
