Layer-2 Blockchain

A layer-2 blockchain is a network that operates on top of another blockchain, executing transactions on its own ledger and recording the results back to the network beneath it. The lower network is called the layer 1 or the base chain, and the numbering is a stack metaphor rather than a technical grade or a ranking. An SEC notice published in the Federal Register carries an exchange's description of one example, a network called Shibarium, as "a Layer-2 blockchain built on Ethereum, designed to reduce transaction costs and increase throughput."

The name is not a legal category, and it is worth being clear about that early. The phrase appears in federal materials only as description: it is not a defined term anywhere in the Code of Federal Regulations, and the Federal Register documents that use it are an exchange's rule filing and a summary of public comments on a tax rule. A network being described as a layer 2 therefore tells a reader something about how it is built, and nothing about who operates it, how it is supervised, or what recourse a holder has.

Two neighboring phrases are easy to run together. The same exchange filing uses "second-layer solutions" for the same idea, applying it to the Lightning Network on bitcoin. "Off-chain" is the one to watch, because it is used two different ways: a June 2026 Treasury proposed rule uses it for "ledger/book transactions made by third-party exchanges for which no evidence appears on the blockchain", which is not a layer 2 at all, since a layer 2 keeps a chain of its own.

The saving is arithmetic rather than invention. Treasury and the IRS, summarizing comments in the preamble to a digital-asset broker reporting rule, recorded the mechanism directly: "some distributed ledgers enable transactions to be aggregated on a layer 2 blockchain before being recorded as a single transaction on the primary distributed ledger." The base chain charges for the work it does, so recording one transaction instead of five hundred spreads a single base-chain cost across all of them. That is the whole economic argument. The layer 2 also charges for its own work, so the cost is reduced rather than removed, and the mechanics of what a base-chain fee is and how it is set belong with gas fees rather than here.

What a layer 2 inherits, and what it does not. The feature that distinguishes this arrangement from an exchange keeping a private internal tally is that the layer 2 records its results to the base chain, so the outcome is meant to be checkable against a public ledger rather than only against one company's books. What it does not inherit is the base chain's software, its operators or its history. While a balance sits on the layer 2, its correctness and its availability depend on the layer 2's own code and on whoever runs that network, in addition to the base chain underneath. A crypto token is already an exposure to two things at once, the token itself and the network it needs in order to exist and to move. Held on a layer 2 it becomes three: the token, the layer 2, and the base chain the layer 2 settles to.

Where the asset actually is, which is the practical point for a household. Because the layer 2 keeps its own record, moving an asset onto one is a change of location and not merely a change of speed. The balance is recorded on that network, so a block explorer or a wallet view pointed at the base chain alone will not report it, and a holder has to know which network a given balance is on in order to find it, move it or account for it. That is also why an exchange or a custodian may support an asset on the base chain and not on a particular layer 2, or the reverse. The question to ask about any crypto balance is which network it is on, not merely which asset it is.

Crossing between the two networks is done by software, and the usual limits on that software apply. Transfers in and out depend on program code running on each side, and the CFTC's own primer attaches a standing caution to code of that kind: a smart contract "is not necessarily 'smart'" and "may not be a legally binding contract." Nothing about a network being called a layer 2 changes what that code can and cannot guarantee.

The label has already been argued over in a rulemaking without ever acquiring a definition. In the comment round on the Treasury and IRS digital-asset broker reporting rule, one comment urged that persons who record transactions on these secondary networks "using sequencer software" be treated the way validators are treated for the purposes of the broker definition. Congress later disapproved that rule under the Congressional Review Act, so none of it is live law. The argument still shows what is at stake in the label: a question about who is doing the recording, and therefore who reports. Every tax question that follows from holding or moving an asset on one of these networks belongs with crypto taxes, including the basis and disposal questions a transfer raises.

A holder moves an asset from the base chain onto the layer 2 through software that records the departure on one network and the arrival on the other. From then on, transactions involving that balance are executed and recorded by the layer 2. Periodically the layer 2 records the state it has reached back to the base chain, which is where the aggregation happens. To return the asset to the base chain, the holder runs the process in reverse.

A hypothetical example, with invented figures used only to show the shape of the arithmetic. Suppose 500 transfers take place on a layer 2 during one interval, and the network then records the resulting state to the base chain as a single transaction costing $12.00 in base-chain fees. The base-chain cost attributable to each of the 500 transfers is $0.024 ($12.00 ÷ 500) rather than $12.00 each. Each of those transfers also pays the layer 2's own charge for doing the work, so $0.024 is the shared component and not the total a user pays.

The comparison that matters is against doing the same thing on the base chain, where each of the 500 transfers would have been its own recorded transaction with its own fee. That is the sense in which a layer 2 makes small transactions economic that would not otherwise be worth making. It is also the sense in which the saving is conditional: it depends on there being enough activity to share the base-chain cost across, and on the layer 2's own charge being small relative to what it saves.

Pros

• Transactions cost less and there is more capacity than on the base chain, which is the stated design purpose of the arrangement.
• Results are recorded back to a public base chain rather than only to a company's internal books, so the outcome is meant to be checkable independently.
• Small transactions that would be uneconomic on a busy base chain become practical, because the base-chain cost is shared rather than paid per transfer.

Cons

• The arrangement adds a second network, with its own code and its own operators, between the holder and the base chain, and a balance there depends on both.
• A balance on a layer 2 is not a base-chain balance. Tools and services that only look at the base chain will not see it, and support for a given network varies by platform.
• Moving assets in and out relies on program code, and the limits of what such code guarantees apply here as anywhere else.
• No federal rule defines the term, so describing a network as a layer 2 carries no legal or regulatory meaning and no set of requirements.
• The cost saving is conditional on activity and on the layer 2's own charges, so it is a design goal rather than a promise about any particular transfer.