Unified
  • What is Unified?
  • How can you use Unified?
  • Exchanges covered by Unified
  • Blockchains and protocols / projects covered by Unified
    • Arbitrum
    • Avalanche
    • BNB Chain
    • Ethereum
    • Fantom
    • Optimism
    • Polygon (Matic)
    • Solana
    • Terra
  • Websites operated by Unified
  • Type of information provided
    • Exchange information provided by Unified
      • Binance
      • Bitfinex
      • Bitmex
      • Bybit
      • Coinbase
      • Deribit
      • Deversifi
      • dydx
      • FTX
      • Huobi
      • Kraken
      • Kucoin
      • OKX
    • Protocols / project information provided by Unified
      • Trade execution
    • Global markets & onchain data provided by Unified
      • Funding rates snapshot
      • Liquidations snapshot
      • Open interest relative to price trend
      • Funding rates relative to price trend
      • Estimated leverage ratio relative to price trend
      • Adjusted SOPR (aSOPR)
      • Short-term holder (STH) SOPR
      • Long-term holder (LTH) SOPR
      • MVRV ratio
    • NFT data provided by Unified
  • Guides
    • Setting up an account
    • Adding on-chain addresses from different protocols
    • Adding accounts from different exchanges
  • Solving technical challenges
    • Scale of data aggregation
    • Security considerations
  • Use Cases
    • For Casual Users
    • For NFT Collectors
    • For Yield Farmers
    • For Money Market Protocol Users
    • For Traders
  • Other
    • Recruitment
    • Our 3 sources of revenue
      • Advertising & sponsorship
      • Subscription
      • API-only subscription (for institutional clients)
    • Donations
    • Unified Token
    • Terms of service
    • Privacy policy
Powered by GitBook
On this page
  1. Solving technical challenges

Scale of data aggregation

The main challenge with a product like Unified is the scale of data aggregation that occurs with multiple concurrent users.

Essentially, the Unified dashboard product automates the collection of data from multiple sources at one time and then displays it to the user.

This is similar to "scraping data" from multiple sources through the use of application programming interfaces (APIs).

Price/volume comparison sites, blockchain explorers and centralized exchanges tend to enforce rate limitations to prevent the APIs from being called frequently.

Consider what will happen when:

  • Multiple users send out a query, and

  • Each user has multiple addresses, which reside in multiple blockchain protocols, and

  • Each user's address may be participating in multiple projects, and

  • Each user may be using multiple centralized exchanges, and

  • All those queries are sent out simultaneously.

To solve for this, Unified employs several approaches.

  • The first solution is that Unified focuses on the major blockchain protocols, although the practical reality is that Unified will eventually cover all blockchain protocols.

  • The second solution is that Unified focuses on the major projects (as represented by TVL and activity). This is a more practical, restrictive condition as there are many projects that eventually fall by the wayside, and it is not practical for Unified to automatically query the explorers in relation to such projects.

  • The third solution is that Unified uses 1,000s of accounts to separate out API calls by users so as to reduce rate limitation by price/volume comparison sites, blockchain explorers and centralized exchanges.

  • The fourth solution is that Unified develops specific partnerships with price/volume comparison sites, blockchain explorers and centralized exchanges so that addresses from which API calls originate are whitelisted for minimal rate limitations.

PreviousAdding accounts from different exchangesNextSecurity considerations

Last updated 3 years ago