Pull Data from Compound V3 Easily with Traceye’s Community Subgraph

Web3 developers and innovators heavily rely on subgraphs to query blockchain data back and forth from a range of networks. If you are a DeFi developer or an enterprise focused on DeFi, you might need to access data from Compound V3 protocol as it has emerged as a popular and highly interactive DeFi lending platform. Through this article, we are highlighting the Compound V3 Subgraph offering of Traceye, an exclusive data indexing solution. We will discuss the end-to-end process of pulling data from the Compound V3 protocol using Traceye’s community subgraphs. Let’s start off.

Compound III, or version 3, is the latest version of the Compound Finance protocol launched back in 2018. This platform introduced a novel idea of user-to-protocol collateralized lending & borrowing. Compound V3 is an EVM-compatible protocol that facilitates supply of crypto assets as collateral, allowing the users to borrow base assets against them. 

Compound III has a significant focus on maintaining reliable security, and it offers the following unique features:

• A thoroughly revamped risk management or liquidation engine to ensure greater safety of funds while enabling a more borrower-friendly ecosystem.

• Imposing market-wide limits for individual collateral assets’ size to reduce risks. 

• Decoupling of interest rate models for both earning and borrowing. Now, governance has complete control of economic policy.

• More powerful account management tools are designed to enable improved UX patterns and applications to build on top of the compound protocol. 

• Chainlink now enables exclusive price feeds, which is seamlessly portable to diverse EVM chains beyond just Ethereum. 

• Governance has become simple and easy to manage as the protocol works as a monolith having parameters set via a single Configurator contract. 

Compound V3 Ethereum Subgraph is one among the multiple subgraphs indexed by Traceye to make it available for queries via its community subgraph offering. Using the Compound V3 subgraph, web3 developers can seamlessly access all the compound III protocol’s on-chain data into their applications, for example– flash loans data, events, borrows, deposits, etc. Traceye indexes bulks of Compound V3 protocol’s data through the implementation of GraphQL schema, manifest, ABI files, and other crucial components running in the backend. It allows users to simply query and pull data for their relevant entity. Following is a snapshot of its core benefits:

>One-click subgraph activation: With Traceye’s community subgraphs, you enjoy one-click activation for all the supported subgraphs, for example- Compound V3 Subgraph in our case. 

>Zero complexity: As community subgraphs do not involve subgraph programming or deployment, anyone with or without technical expertise can pull data using it. 

>Affordable subscription plan: Traceye’s community subgraphs require only $39 per month for data queries. This is an ideal option for projects that do not want a dedicated subgraph or do not require sophisticated web3 data. 

>24/7 monitoring & support: To ensure uptime and performance of all your subgraphs, Traceye offers 24/7 monitoring of your subgraphs. All the logs are presented on the dashboard right away and real-time alerts are produced if anything goes wrong.

As discussed, the community Subgraph offering by Traceye provides the most simple and reliable way to query data from compound V3 protocol. Community subgraph, as the name says, is shared across various data consumers where everyone can simultaneously query data at ultra-fast speed and significantly lower data lag issues.

Note that, Traceye also allows projects to launch their dedicated subgraphs. First, they need to create their subgraph, for example– writing the manifest and creating GraphQL schema using the subgraph studio. After that, they can launch the subgraph on Traceye for effortless management and scaling. 

Need more information on launching Subgraph with Traceye? Refer to the article linked below for a step-by-step guide on: How to deploy Subgraphs with Zeeve’s Traceye? 

Now, let’s discuss how to pull compound V3 data using Traceye’s community compound V3 subgraph. 

Step:1 Login to the Zeeve platform if you already have an account. Or else, complete the signup first. Navigate to the ‘Traceye’ located in the dashboard’s left panel and proceed with Hosted Subgraphs. A new dashboard will appear with the Add Subgraph option.

Step:2 Click on Add subgraph and select ‘Launch Community’ option from the drop-down menu. A list of community subgraphs will now appear, including Compound V3 Ethereum.

Step:3 For activation, you first need to buy a subscription for this subgraph.  Click on ‘Buy Subscription’ that you can see in the above screenshot. This will open a dedicated payment page. Select the quantity of community subgraph you need and proceed ‘Buy Now’. 

Step:4 Once you complete the payment, again navigate to the hosted subgraph under Traceye → Add Subgraph → Launch community to activate Compound V3 Ethereum subgraph from here. 

Immediately after you click Activate, a new page will appear showing details about your  Compound V3 Ethereum subgraph, such as sync status, total requests, API units consumed, date of subgraph creation, network-type (mainnet or testnet), workspace, and Query URL. 

Step:5 Now, to pull data from Compound V3 protocol, click on the ‘Open’ option provided with the Query URL (shown in the above screenshot). It will redirect you to the GraphQL playground environment where you query a variety of data from Compound V3 protocol. 

Step:6 As you may already know, you need to define specific entities for which you want to pull data. Within the GraphQL playground, click on the GraphQL explorer’s icon to see a comprehensive list of entities available to pull data from. Like you can see, there are meta, accounts, borrow, fees, events, etc.

Step:7 Let’s say you want to deposit data for the first 10 IDs. To fetch this data, click ‘deposits’ entity and enter ‘10’ in the ‘first’ sub-entity. Plus, enter ‘id’ the orderby sub entity. You have the flexibility to increase or decrease the number of IDS or you can change the values in the orderby. Additional customization are also there, such as orderDirection, skip, account, accountActor, and so on. For this tutorial, let’s simply focus on fetching deposits data about the first 10 IDs. We’ve already the details, and hence the changes have reflected in the query schema. 

Immediately after you click the play button, the data for all 10 IDs will be available on your screen. And, here we are done. As you can see, Traceye’s community subgraphs have made it extremely easy to pull data from Compound V3 Ethereum subgraphs. The same level of ease you will experience while fetching data from the rest of the Traceye-supported subgraphs.

Apart from one-click subgraph activation, Traceye’s community subgraphs are optimized to offer aggressive monitoring and management of all your subgraphs. From the subgraph details page, you can check logs on multiple parameters like Info, Debug, Warning, and Error. For each parameter, you will get specific logs. This will keep you updated about the performance of subgraphs in real-time, ensuring there’s no downtime or other performance-related issues. 

That’s done! Our discussion on fetching data from Compound V3 protocol has reached its end. The motive of crafting this how-to article is to explain the importance and simplicity of Traceye’s community subgraphs to web3 developers and data consumers. It doesn’t involve a complex process of programming subgraphs, customization, or deployment. However, you can anytime opt for Traceye’s other services, which are dedicated indexer setup and the creation of custom subgraphs from scratch, depending on your specific data needs.

For more information on Traceye or Zeeve’s blockchain-related services, connect with our experts. Send all your queries via mail or schedule a one-on-one call if you want a detailed discussion.