DeFi Contract Requests

Add compound cUSDTv3 token

Proper classification and cost basis handling of Pickle Finance gauge transactions when LP tokens are deposited and withdrawn. Blockchain Explorer Link (Withdrawal): https://etherscan.io/tx/0xa0a66b332d978178d0ff137647c4590bdbd78da19c85bb5863b8c5d51b8d88a9

What is the issue? Transactions using the "Increase Liquidity" function for PancakeSwap v3 on-chain is displayed as a send with multiple assets instead of a liquidity action. This also prevents the category from being manually updated to "Add liquidity." Who is affected? Users reviewing PancakeSwap v3 on-chain transactions that use the "Increase Liquidity" function are affected. What is the workaround? No workaround available. Users may upvote this post to remain notified of updates. Keywords: pancakeswap, liquidity, transaction categorization, manual override, v3

SKALE withdrawBounty staking rewards on Ethereum are being imported as generic “Receive” transactions instead of “Staking reward.” Function: withdrawBounty(uint256 validatorId, address to) MethodID: 0x76d07f6b

What is the issue? Aerodrome Slipstream LP position NFT transactions on Base are classified as trades instead of liquidity lifecycle events such as mint, burn, and transfer. This results in incorrect realized loss calculations. Who is affected? Users interacting with Aerodrome LP positions on Base. What is the workaround? No workaround available. Keywords: base, aerodrome, lp positions, misclassification, defi

Network Name: MegaETH RPC: rpc.megaeth.com ChainID: 4326 Explore: https://mega.etherscan.io/ Currency Symbol: ETH

What is the issue? ROOK token claim transactions are currently categorized as Receives instead of being classified as Reward which leads to incorrect transaction labeling and reporting. Who is affected? Users who claim ROOK tokens from the official ROOK claim contract on Ethereum. What is the workaround? Users can manually reclassify the transaction as a Reward or Airdrop to ensure accurate reporting. Keywords: ROOK token, claim transaction, receive vs reward, airdrop classification, Ethereum claims

Function: withdrawToken(uint256 tokenId, address to, bool withdrawBalances, bytes data) | Method ID: 0x9001a1dd | Contract: 0x5411894842e610c4d0f6ed4c232da689400f94a1 | Transaction Type: Withdraw

Function: adjustTrove(address _asset, uint256 _assetSent, uint256 _maxFeePercentage, uint256 _collWithdrawal, uint256 _VSTChange, bool _isDebtIncrease, address _upperHint, address _lowerHint) | Method ID: 0x74399021 | Contract: 0x3eedf348919d130954929d4ff62d626f26adbfa2 | Transaction Type: Withdraw

What is being requested? Support for accurately reflecting LP tokens received when adding liquidity on Merchantmoe V2. Currently, these tokens are missing from the transaction data. Why is this needed? When LP tokens are not recorded during the Add Liquidity event, it leads to an incorrect or missing cost basis. This results in inaccurate accounting and tax calculations when liquidity is later removed. Keywords: Merchantmoe V2, LP tokens, add liquidity, missing tokens, DeFi cost basis