Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App: fetch loans from the subgraph #420

Merged
merged 25 commits into from
Sep 24, 2024
Merged

App: fetch loans from the subgraph #420

merged 25 commits into from
Sep 24, 2024

Conversation

bpierre
Copy link
Contributor

@bpierre bpierre commented Sep 12, 2024

builds on #375 which should be merged before

Various changes to make the app fetch the loans from the subgraph.

See subgraph/README.md for instructions on how to deploy the subgraph locally.

- Add subgraph/ to the workspaces.
- A script, ./deploy-subgraph, can be used to deploy the subgraph in a
  convenient way. See --help for details.

Some context:

- The subgraph uses subgraph templates for the collateral contracts.
- The script can update the collateral registry address in the
  subgraph.yaml if it doesn’t match the one found in the latest
  deployment context.
- In ./deploy-subgraph, only the local preset is implemented.
This allows to initiate things when `CollateralRegistryAddressChanged`
gets emitted on BoldToken, which happens at the very end of the
deployment process.

Also:

- Use troveNFT.ownerOf() to determinate the trove owner.
- Update README instructions.
- Add ./start-graph
- Remove ./docker-cleanup.sh (replaced by ./start-graph --reset)
- Rename ./deploy to ./deploy-subgraph for clarity
- Update README with new instructions
Base automatically changed from subgraph to main September 24, 2024 11:16
@bpierre bpierre merged commit 530e28b into main Sep 24, 2024
@bpierre bpierre deleted the app-subgraph branch September 24, 2024 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant