Skip to main content

Bailment Framework

The bailment framework

A reference page on how we think about digital-asset operations inside a discretionary managed account. Not tax advice. The framework, the structural elements, the seven grounds, and the supporting parallels — all in one place.

A discretionary investment adviser moving stocks between custodial accounts doesn't trigger a tax event for the client. A portfolio manager participating in a share-class conversion doesn't trigger a tax event. A separately managed account rebalancing across execution venues doesn't trigger a tax event. The beneficial owner is the same; the form changes; the substance does not.

The same logic applies to digital assets when the structural elements line up. We call that the bailment framework.

A bailment is the deposit of property with a fiduciary for management. The bailor (the client) delivers property to the bailee (the adviser) for professional management. Ownership stays with the bailor. The bailee has scoped authority — trade, deploy, route — but no path to convert the relationship into ownership. Tax events occur only when the client's economic position actually changes: a sale of BTC for USD, an exchange of BTC for ETH, a disposition that meets the realization standard of IRC §1001.

Operational steps inside the managed account — wrapping BTC into a 1:1-pegged 1:1-redeemable receipt, depositing USDC into a lending vault for yield, bridging the same asset between chains, entering an LP position to deploy capital — change the form or location of assets without changing economic exposure. We treat these as non-taxable operational events and document the position annually with Form 8275. Below is the framework, the seven legal grounds we rely on for wrapped-BTC operations, and the supporting regulatory parallels we cite alongside it.

What this page is. A description of our internal framework. We publish it because the absence of public IRS guidance on these specific activities — wrapping, vault deposits, liquid staking, bridging — has produced a long-running ambiguity that responsible advisers should be transparent about. Clients, CPAs, and the broader market should be able to see how we think.

What this page is not. Tax advice. Personal advice. A solicitation. A guarantee that the IRS or a court will agree with our position on any specific transaction. The bailment framework is the position we operate from, with documented Form 8275 disclosure on uncertain items, in advisory-agreement language we negotiate with clients. Anyone reading this page should consult their own qualified tax counsel and CPA before applying anything here to their own situation.

Section 1

Five structural elements

A relationship is a bailment when five elements are present. We document each one in the advisory agreement, the IPS, and the operational architecture; absent any of them, the framework does not apply.

1. Delivery

The client deposits digital assets into the managed-account wallet infrastructure. Recorded on-chain. The deposit transaction itself is the evidence.

2. Purpose

The deposit is for professional investment management under a signed advisory agreement and an Investment Policy Statement that defines the scope of discretion (which strategies, which protocols, which assets). No purpose drift.

3. Return

The client can terminate the relationship and receive the assets back. All positions are redeemable. The advisory agreement spells out termination and return mechanics.

4. Possession vs. ownership

We exercise trading authority through a policy engine. We do not possess client private keys. The infrastructure is multi-party computation (Fordefi pattern) or scoped delegated authority on a client-owned smart account — operational signing, not unilateral custody.

5. Retained ownership

The client holds an independent full private-key backup, either self-managed or via a regulated disaster-recovery service registered in the client's name. A withdrawal whitelist enforced at the infrastructure layer prevents us from routing assets to any unapproved address. The client can recover unilaterally without our cooperation; we cannot move client assets to a counterparty without client consent.

Section 2

Operational vs. dispositive

Not every on-chain transaction is a tax event. The distinction we draw is between operational steps that change the form or location of assets without changing economic exposure, and dispositive transactions that change what the client actually owns.

Operational. Wrapping BTC into a 1:1-pegged 1:1-redeemable receipt token. Depositing USDC into a lending vault and receiving vault shares. Converting ETH into a non-rebasing liquid staking token. Bridging the same asset between chains. Entering an LP position. Each of these changes the form or location of an asset under management. None of them change what the client owns. Receipt tokens, vault shares, and LP tokens function as continuing-claim instruments — not new property acquired in exchange.

Dispositive. Selling BTC for USD. Exchanging BTC for ETH. Closing an LP position back to a different mix than entered. Each of these changes the client's economic exposure to a specific risk/reward profile. These are realization events under §1001 — the basis and holding period reset, gain or loss is recognized, and we report accordingly.

The general test. If the client's economic exposure to a specific risk/reward profile is unchanged after the transaction, we treat it as operational. If the exposure changes — different underlying asset, different issuer risk, different return profile — we treat it as dispositive.

Section 3

Activity matrix

How the framework applies to common activities inside a discretionary managed account. The "operational" rows are positions we take with Form 8275 disclosure on the corresponding return.

Activity Treatment Rationale
Wrapping BTC (BTC → cbBTC / tBTC / WBTC) Operational 1:1 pegged, 1:1 redeemable receipt token; no economic change.
Unwrapping (wrapped → native) Operational Reverse of wrapping; same logic.
Bridging (same asset, different chain) Operational Routing decision; same asset, different infrastructure.
Vault deposit (USDC → lending-vault shares) Operational Vault share = pro-rata receipt on underlying pool; mutual-fund analog.
Vault withdrawal Operational Reversing deployment; receiving underlying back.
Liquid staking (ETH → wstETH) Operational Receipt token; redeemable with delay; same underlying ETH exposure.
LP entry (deposit to AMM) Operational LP token = receipt for deposited assets; capital deployed for yield.
Staking rewards (native or restaking) Income New tokens created; accession to wealth at FMV on receipt (Rev. Rul. 2023-14).
LP fee income Income Trading fees accrued — new value to position; ordinary income.
LP position closed Capital gain / loss Entry vs. exit valuation; realization at close.
Selling BTC for USD Dispositive Genuine disposition; economic position changes.
Exchanging BTC for ETH Dispositive Different economic exposure; materially different asset.

Selected rows. The full internal activity matrix covers stablecoin conversions, async-redemption vaults, and other borderline cases that we work through with the client's CPA on a fact-specific basis.

Section 4

Wrapped BTC: seven legal grounds

Wrapping BTC is the operation we get the most questions about, so it gets its own section. Inside a discretionary managed account, with the five structural elements present, our position is that wrapping is not a taxable event under §1001. We rely on seven independent grounds, ranked by defense strength.

Ground 1 IRS FAQ A81 — self-transfer anchor

IRS FAQ A81 states that transferring virtual currency from one wallet to another wallet that you own does not constitute a sale, exchange, or disposition. The client retains an independent full private-key backup; withdrawal whitelisting prevents routing to unapproved addresses. Wrapping moves the client's own property between operational wrappers under fiduciary management — a self-transfer, not a disposition. This is the strongest published IRS guidance directly supporting non-taxable treatment.

Ground 2 IRS regulatory gap

No statute, regulation, revenue ruling, or case law declares wrapping taxable. IRS Notice 2024-57 deferred broker reporting for wrapping and unwrapping pending further study, and the deferral has been extended. The IRS has had every opportunity to classify wrapping as taxable and has not done so.

Ground 3 Substance over form

Gregory v. Helvering, 293 U.S. 465 (1935): tax treatment follows economic substance, not legal form. The client's economic exposure to Bitcoin is unchanged. The wrapped token is pegged 1:1, redeemable 1:1. Beneficial ownership is retained. The form changed; the substance did not.

Ground 4 No accession to wealth

Commissioner v. Glenshaw Glass Co., 348 U.S. 426 (1955): income requires an "accession to wealth, clearly realized." Zero change in net economic position equals zero accession equals no realization event.

Ground 5 Managed-account bailment

The client deposited BTC into a discretionary managed account. Wrapping was our operational implementation decision — not a client-directed exchange. The advisory relationship is a bailment: the client delivers property to the adviser for management, and ownership never transfers. The five structural elements above are present and documented.

Ground 6 Cottage Savings — not materially different

Cottage Savings Ass'n v. Commissioner, 499 U.S. 554 (1991): realization requires an exchange of "materially different" legal entitlements. Wrapped BTC is pegged 1:1, redeemable 1:1, with the same economic rights as the underlying — not materially different. Cottage Savings involved mortgage participations with genuinely different obligors and risk profiles. Wrapped BTC is not that.

Ground 7 Basis and holding-period continuity

IRC §1015 carryover basis exists to defer built-in gain until genuine realization. IRC §1223(2) preserves holding period when no disposition occurs. Treating wrapping as taxable would reset the holding period — potentially converting long-term capital gain into short-term and roughly doubling the rate. The basis-continuity policy embedded in §1015 and §1223 supports the position that wrapping is not a realization event.

Section 5

The single strongest fact

Of all the elements in this framework, one carries more weight than any other: the client's independent full private-key backup.

The backup is a mathematical capability, not a contractual right. The client can recover unilaterally without our cooperation. No equivalent exists in traditional finance — there is no "broker keeps a stamp that also opens your safe deposit box." If the client's BTC were truly sold to a counterparty during a wrapping operation, the client would have no independent path to recover it. The fact that the client retains cryptographic recovery capability is dispositive evidence that beneficial ownership never transferred.

We pair the backup with a withdrawal whitelist enforced at the infrastructure layer — Fordefi policy engine, scoped delegated authority on a client-owned smart account, or equivalent. We are structurally unable to route client assets to an unapproved address. Not by voluntary compliance — by code. An IRS examiner asking "where is the counterparty in this alleged exchange" has to answer their own question against an architecture that forecloses one.

Section 6

Two supporting parallels

Two recent regulatory documents make structural characterizations about non-custodial digital-asset architecture that map directly onto the bailment framework. Neither contains tax analysis. Both are useful as independent federal characterization that the structural relationship we describe is not a custody arrangement.

Veda letter to the SEC and CFTC (March 23, 2026)

Veda Tech Labs proposed that non-custodial smart-contract vault architectures satisfy the qualified-custody requirements of Advisers Act Rule 206(4)-2 and CFTC segregation regulations 1.20 and 4.20 when seven structural guardrails are met. The letter is SEC- and CFTC-facing — no tax analysis. But four of its structural characterizations track the bailment argument almost word-for-word.

  • Receipt token as bailment receipt. Section III.A describes the receipt token as a cryptographic instrument representing the client's proportionate claim against the vault's underlying assets, redeemable upon presentation to the smart contract. Textbook bailment language.
  • No balance-sheet intermediation. Section III.B states that client assets in a qualifying vault are never on any vault participant's balance sheet and no vault participant holds a proprietary interest. If no participant holds a proprietary interest, there is no counterparty to whom ownership could transfer.
  • Non-transferable receipt tokens. Footnote 12 states that the receipt token cannot be moved to any other wallet by the vault owner; the only action available is redemption back to the authorized wallet. This directly supports the Cottage Savings "not materially different" argument — the token is a redemption instrument, not a tradeable asset.
  • SMA analogy. Section VI compares vaults to separately managed accounts. We agree. A portfolio manager moving stocks between custodial accounts within an SMA does not trigger a tax event for the client. Neither should a vault deposit within a discretionary managed account.

SEC staff statement on Covered User Interface Providers (April 13, 2026)

The SEC Division of Trading and Markets issued a staff statement addressing Exchange Act §15 broker-dealer registration for "Covered User Interface Providers" — interfaces that assist users transacting on blockchain protocols using the user's self-custodial wallet. The staff set out twelve conditions under which they will not object to operating without broker-dealer registration. Three premises in the statement are tax-relevant.

  • Self-custodial wallet as architectural prerequisite. Footnote 6 defines the self-custodial wallet as one where neither the wallet provider nor the associated interface has custody of, or access to, the user's encrypted or decrypted private key. This is the same structural fact our framework documents: the client holds the key; we hold scoped execution authority; we have no independent path to move assets to an unapproved destination.
  • No discretion, no recommendation, no order-taking. Section II expressly excludes the carve-out from interface providers that make investment recommendations or take or route orders. The staff drew a clean line between interface activity and advisory activity. We sit on the advisory side of that line — the interface activity our clients route through is the carve-out addressee — but the same self-custody premise applies to our scoped execution role.
  • Fee-neutrality and disclosure. The staff conditioned non-objection on fixed or flat fees that are product-, route-, venue-, and counterparty-agnostic; neutral sort and filter tools; no commentary preferring one execution route; and a nine-prong disclosure set. Our compensation is AUM-based advisory fees only — no protocol-level economic interest, no routing-linked compensation. That removes the factual predicate for any "disguised exchange for consideration" counter-argument.

The staff statement is weaker authority than the Veda letter for tax purposes — it is staff guidance rather than a Commission rule, expressly limited to Exchange Act §15, and treated as withdrawn five years from the publication date absent Commission action. Its value is cumulative. It is a second federal framework, from a different Division on a different statute, describing the same self-custodial / non-possession structure we rely on.

Section 7

Form 8275 is standard practice

Form 8275 is the IRS Disclosure Statement filed when a position is not directly addressed by existing authority but has reasonable basis. Filing it eliminates the 20% accuracy-related penalty under IRC §6662 if the IRS later disagrees with the position. Cost to file: zero. Penalty avoided: 20% of any underpayment.

We treat Form 8275 disclosure as the standard practice for any uncertain position in this framework — wrapping and unwrapping, vault deposits and withdrawals, liquid staking entry and exit, LP entry and exit, bridging, stablecoin conversions across distinct issuers. The position is documented; the basis is cited; the relevant IRC section is named; the FMV at the event is recorded. If guidance later contradicts our position, the worst case is tax owed plus interest — without the penalty.

Recordkeeping matters. On-chain transaction hashes, FMV at each event, cost basis, holding period, and the documented basis for the position taken — all retained under the firm's seven-year retention policy and shareable with the client's CPA on request. If the IRS issues guidance contradicting our position, the records support a clean amended return (Form 1040-X) without reconstructing facts after the fact.

Section 8

When this framework does not apply

The framework is scoped. It applies inside a discretionary managed account with the five structural elements documented. Outside that scope, different analysis applies and the bailment argument may not survive.

  • Client-directed transactions outside the discretionary managed account. If the client signed the transaction themselves on their own initiative, there is no fiduciary deployment decision to point to.
  • Wrapped tokens that are not 1:1 pegged or 1:1 redeemable. The receipt token characterization breaks if the wrapper introduces meaningful economic divergence from the underlying.
  • Transactions on centralized exchanges where the client does not retain independent key backup. Without the fifth structural element, the bailment argument loses its strongest fact.
  • Pooled multi-depositor vaults where the receipt token represents a fungible proportional interest. Single-depositor and SMA-style vaults have a stronger bailment argument; pooled vaults need a different analysis and may be closer to a partnership-interest characterization.
  • Jurisdictions outside the United States. The framework is built on U.S. tax authority — Glenshaw Glass, Cottage Savings, IRC §1001, IRS FAQs. Other jurisdictions require their own analysis.

For any of these, the appropriate path is to have the client's CPA work with qualified tax counsel on the specific fact pattern. We will share our framework documentation, the activity-level audit ledger, and the governing-document language. We will not present our framework as applicable when it is not.

Section 9

Authorities cited

The framework rests on the following authorities. None of them are individually dispositive on every fact pattern; together they form the reasonable-basis foundation we document on Form 8275.

Statutes

  • IRC §1001 — realization requirement for gain or loss
  • IRC §1015(a) — carryover basis for property acquired by gift
  • IRC §1223(2) — holding-period tacking for gifted property
  • IRC §6662 — accuracy-related penalty on underpayments
  • IRC §6664(c)(1) — reasonable-cause / good-faith exception

Case law

  • Commissioner v. Glenshaw Glass Co., 348 U.S. 426 (1955) — accession-to-wealth standard
  • Cottage Savings Ass'n v. Commissioner, 499 U.S. 554 (1991) — "materially different" standard
  • Gregory v. Helvering, 293 U.S. 465 (1935) — substance over form

IRS guidance

  • Notice 2014-21 — virtual currency treated as property
  • Notice 2024-57 — deferred broker reporting for wrapping and unwrapping; staking; lending; LP transactions; short sales; notional principal contracts
  • IRS FAQ A81 — wallet-to-wallet self-transfer is not a sale, exchange, or disposition
  • Rev. Rul. 2023-14 — staking rewards are taxable income at FMV on receipt (distinguished — relevant to staking rewards, not staking entry)

SEC and CFTC material (non-tax, supporting)

  • Veda Tech Labs Inc., letter to SEC and CFTC (March 23, 2026) — recommending recognition of vault architectures as satisfying qualified-custody and segregation requirements
  • SEC Division of Trading and Markets, staff statement on Covered User Interface Providers, File No. 4-894 (April 13, 2026) — Exchange Act §15 carve-out for self-custodial wallet interfaces
  • SEC Custody Rule Modernization Whitepaper (December 19, 2025)

Change log

Versions

v1.0 May 2, 2026

Initial public publication. Five structural elements, operational vs. dispositive distinction, activity matrix, seven legal grounds for wrapped BTC, custody architecture significance, Veda + SEC Covered User Interface staff statement parallels, Form 8275 standard practice, scope limits, and authorities cited.

Last updated: June 5, 2026. Protocol Wealth, LLC is an SEC-registered investment adviser (CRD #335298). See our Form ADV for authoritative regulatory disclosures.

Registration with the SEC does not imply a particular level of skill or training. Advisory services are provided only under a signed advisory agreement.

No tax or legal advice. Protocol Wealth does not provide tax or legal advice. This page describes our internal framework and the structural and legal reasoning we rely on for Form 8275 disclosure of uncertain positions. It is not advice for any specific client, transaction, or fact pattern. Anyone reading this page should consult their own qualified tax counsel and CPA before applying anything here to their own situation. Different facts produce different outcomes; novel fact patterns require independent analysis.

All investments involve risk, including the potential loss of principal. Digital assets are highly speculative and volatile. Past performance does not guarantee future results.