feat: add gasless request flags - #559
Open
CallumGrindle wants to merge 4 commits into
Open
Conversation
CallumGrindle
force-pushed
the
feat/gasless-quote-surface-types
branch
from
August 4, 2026 09:57
61f92db to
41b981a
Compare
Adds the request surface the gasless EVM execution quote flow needs: - `gasless?: boolean` on `QuoteRequest` and `RouteOptionsBase`, placed next to `executionType` in both, since it selects an execution mode. - `LIFI_GASLESS_RELAY_FEE_NAME`, the stable `FeeCost.name` integrators match on to find the relay fee entry in `feeCosts`. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The fee-name constants integrators match on (LIFI_SHARED_FEE_NAME and friends) live in the backend and are published through the docs; FeeCost.name stays a plain string here. This PR now only adds the gasless request flag. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The relay fee constant no longer ships from this package, so the gasless flag comments name the FeeCost.name value directly instead of pointing at an identifier consumers cannot import.
CallumGrindle
force-pushed
the
feat/gasless-quote-surface-types
branch
from
August 6, 2026 14:28
5da178f to
55ace02
Compare
CallumGrindle
changed the title
Contributor
Author
|
Rebased onto the latest |
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.
What
Adds the
gaslessrequest flag for the gasless EVM execution surface (M2 slice of the gasless types train):gasless?: booleanonQuoteRequest— opts the quote into gasless execution: the response returns signable typed data instead of atransactionRequest, and the relay fee is deducted from the input amount. Defaultfalse.gasless?: booleanonRouteOptionsBase— the same flag for/advanced/routes, placed with the other execution-shape options (executionType,allowDestinationCall).The relay-fee
FeeCostname constant originally included here was removed: the fee-name constants integrators match on (LIFI_SHARED_FEE_NAMEand friends) live in the backend and are published through the docs —FeeCost.namestays a plain string in this package.Why
Linear: https://linear.app/lifi-linear/issue/CORE-790
Phase 1 of gasless EVM execution (EIP-7702 batched approve+swap). The backend implementation consumes this via a beta release; the intent factory follows.
Release
No version bump / CHANGELOG edit — standard-version owns both. After merge:
pnpm release:beta+ tag push to cut the beta for lifi-backend and intent factory.🤖 Generated with Claude Code