>>
Industry>>
Cryptocurrency>>
How Web3 Companies Approach Cr...For most Web3 companies, the treasury isn't a side account. It's payroll, vendor payments, and the next product milestone's budget, sitting in a wallet instead of a bank account. Crypto treasury management is the set of decisions that keeps that money usable and accounted for, rather than a pile of keys nobody can trace back to a decision-maker.
Those decisions tend to fall into four areas: who can move the funds, what the funds are held in, who legally owns them, and how they show up on the books at year end. Each one has gone wrong publicly enough, at real companies, that the answers are no longer optional.
A single private key controlling a company treasury is a single point of failure, whether that's a lost laptop, a phishing email, or one employee who leaves on bad terms. The standard fix is a multisignature wallet, usually written as M-of-N: N total signers, M of whom must approve before a transaction executes.
Picking the threshold means weighing two opposite risks at once. Too low, and a handful of compromised keys can move the treasury. Too high, and one traveling signer or one lost device can freeze it. Security frameworks used across the industry generally call for a minimum of three signers, roughly a 50% approval threshold, and seven or more signers once a wallet holds the equivalent of $1 million or more. The Ethereum Foundation, for reference, runs its own multisig at 4-of-7.
The threshold only works if the signers are genuinely independent. Five keys split across two people who sit in the same office, or backed up to the same hardware wallet, function as one or two real signers, no matter what the smart contract says. Most companies also split custody by purpose: a smaller, lower-threshold wallet funded periodically for day-to-day operating expenses, and a separate, higher-threshold cold wallet for the bulk of the treasury that moves rarely and only with more signers involved.
A lot of Web3 treasuries default to holding most of their value in the company's own native token, simply because that's what came in from the raise or from protocol emissions.
A widely cited 2023 academic study from the Blockchain Research Lab found that native tokens made up roughly 81% of the average treasury studied, with stablecoins accounting for only around 5%. That concentration creates a specific problem: if the token's price falls, the treasury's ability to fund payroll and operations falls with it, at exactly the moment the business can least afford it.
The more common fix now is to carve out a stablecoin allocation sized to cover a defined runway, often somewhere in the 12 to 18 month range, so operating expenses aren't hostage to the token's price chart. The native token allocation that remains usually survives for a specific reason, governance weight or an actual product use case, sized on purpose instead of left over from the raise.
For a lot of early Web3 projects, the honest legal answer to who owns the treasury is nobody, which turns out to be a serious problem. No entity stands between the protocol and the people who control its funds.
The clearest example is the CFTC's case against the Ooki DAO. A US court found that an unincorporated DAO can be treated as an "unincorporated association" under US commodities law, and that its members, in that case, token holders who voted to govern the protocol, can be personally liable for the DAO's violations under ordinary partnership-law principles. The case ended with a default judgment and a civil penalty of $643,542 against the DAO, with its founders held personally liable as members. The underlying point generalizes well past that one case: without a legal entity standing between the protocol and the people controlling its funds, the multisig signers and the token holders directing them can end up personally on the hook for whatever that treasury is used for.
The standard structure now is to put a company or foundation, incorporated somewhere with clear rules for digital asset holdings such as the BVI, the Cayman Islands, Switzerland, or Singapore, between the protocol and the individuals. That entity legally owns the treasury, with the multisig signers acting as its authorized agents or directors. That jurisdiction choice, and how the entity's board authority lines up with who actually holds the signing keys, is usually worked out with a web3 legal consultancy like GVRN, well before the first transaction moves.
Where the entity sits also determines how the treasury gets reported, and under US GAAP, the rules changed substantially in 2024. The Financial Accounting Standards Board's ASU 2023-08, effective for fiscal years beginning after December 15, 2024, requires in-scope crypto assets to be measured at fair value every reporting period, with gains and losses flowing straight into net income. That's a real shift from the older cost-less-impairment model, where a token's book value could fall but never recover, even if its price bounced back the same quarter.
Entities reporting under IFRS generally don't have that option. Most crypto holdings fall under IAS 38 as intangible assets, carried at cost less impairment unless there's an active market and the company elects a revaluation model, in which case gains bypass net income and land in other comprehensive income instead. A company holding tokens for resale in the ordinary course of business may instead apply IAS 2's inventory rules. The upshot is that identical treasury holdings can look meaningfully different on two companies' books depending on which standard applies, which matters a great deal for a Web3 company whose operating entity, foundation, and development team might sit in three different jurisdictions.
None of this is static. Standards, thresholds, and case outcomes in this area have moved fast over the past two years, and a company's auditor or counsel is the right source for how a specific treasury should be structured or reported today. What's consistent is the shape of the problem. A Web3 company's treasury needs a custody model, an asset mix, a legal owner and an accounting treatment, settled in that order, before a wallet full of keys becomes an actual treasury.
Comments