feat(solana-solvers): report uniform clearing prices in engine solutions - #4763
Merged
Conversation
squadgazzz
marked this pull request as ready for review
August 20, 2026 13:43
Contributor
|
Claude finished @squadgazzz's task in 1m 44s —— View job PR Review
The One issue found — the I couldn't run |
tilacog
approved these changes
Aug 20, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
The engine wire reports one executed amount per trade and nothing else, so the driver cannot know the trade's other leg and currently answers the autopilot with a zero placeholder that the ranking math rejects (discussed on #4759). The EVM engine wire solves this with uniform clearing prices per solution, and the Jupiter engine already holds both numbers: the quote's in and out amounts.
This adds the EVM-shaped
pricesmap to the engine's solution DTO, oriented like the EVM solvers build it: the sell mint maps to the amount bought, the buy mint to the amount sold. The driver ignores unknown fields today, so this lands independently, and the driver-side consumption (deriving the counterpart leg and dropping the zero placeholder) follows in the driver's own PR.Changes
prices(mint to amount, decimal strings on the wire), populated from the executed swap's two amountsHow to test
Updated unit tests.