A company transfers 100 bitcoin to another party. The blockchain leaves little doubt about what happened technically: 100 bitcoin have moved from one address to another.
For the accountant, however, that is only where the analysis begins.
Was the bitcoin sold, lent, wrapped or deposited into a blockchain protocol? Which rights were surrendered, retained or newly acquired? Most importantly, should the transferred bitcoin still be recognized on the company's balance sheet?
That last question has become increasingly urgent. The Financial Accounting Standards Board is addressing it through its
On Aug. 19, 2026, the FASB continued its deliberations and reached further tentative decisions on crypto asset lending and other transfers of crypto assets. For lending transactions involving crypto intangible assets, the board tentatively decided that the lender should continue to recognize the lent asset rather than derecognize it. For nonlending transfers of crypto intangible assets, it tentatively decided to continue applying the ASC 606 control model, supplemented by crypto-specific implementation guidance. The board then directed the staff to draft a proposed Accounting Standards Update for written ballot, with a 60-day comment period. These tentative decisions do not yet change U.S. GAAP.
The problem is simple: A blockchain records that a crypto asset has moved. It does not determine what asset, for accounting purposes, remains after that transfer.
Three transfers, three different accounting outcomes
Consider three separate scenarios involving company A, which holds crypto assets within the scope of ASC 350-60. That guidance applies to a defined category of fungible crypto assets, including bitcoin and ether, and requires subsequent measurement at fair value, with changes recognized in net income.
In the first scenario, company A lends 100 bitcoin to company B for six months. During the term of the arrangement, company B may sell, pledge or otherwise use the bitcoin but must return 100 bitcoin at maturity, together with a fee. Company A does not receive a new token. What remains, at a minimum, is a contractual right against company B to the return of 100 bitcoin.
In the second scenario, company A wraps 100 ether and receives 100 wrapped ether (WETH). Economically, this may resemble the same ether exposure in a different technical form. From an accounting perspective, however, it is necessary to determine what rights the WETH represents and whether company A, after the transaction, continues to hold the same accounting asset or has acquired a different one.
In the third scenario, company A contributes 100 ether and an equivalent value of another crypto asset that also falls within the scope of ASC 350-60 to a two-asset liquidity pool and receives an LP token in return. That token may represent a proportional interest in the pool whose composition changes continuously as other users trade against it. When company A exits the pool, it may therefore receive a different quantity and mix of crypto assets from those originally contributed.
All three transactions may begin with the same on-chain picture: crypto out. But what remains afterward differs fundamentally. The relevant accounting question is not "What token came in?" but "What right remains?"
Crypto lending reveals the fault line
At the 2022 AICPA & CIMA Conference on Current SEC and PCAOB Developments, SEC staff
SEC staff indicated that they would not object to an accounting treatment under which the lender derecognizes the transferred crypto assets because it no longer controls them during the term of the loan. At the same time, the lender recognizes a crypto asset loan receivable, representing its right to receive the same type and quantity of crypto assets back from the borrower. The receivable is measured at inception and at subsequent reporting dates based on the fair value of the crypto assets lent, with changes in fair value recognized in net income. Because the arrangement exposes the lender to the borrower's credit risk, the lender also recognizes an allowance for credit losses, applying the principles of ASC 326. Under that model, the crypto asset is effectively replaced by a receivable.
On Aug. 19, 2026, however, the FASB tentatively moved in a different direction. For transactions involving crypto intangible assets that ultimately qualify as crypto asset lending transactions, the lender would not derecognize the crypto asset that has been lent. Instead, the asset would remain on the balance sheet under ASC 350-60 and be reclassified as an encumbered asset, measured at fair value, adjusted to reflect the borrower's credit risk.
The difference is fundamental.
Under the SEC staff approach, a transfer of 100 bitcoin would result in derecognition of the crypto asset and recognition of a crypto asset loan receivable. Under the FASB's tentative approach, if the transfer qualifies as a crypto asset lending transaction, the same 100 bitcoin would remain recognized as an encumbered asset.
The blockchain transfer is the same; what remains recognized on the balance sheet is not. That is why the current FASB discussion is about much more than a technical change in crypto accounting. It goes to a more fundamental question: "What does company A actually continue to hold after the transfer?"
The transaction label does not answer the question
The FASB has not yet definitively determined which transactions will qualify as crypto asset lending transactions. That is relevant for decentralized lending protocols and liquidity pools. A direct loan to an identifiable borrower fits relatively easily within the traditional lending model. A transfer to a protocol, however, may create a more complex legal and risk position. The same issue arises with wrapped tokens and receipt tokens. "Wrapped" suggests that the same asset has simply been given a different digital form. "Receipt token" suggests the token merely evidences something that continues to exist elsewhere unchanged. Neither label determines the accounting conclusion.
The accountant must begin with the rights and obligations before and after the transaction. Can company A demand the return of the same quantity of the same crypto asset? Against whom is that right enforceable? Is company A exposed to company B's credit risk? Does the token received represent a claim on one underlying crypto asset or a proportional interest in a changing pool? Can redemption be suspended or made subject to conditions?
Holding 100 ether directly is not the same as holding a receivable from a borrower for the return of 100 ether. Both differ from a proportional interest in a changing pool. Only after that bundle of rights and obligations has been identified can the appropriate U.S. GAAP model be determined.
That also explains why the FASB has tentatively decided to expand the scope of ASC 350-60 to include certain wrapped tokens and receipt tokens that give the holder the right to receive another crypto asset that itself falls within the scope of ASC 350-60. The expansion does not replace the rights analysis; it depends on it.
Derecognition does not come from the blockchain
For nonlending transfers of crypto intangible assets, the FASB has tentatively decided to continue applying the ASC 606 control model, supplemented by crypto-specific implementation guidance. But that is not the only possible transfer model. If a digital asset qualifies as a financial asset and falls within the scope of ASC 860, the transfer is instead accounted for under ASC 860.
That creates another important classification boundary. Two digital assets may sit in the same wallet, move on the same blockchain, and be transferred through technically similar transactions, yet one may be an asset within ASC 350-60 while the other is a financial asset. The applicable derecognition model may therefore differ before a single journal entry is recorded.
Technology does not determine which accounting guidance applies. The nature of the asset and the rights and obligations that remain after the transaction do.
What must happen before the journal entry
As crypto assets are increasingly lent, wrapped, staked, used as collateral or contributed to decentralized protocols, accounting firms will encounter this issue more often. The danger is moving too quickly from evidence of a blockchain transfer to a journal entry.
A more defensible approach begins by determining which rights have been transferred, retained and acquired, and which obligations have arisen. Only then can the accountant determine what asset remains for accounting purposes, identify the applicable recognition and derecognition model, and address measurement, presentation and disclosure.
On-chain evidence can establish precisely that 100 bitcoin moved from address A to address B. What it cannot establish, by itself, is whether the reporting entity still holds 100 bitcoin for accounting purposes, instead holds a receivable against a borrower, has acquired a wrapped asset, or now holds an interest in a changing pool.
That is the classification gap exposed by the FASB's current deliberations. An immutable ledger can record precisely that a crypto asset has moved, but it cannot determine whether derecognition follows.
The blockchain records the movement. U.S. GAAP determines what remains recognized on the balance sheet.
