This is an internal guide to juicebox subgraph architecture and maintenance.

The Peel multisig wallet owns and maintains the following subgraphs:

juicebox - primary Juicebox subgraph published to mainnet, used by juicebox.money
juicebox-goerli - unpublished goerli subgraph, used by goerli.juicebox.money
- To mitigate issues with rate-limiting on goerli.juicebox.money, this URL should be kept private (even though it will be exposed in the app). Devs should be encouraged to use the goerli-dev subgraph, which will be identical.
mainnet-dev - unpublished mainnet subgraph used for development
goerli-dev - unpublished goerli subgraph used for development

Basic concepts

subgraph: A set of instructions for Graph infrastructure to index specific events, emitted from specific contracts, on a specific chain, and store them as entities as defined in mapping functions.
studio: The Subgraph Studio is a wallet-gated app for managing subgraphs. Only multisig signers will be able to access it.
deploying: When changes are made to a subgraph, changes are deployed and a new version is created.
- Deploying is free and can be done liberally
publishing: Publishing a subgraph version instructs graph indexers to begin indexing that version. Previously indexed versions will be deprecated automatically as indexers migrate to the new version.
- Publishing requires paying a GRT migration tax
- When a subgraph is published for the first time, a NFT will be minted representing ownership
mappings: Mapping functions determine how data emitted from contract events is stored as entities to be queried later.
entities/schema: Entities are objects defined in a subgraph schema.graphql file, that determine how data is stored and queried. (Projects, Participants, etc)

Accessing Subgraph Studio via Gnosis multisig wallet