How to Track Lightning Payments for Tax Season Using Clams

Lightning Network makes Bitcoin payments fast and cheap, but come tax season, that speed creates a documentation headache. Every payment you send, every routing fee you earn, and every channel open or close is potentially a taxable event under current IRS rules. Tracking it all manually borders on impossible.

Clams offers a way to automate this process by syncing directly with your Lightning node and converting raw activity into categorized, audit-ready records. Here's how to set it up and what you need to know about Lightning tax reporting in 2026.

Why Lightning Transactions Need Special Attention

The IRS treats Bitcoin as property, not currency. That means using bitcoin to pay for goods or services triggers a taxable disposition, just like selling stock. You need to track your cost basis (what you paid for that bitcoin), the fair market value at the moment you spent it, and calculate any capital gain or loss.

Lightning adds layers of complexity. Your node might handle:

• Invoices and payments: Outgoing payments for purchases, incoming payments for services rendered
• Routing fees: Small amounts of satoshis earned by forwarding other users' payments
• Channel opens and closes: On-chain transactions that lock and unlock funds, each with different tax implications depending on close type (cooperative, force, or breach)
• Rebalancing: Moving liquidity between channels, which may or may not be taxable depending on how you categorize it

According to Clams' documentation, proper Lightning accounting requires distinguishing between all these event types. Lumping them together invites problems if you're ever audited.

Setting Up Clams With Your Lightning Node

Clams supports direct integration with LND and Core Lightning. The connection pulls your node's complete transaction history and categorizes events automatically.

Step 1: Create Your Clams Account and Connect Your Node

Start by creating an account at Clams. From the dashboard, navigate to the integrations section and select your node implementation (LND or Core Lightning).

For LND, you'll need to provide connection credentials, typically your node's address and a macaroon file with read permissions. Core Lightning users connect via a similar process using their node's RPC credentials.

Clams' sync pulls historical data, so even if you're connecting mid-year, your past transactions should populate.

Step 2: Review Automatic Transaction Categories

Once synced, Clams categorizes your Lightning activity into distinct buckets:

• Routing revenue: Fees earned from forwarding payments. This is taxable income, valued at the USD equivalent when received.
• Channel opens: On-chain transactions that fund new channels. These aren't immediately taxable but establish basis.
• Channel closes: The tax treatment depends on whether you received more or less satoshis than your basis in that channel, and whether it was cooperative, forced, or a breach remedy.
• Payments sent/received: Each outgoing payment is a potential disposition; incoming payments for services are income.
• Rebalancing: Internal liquidity moves. Clams helps flag these so they're not incorrectly treated as sales or income.

Review the automatic categorization and adjust any transactions that were miscategorized. For example, a payment to yourself via a circular route for rebalancing shouldn't be treated the same as a payment to a merchant.

Step 3: Assign Cost Basis Methods

The IRS requires you to track basis, meaning what you originally paid (in USD) for the bitcoin you're spending or selling. Clams supports standard accounting methods like FIFO (first in, first out), LIFO (last in, first out), and specific identification.

Choose the method that applies to your situation. If you're unsure, FIFO is the most commonly used default, but talk to a tax professional if your holdings are substantial.

Step 4: Connect On-Chain Activity

Your Lightning activity doesn't exist in isolation. Channel funding comes from on-chain wallets, and channel closes return funds on-chain. Clams also integrates with on-chain wallets to create a unified view.

Connect your primary Bitcoin wallets so Clams can trace the full lifecycle: on-chain funds opening a channel, Lightning activity within that channel, and on-chain settlement when it closes. This prevents orphaned transactions that create accounting gaps.

Step 5: Generate Tax Reports

Once your data is synced and categorized, Clams can generate reports showing capital gains and losses, income from routing or services, and transaction-level detail the IRS expects.

The IRS guidance specifies that records should include the asset type, date and time of each transaction, number of units, fair market value in USD, and your basis. Clams structures its exports to meet these requirements.

What the IRS Expects in 2026

Broker reporting requirements have been phasing in. As of January 1, 2025, brokers began reporting gross proceeds on Form 1099-DA. Basis reporting for certain transactions starts in 2026.

This matters because the IRS is building infrastructure to cross-reference what you report against what brokers report. Self-custody Lightning nodes aren't brokers, so you won't receive a 1099-DA for your routing fees. But that doesn't mean the income isn't taxable. It means the responsibility for accurate reporting falls entirely on you.

Common Pitfalls to Avoid

Ignoring small routing fees: Even tiny amounts add up and constitute taxable income. If you earned 50,000 satoshis in routing fees across the year, that's income valued at whatever USD equivalent prevailed when each fee was earned.

Treating rebalancing as sales: Circular rebalancing routes move your own liquidity around. They shouldn't generate capital gains if structured correctly, but poor record-keeping can make them look like sales.

Forgetting channel close timing: A channel that appreciates in bitcoin value between open and close generates a capital gain. If the channel exists for over a year, that gain may qualify for long-term capital gains rates.

Missing the connection between on-chain and Lightning: If you can't trace where channel funding came from, you can't prove your basis. Clams' unified approach helps prevent this.

The Bigger Picture

Lightning's growth makes this more urgent, not less. Vendor-reported figures (from Clams' own blog) suggest Lightning volume grew substantially in 2025, though independent verification of specific numbers is difficult. What's clear is that more transactions flowing through Lightning means more taxable events requiring documentation.

Software like Clams doesn't eliminate the underlying complexity of treating bitcoin as property. But it does automate the tedious work of logging every transaction, converting to USD at the right timestamp, and categorizing activity correctly. For anyone running a Lightning node with meaningful activity, that automation isn't optional; it's the difference between being audit-ready and scrambling.

Start the sync early. Waiting until April guarantees frustration.