Bean Subgraph - Split Cross Entity #642
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for basin canceled.
|
✅ Deploy Preview for beanstalk-ui canceled.
|
hellofromguy
approved these changes
Sep 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously there was only one pool to track peg crosses, and the overall Bean peg was tied to that one pool. With the introduction of the Bean:ETH well, the overall Bean price can cross peg independently of an individual pool have a cross at the same time.
Schema changes:
Crossentity removed and replaced by the following two entitiesBeanCrossentity added to track the overall Bean peg cross. This uses the liquidity weighted price returned by the current price contract.PoolCrossentity added to track individual peg crosses within a pool. Each pool has their own incremental counter for the number crosses observed.