feat: Bridge quotestream token warning events#8198
Merged
infiniteflower merged 19 commits intomainfrom Mar 20, 2026
Merged
Conversation
881e93d to
6d8a822
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
GeorgeGkas
previously approved these changes
Mar 20, 2026
micaelae
reviewed
Mar 20, 2026
micaelae
reviewed
Mar 20, 2026
micaelae
previously approved these changes
Mar 20, 2026
micaelae
approved these changes
Mar 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Explanation
The bridge-api SSE quote stream (
getQuoteStream) now emitstoken_warningevents alongsidequoteevents. These warnings come from Blockaid security scanning of the destination token and contain information like whether a token is a honeypot or has unstable pricing.Previously,
fetchBridgeQuoteStreamignored the SSEevent:name and attempted to validate every message as a quote response. This meanttoken_warningevents were silently dropped (or caused spurious validation failures).This PR:
fetchBridgeQuoteStream— onlyquoteevents go through quote validation,token_warningevents are validated separately via a new superstruct schema and routed to a dedicated handler, and all other event types are skipped.tokenWarnings: TokenFeature[]field toBridgeControllerState, populated from the SSE stream and cleared on reset / new quote fetch.onValidationFailuretoonQuoteValidationFailureand#trackResponseValidationFailuresto#trackQuoteValidationFailuresfor clarity now that there are multiple event types.TokenFeaturetype andTokenFeatureTypeenum for use by clients.References
https://consensyssoftware.atlassian.net/browse/SWAPS-4226
Checklist
Note
Medium Risk
Medium risk: changes SSE stream message routing and BridgeController state shape, which could affect quote streaming behavior and downstream consumers expecting previous handler names/state fields.
Overview
Adds support for
token_warningevents in the bridge-api quote SSE stream by routing SSE messages byeventtype, validating warnings with a newTokenFeatureschema, and exposing them via a newtokenWarningsfield onBridgeControllerState(reset on new requests andresetState, and de-duplicated byfeature_id).Renames the stream callback
onValidationFailuretoonQuoteValidationFailure(and corresponding internal tracker) to clarify metrics for quote-validation failures, and exportsTokenFeature/TokenFeatureTypeplus a newselectTokenWarningsselector. Tests/snapshots are updated and extended with SSE warning stream fixtures and dedup/reset coverage.Written by Cursor Bugbot for commit 37d8983. This will update automatically on new commits. Configure here.