How to Track DeFi Positions Across Multiple Chains Using Rabby Wallet?

Multi-Chain Address Mapping

1. Rabby Wallet automatically detects and indexes wallet addresses across Ethereum, BSC, Polygon, Arbitrum, Optimism, Base, and zkSync Era upon first connection.

2. Each chain maintains its own independent nonce, balance, and transaction history—Rabby aggregates these without merging state or assuming cross-chain identity equivalence.

3. When a user connects to a dApp on Arbitrum, Rabby injects only the Arbitrum-specific address and signature context, preserving isolation from Ethereum Mainnet keys.

4. Contract deployments on different chains generate distinct addresses—even identical bytecode yields different contract addresses due to chain-specific salt and deployer nonce derivation.

DeFi Position Discovery Mechanism

1. Rabby scans on-chain balances for ERC-20 tokens, ERC-721 NFTs, and LP tokens held directly in the EOA, then cross-references those token contracts against known DeFi protocols’ registries.

2. For liquidity positions, it identifies staking contracts by parsing transfer events emitted during deposit and withdrawal actions, matching them with protocol-specific ABI signatures.

3. It queries subgraphs hosted by The Graph for Uniswap V3 positions, Aave v3 health factors, and Compound v2 borrow balances—each subgraph is chain-scoped and versioned.

4. Rabby does not rely on centralized APIs for position reconstruction; all data originates from public RPC endpoints and verified contract ABIs.

Token Balance Normalization

1. Rabby applies chain-aware decimals handling: USDC on Ethereum uses 6 decimals, while USDC.e on Avalanche uses 6 and Bridged USDC on Polygon uses 6—yet all display as unified “USDC” in the UI with correct scaling.

2. Native tokens like ETH, BNB, MATIC, and OP are auto-detected per chain and labeled with their canonical symbol—not generic “gas tokens”.

3. Wrapped assets such as wETH, wBTC, and renBTC are identified via standardized contract names and verified proxy patterns, preventing misattribution of bridged assets.

4. Rabby excludes tokens flagged as honeypots or blacklisted by community-maintained lists like TokenSniffer and CertiK’s threat database.

Transaction Context Enrichment

1. Every transaction displayed in Rabby’s activity tab includes decoded function calls, parameter values, and human-readable intent labels—e.g., “Deposit 0.87 WETH into Aave v3 (Ethereum)”.

2. Cross-chain bridge actions trigger dual-entry logging: one record on source chain showing “Initiate Transfer”, another on destination chain showing “Complete Receive”, linked via message hash.

3. Rabby parses logs from event emitters like Transfer, Deposit, Mint, and Staked to infer position changes without requiring user input.

4. It recognizes permissionless vault interactions (e.g., Yearn v3 vault deposits) by matching calldata patterns against open-sourced vault ABI templates.

Frequently Asked Questions

Q1: Does Rabby store private keys or seed phrases on its servers?No. Rabby is a non-custodial browser extension. All key material remains inside the user’s local browser storage and never transmits to any remote endpoint.

Q2: Can Rabby track positions inside smart contract wallets like Safe or Argent?Yes—if the contract wallet exposes standard balance and event interfaces, Rabby reads from those on-chain sources. It does not support arbitrary delegatecall-based logic unless explicitly whitelisted via verified ABI.

Q3: Why does my staking position on Curve appear under “Unknown Protocol” on Fantom?This occurs when the Fantom deployment of the Curve gauge contract lacks indexed subgraph support or has divergent event signatures from Ethereum Mainnet—Rabby defaults to generic labeling until verification completes.

Q4: How does Rabby handle rebase tokens like AMPL or YFI when calculating portfolio value?Rabby fetches real-time supply-adjusted balances from on-chain rebase trackers and multiplies them against price feeds sourced from Chainlink or Redstone oracles—no static decimal assumptions are applied.