JobProtocol All articles
Hiring Protocols

The Treasury Moved. Did Your Job Move With It?

JobProtocol
The Treasury Moved. Did Your Job Move With It?

Photo: Colin Smith, CC BY-SA 2.0, via Wikimedia Commons

A fourteen-person contributor team found out on a Tuesday. The lending protocol they'd worked on for two years had been absorbed by a larger one — treasury, codebase, and, nominally, them. The announcement post used the word "seamless" three times. In the contributors' private channel, the first question was simpler: do we still get paid on Friday, and in what?

This is the new shape of the acqui-hire. In traditional tech, the acquiring company buys the entity, assumes the employment contracts, and inherits a workforce with W-2s, severance policies, and — in larger deals — WARN Act obligations. In decentralized-land, there's often no entity to buy, no employees to inherit, and no HR department to explain what just happened to your four-year vest.

The asset was the treasury. You were a line item.

When a DAO winds down or merges, what actually gets acquired is usually a multisig balance, a token supply, a repo, and a brand. Contributors attach to the deal through a patchwork of arrangements: grant agreements issued by a Cayman foundation, 1099 contracts with a Delaware LLC, informal retainer payments approved by a monthly governance vote, or nothing at all beyond a recurring stream and a handshake in a Discord thread.

That patchwork is the problem. If your compensation was approved by token vote rather than written into an enforceable contract, the acquisition doesn't necessarily transfer anything. The new protocol may generously re-hire you. It is not obligated to.

What happens to the unvested tokens

This is where most contributors lose the most money, and where the least documentation exists.

When a token migrates, the old grant usually dies with it. The questions you want answered in writing, before a deal closes if you have any warning at all:

Ask for a copy of any agreement governing your grant and read the assignment clause. If the answer is "it's on the governance forum," that's an answer about enforceability, and you should hear it clearly.

Your contractor agreement says "at-will" and nothing else

Most DAO contributor agreements are short. They specify a monthly rate, a token allocation, and a termination clause written to protect the protocol. They rarely include severance, notice periods, or change-of-control protections, because whoever drafted them was optimizing for flexibility and not for you.

In the US, that means a few practical things. As a 1099 contractor you generally aren't covered by unemployment insurance, and you're outside the WARN Act's mass-layoff notice requirements. If your deal runs through a staffing intermediary or a grants program, the party technically terminating you may not be the party you've been talking to every day.

Ask directly: who is my counterparty, in what jurisdiction, and what does the contract say about a change of control? If nobody can answer, you've learned something important about how the acquisition will treat you.

The pseudonymous contributors get hit hardest

The people hit hardest tend to be the ones who've been most loyal to the ethos. A pseudonymous contributor can't be added to a corporate payroll, can't sign a standard employment agreement under a legal name they haven't disclosed, and often can't pass the KYC the acquiring company suddenly requires. Some have been paid in stablecoins for years with no invoice trail the acquiring entity's finance team recognizes.

If you work under a handle, decide early how you'd handle an acquisition, an audit, or a request for identity verification. And if you're leading a team, don't leave your anonymous contributors to negotiate the transition alone — they have the least leverage and the most to lose.

Culture doesn't survive the transfer, and that's not a scandal

The part people mourn isn't the token. It's the weekly call where decisions got made in forty minutes, the governance process where a good argument actually won, the absence of a middle manager. Post-acquisition, those become someone else's roadmap review, someone else's sprint cadence, someone else's performance rubric.

Some of that is fine. A protocol with real revenue needs real operations. But if what you loved was the flatness, understand that the acquiring organization is buying your output, not your governance philosophy. Budget for the change.

Nine questions to ask before joining a project that might get bought

  1. Which legal entity pays me, and what happens to that entity in a merger?
  2. Is my grant documented in a signed agreement, or only in a forum post?
  3. Does my agreement include change-of-control acceleration?
  4. What's the remaining runway, and does the treasury hold stablecoins or mostly its own token?
  5. Has the team had acquisition or wind-down conversations before? What happened to contributors then?
  6. Who controls the multisig, and how many signers would need to agree to change my grant?
  7. If the token migrates, is there a written conversion policy for unvested allocations?
  8. Can I get a name and a legal jurisdiction for the counterparty to my contract?
  9. What's the notice period if this ends?

None of these are hostile questions. They're the questions an adult asks before moving their livelihood into a structure with no HR department. The best DAO operators will have answers ready — and the ones who get defensive are telling you something worth knowing.

All Articles

Related Articles

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

Your Next Boss Might Score You Like a Credit Bureau: Inside Web3's Reputation Algorithms

Your Next Boss Might Score You Like a Credit Bureau: Inside Web3's Reputation Algorithms

The Vouching Problem: When Your Old DAO Has Dissolved and Nobody's Left to Call

The Vouching Problem: When Your Old DAO Has Dissolved and Nobody's Left to Call