DeFi Contract Requests

Function: stake(uint256 amount) MethodID: 0xa694fc3a YFII.finance : yearn

Solayer unstake + claim process: Claim

The following Remove Liquidity transaction is showing as a Trade in CoinTracker. 4DaodmLTJZpzVSHfnjDb72us5eMKVpBNJSDNMZY3ehcVP9XvgMYj57NsjkFwNnc9pB3mUzXwq8QLTkZmyatCTcn6

Solayer unstake + claim process: Unstake

Orca Whirlpool Position tokens are not properly tracked as a DeFi Liquidity NFT on the Solana chain, token name: Orca Whirlpool Position token symbol: OWP token image: https://position-nft.orca.so/static-gen3-image.png

Raydium Concentrated Liquidity tokens are not properly tracked as a DeFi Liquidity NFT on the Solana chain, token name: Raydium Concentrated Liquidity token symbol: RCL token image: https://img-v1.raydium.io/share/ea1ef711-652b-422b-a593-04426f8f2a04.jpg

Function: claim(address owner) | Method ID: 0x1e83409a | Contract: 0xce4dcc5028588377e279255c0335effe2d7ab72a

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