How Oath hides spam and phishing activity

How to do it

1. Use History or an asset’s Activity as usual. Safety filtering runs automatically; no separate switch is required.
2. If an unexpected token is absent, check whether it is unverified or has a suspicious name containing a link or a claim instruction.
3. For an expected legitimate transfer, verify the network, public account and full token contract or asset identity using independent information.
4. For supported manual-lookup networks, you can deliberately add a token you recognize through Wallet → Search. Review the full identity before adding it.
5. If a discrepancy remains, compare the public explorer record or contact support with the network and transaction ID.

The same visibility rules apply to the full history, asset previews, transaction search, filter choices and transaction details. Previously saved activity is also checked, so old spam does not need a fresh arrival to be hidden.

Oath combines available provider verification with network-specific asset catalogs and local checks. A token is matched by its network and exact contract, mint, issuer or asset reference. Matching a popular symbol or having a quoted price is not enough.

Unlisted tokens are hidden by default from history unless you have explicitly chosen to track them. Explicit tracking does not override detected phishing metadata, known blocked-token evidence or zero-value transfer rules.

Filtering changes the app’s presentation. It does not delete public blockchain records, reverse a transfer or revoke a contract allowance. The explorer can still show entries that Oath hides.