Ethring
  • Introduce
    • Overview
    • Core Benefit
    • Protocol Components
  • Core
    • Wallet Adapter
    • Operation Bag System
    • Config Provider
    • Balance Provider
    • Transaction Manager Service
    • Bridge-Dex Module
    • Asset Integration Layer
    • LP/Assets Standards Support
    • Security for Ethring Middleware
    • Deployment Addresses
  • Resourses
    • FAQ
      • What is Ethring?
      • How does Ethring work?
      • What makes Ethring unique?
      • What yield strategies can I use?
      • How does routing work?
      • Does Ethring hold tokens in its smart contracts?
      • Which networks does Ethring support?
      • What protocols does Ethring support?
      • Which providers does Ethring support?
      • What is The Bag?
      • How to deposit liquidity?
      • How to withdraw liquidity?
      • How can I integrate my LP assets and protocol into Ethring?
      • Partnership
    • Glossary
    • Brand Kit
  • Social
    • Ethring
    • Discord
    • X
    • Warpcast
    • Lens
    • Mirror
Powered by GitBook
On this page
  1. Core

Balance Provider

A service that provides information about balance of a wallet address

PreviousConfig ProviderNextTransaction Manager Service

Last updated 1 month ago

Collects and normalizes token balances and protocol-level data from multiple sources, including EVM APIs and price feeds.

Why it matters:

In Web3, a user's wallet balance is their most visible asset. We provide fast, accurate, and transparent balance tracking by combining:

  • Live on-chain queries (via EVM and other APIs)

  • Real-time socket updates after every transaction

  • Local caching to improve UX and reduce provider load

  • Price feeds to calculate fiat-equivalent portfolio value

This system ensures users always see their true portfolio state, while also giving investors confidence in how we compute valuations.

The Balances module builds a full portfolio view for users and gives investors confidence in how we calculate holdings and valuations. It combines live blockchain queries with local caching for both performance and transparency.

How it works:

  • Single-token balances (ERC20, native assets): Fetched via alchemy_getTokenBalances — fast, stable, and scalable.

  • DeFi positions (LPs, vaults, pools): Retrieved via Enso API — a high-quality source for structured protocol-level asset exposure.

  • Price data: Sourced from CoinGecko, ensuring real-time fiat conversion.

  • Live updates: After each user transaction, to reflect balance changes in real time.

  • Caching layer: Frequently accessed balances are cached locally (IndexedDB) for optimal performance and offline-friendly UX.

🌐 Highlights

  • Accurate, normalized balances across wallets.

  • Real-time updates post-transaction via socket events.

  • Modular data provider logic — easily extendable

Service Name
Balance type
Active

Tokens

Tokens, Pools

Pools

🧠
⚙️
Alchemy
Enso
Portals