EST · MMXXVI
Home/Insights/Regulatory/Crypto Treasury Companies: Legal and Disclosure Framework
Funds & Investment Vehicles

Crypto Treasury Companies: Legal and Disclosure Framework

Crypto Treasury Companies: Legal and Disclosure Framework. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee engagem

A public software company announces a $500 million Bitcoin purchase. Thirty days later, an activist investor files a proxy demand seeking board-level disclosure of custody arrangements, impairment policy and hedging authority. The general counsel discovers that the treasury resolution authorising the purchase said nothing about valuation methodology, that the custody agreement sits with an unregulated third party, and that the CFO applied a cost-basis accounting treatment the auditor now questions. The legal question is not whether holding digital assets on balance sheet is permissible – it plainly is – but what governance, disclosure and structural obligations apply when a listed or private company converts treasury reserves into crypto assets, and how those obligations change when the holder is domiciled in one jurisdiction, banked in another, and serving investors or stakeholders across a third set of borders.

Operating a digital-asset treasury within a conventional corporate structure creates a three-layer compliance problem: the custody layer (how the assets are held and who controls the private keys), the disclosure layer (what shareholders, creditors and regulators are told about exposure, valuation and risk), and the governance layer (which corporate organs approve the initial allocation, set hedging limits and authorize disposals). Companies entering this space often treat the decision as a treasury diversification exercise – analytically similar to buying foreign-exchange reserves or commodities – and discover only after the first reporting cycle that digital assets on balance sheet trigger a distinct set of legal, accounting and disclosure expectations. This analysis maps the legal perimeter for corporate treasury holders, the common structural mistakes, and the decision points that determine whether a given allocation model withstands shareholder scrutiny and regulatory review.

Why companies hold crypto on balance sheet

The motivations fall into three categories. First, inflation hedging and reserve diversification: management views Bitcoin or other large-cap digital assets as a store of value separate from fiat currency exposure, analogous to gold but with lower storage and transfer costs. This approach is common among technology companies with significant cash reserves and a board willing to accept price volatility in exchange for asymmetric upside. Second, strategic alignment: companies whose business model touches digital assets – payments processors, mining operations, blockchain-infrastructure providers – hold crypto to demonstrate commitment to the ecosystem and to facilitate operational flows (paying vendors in crypto, accepting customer deposits in stablecoins). Third, yield generation: firms deposit stablecoins or blue-chip tokens into DeFi protocols or centralized lending platforms to earn a return on idle treasury balances, treating the allocation as a short-term investment rather than a strategic reserve.

Each use case carries a different legal profile. A listed company holding Bitcoin as a reserve asset faces disclosure obligations under securities law, must adopt a clear impairment and revaluation policy under accounting standards, and will be questioned by auditors and investors on custody safeguards and liquidity risk. A private company staking Ether through a validator it controls faces operational and tax questions – the income character of staking rewards, the appropriate consolidation treatment if the validator is a separate entity, and the employment or contractor status of the individuals managing the validator node. A software firm accepting USDC from enterprise clients and holding it on balance sheet for 30–90 days before converting to fiat faces AML expectations (if the volume is material) and must address whether it is inadvertently conducting a payment service requiring licensing. In our cross-border practice, the single most common error is treating all three scenarios as fungible and applying a one-size-fits-all custody and reporting approach, when the legal perimeter varies by asset type, holding period and the regulatory classification of the activity.

Custody structures and control risk

Custody is the threshold issue. Unlike fiat cash, where the bank is the custodian and the depositor holds a contractual claim, digital assets exist on a blockchain and control is determined by possession of the private keys. The legal question is: who holds the keys, under what arrangement, and what happens if that party becomes insolvent, is hacked or refuses to execute a transfer instruction? The custody models in use today are self-custody (the company holds the keys directly, typically using a multisignature wallet or hardware security module), qualified custodian (a regulated third-party custodian holds the keys under a bailment or custody agreement), and exchange custody (the company maintains a balance at an exchange, holding a contractual claim against the platform rather than direct control of on-chain assets).

Self-custody offers maximum control but exposes the company to operational risk: key loss, insider theft and the need to establish internal controls that satisfy auditors. For a listed company, the auditor will require evidence of segregation of duties (no single employee can move funds), disaster-recovery procedures (how keys are backed up and reconstructed if the primary system fails), and insurance coverage (which is available but expensive and limited in scope). The board resolution authorizing a self-custody model must explicitly assign responsibility for key management, set transaction-approval thresholds and establish a process for periodic key rotation. We have seen two disputes in the past year where a departing CTO held one key in a multisignature setup and the company had no enforceable protocol to compel its return; the matter was resolved by negotiation, but the legal position was weak because the employment contract and the treasury policy were silent on key-handover obligations.

Qualified custody mitigates operational risk but introduces counterparty and regulatory risk. The custodian must be demonstrably solvent, must hold the assets in segregated accounts (so that the company's holdings are not part of the custodian's estate in bankruptcy), and ideally must be licensed or registered in a jurisdiction with a clear insolvency regime for digital-asset custodians. In the European Union under MiCA, a CASP providing custody services must meet capital and safeguarding requirements; in the United States, custodians may be chartered as trust companies under state law or may operate under federal banking authority. The custody agreement must address the standard of care (negligence vs strict liability), the process for disputed instructions, and whether the custodian has any right to rehypothecate or lend the assets. A listed company using a qualified custodian should obtain a SOC 2 Type II report (or equivalent) covering the custodian's key-management and access controls, and should require the custodian to carry insurance or maintain a reserve fund to cover loss events.

Exchange custody is the riskiest model from a legal perspective because the company does not hold the assets – it holds a claim. If the exchange becomes insolvent, the company is an unsecured creditor (or, in some jurisdictions, a beneficiary of a trust if the exchange operated a proper segregation regime, but establishing that position in a cross-border insolvency is slow and expensive). Auditors increasingly require a representation from the exchange confirming that the company's balance is held in a segregated account, that the exchange does not lend or stake those assets without explicit authorization, and that the company can withdraw on demand (or within a specified notice period). For operational convenience, many companies use exchange custody for short-term trading positions and move long-term holdings to a qualified custodian or self-custody. The governance-approval process should treat the two buckets separately, with a lower board-level threshold for exchange-held balances and a requirement that any balance above a specified limit be swept to cold storage.

Disclosure obligations for listed companies

A listed company holding material digital assets on balance sheet faces three disclosure regimes: periodic reporting under securities law (annual and quarterly filings), continuous disclosure of material events, and proxy-statement disclosure if the holdings are significant enough to warrant a shareholder vote or if an activist raises governance concerns. In the United States, the Securities and Exchange Commission has not issued crypto-specific guidance for corporate holders, but the general materiality standard applies: if the size of the position, the volatility of the asset or the custody risk could reasonably influence an investor's decision, it must be disclosed. In practice, this means that a $50 million Bitcoin allocation by a company with a $2 billion market cap will appear in the MD&A (management discussion and analysis) section of the 10-K, with a description of the custody arrangement, the accounting policy and the risk factors specific to digital assets.

The risk-factor section typically addresses price volatility (Bitcoin's 30-day volatility routinely exceeds that of equity indices), regulatory risk (the possibility that holding or transacting in digital assets becomes restricted or taxed more heavily), custody risk (loss, theft or inaccessibility of keys), and liquidity risk (the ability to exit a large position without material slippage, particularly for assets outside the top ten by market capitalization). A company that stakes or lends its holdings must also disclose counterparty risk and the terms of the staking or lending arrangement. The auditor will test these disclosures against the underlying custody agreements, board resolutions and transaction records, and will flag any mismatch between what the company told the market and what the internal documentation shows.

Accounting treatment turns on the asset classification. Under US GAAP, most digital assets are treated as indefinite-lived intangible assets, carried at cost less impairment. The company tests for impairment each reporting period: if the fair value of the asset falls below its carrying value, the company writes down the asset and records an impairment loss. Critically, under current US GAAP there is no reversal of impairment if the price subsequently recovers – the asset remains at the impaired value until it is sold. This creates a significant accounting distortion for volatile assets: a company that bought Bitcoin at $60,000, saw it drop to $40,000 (recording a $20,000 impairment), and then watched it rise to $70,000 shows the asset on the balance sheet at $40,000 until disposal, even though the economic reality is a gain. FASB issued an exposure draft in 2023 proposing fair-value accounting with changes in value running through earnings; if adopted, this would align the accounting treatment with the economic position but would introduce earnings volatility. Until the standard changes, companies must live with the impairment-only model and explain the distortion in the footnotes.

In the European Union, IFRS does not have a specific standard for digital assets. IAS 38 (intangible assets) is the fallback, yielding a treatment similar to US GAAP (cost less impairment), though some preparers argue for IAS 2 (inventories) if the company's business model involves regular trading, or for fair value through profit or loss if the company applies the fair-value option. The key point: the accounting policy must be disclosed, must be applied consistently, and must be justified in terms of the company's business model and the nature of the holdings. A company that describes its Bitcoin position as a "strategic reserve" but applies inventory accounting (because it plans to trade actively) will face questions from the auditor and from sophisticated investors.

Governance approvals and board authority

Allocating treasury reserves to digital assets is a material decision requiring board approval in almost every jurisdiction. The board resolution should specify the maximum allocation (as a percentage of treasury or as a dollar cap), the permissible assets (Bitcoin only, or a defined list of large-cap tokens), the custody model, the authority to execute trades (CFO, treasurer or a committee), and the hedging or disposal authority (who can sell, under what circumstances, and whether board re-approval is required above a certain size). The resolution should also address the accounting policy, the disclosure policy and the review cadence (quarterly reporting to the board on the position, gains/losses and any custody or operational incidents).

For a public company, the allocation may trigger a shareholder vote if it exceeds a certain threshold of assets or if the company's articles or the applicable listing rules require shareholder approval for material changes in investment policy. In the United Kingdom, the Listing Rules require shareholder approval for a "Class 1" transaction (broadly, one exceeding 25% of the company's gross assets, profits or market cap); a large Bitcoin purchase could meet that test. In the United States, there is no automatic shareholder-vote trigger for treasury management, but if the allocation is significant enough to change the risk profile of the company, the board may choose to seek a non-binding shareholder resolution to insulate directors from a later breach-of-duty claim. An activist investor challenging a crypto allocation will typically allege that the board failed to adequately investigate the risks, failed to establish proper controls, or acted outside its authority by converting cash into a speculative asset without shareholder consent. The defenses are process and documentation: minutes showing that the board received expert advice, considered alternatives, set limits and established a monitoring framework.

In our cross-border practice, we regularly see boards approve an initial allocation but fail to establish a sell discipline. The resolution says "up to $100 million in Bitcoin" but is silent on when or how the position is closed, leaving the CFO to make ad hoc decisions during periods of volatility. A better approach is to specify exit triggers (sell if the position exceeds 15% of treasury, or if Bitcoin falls below a specified price, or if the company needs the liquidity for an acquisition) and to require board re-approval if the exit strategy is overridden. This disciplines the decision-making and creates a paper trail that protects directors if the investment performs poorly.

Tax treatment of treasury holdings

The tax treatment of digital assets on balance sheet varies by jurisdiction, by the legal form of the company, and by whether the company is trading or holding. In the United States, digital assets are treated as property for federal income-tax purposes. A company that buys Bitcoin and holds it realizes no taxable event on purchase; gain or loss is recognized on disposal, calculated as the difference between the sale price and the cost basis. If the company uses Bitcoin to pay a vendor, that is a disposal triggering gain or loss. If the company receives Bitcoin as payment for goods or services, it recognizes ordinary income equal to the fair market value of the Bitcoin on the date of receipt, and that value becomes the cost basis for a subsequent disposal. Staking rewards and mining proceeds are ordinary income when received. A company staking Ether and earning 4% annually in rewards must report that 4% as income in the year earned (valued at receipt), even if it does not convert the rewards to fiat.

For a non-US company holding digital assets, the tax position depends on the company's residence and the source of the gain. In many jurisdictions, gains on the disposal of digital assets by a corporate holder are taxed as ordinary business income (not capital gains), particularly if the company's business involves digital assets or if the holding period is short. In the United Kingdom, a company disposing of crypto assets pays corporation tax on the chargeable gain, calculated under the general corporate capital-gains rules (cost basis vs disposal proceeds, indexed for inflation if the asset was acquired before a specified date). The company can offset losses in the same period and can carry forward unused losses against future crypto gains. VAT treatment: under UK and EU law, the exchange of fiat for Bitcoin or other payment-type digital assets is exempt from VAT (following the *Hedqvist* CJEU decision), but fees charged by an exchange or custodian for services are subject to VAT at the standard rate.

A company holding digital assets across multiple jurisdictions must address permanent-establishment risk. If the company's trading activity is managed from a jurisdiction different from its place of incorporation, the trading jurisdiction may assert that the company has a taxable presence there. This risk is heightened if the company uses a local exchange or a local custodian and if employees in that jurisdiction make trading decisions. The mitigation is to centralize decision-making in the company's home jurisdiction, to use the local service provider purely for execution (not advice or discretion), and to document the arrangement in board resolutions and service agreements. We have advised a European software company on a structure where the parent held the digital assets but delegated execution to a subsidiary in a lower-tax jurisdiction; the structure worked because the parent board retained approval authority over all trades above a specified size, and the subsidiary acted purely on instruction.

Private companies and closely held structures

A private company holding digital assets on balance sheet faces fewer disclosure obligations than a listed company but must still address custody, governance and tax. The key difference: there is no public market to discipline management, so the risk is that a founder or controlling shareholder makes a large crypto allocation without board approval or without establishing adequate controls, and the other shareholders or creditors learn of it only when the position has lost value or when a custody event (hack, insolvency of the custodian) crystallizes the risk. The legal mechanism to prevent this is the company's articles of association and any shareholders' agreement: these documents should specify the activities that require board approval (investing in digital assets, staking, lending) and the activities that require a shareholder vote (large allocations, changes in accounting policy). If the company has external investors (venture-capital funds, family offices), the investment agreement typically includes a reserved-matters clause requiring investor consent for material changes in business or investment strategy; an allocation of 20% of the company's cash to Bitcoin would likely fall within that clause.

For a closely held company, the custody question often turns on the founder's personal control preferences. A founder who built the company may be comfortable self-custodying the company's digital assets using a multisignature wallet, with the founder holding one key and a trusted advisor or co-founder holding the other. This arrangement works operationally but creates an exit problem: when the company is sold or raises a funding round, the acquirer or the new investors will insist on professional custody as a condition of closing. The company then faces a forced migration of assets to a qualified custodian (incurring setup fees and operational changes) and must address the historical custody position in the due-diligence process. A cleaner approach is to establish qualified custody from the start, even for a closely held company, if there is any prospect of institutional capital or a trade sale in the next three to five years.

Staking, lending and yield-generating activities

A company that stakes its Ether through a proof-of-stake validator or deposits stablecoins into a DeFi lending protocol is no longer simply holding a treasury reserve – it is conducting an income-generating activity, and that activity may trigger additional regulatory, accounting and disclosure obligations. The regulatory question is whether the activity requires a licence. In most jurisdictions, staking by a company on its own account does not require authorization, but if the company offers staking-as-a-service to customers (holding and staking customer assets and paying out rewards), it is likely conducting a custody or investment-management service requiring a licence. The line is clear if the company is staking only its own balance-sheet holdings; it becomes ambiguous if the company runs a validator and accepts delegated stakes from unrelated parties (even if structured as a technical delegation rather than a custody relationship).

Lending creates counterparty risk. A company that deposits $10 million in USDC into a centralized lending platform (or a DeFi protocol) is relying on the platform's solvency and on the over-collateralization of the loans funded by that deposit. If the platform experiences a wave of defaults or a liquidity crisis, the company may be unable to withdraw its funds. The accounting treatment: if the deposit is a loan (the company has a contractual right to the return of the principal plus interest), it is recognized as a financial asset and tested for impairment under the expected-credit-loss model. The company must assess the creditworthiness of the platform and must write down the loan if recovery is doubtful. The governance-approval process for lending should specify the permissible counterparties (e.g., platforms with a SOC 2 Type II report, or DeFi protocols with audited smart contracts), the maximum exposure per counterparty, and the interest-rate or yield threshold that justifies the risk.

Staking rewards and lending interest are ordinary income when received. In a DeFi context, "received" typically means when the rewards or interest are claimed and moved to the company's wallet (not when they accrue in the protocol but remain locked). The company must track the fair market value of the rewards at the time of receipt, report that value as income, and establish a cost basis for a subsequent disposal. For a company with a large staking operation, this creates a significant administrative burden (daily valuation of rewards, reconciliation of on-chain data with accounting records) and may justify the use of a specialized tax-reporting tool or a service provider that handles crypto accounting.

Cross-border treasury allocation

A company incorporated in Delaware, with its treasury managed from London, holding digital assets through a custodian in Switzerland, must address three layers of law: the corporate law of the place of incorporation (Delaware, which governs the board's authority and fiduciary duties), the employment and operational law of the place where decisions are made (UK, which may create permanent-establishment exposure), and the custody and insolvency law of the place where the assets are held (Switzerland, which determines the company's rights if the custodian fails). The company's tax residence is usually the place of incorporation or the place of effective management, but the source of gains is the place where the trading or disposal occurs, which may be a fourth jurisdiction if the company uses an exchange domiciled elsewhere. This multi-jurisdiction reality requires a coordination of board resolutions, custody agreements, tax registrations and internal policies, all of which must acknowledge that different pieces of the legal stack sit in different places.

The custody agreement must specify governing law and the forum for disputes. A company incorporated in Singapore using a US custodian will typically choose New York or Delaware law for the custody agreement and will require the custodian to submit to the jurisdiction of a specified court. The company should also address insolvency: if the custodian becomes insolvent, does the company have a proprietary interest in the assets (so that it can recover them ahead of the custodian's creditors), or is it merely a contractual creditor? The answer depends on whether the custody arrangement is a bailment (the custodian holds the assets on trust or as agent, and the company retains beneficial ownership) or a deposit (the custodian becomes the owner and the company holds a claim). For digital assets, the better structure is bailment, documented in the custody agreement with an explicit acknowledgment that the company is the beneficial owner and that the custodian holds the assets in a segregated wallet. The company should obtain legal advice in the custodian's jurisdiction confirming that the segregation is effective under local insolvency law.

For a group with operating subsidiaries in multiple jurisdictions, the question is whether the parent or a subsidiary should hold the digital assets. Centralizing the holdings in the parent simplifies governance (one board making all decisions) and avoids double taxation of gains when funds are repatriated, but it may expose the parent to regulatory obligations in jurisdictions where the parent has no other presence. Decentralizing the holdings (each subsidiary holds its own local digital-asset reserve) matches the assets to the operational jurisdiction but multiplies the compliance burden (multiple custody arrangements, multiple tax filings, multiple audit processes). In our cross-border practice, we generally recommend that a company centralize holdings in a single entity (the parent or a dedicated treasury subsidiary) if the group's operations are concentrated in two or three jurisdictions, and decentralize only if the group has material operations in five or more jurisdictions and needs local digital-asset reserves to manage currency risk or to settle local liabilities in crypto.

Common structural mistakes

The first mistake is mixing personal and corporate holdings. A founder who controls the company's multisignature wallet and also holds personal Bitcoin in a wallet with similar access controls creates an audit trail problem and a risk of inadvertent commingling. If the founder uses the same hardware wallet for both personal and corporate keys, and if a transaction occurs, it may be unclear whether the transaction is a corporate disposal or a personal trade. The mitigation is to maintain completely separate custody environments: corporate keys held on enterprise-grade hardware or with a qualified custodian, personal keys held on consumer hardware or with a different custodian, and a policy requiring that any corporate transaction be approved by at least two officers (so that the founder cannot unilaterally move corporate funds). For a listed company, the auditor will insist on this separation, and the board should memorialize it in a policy.

The second mistake is inadequate insurance. Many companies assume that the custodian's insurance or the company's general commercial crime policy covers loss of digital assets. In practice, custodian insurance typically excludes losses caused by the customer's own error (phishing, insider theft by the customer's employees) and covers only losses caused by the custodian's negligence or a breach of the custodian's systems. The company's commercial crime policy typically excludes digital assets unless specifically endorsed, and even with an endorsement the coverage is sub-limit (e.g., a $50 million policy with a $5 million sub-limit for crypto) and subject to a high deductible. A company holding material digital assets on balance sheet should obtain standalone digital-asset insurance (a "specie" policy covering theft, loss and certain cyber events) or should negotiate a custody agreement that makes the custodian strictly liable for loss, regardless of fault. The board resolution authorizing the allocation should require evidence of insurance before the first purchase.

The third mistake is treating all digital assets identically. A $100 million Bitcoin allocation and a $10 million allocation spread across 20 altcoins carry different risks and require different controls. Bitcoin is highly liquid, has a deep derivatives market for hedging, and is widely accepted by qualified custodians. A low-cap altcoin may be illiquid (a large sale would move the market materially), may lack custody options (many custodians support only a narrow list of assets), and may have technical or regulatory risk (the token's smart contract may have exploits, or the token may be deemed a security). The governance-approval process should tier the permissible assets: Bitcoin and Ether in a first bucket (high allocation cap, streamlined approval), large-cap stablecoins in a second bucket (medium allocation cap, quarterly board review), and all other assets in a third bucket (low allocation cap, board approval required for each token, mandatory use of a qualified custodian). We advised a private gaming company that initially applied a single $50 million cap to "digital assets" and within six months had $40 million in illiquid NFTs and gaming tokens with no exit liquidity; the company restructured the policy to limit illiquid assets to $5 million and to require proof of liquidity (on-chain volume data, exchange listings) before any purchase over $1 million.

Decision matrix: listed vs private

A listed company holding Bitcoin as a reserve asset should use a regulated custodian, apply cost-less-impairment accounting under current US GAAP (or fair value once FASB's proposed standard is adopted), disclose the position in the MD&A with detailed risk factors, obtain board approval for the allocation policy and for any allocation exceeding a specified percentage of market cap, and should establish a quarterly reporting process so that the board sees the position, any gains or losses, and any custody or operational incidents. The company should also address hedging: if the position becomes large relative to market cap, the board may authorize the purchase of put options or a collar to limit downside, and that hedging activity must be disclosed and accounted for as a derivative. Indicative timeline for establishing this framework: six to ten weeks from board authorization to first purchase, assuming the custody agreement and the insurance are negotiated in parallel.

A private company with a concentrated ownership and a short-term holding horizon (buying stablecoins to settle vendor payments in crypto, holding for 30 days, then converting back to fiat) can use exchange custody if the balance is modest, can treat the assets as inventory under the accounting standards, and can apply a more streamlined governance process (CFO approval up to a cap, board approval above the cap). The key control is a reconciliation process: the CFO or treasurer must reconcile the exchange balance to the accounting ledger monthly, and any discrepancy (loss, unauthorized withdrawal) must be investigated immediately. For a private company holding digital assets as a long-term reserve (analogous to the listed-company Bitcoin reserve strategy), the custody, accounting and governance disciplines converge with the listed-company model, even though there is no public disclosure obligation – because the auditor will apply the same level of scrutiny and because future investors or acquirers in a due-diligence process will expect to see a professionally managed custody and control environment.

For advice on structuring the board resolution, the custody stack and the disclosure framework for a corporate digital-asset treasury, contact OBOLUS at info@oboluslaw.com. We have guided listed and private companies through the first allocation, the audit-readiness process and the cross-border tax and custody interaction.

Audit readiness and year-end procedures

Auditing digital assets presents unique challenges because the asset exists on a blockchain and the auditor must verify both the company's ownership and the accuracy of the reported balance. The standard audit procedure is a blockchain confirmation: the company provides the auditor with the public address of the wallet or custodial account, and the auditor queries the blockchain directly to confirm the balance as of the reporting date. For self-custody, the auditor will also require the company to prove control by executing a small test transaction (moving a nominal amount from the address to a different address and back, or signing a message with the private key). For third-party custody, the auditor will request a confirmation letter from the custodian, and may request the custodian's SOC 2 report to evaluate the controls around key management and access.

The company must also provide a reconciliation of the on-chain balance to the accounting ledger: if the ledger shows 100 Bitcoin but the wallet shows 98, the company must explain the difference (was there a disposal, a transfer to another wallet, a loss event?). The auditor will test a sample of transactions during the year: purchases (matching the cost basis to the exchange confirmation or invoice), disposals (matching the sale proceeds to the exchange trade report), and transfers (matching the on-chain transaction to the internal approval and the business purpose). For staking or lending activities, the auditor will test the recognition of rewards or interest income, requiring the company to demonstrate how it valued the rewards on receipt and how it tracked the cost basis for subsequent disposals.

Year-end procedures should include a board-level review of the digital-asset position: the opening and closing balance, the realized and unrealized gains or losses, any impairment charges, any custody or operational incidents during the year, and any changes in the accounting policy or the custody arrangement. The board minutes should record this review and should re-approve the allocation cap and the permissible assets for the following year. If the allocation has grown to a size that materially affects the company's risk profile, the board should also review the insurance coverage and the hedging strategy. For a listed company, the CFO should prepare a memo for the audit committee summarizing the audit findings and any control deficiencies identified during the audit; that memo becomes part of the audit-committee's record and provides assurance that the committee exercised oversight.

A common assumption is that custody is a solved problem

Operators often assume that if they use a "brand-name" custodian or a large exchange, custody risk disappears. The reality is that even the largest platforms have experienced hacks, insolvencies and operational failures. Custody is a multi-party problem: the custodian's technical controls, the customer's access controls (who can instruct a withdrawal), the legal segregation of assets (does the customer have a proprietary interest or merely a claim), and the insurance or reserve fund backing the arrangement. A company relying solely on the custodian's brand is exposed if any of those layers fails. The due-diligence process should test all four: request the custodian's SOC 2 report, review the terms of the custody agreement (is it bailment or deposit, what is the standard of care, how are disputed instructions resolved), confirm that the customer's assets are held in a segregated on-chain wallet (not pooled with the custodian's proprietary assets), and verify the insurance or reserve-fund coverage. If the custodian is unwilling to provide this information, the company should look elsewhere.

Disclosure for activist and proxy scenarios

An activist investor or a shareholder advocacy group targeting a company with significant digital-asset holdings will typically raise three arguments: (1) that the allocation was not properly disclosed or that the risk factors are inadequate, (2) that the board failed to establish adequate controls or failed to monitor the position, or (3) that the allocation is inconsistent with the company's stated strategy or capital-allocation priorities (e.g., the company should be returning cash to shareholders rather than speculating on Bitcoin). The company's defense rests on the quality of its process documentation. If the board minutes show that the board received a detailed presentation on the risks, compared the digital-asset allocation to alternative uses of cash, set clear limits and established a monitoring framework, the activist's claims are weak. If the board minutes are sparse or if the allocation was made by management without board involvement, the activist has a credible governance claim.

Proxy disclosure: if the activist files a shareholder proposal seeking a report on the company's digital-asset holdings or seeking a board declassification to make directors more accountable, the company must respond in the proxy statement. The response should describe the board's oversight process, the controls in place, the performance of the position to date, and the board's rationale for maintaining or adjusting the allocation. The company should avoid defensive language ("the board believes the allocation is prudent") and instead present the facts: the allocation cap, the custody model, the accounting policy, the insurance coverage, and the quarterly reporting discipline. Sophisticated institutional investors will evaluate the response on the quality of the controls, not on the performance of the investment.

Regulatory developments and forward-looking considerations

Regulatory treatment of corporate digital-asset holdings is evolving. In the United States, the SEC has signaled that it views certain custody arrangements (particularly where the custodian also acts as a trading platform) as implicating investor-protection concerns, but has not issued formal guidance for corporate holders. The proposed FASB accounting standard would move digital assets to fair-value accounting, which would better reflect economic reality but would introduce earnings volatility; companies should model the impact of the proposed standard on their financial statements and consider whether to comment on the proposal. In the European Union, MiCA establishes a licensing regime for custodians and for issuers of asset-referenced tokens and e-money tokens, but does not directly regulate corporate holders; the relevant obligations are custody (use a MiCA-authorized custodian if holding on behalf of third parties) and disclosure (if the company is listed, the usual materiality and risk-factor rules apply).

For a company planning a digital-asset treasury allocation, the forward-looking question is: how much optionality do we preserve? A company that buys Bitcoin and holds it in self-custody using a multisignature wallet has maximum flexibility but must build internal expertise and controls. A company that uses a qualified custodian can scale the position easily (the custodian supports multiple assets, multiple wallets, API integration for reporting) but pays a custody fee and accepts counterparty risk. A company that uses exchange custody can deploy capital quickly and can trade actively, but faces the highest risk if the exchange fails and may find that future investors or acquirers view the arrangement as sub-standard. In our cross-border practice, we recommend that a company building a long-term digital-asset reserve start with qualified custody and migrate to self-custody only if the internal capability (security team, key-management discipline, insurance) reaches institutional grade. For short-term trading positions, exchange custody is acceptable if the balance is monitored daily and swept to cold storage when it exceeds a specified threshold.

Related at OBOLUS

FAQ

Where should this fund be domiciled?

Domicile choice for a digital-asset fund turns on the investor base (UCITS-eligible EU investors vs US qualified purchasers vs offshore institutional investors), the asset mix (vanilla tokens vs DeFi positions vs staking) and the tax and regulatory position of the manager. BVI and Cayman offer flexibility and low tax leakage, but an EU manager serving EU retail may need a Luxembourg or Irish UCITS wrapper. A US manager with only US accredited investors may use a Delaware or Cayman structure. The wrong domicile locks in withholding tax on distributions, limits investor eligibility and creates operational friction. The decision is made at the start and is expensive to unwind.

Does the manager need a licence?

Manager licensing depends on the jurisdiction of management (where portfolio decisions are made), the legal form of the fund, and whether the manager is delegating investment authority or merely advising. In the European Union, managing a UCITS or an alternative investment fund (AIF) requires an AIFM authorization; many digital-asset managers use a MiFID portfolio-management licence as a pathway. In the United States, an investment adviser managing client assets typically registers with the SEC (if assets under management exceed the threshold) or with a state regulator. Offshore managers (BVI, Cayman) are not licensed locally but must comply with AML and with any registration obligation in the jurisdiction where they are marketing the fund. A manager operating from multiple jurisdictions must map the licensing stack and may need to establish a licensed entity in the primary jurisdiction of activity.

How is custody arranged for this vehicle?

Custody for a digital-asset fund depends on the asset mix and the fund's domicile. A fund holding only Bitcoin and Ether will typically use a qualified custodian (Anchorage, BitGo, Copper, Fireblocks) under a custody agreement that segregates the fund's assets and grants the custodian no rehypothecation rights. A fund with DeFi positions may hold assets in smart-contract wallets controlled by the fund manager (technically self-custody, but with operational controls and insurance). The fund's offering documents must describe the custody model, and the auditor will verify custody annually. For a UCITS or an AIF, EU law requires that the depositary (the custodian or oversight agent) be a licensed entity; the manager cannot self-custody without an exemption. Investors will test custody in due diligence and will require evidence that the custodian is solvent, insured and subject to a robust audit regime.

About OBOLUS

OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. Our disputes team coordinates freezing relief and on-chain tracing across leading common-law forums, matching domicile to investor base, asset mix and redemption profile for every fund vehicle. To discuss your situation, contact info@oboluslaw.com.

By Lydia Brennan, Tax & Structuring Analyst – specializing in cross-border tax planning and the accounting and disclosure obligations for corporate digital-asset holders.

This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours