-
Notifications
You must be signed in to change notification settings - Fork 25
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(stargate): Stargate bridge #22
Conversation
🦋 Changeset detectedLatest commit: ef6b199 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
? CHAIN_AND_POOL_TO_TOKEN_ADDRESS[sourceChainId][tokenAddress] | ||
: 0 | ||
|
||
if (sourcePool === 13) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this const ETH_POOL = 13
accurate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, I'll create a const and compare against that vs a magic number for increased clarity.
…into stargate_bridge
…stdk-plugins into stargate_bridge
…stdk-plugins into stargate_bridge
…into stargate_bridge
…into stargate_bridge
…stdk-plugins into stargate_bridge
…stdk-plugins into stargate_bridge
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Some of the data in
CHAIN_AND_POOL_TO_TOKEN_ADDRESS
in thecontract-addresses.ts
file are the pool token instead of the actual token. Going to have to fix the data in that lookup before we merge this in.Fixed the
CHAIN_AND_POOL_TO_TOKEN_ADDRESS
forUSDC
USDT
andWETH
. Should be G2G.