Conversation
The endpoint only read the static token config, so tokens the quote engine accepts via the dynamic Squid Router list (e.g. PAXG) were never advertised. Read the merged dynamic config instead, dedupe the alias keys, and expose rampTypes so integrators can see that routed tokens are BUY-only. The network filter is now required to keep responses per-network.
Squid sends a native source token (ETH, POL) as msg.value, so the route's transaction value carries the swapped principal on top of the router fee. Pricing the whole value as network fee exceeded the bridged amount, the fee distribution zeroed the swap input, and every native-token SELL quote failed with "Input amount for swap must be greater than 0". Subtract the principal for native sources so only the router fee is charged.
The block-flow port gated every EVM SELL definition on the static token enum and config, while the legacy route resolver accepted any token the Squid-discovered catalog knew. Resolve SELL sources through the same merged token catalog BUY destinations use, restoring sells of routed tokens such as PAXG.
With the SELL catalog resolving routed tokens, rampTypes no longer depends on whether an EVM token comes from the static config.
Startup re-resolves every pending quote and resumable ramp through the catalog's match predicates and exits the process on failure. Matching SELL sources against live Squid discovery meant one routed-token ramp plus a failed token fetch at boot would crash-loop the API. Match SELL sources structurally, as BUY destinations already are, and let the flow input resolver reject unknown symbols with a 400 at quote time.
rampTypes claimed BUY and SELL for Moonbeam, testnets, and AssetHub, although quote creation rejects those networks or has retired their only corridors. Derive the directions from the same guards the quote service applies, naming the AssetHub retirement so both share it.
The phase processor enqueues the ramp-completion email without awaiting it, so the INSERT can still be in flight when the next test's beforeEach truncates every table. Postgres then deadlocks the two (the INSERT's FK check waits for a table the TRUNCATE holds, and vice versa) and the next test fails at random. Route the enqueue through a background-work registry from the fake world and have truncateAllTables wait for it.
…email-race Drain fire-and-forget work before truncating test tables
…rencies-routed-tokens List routed EVM tokens in supported cryptocurrencies
✅ Deploy Preview for vrtx-dashboard canceled.
|
✅ Deploy Preview for vortex-sandbox ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for vortexfi canceled.
|
Agents reading the docs inferred that a custom UI or API-driven onboarding requires managed profiles. State the standalone-profile alternative where that inference happens.
Browser integrations fail at the CORS preflight until Vortex adds their exact origin, and the docs never said how to get one added.
…rifications Clarify that managed profiles are optional and document the browser origin allowlist
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.