-
Notifications
You must be signed in to change notification settings - Fork 169
feat: paradexsepolia<>sepolia warp deployment #551
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
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
connections: | ||
- token: ethereum|paradexsepolia|0x0417c1391aba15b35373012970386f8096887c74504b7381d94e646ee9c3815a | ||
- token: ethereum|paradexsepolia|0x0417c1391aba15b35373012970386f8096887c74504b7381d94e646ee9c3815a |
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.
The connections array contains a duplicate entry for the same token address. This appears to be unintentional and should be fixed by removing one of the entries:
connections:
- token: ethereum|paradexsepolia|0x0417c1391aba15b35373012970386f8096887c74504b7381d94e646ee9c3815a
- token: ethereum|paradexsepolia|0x0417c1391aba15b35373012970386f8096887c74504b7381d94e646ee9c3815a # Duplicate entry
Having duplicate connections could potentially cause issues with the warp route configuration or lead to unexpected behavior.
connections: | |
- token: ethereum|paradexsepolia|0x0417c1391aba15b35373012970386f8096887c74504b7381d94e646ee9c3815a | |
- token: ethereum|paradexsepolia|0x0417c1391aba15b35373012970386f8096887c74504b7381d94e646ee9c3815a | |
connections: | |
- token: ethereum|paradexsepolia|0x0417c1391aba15b35373012970386f8096887c74504b7381d94e646ee9c3815a |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
collateral USDC on sepolia and synthetic on paradexsepolia
Note: the UI doesn't connect with the Paradex network because of their custom account derivation. For sepolia->paradexsepolia, in the recipient field, manually enter the paradexsepolia address.
Note: doesn't support withdrawals from Paradex for the same reason; instead you can use the CLI as following: