badger-finance / badger-subgraph Goto Github PK

Noticed the following query gives total of 8 different vaults in the following subgraph: https://thegraph.com/explorer/subgraph/darruma/badger. However, the site shows 11 at https://app.badger.finance/.

Is there a way to get these added soon?

Come up with deployment CI/CD for badger subgraphs.

• Does fully automating after code review and merge into main make sense?
• Set up security and branch protections
• Set up staging CI/CD
• Set up prod CI/CD

currently does not have a decentralised subgraph

Use existing jintao or new subgraph for staging system and testing new changes

Migrate aura-bribes subgraph and use it in aura-autovoter repo

This is a first ticket in a series of tickets to migrate all our subgraphs to decentralized network

BadgerDAO Megagraph Hackathon

BadgerDAO has multiple subgraphs that all need to be curated by GRT stakers. By separating these subgraphs, it causes the amount of signalers to be fractured and the responsiveness of the subgraphs to be much slower / less reliable.

The Front End subgraph has 10x the amount of GRT from signalers as the other subgraphs, and would be beneficial to combine all ETH graphs under this one ID. This hackathon is to create a Badger Megagraph, which includes the details from the above graphs, as well as the below specification from Token Terminal to provide the data they need to include BadgerDAO in their product.

vaults {
  token {
    symbol
    decimals
    name
  }
  activeDeposits
  tokensInvested
  totalFeesGenerated
  protocolFeesAccrued
}

Helpful Links:

• Current Badger Contracts list: https://github.com/Badger-Finance/badger-system/blob/develop/deploy-final.json
• Current Subgraphs:
  • Setts-ETH: https://thegraph.com/explorer/subgraph?id=0xba5edb751ccf93770796e273d8bce83e1e81e2d4-4&view=Overview
  • Harvests-ETH: https://thegraph.com/explorer/subgraph?id=0xba5edb751ccf93770796e273d8bce83e1e81e2d4-2&view=Overview
  • Tokens-ETH: https://thegraph.com/explorer/subgraph?id=0xba5edb751ccf93770796e273d8bce83e1e81e2d4-4&view=Overview
  • NFTs: https://thegraph.com/explorer/subgraph?id=0xba5edb751ccf93770796e273d8bce83e1e81e2d4-3&view=Overview
  • Front End: https://thegraph.com/explorer/subgraph?id=0x8d26c9dac7e16738752fa1446b956a97c63e2f39-0&view=Overview
• Current Subgraph Code:
  • Setts-ETH: https://github.com/Badger-Finance/badger-subgraph/tree/master/subgraphs/setts_tricrypto2
  • Harvests-ETH: https://github.com/Badger-Finance/badger-subgraph/tree/master/subgraphs/tree-rewards
  • Tokens-ETH: https://github.com/Badger-Finance/badger-subgraph/tree/master/subgraphs/tokens
  • NFTs: https://github.com/Badger-Finance/badger-subgraph/tree/master/subgraphs/nfts
  • Front End: https://github.com/Badger-Finance/badger-subgraph/tree/master/subgraphs/badger-dao
• ETH v2 registry
  • ETH Contract: https://etherscan.io/address/0xfda7eb6f8b7a9e9fcfd348042ae675d1d652454f
  • ETH Code: https://github.com/Badger-Finance/badger-registry

Expectations

• A unified subgraph is created that includes the unique details from the above listed subgraphs, as well as enhancement of the vaults return to include the data required from Token Terminal
• MUST HAVE: Registry vault implementation utilizing v2 registry to automatically index new vaults
• An example legacy subgraph is launched with example queries provided
• Bonus points for a fun image / name for the subgraph to distinguish when users are searching

Rewards

• Badger will provide 100 Badger to the selected submission, as well as 100 additional Badger if we deploy the subgraph for use in production.

Any further questions can be directed to the Badger Discord