You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have an additional way to select multiple transactions that is more similar to what people are used to. On the left side of the screen I would like some interface that allows the user to filter transactions by their properties (counterparty, tokens, addresses etc.). It will need to support both AND and OR logic. For example, the user should be able to select the following using these filters:
(transaction.counterparty=UNISWAP OR transaction.counterparty=1INCH) AND transaction.token=SOL
It should be accomplished in the following way:
The user creates a new filter by counterparty and types "UNISWAP" there
The user creates a new filter by counterparty and types "1INCH" there
The user creates a new filter by token and types "SOL" there
So it's "OR" logic for the same kind of filter, but "AND" logic for different kind of filters
The text was updated successfully, but these errors were encountered:
It would be nice to have an additional way to select multiple transactions that is more similar to what people are used to. On the left side of the screen I would like some interface that allows the user to filter transactions by their properties (counterparty, tokens, addresses etc.). It will need to support both AND and OR logic. For example, the user should be able to select the following using these filters:
(transaction.counterparty=UNISWAP OR transaction.counterparty=1INCH) AND transaction.token=SOL
It should be accomplished in the following way:
The user creates a new filter by counterparty and types "UNISWAP" there
The user creates a new filter by counterparty and types "1INCH" there
The user creates a new filter by token and types "SOL" there
So it's "OR" logic for the same kind of filter, but "AND" logic for different kind of filters
The text was updated successfully, but these errors were encountered: