LiquidLoans / Fetch Oracle

The problem

DeFi interfaces have to stay correct under constantly changing on-chain state: prices, positions, and transaction status can all shift mid-interaction. The frontend has to represent that state faithfully or users lose money.

What I owned

• React/TypeScript interfaces for borrowing, Stability Pool interactions, staking, farming, redemptions and liquidations
• Wallet integrations, ERC-20 balances, approvals, transactions and transaction-state handling
• Fetch Oracle interfaces: oracle reporting, staking/reporting APR, disputes, voting and rewards
• Multi-chain deployment work, including adapting existing DeFi flows to an additional chain
• Testnet/configuration migration work and developer-facing integration material

Technical challenges

• Keeping wallet and transaction state consistent through pending, confirmed, and failed states across multiple chains
• Debugging RPC limits, chain-sync issues and application-state drift under production load
• Representing oracle pricing and staking/reward data accurately in real time

Engineering decisions

• wagmi and ethers for wallet/contract interaction, chosen for type-safe, composable state handling
• GraphQL/Apollo against subgraphs for indexed on-chain data instead of querying contracts directly for every read
• Careful separation of on-chain read state from optimistic UI state to keep financial dashboards trustworthy

Technology