How a crypto or web3 company acquisition is settled
Acquiring a crypto-native company is not a standard M&A transaction with a skin of blockchain complexity over it. The assets are different, the consideration can be denominated in tokens, the balance sheet may hold more ETH than cash, and the governance of the target might be distributed across a DAO rather than concentrated in a cap table. For the brokers, advisors, and dealmakers orchestrating these transactions, each one of those differences changes how the deal structures, how it closes, and how everyone in the transaction actually gets paid. This article is a field guide to all of it — the mechanics, the friction points, the deal structures in current use, and the settlement layer that actually moves money at close.
Why a crypto acquisition is categorically different from a tech acquisition
The conventional M&A checklist — equity purchase agreement, wire instructions, attorney disbursements, title transfer — still applies to a web3 company acquisition in broad strokes. But the underlying assets, the form of consideration, and the way value is held and controlled by the target introduce complications that a deal team accustomed to SaaS or traditional tech M&A will run into quickly.
What makes this deal cycle distinct is the nature of the transactions themselves. Web3 acquisitions are increasingly structured around token-based consideration, treasury-funded grants, DAO-to-DAO governance approvals, and validator buyouts. None of those instruments exist in a standard acquisition. An advisor who approaches a DeFi protocol acquisition the same way they would approach a software company acquisition is going to misread the deal structure, misvalue the target, and potentially mishandle the settlement.
The first distinction is the asset base. A Web3 company’s books look familiar at the top level: revenue, expenses, payroll, cash. The complexity starts where the cash ends. A treasury holding ETH instead of dollars, a payroll partially paid in tokens, an NFT minted as marketing collateral — all of it has to land in a chart of accounts that auditors and investors will accept. When you are valuing the target for the purchase price, those assets count. When the deal closes, those assets transfer. The settlement process has to account for all of them.
The second distinction is the form of consideration from the buyer. In traditional M&A, the buyer pays in cash, stock, or a combination. In web3 acquisitions, the buyer may pay in cash, in the acquirer’s native token, in the target’s token (as part of a treasury management arrangement), in stablecoins, or in some hybrid. If the company remains centralized and follows the traditional startup route, value will be in the stock of the company. However, if the company decides to decentralize and issue a token, value will be in the token itself. An advisor structuring the deal needs to know not just the headline number, but what form it takes, when it vests, and what the conversion mechanics are if part of the consideration is illiquid at close.
The third distinction is governance. Some web3 companies are organized through a DAO, where the community of token holders collectively governs major decisions including, in some cases, approving an acquisition itself. A sale requires passing a governance vote, not just getting founder and board sign-off. That introduces a timeline variable and a counterparty count that traditional deal timelines do not accommodate.
What the acquirer is actually buying
Understanding what transfers at close shapes every other element of the settlement. In a conventional acquisition, you are buying equity — ownership of a legal entity, with all assets and liabilities attached. In web3, the picture is more fragmented.
An asset purchase involves acquiring the assets of another company — which can include technology, intellectual property, and customer base — without taking on any of the liabilities of the acquired company. This is often used when the acquiring company wants to acquire specific assets but does not want to take on the risks associated with the acquired company’s liabilities. In web3, this is frequently the structure of choice, especially when the target has regulatory ambiguity attached to its token or to prior fundraising instruments.
A protocol acquisition typically involves the buyer taking control of:
- Smart contracts — the deployed code governing the protocol, including upgrade keys and admin roles
- Protocol treasury — the DAO or foundation wallet holding the project’s native tokens and stablecoins
- Intellectual property — underlying code, documentation, brand assets
- Team — often the primary motivation, commonly structured as an acqui-hire with token vesting
Most acquisitions center around acquiring capabilities or user bases rather than revenue. Protocols are still under-monetized, and usage remains fragmented. Acquirers are valuing time-to-market and ecosystem alignment above all else. What that means in practice is that the deal value is often justified by the cost of building the capability from scratch, not by a revenue multiple. That changes the valuation conversation, and it changes how the purchase price is allocated at close.
Smart contract control is the most critical asset transfer. A multi-sig pledge means any smart contract that is ownable, has administrative roles, or includes privileged functions should have those privileges controlled by a multi-sig wallet. This prevents a single developer’s compromised key from jeopardizing an entire protocol. In an acquisition, the administrative keys to the protocol — the addresses that can upgrade contracts, pause functions, or drain the treasury — must transfer cleanly to the acquirer at close. This is the equivalent of handing over the keys to the building, and it is an event that has to be coordinated and confirmed on-chain at the moment of settlement.
Projects with unaudited smart contracts represent a major discount or no deal. Security matters, and no audit equals a discount. Buyers also worry about projects with regulatory red flags — anything that looks like an unregistered security gets avoided. Due diligence in a web3 acquisition therefore includes a technical layer that has no equivalent in a SaaS deal: a full smart contract audit to confirm the codebase does what the sellers represent it does, and to surface any vulnerabilities that would constitute a material liability on acquisition.
The token consideration problem
Token-based consideration is where web3 deals diverge most sharply from traditional M&A, and where advisors earn their value structuring the deal correctly.
When the buyer is paying partly or entirely in its own native token, or when the deal involves any transfer of tokens as consideration, three questions define the economics: what is the token worth at close, when can it be sold, and what happens to the price between those two events.
Mechanically, token-based consideration follows similar ASC 718 stock-based compensation rules. The difference is valuation: stock options have established models like Black-Scholes. Tokens often lack public pricing or have restrictions, so valuation requires judgment and documentation that auditors will scrutinize. A token that is traded on a major exchange has a market price, but that price may be thin, meaning a large transfer would move the market materially. A token that is not yet publicly traded has no price discovery mechanism at all.
Lockups apply to both investors and core team members, and they are used to manage token supply and market dynamics. This aligns token holders to the same unlock dates, because you do not want any stakeholder to sell immediately upon launch or ahead of anyone else. To prevent massive selling pressure at the same time, you might strategically stagger lockup schedules for the team, pre-seed investors, seed investors, and advisors. In an acquisition, the sellers receiving token consideration as purchase price consideration are subject to the same logic. Vesting schedules attached to the buyer’s token grants to the sellers typically run one to four years, with a cliff of six to twelve months. The practical result is that the seller receives the nominal purchase price on paper at close, but the liquidity of that consideration is staged over time.
This creates an earnout-adjacent dynamic that has to be priced into the deal. If the buyer’s token drops forty percent between signing and the end of the vesting period, the sellers received materially less than the agreed purchase price. If it doubles, they received more. Negotiating floors, price protection mechanisms, or a stablecoin-denominated portion of the consideration is how experienced advisors protect their clients from that variance.
The scenario where the buyer’s token is illiquid — a layer-1 protocol, a DeFi governance token without significant exchange volume — is the hardest. Tokens often lack public pricing or have restrictions, so valuation requires judgment and documentation that auditors will scrutinize. In these deals, the advisors and closing attorneys need an agreed methodology for arriving at a fair value at close, and that methodology needs to be written into the purchase agreement. Disagreements over token valuation at close have unwound deals that were otherwise ready to sign.
Treasury: what transfers, what does not, and the accounting that follows
The target’s treasury is one of the most consequential and most mishandled elements of a web3 acquisition. A crypto-native company operating a protocol may be holding a mixed treasury of its own native tokens, blue-chip assets like ETH or BTC, stablecoins, and potentially positions in DeFi protocols.
Crypto treasury management involves overseeing the acquisition, storage, usage, and reporting of digital assets like cryptocurrencies, stablecoins, and tokens. The goal is to align treasury operations with an organization’s financial strategy. When the company is acquired, all of those positions need to be valued as of close, and then transferred. The mechanics of transferring a multisig treasury are technical: the signing keys held by the sellers must be replaced with keys held by the acquirer, or funds must be moved to a buyer-controlled wallet. Either path requires coordination between the legal team and the technical team, and the transfer itself is an on-chain event with a public transaction hash — meaning the timing and the amount are verifiable by anyone watching the blockchain.
FASB issued ASU 2023-08, which now requires crypto assets held for investment to be measured at fair value with changes flowing through net income. This was a major shift from the prior model that treated crypto as an indefinite-lived intangible subject to impairment only. Most Web3 startups now operate under fair value accounting for their crypto holdings. This matters for the buyer’s accounting team at close. The treasury assets being acquired have to be recorded at fair value on the acquisition date, and the day-one balance sheet will reflect any unrealized gains or losses embedded in those positions.
The volatility of the treasury assets is also a material deal risk. If the target holds a large position in its own native token, that position’s value is not independent of the deal — news of the acquisition can move the token price, changing the purchase price calculation simultaneously. Deals with this structure often include price protection clauses that set a fixed exchange rate for treasury assets as of a specific date before any announcement.
Crypto treasuries often face more liquidity challenges than traditional ones due to market volatility, asset fragmentation, and unpredictable inflows and outflows. When an acquirer receives a treasury holding illiquid governance tokens or DeFi positions with lockups, those positions are not immediately convertible to the deal currency without market impact. This affects the true net assets delivered at close and needs to be accounted for in the purchase price adjustments and reps-and-warranties framework.
Structural variations: asset purchase, acqui-hire, and DAO-to-DAO
Not every web3 acquisition follows the same path to settlement. The structure chosen shapes almost everything about how the money moves.
Asset purchase
The cleanest version. The buyer acquires specific assets — smart contracts, intellectual property, domain names, social accounts — from the target entity, without inheriting its liabilities or legal structure. An established company looking to acquire a startup may prefer an asset purchase as they are only interested in a specific technology or IP that the startup has developed. Settlement involves the buyer wiring fiat consideration to a designated account, or transferring token consideration to a designated wallet address, and the sellers simultaneously transferring admin keys, signing over IP assignments, and delivering wallet control. The closing is legal until both deliveries complete.
Acqui-hire
Most “acquisitions” are actually talent grabs. The deal is structured around team retention, not asset transfer. The buyer acquires the target company at a nominal price, the founders and team agree to employment or contractor agreements with the buyer, and the real economic value is delivered through signing bonuses and token grants. Settlement at close involves minimal asset transfer — often just the IP and the brand — and the bulk of the consideration flows over the vesting period of the employment grants. For brokers and advisors working these deals, the headline deal value and the net present value of the actual consideration can be very different numbers.
DAO-to-DAO acquisition
Several recent transactions have demonstrated that complex deals can be executed entirely on-chain. From DAO-governed treasury allocations to smart contracts controlling vesting schedules, the infrastructure to support non-custodial M&A execution is no longer theoretical. In a DAO-to-DAO structure, one DAO’s governance passes a proposal to acquire another protocol and allocate treasury funds to that acquisition. Both communities vote. The settlement happens on-chain: the acquiring DAO’s treasury wallet sends consideration tokens to the target DAO’s treasury, and admin keys are transferred via governance mechanics.
While DAOs now control billions in capital, very few have reliable mechanisms for due diligence, counterparty risk analysis, or post-merger integration. That creates the role for a professional advisor who can operate across the technical, legal, and financial dimensions of the deal. The governance vote provides legitimacy, but it does not replace legal documentation, tax analysis, or proper settlement mechanics.
The due diligence layer specific to web3
Before anything settles, the due diligence has to clear a set of items that have no equivalent in a conventional deal.
Smart contract security. $3.35 billion was stolen from Web3 protocols in a single year, a 37% increase over the prior year, across 630+ incidents, with the average hack yielding $5.3 million. A buyer acquiring a live protocol is acquiring the risk of those vulnerabilities if they exist. The technical due diligence includes a full smart contract audit by a qualified firm, a review of the audit history, and an assessment of whether any identified vulnerabilities were properly remediated. An unaudited protocol is a liability, not an asset.
Token regulatory status. Whether the target’s token was sold in a manner that could expose the acquirer to securities law liability is among the most consequential representations in a web3 purchase agreement. Projects with regulatory red flags — anything that looks like an unregistered security — get avoided. The buyer’s legal team needs to conduct a full analysis of the token’s issuance history, the representations made to initial token purchasers, and the current regulatory posture before the deal proceeds to close.
Wallet address and key verification. In a traditional acquisition, the seller’s bank account details are verified through normal wire confirmation channels. In a web3 deal, the seller may be receiving consideration at one or more on-chain wallet addresses. Confirming that those addresses are actually controlled by the parties receiving consideration — and not a compromised address or social engineering substitution — requires a verification step that should be conducted independently by the closing attorney and confirmed with the recipients out-of-band before any tokens or stablecoins are sent.
On-chain revenue recognition. On-chain revenue must be translated to fiat at the transaction date. Web3 accounting is the application of standard accounting principles to companies that hold crypto assets, pay or receive in tokens, or operate on-chain. It is not a separate framework — it is GAAP applied to a new asset class with rules that are still being written by FASB and the SEC. Confirming the target’s actual revenue history requires pulling on-chain transaction data and reconciling it against the financial statements. This is a different process from reviewing bank statements, and it requires an accounting team that is fluent in reading block explorers and working with crypto-native financial data.
How the money moves at close
Settlement in a web3 acquisition combines the traditional closing mechanics — legal documents executed, title transferred — with on-chain transactions that are final, public, and irreversible. That combination is both a feature and a risk surface.
For the fiat components of the purchase price, the mechanics are conventional: wire instructions in the purchase agreement, confirmed delivery by the closing attorney, disbursement to the designated recipients. For deals where part of the consideration is a stablecoin — USDC, USDT, or an equivalent — these tokens are typically backed 1:1 by cash and cash equivalents and enable near-instant settlement, programmable compliance, and global operability. Compared to ACH or credit card networks, which can take days to clear, stablecoin transactions settle in seconds at materially lower cost. That means the seller can confirm receipt of stablecoin consideration in the same closing window as the rest of the deal, without waiting for banking clearance.
For token consideration, settlement involves transferring the specified token amount from a buyer-controlled wallet to a seller-designated wallet address. Vesting is typically enforced through a smart contract — stablecoins and tokens interact with smart contracts, which are self-executing code that automates complex financial workflows, reducing manual intervention and operational error. A vesting contract programmatically releases tokens to the seller’s address on a schedule, removing the need for the buyer to manually administer distributions and eliminating the risk of non-payment.
The transfer of admin keys — the wallet addresses that control the target’s smart contracts and treasury — is the most consequential on-chain event at close. Multi-signature wallets are smart contracts that require the agreement of multiple people to perform an action. They can be useful for protecting assets or to ensure that certain actions are only taken in accordance with the wishes of the multisig’s owner or a majority of owners. Standard practice is for the seller to add the buyer’s designated addresses to the multisig with the required signing authority, and then remove the seller’s addresses only after the buyer has confirmed control. The sequence matters: adding first, removing second. Removing the seller’s keys before confirming the buyer’s control creates a window where the contract is owned by nobody, which is effectively a protocol-ending event.
For deals where the consideration is partly fiat or stablecoins and partly tokens — the most common structure in arm’s-length web3 acquisitions — the closing involves multiple simultaneous deliveries that need to be coordinated across a legal team and a technical team. The fiat wire, the stablecoin transfer, the token consideration, the smart contract key transfer, and the IP assignments all need to complete in the correct sequence. When there are multiple recipients — brokers, advisors, selling founders, investor distributions from the proceeds — each of those flows needs to be separately addressed and tracked.
That is precisely the kind of multi-party, multi-wallet disbursement that benefits from a payment router built to handle it. When a broker or closing attorney is coordinating the distribution of deal proceeds across several wallets simultaneously — seller proceeds, advisor fees, investor returns, co-broker splits — Shaka lets them configure those splits in advance and execute them in a single transaction. Every recipient gets paid directly and instantly, with no routing through a holding account and no manual disbursements to chase down after close.
What the settlement record looks like
One characteristic of an on-chain settlement that experienced practitioners treat as an asset rather than a curiosity: every token and stablecoin transfer is permanently recorded on a public blockchain. The transaction hash, the amount, the sending address, the receiving address, and the block timestamp are immutable. Blockchain transactions are irreversible once confirmed. While this shifts responsibility toward upfront transaction screening, it removes post-settlement dispute cycles that affect revenue predictability.
In practice this means the deal record has two layers: the legal layer — executed purchase agreement, IP assignments, closing certificates — and the on-chain layer, where the actual movement of digital assets is recorded permanently. The closing attorney should capture the transaction hashes for all on-chain deliveries at close as part of the closing set, the same way they would retain wire confirmations for fiat transfers. Those hashes are the proof of payment, and they are available to any party, at any time, without requesting confirmation from a bank.
It also means that errors in wallet addresses at close are final. There is no reversal, no chargeback, no bank to call. Smart contract vulnerabilities, node failures, or chain congestion can disrupt processing. Key management failures can result in total loss of wallet access. Unlike traditional rails, there is no established dispute resolution pathway. This is why address verification before the transaction — not during — is a non-negotiable step in the closing protocol. Confirm the addresses with each recipient through a voice or video call where the address is read out digit by digit, or by requesting a small test transaction be returned before sending the full amount.
The regulatory dimension that every party at the table carries
As digital asset capabilities become table stakes for financial services, companies will focus on acquisition strategies instead of building from scratch. To meet market demands ranging from stablecoin capabilities to full-stack crypto banks, exchanges, custodians, infrastructure providers, and brokerages will consolidate into multiproduct companies. That consolidation wave is running through a still-evolving regulatory environment, and every professional advising on these deals carries a share of the regulatory exposure.
The transfer of token consideration has tax implications for both sides. Paying a vendor in crypto is a taxable disposition for the payer. You recognize gain or loss equal to the difference between the fair value of the crypto on the payment date and your cost basis. The vendor recognizes income equal to the fair value received. Both sides have a tax event. In an acquisition, the same logic applies: delivering token consideration is a disposition event for the buyer if those tokens were held on the buyer’s balance sheet, and receiving token consideration is income or gain recognition for the sellers. Structuring the deal to address this — including representations about each party’s cost basis, their holding period, and the agreed fair value at close — is part of the closing documentation.
You need an accountant who understands fair value accounting, lot-level cost basis tracking, on-chain reconciliation, and the FASB and IRS guidance specific to crypto. Some traditional accountants have built this capability; many have not. The cleanest approach is to work with a finance partner who handles Web3 books routinely. For a dealmaker advising on these transactions, knowing which accounting and legal resources are fluent in web3 mechanics is as important as knowing the deal structure. A closing attorney who does not understand how multisig key transfers work, or a tax advisor who does not know how to handle the disposition of governance tokens, will slow the deal and potentially mishandle the mechanics.
A deal and its settlement, assembled
Consider a concrete example: a Layer-2 protocol acquires a smaller DeFi infrastructure company for $12 million. The deal structure is 50% in the acquirer’s token, vested over two years with a six-month cliff, and 50% in USDC, paid at close. The target has a treasury holding $3 million in ETH and $1 million in its own native token, which transfers as part of the deal.
At close, the settlement involves: a $6 million USDC transfer from the buyer’s treasury wallet to a designated seller wallet; a two-year vesting contract deployed on-chain with $6 million in the acquirer’s token allocated at the current price, releasing to the sellers according to the schedule; the target’s treasury multisig updated to replace the sellers’ signing keys with the buyer’s keys; and the IP assignments executed alongside.
The deal advisor is receiving a fee from the proceeds. The sellers have three individual founder wallets to receive their respective shares. There are two co-advisors with agreed splits. All of those distribution decisions need to be pre-configured before the USDC transfer is executed, so that each recipient receives their allocation directly without manual routing. That is the closing discipline that makes settlement clean — and it is where a purpose-built payment routing tool turns a complex multi-party disbursement into a single, verifiable, final transaction.
The web3 acquisition market is maturing fast, with the deal structures and the settlement mechanics evolving alongside it. The professionals who understand the full stack — legal, financial, technical, and on-chain — are the ones who actually get these deals closed. Everything else is noise.
