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

feat(#major); curve; handle TricryptoPoolDeployed event #2573

Open
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

fishTsai20
Copy link

@fishTsai20 fishTsai20 commented Jun 28, 2024


name: Feature request
about: Support Curve new protocol
title: "#feature; curve; handle TricryptoPoolDeployed event"
labels: enhancement
assignees: ishraq8

What do you think is missing?
The Curve configuration was outdated and missing the factory address for the tricrypto pools as well as the function to handle the creation of pool contracts.

Describe the solution you'd like

  • add CurveTricryptoFactory address

  • add handle TricryptoPoolDeployed function

  • support new protocol

Description
The Curve configuration was outdated and missing the factory address for the tricrypto pools as well as the function to handle the creation of pool contracts.

  • add CurveTricryptoFactory address
  • add handle TricryptoPoolDeployed function

Additional context
https://thegraph.com/explorer/subgraphs/AxY4fTdsWG3Y48apG8T6WwKEwRKGrsr4WFBZWJp5HzYC?view=Query&chain=arbitrum-one

When pool is tricrypto-pool, sometimes not exist Transfer event that from_address = pool_address and to_address = provider, when RemoveLiquidityOneWithPriceScale event occured.
Such as  pool='0x7F86Bf177Dd4F3494b841a37e810A34dD56c829B', transaction_hash='0x1804be3e0c5ffa486baefd537b9e393e7d2b53f1abf829e98d10bfa8f12b1d6a'.

But the event provide 2 args: coin_amount, coin_idx.
When handle RemoveLiquidityOneWithPriceScale, there is no need to use transfer event to get the withdraw tokens and amounts.
Copy link
Collaborator

@harsh9200 harsh9200 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @fishTsai20, I've reviewed your PR, and overall, the changes look really good! Thanks for your work on this.

Just one thing: could you please take a look at and fix the linting issues in the CI/CD? It would ensure everything aligns perfectly with our coding standards. Also, can you send the deployment id of the subgraph?

When pool is tricrypto-pool, sometimes not exist Transfer event that from_address = pool_address and to_address = provider, when RemoveLiquidityOneWithPriceScale event occured.
Such as  pool='0x7F86Bf177Dd4F3494b841a37e810A34dD56c829B', transaction_hash='0x1804be3e0c5ffa486baefd537b9e393e7d2b53f1abf829e98d10bfa8f12b1d6a'.

But the event provide 2 args: coin_amount, coin_idx.
When handle RemoveLiquidityOneWithPriceScale, there is no need to use transfer event to get the withdraw tokens and amounts.
@fishTsai20
Copy link
Author

Hi @fishTsai20, I've reviewed your PR, and overall, the changes look really good! Thanks for your work on this.

Just one thing: could you please take a look at and fix the linting issues in the CI/CD? It would ensure everything aligns perfectly with our coding standards. Also, can you send the deployment id of the subgraph?

subgraph ID : AxY4fTdsWG3Y48apG8T6WwKEwRKGrsr4WFBZWJp5HzYC

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.

2 participants