Superfluid Automation Subgraphs ·

Superfluid Automation Subgraphs index the peripheral Superfluid automation contracts.

Example Deployments

Vesting Scheduler: https://api.thegraph.com/subgraphs/name/superfluid-finance/vesting-v1-eth-goerli
Flow Scheduler: https://api.thegraph.com/subgraphs/name/superfluid-finance/scheduling-v1-eth-goerli
Auto-Wrap: https://api.thegraph.com/subgraphs/name/superfluid-finance/auto-wrap-v1-eth-goerli

Automation Smart Contracts

Inspect the source code in the protocol-monorepo
Find the deployment addresses programmatically from @superfluid-finance/metadata

Other

The Graph Supported Networks CLI names: https://thegraph.com/docs/en/developing/supported-networks/

License

The Superfluid Automation Subgraphs are MIT licensed.

automation-subgraphs's People

Contributors

Stargazers

Watchers

automation-subgraphs's Issues

Auto-Wrap subgraph's WrapSchedule entity has unnecessary nullable fields

What?

Fields like createdAt shouldn't be nullable.

WrapSchedule schema from production (note the no "!" specified for createdAt):

Why?

This is a problem because it makes consumer code unnecessarily handle null values.

How?

Specify as non-null in the subgraph mapping code.

[SPIKE] Experiment with GraphQL Mesh

Why?

Bring us in line with industry best practice
Helps us manage bigger protocol subgraph changes with fewer issues
Better monitoring

GraphQL Mesh shows promise to be used as a gateway for our subgraphs with additional capabilities like schema stitching, schema monitoring, caching, etc. Automation subgraphs are a great place to experiment, as we've currently given out direct links to the GraphQL server hosted on The Graph's hosted service.

Recommend Projects