fix(assets-controller): exempt user-initiated activity from spam filtering - #9768
Draft
salimtb wants to merge 4 commits into
Draft
fix(assets-controller): exempt user-initiated activity from spam filtering#9768salimtb wants to merge 4 commits into
salimtb wants to merge 4 commits into
Conversation
Contributor
|
Hmm, I think the intention it correct here, but this still impacts:
|
salimtb
added a commit
that referenced
this pull request
Aug 6, 2026
Co-authored-by: Cursor <cursoragent@cursor.com>
salimtb
added a commit
that referenced
this pull request
Aug 6, 2026
salimtb
force-pushed
the
fix/assets-controller-ws-spam-filtering
branch
from
August 6, 2026 11:36
dd3cdfb to
ea2be1f
Compare
…ering Occurrence-floor / Blockaid spam filtering now applies only to passively discovered tokens (auto-detection, incoming-only websocket transfers such as airdrops). Assets acquired through user-initiated activity — the account sent funds in the same transaction, e.g. swap outputs — are listed on a new DataResponse.userInteractedAssets field by AccountActivityDataSource and bypass the filter in TokenDataSource, so they always show even when below the per-chain occurrence floor. Filtered-out spam is now also stripped from stub assetsInfo on the response, and balance deletions match asset IDs case-insensitively. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…ed after rebase Co-authored-by: Cursor <cursoragent@cursor.com>
salimtb
force-pushed
the
fix/assets-controller-ws-spam-filtering
branch
from
August 6, 2026 11:43
ea2be1f to
51a48e1
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
2 participants
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.
Occurrence-floor / Blockaid spam filtering now applies only to passively discovered tokens (auto-detection, incoming-only websocket transfers such as airdrops). Assets acquired through user-initiated activity — the account sent funds in the same transaction, e.g. swap outputs — are listed on a new DataResponse.userInteractedAssets field by AccountActivityDataSource and bypass the filter in TokenDataSource, so they always show even when below the per-chain occurrence floor.
Filtered-out spam is now also stripped from stub assetsInfo on the response, and balance deletions match asset IDs case-insensitively.
Explanation
References
Checklist