We integrate POST /quote/v2 for same-chain Solana swaps with depositFeePayer, appFees, and fee/rent sponsorship. Some DFlow-routed quotes return SOLANA_TX_TOO_LARGE at quote time even with maxRouteLength: 3 (observed compiled sizes 1243–1400 bytes). A changed-parameter quote with maxRouteLength: 2 recovered the 18 oversized cases in a bounded read-only sample, but route-length limits do not provide a byte-size guarantee.
Could the Relay team clarify whether /quote/v2 currently supports, or plans to support, any of the following for Solana-origin quotes?
- DFlow's user-executed sponsored mode (
sponsorExec: false), with our depositFeePayer still paying SOL fees and rent. DFlow documents this mode as removing the sponsor input/output transfers and reducing transaction size. Is there a Relay option that selects this mode without changing the user-facing sponsorship semantics?
- A serialized transaction byte budget (for example, 1232 bytes) applied while choosing route candidates, so Relay can return another eligible route instead of rejecting only the chosen oversized candidate. Is there a documented route-size control or candidate fallback beyond
maxRouteLength and source filters?
- Solana v1 transactions through Relay quotes and settlement, now that Solana mainnet supports the 4096-byte v1 envelope. Is there a
transactionVersion parameter or a timeline for v1 support?
The current Solana transaction-size guide still says all Solana-origin quotes are gated at 1232 bytes, and the quote request reference does not list the three controls above. We are looking for a supported API contract, rather than relying on unlisted fields that may be silently ignored.
We integrate
POST /quote/v2for same-chain Solana swaps withdepositFeePayer,appFees, and fee/rent sponsorship. Some DFlow-routed quotes returnSOLANA_TX_TOO_LARGEat quote time even withmaxRouteLength: 3(observed compiled sizes 1243–1400 bytes). A changed-parameter quote withmaxRouteLength: 2recovered the 18 oversized cases in a bounded read-only sample, but route-length limits do not provide a byte-size guarantee.Could the Relay team clarify whether
/quote/v2currently supports, or plans to support, any of the following for Solana-origin quotes?sponsorExec: false), with ourdepositFeePayerstill paying SOL fees and rent. DFlow documents this mode as removing the sponsor input/output transfers and reducing transaction size. Is there a Relay option that selects this mode without changing the user-facing sponsorship semantics?maxRouteLengthand source filters?transactionVersionparameter or a timeline for v1 support?The current Solana transaction-size guide still says all Solana-origin quotes are gated at 1232 bytes, and the quote request reference does not list the three controls above. We are looking for a supported API contract, rather than relying on unlisted fields that may be silently ignored.