Conversation
jgalat
force-pushed
the
feat/zap2-provider
branch
from
September 16, 2026 15:09
ede7a6b to
c87edac
Compare
Deploying react-zapper with
|
| Latest commit: |
801a851
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f0f66b35.react-zapper.pages.dev |
| Branch Preview URL: | https://feat-zap2-provider.react-zapper.pages.dev |
Quoted through the reserve-api api/zapper2/{chain}/swap proxy with the
same query and response contract as zap. Enabled on Ethereum, Base and
BSC; competes like an outside venue with no tie-break preference.
jgalat
force-pushed
the
feat/zap2-provider
branch
from
September 16, 2026 15:12
c87edac to
801a851
Compare
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.
Summary
Adds
zap2, the Rust zapper, as a quote provider (2.12.0, on top of the 1inch release 2.11.0).api/zapper2/{chain}/swapproxy with the same query string and response contract aszap, so it uses the samezapperApiUrl.src/types/api.tstakes a service slug for the native URL builder;src/utils/providers.tsadds the provider (label "Zap v2", Bolt icon), enabled on Ethereum, Base and BSC (the Rust zapper does not serve Arbitrum).zap2competes like an outside venue:compareQuotesandpickBestQuotekeep theirzap-only tie-break, documented as deliberate.ProviderIdgains'zap2'; hosts building exhaustiveRecord<ProviderId, …>maps need the new key (hence the minor bump). The route list, tracking and Mixpanel ids pick it up automatically.zapperApiUrldropdown gains the staging API. README and CHANGELOG updated.Verification
pnpm test17 files / 96 green,pnpm build(type check) andpnpm lintgreen.tests/zap2-provider.test.tsx: the endpoint isapi/zapper2/1/swapwith the same query keys aszapand its transaction executes; a betterminAmountOutwins the round next to thezaprow; an equalminAmountOutgoes tozap, proving no tie preference.Zap v2row needs reserve-protocol/reserve-apifeat/zapper2-proxy-zrs1-pricesdeployed to staging; until then the row errors onapi-staging(404 onapi/zapper2).