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

Config Provider

A service that provides information about chains and tokens

PreviousOperation Bag SystemNextBalance Provider

Last updated 1 month ago

The Config Provider is our internal service that enables rapid integration of new blockchains.


Why it matters:

It enables rapid onboarding of new networks without touching the core logic. With a declarative approach, the team can add support for new blockchains in hours, not weeks — a key advantage when expanding across ecosystems.


How it works

We use automated parsers that fetch metadata from external sources (e.g., block explorers, token lists, RPC registries). These are updated regularly and serve as the foundation for each network config.

When adding a new EVM-compatible (or other) chain:

  • No custom code is required.

  • Parsers are already preconfigured.

  • Only the chain definition needs to be added to the registry.



  • Uses a declarative config model: adding a new chain only requires defining a config object.

  • No hardcoded logic — all providers (explorers, tokens, RPCs) are injected via config.

  • All chain metadata lives in one place, making version control and auditing simple.


  • Network-agnostic integration logic

  • Supports chain aliases, dynamic RPC switching, and fallbacks

  • Used at both frontend and backend levels


The list of networks that we currently support

ID
Chain
Status
Chain Parser
Token Parser

1

Ethereum

56

BSC

42161

Arbitrum

8453

Base

10

Optimism

Why Integration is Fast

Highlights

Active

Active

Active

Active

Active

🚀
🌐
✅
✅
✅
✅
✅
🧠
⚙️