πŸ’»
Rubicon Subgraphs
Rubicon utilizes The Graph to track and record activity on the Rubicon Protocol in support of market participants and the web application's historical data.
​The Graph is a decentralized protocol for indexing and querying data from blockchains, allowing easy access to data that is typically difficult to query directly from the blockchain.
Projects with complex smart contracts like Rubicon store data directly to the Ethereum blockchain across multiple Layer 2 networks, making it both difficult and time-consuming to analyze current or historical market data. Through the development of subgraphs, which can simply be thought of as databases that contains groups of entities (tables) that store data collected from activity (trades, deposits, etc.) on the Rubicon Protocol, users can now access formatted, historical and real-time, data through a standard GraphQL API.
Key Subgraphs
The core functionality of the Rubicon Protocol can be thought of in three parts: 1) Trading, 2) Liquidity Providing, and 3) Strategist Market Making activities. Three subgraphs have been created to support the processing of data related to these core functionalities:
  • ​The RubiconMarket Subgraph: Tracking all trading activity (maker/taker trades) on Rubicon's Order Books. This subgraph also acts as a reference for any asset's price history on Rubicon.
  • ​The BathToken Subgraph: Tracking all activity (deposits/withdraws/earnings) of liquidity pools on the Rubicon Protocol. This subgraph can also be referenced to analyze historical performance of BathTokens.
Deployments
The Rubicon team supports and maintains the development of the three subgraphs listed above across any network that it is actively deployed to. You can find an active list of these network subgraphs below.
Optimism
Optimism-Kovan
​
Copy link