JobProtocol All articles
Treasury

Read the Multisig, Not the Manifesto: A Treasury Due Diligence Checklist

JobProtocol
Read the Multisig, Not the Manifesto: A Treasury Due Diligence Checklist

Photo: blockchain explorer dashboard on laptop screen with financial charts, desk overhead view, via www.keengamer.com

A DAO's hiring page is marketing. Its treasury is a financial statement, published in real time, free to read, and almost nobody applying for the job bothers to open it.

That's an odd gap. You would not take a startup offer without asking about runway. Yet people sign contributor agreements with protocols whose entire war chest is denominated in a token that's down 70% from its all-time high, sitting behind a three-of-five multisig controlled by the two co-founders and their group chat.

Here's the checklist. It takes about an hour, most of it on Etherscan and a treasury dashboard, and it will occasionally save you a year of your life.

1. Runway, in dollars, not in tokens

The headline number on a treasury dashboard is usually total value. That number is a fiction if most of it is the protocol's own token. Look for the stablecoin line specifically — USDC, USDT, DAI, whatever they hold — and divide it by monthly burn. What you want is the number of months the team can pay salaries if the token goes to zero tomorrow and never recovers.

Under six months of stablecoin runway with no announced raise is a red flag worth raising in the interview. Under three is a countdown clock.

2. Native token concentration

What percentage of the treasury is the project's own token? Above 70% means the protocol's payroll is effectively a bet on itself, and a drawdown becomes a layoff. It also tells you what happens to your token grant: if the treasury is illiquid, so is everyone's compensation, including yours.

3. Burn rate trend, not just burn rate

One month of data means nothing. Pull three to six months of outflows from the treasury address. Is spend flat, climbing with headcount, or spiking? A team that hired eleven people last quarter and doubled grants outstanding is a team that needs either revenue or a raise — and you should know which before you become a line item.

4. Revenue that arrives in something other than the token

A surprising number of DAOs have real revenue: protocol fees, sequencer income, licensing, MEV share. The question is denomination. Fees collected in ETH or USDC are durable. "Revenue" that is mostly the protocol's own emissions recycled into its own treasury is accounting, not business.

5. Who's on the multisig, and how many keys

This one is underrated. Look up the treasury address and check the signer set. A three-of-five where all five signers work at the same protocol is centralization with extra steps — acceptable for a young team, risky for a mature one. Look for independent signers, a documented key ceremony, hardware wallets, and any public policy on transaction limits. If the multisig controller list isn't public, note that too.

6. Pending liabilities nobody tweets about

Treasuries carry debts that don't appear in a dashboard total. Look for:

7. The token's own unlock calendar

Pull the vesting schedule for the token itself, not just your grant. If investor and team allocations unlock during your first year, the price pressure is not hypothetical and neither is the recruiting pressure — teams often hire aggressively right before unlocks, then tighten after.

8. Who actually signs your payment

Find the address that pays contributors. Is it a foundation wallet, an operations multisig, or a grants program with its own committee? How many signatures does a monthly payroll run need, and how often does it fail to clear on time? Public payment history will show you whether paydays are reliable or improvisational. Contributors talk; the chain talks louder.

9. Governance risk to your own comp

Read the governance docs for one specific thing: can token holders vote to modify, cancel, or claw back grants? Can they change the treasury's spending policy mid-year? The answer is often technically yes. That doesn't make the DAO lawless, but it does mean your compensation is a political object, and you should know who holds the votes.

The five questions to ask in the interview

On-chain data gets you 80% of the way. These close the rest:

  1. "What's our stablecoin runway at current burn, and what's the plan if the token halves?"
  2. "How much of the treasury is the native token, and is there a diversification policy?"
  3. "Who are the multisig signers, and are any of them independent of the core team?"
  4. "What grants and liabilities are already committed but unvested?"
  5. "If revenue doubled or halved next quarter, what changes about hiring?"

Ask these calmly and with curiosity, not suspicion. A good operator will enjoy the conversation — it's rare that a candidate has read the treasury, and it signals you'll be useful on the ops side too. A defensive, hand-wavy answer to question one is itself an answer.

The one-hour version

If you only do three things: find the stablecoin balance, divide by monthly burn, and check who's on the multisig. That's the difference between joining a funded team and joining a hope. The manifesto is optional reading. The multisig isn't.

All Articles

Related Articles

Cliff Notes: What a Four-Year Token Vest Actually Costs You

Cliff Notes: What a Four-Year Token Vest Actually Costs You

The Treasury Moved. Did Your Job Move With It?

The Treasury Moved. Did Your Job Move With It?

Fired by Committee: Inside the DAO Layoffs Where Token Holders Decide Who Goes

Fired by Committee: Inside the DAO Layoffs Where Token Holders Decide Who Goes