How does an OTC desk actually settle a trade with a DAO that has no single signer?

Settling an OTC trade with a decentralized autonomous organization, or DAO, means working with a treasury typically controlled by a multisig wallet requiring multiple independent signers to approve any transaction, rather than a single authorized individual who can simply confirm and execute a trade — this changes several practical aspects of how an OTC desk needs to structure the deal, from how it verifies who's actually authorized to negotiate on the DAO's behalf, to how long settlement actually takes once terms are agreed, to how liability and recourse work if something about the arrangement is later disputed by the DAO's broader membership.

This is a genuinely different counterparty structure than dealing with a traditional company or individual, where a single authorized signatory can bind the organization to a trade — a DAO's governance structure means no single person typically has that unilateral authority, and an OTC desk needs to understand and work within that structure rather than assuming it functions like any other institutional counterparty.

What does it actually mean that a DAO has "no single signer," and why does this matter for settlement?

Most DAOs hold their treasury funds in a multisignature (multisig) wallet, which requires a specified minimum number of designated signers — often a subset of the DAO's broader governance structure, such as elected council members or a designated multisig committee — to each independently approve and sign off on a transaction before it executes, rather than any single person having the unilateral ability to move the treasury's funds. This structure exists specifically to prevent any single individual, even one with significant authority within the DAO, from being able to unilaterally move or misappropriate treasury funds, distributing that control across multiple independent parties instead.

For an OTC desk settling a trade with a DAO, this means the desk isn't simply negotiating with and receiving confirmation from one authorized counterparty representative — the actual execution of the trade depends on multiple independent signers each separately reviewing and approving the transaction, which introduces both additional verification considerations and a potentially longer and less predictable settlement timeline than working with a traditional, single-signatory counterparty.

How should an OTC desk actually verify it's negotiating with someone genuinely authorized to represent the DAO?

Does a DAO typically need a formal governance vote before a large OTC trade can actually proceed?

This depends entirely on the specific DAO's own governance rules, but many DAOs with meaningful treasuries do require some form of formal community or token-holder vote before a significant treasury transaction — such as a large OTC trade — can proceed, separate from and prior to the actual multisig signers executing the transaction itself. This means the negotiation and agreement of terms between the OTC desk and the DAO's representatives is sometimes only the first step, with a subsequent governance process needing to run its course (which can itself take days or weeks, depending on the DAO's specific voting period and quorum requirements) before the trade can actually be authorized for execution.

An OTC desk unfamiliar with this structure might reasonably assume that reaching an agreement with the DAO's negotiating representatives means the deal is essentially done, only to discover that a governance vote is still required and hasn't yet occurred — this is worth clarifying explicitly and early in any discussion with a DAO counterparty, since it meaningfully affects the realistic timeline for actually closing the trade.

How does the actual multisig signing process work once a trade is authorized to proceed?

Once authorized — whether through a completed governance vote or through whatever process the specific DAO's rules establish — the designated multisig signers each need to independently review and sign the transaction using their own individual keys, with the transaction only executing once the required minimum number of signatures (a common structure is requiring, for instance, five out of nine designated signers, though the specific threshold varies by DAO) has been collected. This process happens on-chain and is often visible and verifiable in real time, which is actually a meaningful transparency advantage compared to a traditional institutional counterparty's internal approval process, which typically happens entirely behind closed doors with no external visibility into its progress.

An OTC desk can often track the signing progress directly by monitoring the multisig wallet's pending transaction status, which provides real, verifiable insight into exactly how many signatures have been collected and how many are still needed, rather than simply waiting on a traditional counterparty's internal assurance that "the paperwork is being processed" with no independent way to verify that claim.

What happens to the deal if the required number of signers isn't actually reached?

If a DAO's multisig transaction doesn't collect the required minimum number of signatures within whatever timeframe applies — whether because a signer is unresponsive, a disagreement emerges among the signers about whether to actually proceed, or some other complication arises — the transaction simply doesn't execute, and the trade effectively stalls or falls through entirely, since there's no equivalent to a single authorized signatory who could simply decide to proceed unilaterally despite other parties' hesitation. This is a genuine practical risk worth planning for: an OTC desk should have a clear understanding, agreed upfront, of what happens to any interim arrangements (a price lock, a reserved allocation) if the DAO side's internal signing process ultimately fails to produce the required authorization within a reasonable timeframe.

This risk is somewhat analogous to a traditional deal falling through due to an internal corporate approval process failing, but it's worth being explicit about with a DAO counterparty specifically, since the decentralized, multi-party nature of the authorization process can make it genuinely harder to predict or control compared to a more centralized traditional counterparty's internal approval chain.

How does liability and recourse actually work if a DAO-side dispute arises after a trade settles?

This is one of the more legally novel and sometimes genuinely unresolved aspects of dealing with DAOs, since many DAOs don't have the same clear legal entity status and liability structure that a traditional corporation does, which can create real ambiguity about who, exactly, bears responsibility or can be held accountable if a dispute arises after a trade has settled — for instance, if some DAO members later object to a trade that the designated signers executed, claiming it wasn't properly authorized under the DAO's own governance rules. Some DAOs have structured themselves with a formal legal wrapper (a foundation, an LLC, or another legal entity specifically created to give the DAO clearer legal standing and accountability), which provides a more traditional and predictable basis for recourse than an entirely unincorporated, purely on-chain governance structure.

An OTC desk engaging with a DAO counterparty, particularly for a significant transaction, should understand clearly whether the specific DAO has this kind of legal wrapper in place, and should factor the relative legal and governance clarity (or lack of it) into its overall risk assessment of the counterparty, the same way it would assess any other counterparty's legal standing and accountability before committing to a significant trade.

How does this play out for an OTC desk actually executing a trade with a DAO counterparty?

Call it a mid-sized OTC desk approached by a well-established DAO wanting to diversify a significant portion of its treasury holdings through a large stablecoin-for-token swap. The desk's initial negotiating contact was a member of the DAO's elected treasury council, who confirmed the proposed terms but explained clearly, when asked directly, that the transaction exceeded the council's own authorized spending threshold and would require a formal token-holder governance vote before the designated multisig signers could execute it.

The desk, having built flexibility into its own timeline expectations based on this upfront disclosure, agreed to a price structure that remained valid for a defined window accommodating the DAO's stated voting period, rather than assuming the deal would close immediately. The governance vote passed within the expected timeframe, and the desk was able to monitor the subsequent multisig signing process directly on-chain, watching the required signatures accumulate in real time until the transaction executed successfully, settling through an atomic payment router that eliminated any sequencing risk once the DAO's own internal authorization process had actually concluded. The entire process took meaningfully longer than a comparable trade with a traditional institutional counterparty might have, but proceeded smoothly precisely because the desk had understood and planned around the DAO's actual governance and signing structure from the outset, rather than assuming it would function like any other counterparty it had previously worked with.

What's the practical takeaway for an OTC desk considering a trade with a DAO counterparty?

Understand the specific DAO's governance and treasury signing structure clearly before finalizing any terms, including whether a formal governance vote is required and how many signers must approve the actual transaction. Build realistic timeline expectations around this process rather than assuming it mirrors a traditional single-signatory counterparty's speed, and use the genuine transparency advantage of being able to monitor an on-chain multisig signing process directly as a meaningful tool for tracking real progress rather than relying solely on a counterparty's own assurances. Assess the DAO's broader legal standing and accountability structure as part of your overall counterparty risk evaluation, and settle the actual trade through a mechanism — such as an atomic payment router — that eliminates sequencing risk once the DAO's own internal authorization process has genuinely concluded, rather than assuming the complexity of the DAO's governance structure also means the final settlement step itself needs to carry additional risk beyond what any OTC trade already involves.

Should price terms be locked for the full duration of a DAO's governance and signing process, or adjusted over time?

This is worth negotiating explicitly rather than assuming either approach by default, since a DAO's governance and multisig process can genuinely take days or weeks, during which market prices for the underlying assets may move meaningfully. A fixed price locked for the entire process protects the DAO side from an adverse price move during what can be a lengthy internal approval process, but exposes the OTC desk to the same risk in reverse — an agreed price that becomes unfavorable to the desk if the market moves considerably before the DAO's internal process concludes and the trade can actually execute.

Common approaches to manage this include a price band rather than a fixed figure (allowing some movement within an agreed range before requiring renegotiation), a price that floats until the actual point of execution based on a formula agreed upfront, or a defined expiration after which the terms need to be reconfirmed or renegotiated if the DAO's process hasn't concluded by then. Whichever approach is chosen, it's worth agreeing to it explicitly and in detail before the DAO's governance process even begins, since renegotiating pricing terms partway through an already-initiated governance vote is a considerably more awkward conversation than settling this upfront.

Does working with a DAO counterparty change anything about how an OTC desk handles its own compliance obligations?

Yes, in ways worth considering carefully — standard counterparty due diligence and compliance processes, including understanding who's ultimately behind a transaction for anti-money-laundering and know-your-customer purposes, can be genuinely more complex when the counterparty is a decentralized organization with many token holders and a distributed governance structure, rather than a traditional entity with clearly identified owners and officers. An OTC desk should think through how it applies its own compliance framework to this kind of counterparty — whether its obligations focus on the specific individuals it's actually negotiating and transacting with (the treasury council members and designated signers), the DAO's legal wrapper entity if one exists, or some combination of both, depending on the desk's own regulatory obligations and risk tolerance.

This is worth resolving as a matter of internal policy before engaging in a DAO transaction of any real size, ideally with input from compliance or legal counsel familiar with how existing regulatory frameworks are currently being applied to this still-evolving organizational structure, rather than improvising a compliance approach for the first time in the middle of an active negotiation with real money and a specific deal timeline already in motion.

This is an area where regulatory guidance continues to develop, and an OTC desk that establishes a thoughtful, documented internal approach now is in a considerably stronger position than one that waits until a regulator or auditor asks how DAO counterparties have been handled, only to discover there was never a clear, consistent policy applied across the desk's prior DAO transactions in the first place.