Alert Types

This page is the field-by-field tour of each alert type. For the conceptual overview of how alerts are structured see Alert Anatomy; this page is for “what does each event type actually look like, and what can I configure on it?”

Every alert type can be toggled on or off in the dashboard’s Alert Types page, independently per event type, and (when Solana is enabled) independently per chain.

Swaps (buys + sells)

Token-for-token or native-for-token trades on a DEX. Classified as a buy when the wallet receives a non-native non-stablecoin token; otherwise sell.

🔷 MyWallet 1.23 ETH | 🟢 Buy PEPEp

1.50 ETH ($5,600.00) swapped for 17,760,000 PEPEp ($5,190.00)

$292.2K | Tx: 0.15% | H: 2.45% | Gas: 0.0023 ETH | Etherscan | First 47h ago
DS | DT | DEF | GMGN | Maestro Pro | SIGMA

0xa2206AB1534f58cfE688628ce475a8eAA8663058

Customizable fields: wallet name + balance, token name, token amount, USD value, token CA, market cap, transaction holding %, total holding %, gas, DEX, every trading-link button, explorer link, “first seen” timestamp.

Transfers (incoming + outgoing)

Plain token or native-currency moves that aren’t part of a swap.

🔷 MyWallet | Transfer WETH

Amount: 100 WETH
Value: $345,600.00
To: 0x28C6c06298...
Market Cap: $2.3M
Tx: 0.15%
H: 2.45%
Gas: 0.0015 ETH

Etherscan

0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2

Customizable fields: wallet name, token name + CA, amount, USD value, to-address, market cap, holdings %, gas, explorer.

Incoming and outgoing transfers share the same toggle — toggling “Transfers” off silences both directions.

Bridges

Cross-chain transfers detected via the bridge registry (25+ protocols including DeBridge, Stargate, Across, Synapse, Hop, Celer, Wormhole, Axelar, Relay, LI.FI, Socket / Bungee, official rollup bridges).

🔷 MyWallet | Bridge USDC

ETHEREUM → BASE
10,000 USDC ($10,000.00) on ETHEREUM

View TX

Customizable fields: wallet name, USD value, explorer link.

For DeBridge specifically, the bot pulls the order completion status (when available) and includes the destination tx link once the order resolves.

Approvals

When a tracked wallet grants a smart contract permission to spend a token. The unlimited-approval pattern (max uint256) is detected and shown with the ♾️ symbol.

🔷 MyWallet | Approved USDC

Amount: ♾️
To Trade on: Uniswap V2 Router
Gas: 0.0042 ETH

Etherscan

0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48

Customizable fields: wallet name, amount, spender (resolved to a friendly name when known), gas, explorer.

Approvals fire even when there’s no Transfer event in the same transaction — useful for catching wallets prepping a big trade before it executes.

Contract interactions

Any contract call that doesn’t produce a Transfer, Approval, or recognized swap event. Things like pauseCraft(bool), governance votes, NFT contract config changes, anything custom.

🔷 MyWallet | Contract Call stake(uint256)

Function: stake(uint256)
Method ID: 0xa694fc3a
Contract: Staking Pool V2
Contract Address: 0x1234...5678

Parameters:
  amount: 1000000000000000000 (1.0 tokens)

Input Data:
0xa694fc3a000000000000000000000000000000000000000000…

Gas: 0.0028 ETH

Etherscan

Customizable fields: function name, method ID, contract name + address, decoded parameters (when ABI is verified on Etherscan), input data, gas, explorer.

The bot resolves method names through a 3-tier signature service — hardcoded common methods, then the bot’s database cache, then 4byte.directory, then the contract’s verified ABI on Etherscan. Custom contract methods that nobody has decoded before tend to surface as the raw method ID until someone (anyone) views the contract’s verified source.

Failed transactions

When a transaction reverts on-chain. The bot extracts the revert reason from the receipt when available.

🔷 MyWallet | ❌ CallFailed (target=0x0000...2734)

Function: Swap
Contract: Uniswap V2 Router
Gas: 0.0042 ETH

Etherscan

Customizable fields: wallet name, function name, contract name, gas, explorer.

Failed txs are useful for catching slippage events, frontrun attempts, and wallets in trouble — but if you find them noisy, toggling the type off in the dashboard silences them entirely.

NFT transfers

ERC-721 and ERC-1155 transfers (EVM) and Solana NFT events (compressed mints, transfers, sales) detected via Helius. Treated as a transfer with the isNFT: true flag, so toggling NFTs off via the NFT alert-type toggle silences them independently of regular transfers.

NFT alerts include the collection address, token ID, and the marketplace name (Tensor, Magic Eden, OpenSea router, Blur, etc.) when one is involved.

Customization on the Alert Types page

Open the dashboard → Alert Types. The page has:

Chain tab — EVM / Solana (separate settings; turning a field on for EVM doesn’t affect Solana)
Event-type tab — Swap / Transfer / Approval / Bridge / Contract / Failed (filtered by chain — bridges only on EVM, etc.)
Live preview — Telegram-style dark message bubble that updates as you toggle fields. Real-looking sample data, real layout.
Field toggles — grid of every field for the active event type, each with a checkmark indicating enabled
Number format — Compact ($1.2M, 5.67K tokens) or Full ($1,234,567.89)
Save bar — fixed at the bottom; appears when you have unsaved changes, with Discard / Save buttons

Settings are stored separately for EVM and Solana under the hood (evm_alert_fields, solana_alert_fields, evm_number_format, solana_number_format), so EVM-heavy users running compact and Solana-heavy users running full can coexist on one account.

Trading-link buttons

The buttons at the bottom of each alert (Dexscreener, DexTools, Photon, GMGN, Maestro, Bloom, Sigma, Etherscan, etc.) are individually toggleable. Some are EVM-only, some Solana-only, and some support both — the dashboard greys out the ones that don’t apply to the active chain.

What’s next

Customize alert formatting The full set of customization knobs in one place.

Notifications & Delivery Filter by min USD, mute chains, and understand the delivery layer.