> ## Content Index
> Fetch the complete content index at: https://altcoininvestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How To Reconstruct Tax Records When Pool Drops Mid-Year
- URL: https://altcoininvestor.com/recover-yield-history-pool-stopped-tracking/
- Published: 2026-11-21T18:04:07.000Z
- Updated: 2026-11-21T18:04:08.000Z
- Description: When Sky STUSDS, Uniswap WETH-USDT, or Curve msETH-WETH vanish from tracking mid-year, you need position history for taxes. Here is the on-chain recovery protocol.
- Author: Lana Sparrow
- Tags: Crypto Tax Tips, DeFi Yield Strategies, Stablecoin Income, Intermediate, Passive Income

## What You Will Accomplish

![DeFi protocol logos above incomplete transaction records showing data gaps from pool discontinuation](https://cdn.getmidnight.com/13448471d89a9cd8d7f71026a0334ec8/2026/11/crypto-tax-record-reconstruction-after-h2-1.webp)

When a liquidity pool drops from yield tracking platforms mid-tax-year, you lose the transaction history needed to file accurate returns. Missing six months of yield records on a $300,000 position forces a choice: pay tax on estimated maximum income and overpay $3,000 to $8,000, or file incomplete records and face IRS inquiry. Neither is acceptable.

This week, three pools dropped from major tracking platforms: Sky STUSDS, Uniswap WETH-USDT, and Curve msETH-WETH. Combined TVL across these pools totals $248 million. The tracking gap creates immediate tax record problems for liquidity providers who need complete position history before filing deadline.

This protocol reconstructs complete yield history using Etherscan transaction logs, protocol-specific subgraphs on The Graph, and block-by-block balance queries. You will build a CSV export matching common tax software import formats. The process takes two to four hours depending on transaction volume. No specialized blockchain development knowledge required.

Prerequisites: you need the wallet address that held LP tokens, the specific pool contract address, and approximate dates you entered and exited the position. You need an Etherscan API key for high-volume wallets. Free tier provides 100,000 queries per month across Ethereum, Polygon, Arbitrum, Base, BSC, and Optimism.

## Protocol-Specific Recovery Methods By Pool Type

![Etherscan API transaction list displaying blockchain event logs and timestamps for liquidity positions](https://cdn.getmidnight.com/13448471d89a9cd8d7f71026a0334ec8/2026/11/crypto-tax-record-reconstruction-after-h2-2.webp)

Each DeFi protocol writes position data to the blockchain differently. Sky's lending pools, Uniswap v3 concentrated liquidity, and Curve's automated market maker all emit different event signatures. The recovery method depends on which contract standard your pool uses.

Sky STUSDS positions involve ERC-4626 vault shares. When you deposit USDS, you receive stUSDS tokens that accrue yield through rebasing. The taxable events are deposit (disposal of USDS), withdrawal (disposal of stUSDS), and ongoing yield accrual. Sky's subgraph tracks balance snapshots and yield distribution events.

Uniswap WETH-USDT uses the Uniswap v3 liquidity position NFT standard. Each position is an NFT with specific price range bounds. The pool currently holds $59.11 million TVL and operates across three fee tiers: 0.05%, 0.30%, and 1%. This is the most liquid USDT pair on Uniswap v3, with over $200 million in daily volume. Your taxable events include minting the position NFT, collecting fees, adjusting liquidity, and burning the NFT. Fee collection happens separately from principal and must be tracked independently.

Curve msETH-WETH is a Curve v2 crypto pool. The pool ranked third in Curve volumes at $73.4 million with $29.4K in fees during recent reporting. It offered 5.2% yield through CRV emissions and trading fees. As of recent data, the pool shows $11.2 million TVL with 41.7K CRV emissions, though the pool has been unwinding with negative $7.48 million TVL change. Curve positions involve LP token minting, gauge staking for CRV rewards, fee accrual within the LP token, and claim events for external rewards.

The same token pair can exist across multiple fee tiers with different addresses and different yield profiles. You must identify the exact contract address you deployed liquidity to. Pool contract addresses are immutable. If tracking platforms consolidated multiple fee tiers into one display line, you need to separate them in your reconstruction.

When you're trying to [earn passive income from stablecoins](https://altcoininvestor.com/how-to-earn-passive-income-stablecoins-2026/), keeping accurate records of positions like USDT and USDC pools is essential for both tax compliance and portfolio management.

## Etherscan Transaction History Query Method

![Spreadsheet showing block-by-block token balance reconstruction with timestamps and accrued yield data](https://cdn.getmidnight.com/13448471d89a9cd8d7f71026a0334ec8/2026/11/crypto-tax-record-reconstruction-after-h2-3.webp)

Start with the Etherscan API txlist endpoint. This returns all external transactions for a given address within a specified block range. Navigate to the Etherscan API documentation and generate a free API key if you don't have one. The key works across all Etherscan-compatible block explorers.

Construct your query URL with these parameters: your wallet address, start block number, end block number, sort order, and API key. If you don't know exact block numbers, use the Etherscan block explorer date-to-block tool. Tax year 2026 runs from block 18,900,000 (approximate January 1) to block 21,400,000 (approximate December 31) on Ethereum mainnet. Adjust for the actual chain your pool operates on.

The response returns JSON with transaction hash, block number, timestamp, from address, to address, value, and gas used. Filter transactions where the to address matches your pool contract address. These are your deposit and withdrawal transactions. Each transaction hash links to full event logs.

Query the transaction receipt using eth\_getTransactionReceipt via Etherscan's API or any Ethereum RPC provider. The receipt contains event logs emitted by the pool contract during execution. Look for Transfer events with your address as a parameter. For Uniswap v3, look for IncreaseLiquidity, DecreaseLiquidity, and Collect events tied to your position NFT token ID. For Curve, look for AddLiquidity, RemoveLiquidity, and TokenExchange events.

Transaction queries require specifying starting block number and sort order. Use ascending sort for oldest transactions first when building chronological history. Large address histories exceed single API response limits. The API returns a maximum of 10,000 transactions per query. If your wallet has high activity, you must paginate by incrementing the start block parameter across multiple queries.

Download each transaction receipt and extract the decoded event parameters. Event logs are emitted in hex format. Etherscan's web interface decodes them automatically. If you're using the API directly, you need the contract ABI to decode logs. Contract ABIs are available through Etherscan's contract page or the getabi API endpoint. Match the event signature hash against the ABI to identify which event fired and extract the parameter values.

For pools that dropped tracking, it's critical to follow the same systematic approach outlined in [how to prioritize when multiple pools stop tracking](https://altcoininvestor.com/multiple-yield-pools-disappeared-same-day/), ensuring you're addressing the highest-dollar positions first.

## Subgraph Query Method For Historical Pool State

The Graph network hosts protocol-specific subgraphs that index blockchain data into queryable databases. Uniswap, Curve, and most major DeFi protocols maintain official subgraphs. These subgraphs aggregate position state, historical balances, fee accruals, and reward distributions in a single query endpoint.

Navigate to The Graph Explorer at thegraph.com/explorer and search for the protocol name. Uniswap v3 has an official subgraph maintained by Uniswap Labs. Curve has a Messari-maintained subgraph using the standardized schema. Sky's subgraph may be listed under MakerDAO or Sky Protocol depending on deployment timing.

Each subgraph has a query URL displayed at the top of its Explorer page. This is a GraphQL endpoint. You send POST requests with GraphQL queries in the body. The Graph supports time-travel queries by specifying block number, allowing you to retrieve entity state at any historical point.

For Uniswap v3 WETH-USDT positions, query the Position entity filtered by your wallet address. The query returns position ID, liquidity amount, token0 and token1 deposited amounts, fees earned in token0 and token1, and tick range. The subgraph tracks fee accrual over time through position snapshots. Query positionSnapshots with your position ID to get daily or hourly balance and fee data.

Here is a sample GraphQL query for Uniswap v3 position history:

{  
 positions(where: {owner: "0xYourAddress"}) {  
 id  
 liquidity  
 token0 {symbol}  
 token1 {symbol}  
 depositedToken0  
 depositedToken1  
 collectedFeesToken0  
 collectedFeesToken1  
 transaction {timestamp}  
 }  
}  

For Curve msETH-WETH, query the LiquidityPool entity for the specific pool address, then query LiquidityPoolDailySnapshot filtered by your wallet to retrieve daily balance and reward distribution. Curve pools emit RewardPaid events for CRV distributions that the subgraph indexes. Cross-reference these reward events against your wallet's claim transactions.

Subgraph queries return data in JSON format. Parse the response to extract deposit amounts, withdrawal amounts, fee totals, and reward claim amounts. The timestamp field gives you UTC unix timestamp for each event. Convert this to human-readable date for your tax records.

Subgraph deprecation risk is real. Individual protocol subgraphs can be sunset or migrated to different endpoints. Before writing complex queries, verify the subgraph is actively syncing by checking the latest indexed block number displayed on the Explorer page. If the subgraph is months behind chain head, it won't have recent data. In that case, fall back to direct transaction log queries.

Messari-maintained subgraphs use a unified schema across protocol types, making queries more portable. The standardized schema is documented in Messari's subgraph GitHub repository. If the official protocol subgraph is deprecated, search for Messari's version as a backup data source.

## Block-By-Block Balance Reconstruction For Yield Accrual

Some yield accrues passively without explicit claim transactions. Rebasing tokens like stUSDS increase your balance over time. Curve LP tokens accrue trading fees internally without external events. To calculate taxable income, you need to know your balance at the start and end of each reporting period, plus the fair market value at each measurement point.

Use an archive node RPC provider to query historical balance at specific block heights. Alchemy, Infura, and QuickNode offer archive node access. The eth\_call method allows you to call contract view functions at historical blocks. For ERC-20 LP tokens, call balanceOf(yourAddress) at the block corresponding to each month-end or quarter-end.

Identify the block numbers for your reporting intervals. For monthly income reporting, find the block closest to 23:59:59 UTC on the last day of each month. Use Etherscan's block search or a date-to-block API. Query your LP token balance at each of these blocks. The difference in balance between consecutive intervals represents yield accrued during that period.

For impermanent loss calculation, you also need the reserve balances of the pool itself at each interval. Query the pool contract's reserves using getReserves() or balances() depending on the protocol. This gives you the token ratio at each point. Compare the ratio at entry versus exit to calculate impermanent loss impact.

Fair market value at each timestamp determines income amount in USD terms. Use CoinGecko or CryptoCompare historical price API to retrieve token prices at each block timestamp. Multiply your accrued token quantity by the price at that timestamp to calculate income. For tax purposes, income is recognized when you have dominion and control, which for liquid DeFi positions is generally the moment tokens accrue to your wallet.

Automated tax software often misses IL events. When you withdraw liquidity from a pool, you receive different token quantities than you deposited. The difference in token composition is a taxable swap, separate from the yield income. Your cost basis in the original tokens carries forward. The tokens you receive back have a new cost basis equal to their fair market value at withdrawal.

If you're tracking [cryptocurrency taxes](https://altcoininvestor.com/cryptocurrency-taxes/) properly, understanding that adding and removing liquidity counts as a disposal event is critical to avoiding incorrect filings.

## Building The CSV Export For Tax Software Import

Once you've collected all transaction data, event logs, and balance snapshots, consolidate into a structured format. Most crypto tax software accepts CSV imports with specific column schemas. CoinTracker, Koinly, TokenTax, and CryptoTaxCalculator all support custom CSV uploads.

Your CSV should include these columns: Transaction Hash, Block Number, UTC Timestamp, Pool Address, Asset In Quantity, Asset In Symbol, Asset Out Quantity, Asset Out Symbol, FMV USD at Transaction Time, Event Type, and Cost Basis Assignment Method. Event Type should distinguish Deposit, Withdraw, Fee Claim, Reward Claim, and LP Token Transfer.

For Uniswap v3 fee collection events, create separate rows for each Collect transaction. Mark these as income events. The fee tokens are new assets with cost basis equal to their FMV at collection time. When you later sell those fee tokens, you'll calculate capital gain or loss from that basis.

For Curve CRV rewards, each claim transaction is an income event. The CRV tokens have cost basis equal to their price at claim time. If you staked those CRV tokens for veCRV, that's a separate transaction with the CRV as asset out and veCRV as asset in. The veCRV has the same cost basis as the CRV you locked.

For Sky stUSDS, calculate the yield accrued each month by comparing balance snapshots. Create a synthetic transaction row for each month-end showing the increase in stUSDS balance. Mark this as income. The incremental tokens have cost basis equal to the USDS price at that month-end, which is typically $1.00 for stablecoins but should be verified against actual market price.

Cost basis assignment method matters for positions with multiple entries. FIFO is default in the US unless you elect specific identification. If you added liquidity to the same pool three times at different prices, your withdrawal consumes the earliest position first under FIFO. Mark your cost basis method in the CSV so your tax software applies the correct calculation.

Include the transaction hash for every row. This is your audit trail. If the IRS questions a reported figure, you provide the transaction hash as proof. The blockchain is immutable. The transaction receipt is verifiable by anyone with an Ethereum node. This is stronger evidence than a brokerage statement.

Some pools distribute rewards in non-standard tokens. The msETH-WETH pool offers CRV emissions. If you don't have historical price data for an obscure reward token, use a DEX subgraph to query the token's pool price at the reward distribution block. Uniswap and Curve subgraphs index token prices derived from their pools. Query the token's most liquid pool at the specific block to get a verifiable price.

## Common Failure Modes And How To Avoid Them

The most common error is using the wrong contract address. If you query transaction history for a different fee tier of the same token pair, you'll see zero deposits and conclude your position vanished. Verify the exact contract address from your wallet's transaction history. Look at the To address on the transaction where you originally added liquidity. That is your pool contract.

Second failure mode: missing internal transactions. Some protocols use router contracts that forward your deposit to the pool in an internal transaction. Etherscan's default txlist endpoint only shows external transactions. Query txlistinternal separately to catch internal transfers. This is common with aggregator protocols and certain Curve factory pools.

Third failure mode: incorrect event decoding. If you don't have the correct ABI, you'll see raw hex logs but won't know which event fired or what the parameters mean. Always download the verified contract ABI from Etherscan. If the contract isn't verified, you need to find the ABI from the protocol's GitHub repository or documentation.

Fourth failure mode: querying the wrong chain. If you provided liquidity on Arbitrum but query Ethereum mainnet Etherscan, you'll find nothing. Verify which network the pool operates on. Use the appropriate block explorer: arbiscan.io for Arbitrum, polygonscan.com for Polygon, basescan.org for Base. Your Etherscan API key works across all of them.

Fifth failure mode: ignoring LP token transfers between wallets. If you transferred LP tokens from a hot wallet to cold storage mid-year, the position history is split across two addresses. Query both addresses and merge the data chronologically. The transfer itself is not a taxable event if both wallets are your own, but you must document the transfer to prove continuous ownership.

Sixth failure mode: not accounting for bridge transactions. If you bridged assets from Ethereum to Arbitrum, deployed them in a pool, then bridged back, you have taxable disposal events at both bridge crossings. Bridging is treated as disposal of the origin-chain token and acquisition of the destination-chain token. Query bridge contract events on both chains to capture the full flow.

When facing [pool disappearances from yield trackers](https://altcoininvestor.com/uniswap-pool-disappeared-from-tracker/), it's essential to determine quickly whether the issue is a data glitch or actual liquidity crisis before you spend hours reconstructing history.

## What To Do After Reconstruction

Once you've built your CSV, import it into your crypto tax software. Run the tax calculation to verify total income and capital gains match your expectations. Compare the software's calculated figures against your manual spot checks. If there's a discrepancy larger than 5%, review the specific transactions flagged by the software.

Export the final tax report and review the Schedule 1 and Form 8949 line items. Each liquidity pool transaction should appear as a separate line on Form 8949 if it involved a taxable swap. Yield income should sum correctly on Schedule 1 as Other Income. If your software doesn't break out DeFi yield separately, add a statement to your return explaining the source and providing aggregate totals by protocol.

Keep the full CSV file and all transaction receipts in your tax records. The IRS has three years from filing date to audit, six years if they suspect underreporting over 25%. In practice, crypto audits sometimes stretch longer due to complexity. Retain your records for seven years minimum. Store them off your local machine. Encrypted cloud backup is sufficient.

If you discover that reconstructing history reveals you owe substantially more than estimated, consult a tax professional before filing. Underreporting penalties are steep. If you proactively file an amended return or accurate original return with payment, penalties are lower than if the IRS discovers the gap first. A forensic record showing you attempted good-faith reconstruction is valuable defense.

Set up monitoring to prevent future gaps. Use a portfolio tracker that supports multiple data sources. When one source drops a pool, another may still track it. Zapper, DeBank, and Zerion aggregate data differently. Run parallel tracking. Export your position history monthly, not just at year-end. Monthly exports give you redundant data sources if one tracker fails.

For high-value positions over $100,000, consider running your own Graph node and indexing the specific subgraphs you depend on. This costs approximately $200 per month in infrastructure but guarantees you control the data source. If the official subgraph gets deprecated, your node continues indexing. This is overkill for most users but reasonable for six-figure positions.

For detailed context on when pools like [Tether (USDT)](https://altcoininvestor.com/usdt/) pools disappear from trackers, understanding the underlying asset's stability and market behavior is part of proper diligence.

## Verification And Audit Defense

The strength of blockchain-based tax records is verifiability. Every figure you report can be traced to a specific transaction hash on a public ledger. If audited, you provide the transaction hash. The IRS or their contractors can verify it against their own blockchain analytics tools.

The IRS uses Chainalysis, Elliptic, and TRM Labs for blockchain surveillance. These firms track DeFi activity and generate reports for tax enforcement. Your reconstructed history should align with what their tools see. If you omit a transaction, their tools will flag it. If you report it accurately with correct timestamp and amounts, their tools will confirm it.

When you file, include a statement describing your reconstruction methodology. State that tracking platforms dropped coverage mid-year. State that you reconstructed history using Etherscan transaction logs and protocol subgraphs. Provide links to the specific API endpoints and subgraph URLs you queried. This shows good faith effort and makes it clear you're working from primary sources, not estimates.

If you're uncertain about treatment of a specific transaction type, disclose the uncertainty in your filing statement. The IRS is more lenient when taxpayers disclose ambiguous treatment than when they omit transactions entirely. Disclosure doesn't prevent assessment, but it reduces penalties.

For [liquidity pool staking](https://altcoininvestor.com/liquidity-pool-staking/) positions, understanding the mechanics of rewards and fees is essential to categorizing income correctly during reconstruction.

## The Takeaway

When Sky STUSDS, Uniswap WETH-USDT, or Curve msETH-WETH drop from tracking mid-year, you have a two-to-four-hour window to reconstruct complete position history before tax filing deadlines create pressure. Use Etherscan transaction logs to capture deposit and withdrawal events, protocol subgraphs to aggregate fee and reward accrual, and block-by-block balance queries to document passive yield. Build a CSV export with transaction hashes as audit trail. The blockchain is immutable. Your records are verifiable. Missing documentation costs $3,000 to $8,000 in overpaid tax or exposes you to IRS inquiry. Accurate reconstruction from on-chain sources eliminates both risks.

The pattern repeats every tax season. Tracking platforms deprioritize pools with declining TVL. Users discover the gap in March when preparing returns. By then, panic leads to estimated filings. Set up redundant tracking now. Export position history monthly. When a pool drops from one tracker, you already have the data.

## Frequently Asked Questions

### How long does it take to reconstruct complete yield history for a dropped pool?

Full reconstruction takes two to four hours depending on transaction volume. Wallets with under 100 transactions can be reconstructed in 90 minutes using Etherscan transaction logs and protocol subgraphs. High-activity wallets with over 500 transactions require pagination across multiple API queries and may take four hours. Set aside time before tax filing deadlines to avoid rushed estimates.

### Do I need blockchain development skills to query Etherscan and subgraphs?

No specialized development knowledge is required. Etherscan API returns data in JSON format accessible through web browser or simple scripts. The Graph subgraphs use GraphQL, which is human-readable query language. You can test queries directly in the browser-based Graph Explorer interface. Basic familiarity with CSV spreadsheets and API concepts is sufficient. Most reconstruction can be done through Etherscan's web interface without writing code.

### What happens if the protocol subgraph has been deprecated?

If the official subgraph is deprecated, fall back to direct transaction log queries using Etherscan API. Query txlist and txlistinternal endpoints for your wallet, filter transactions by pool contract address, then decode event logs using the contract ABI. Messari maintains standardized subgraphs for major protocols as backup data sources. Check The Graph Explorer for alternative subgraphs indexing the same protocol. Archive RPC nodes provide third fallback through historical balance queries.

### How do I prove my reconstructed records are accurate if audited?

Every transaction hash you report is verifiable on the public blockchain. Include transaction hashes in your CSV export and filing statement. The IRS uses Chainalysis and similar tools to verify blockchain data. When you cite specific transaction hashes with block numbers and timestamps, their tools will confirm the same figures. Keep the full query methodology documented: which API endpoints, which subgraph URLs, which block ranges you queried. This documentation demonstrates good faith reconstruction effort.

### Are Uniswap v3 fee collections taxed differently than Curve CRV rewards?

Both are ordinary income when received, but mechanics differ. Uniswap v3 fees accumulate in the pool until you explicitly collect them through a Collect transaction. That transaction triggers taxable income at the token values on collection date. Curve CRV rewards are distributed through gauge claim transactions. Each claim is income at CRV's price that day. For tax purposes, both are reported as Other Income on Schedule 1\. The tokens you receive have cost basis equal to FMV at receipt for future capital gains calculations.

Tool mentioned above

Koinly

Koinly imports from 800+ exchanges and wallets and handles the DeFi cases most tools get wrong - rebasing tokens, LP positions, staking rewards.

[Try Koinly](https://koinly.io/?via=F6E2E35A&utm%5Fsource=affiliate) 

We may earn a commission if you sign up through this link, at no cost to you. It does not change what gets recommended.

The Weekly Yield Report

You just reconstructed six months of missing yield data from three different pool types using on-chain sources. Those pools will drop from tracking again next quarter. That documentation protocol becomes your recurring workflow.

Every Thursday: where crypto yield actually is - stablecoins, liquid staking and DeFi lending, with the risk named next to the rate and what changed since last week.

[Get it free every Thursday](#/portal/signup) 

Free. No trade calls, no allocations, no hype. Unsubscribe in one click.