---
name: salem-wallet
description: fomo user Salem1299534, his real Robinhood Chain wallet, the SCHIFFY "Received" rows, the salemwatch alert service, and the PENDING 3 Oct gift-fill signer patch for all 10 wallet bots. Read before any Salem, salemwatch or fake-buy alert question.
sources: [cowork, chat]
aliases: [Salem1299534, Salem, salemwatch, SALEM ALERT, SCHIFFY whale]
---
Fleet log in [[alert-bot-fleet-10]]. Same fomo-to-chain method as [[uberm-wallets-3]].

## 19 Sep 2026 — "Salem received a lot of SCHIFFY on his fomo wallet. Where did it come from? If we can identify the wallet where he accumulated it, track it plus his fomo wallet."
- [stated] Ben pasted Salem1299534's fomo SCHIFFY position: three "Received" rows on 18 Sep (11:57, 12:00, 12:09 Bangkok) plus two small buys, thesis about stock-pair memes and gold.
- **Answer: there is no separate accumulation wallet. The three "Received" rows are BUYS from his own wallet** routed through `0x0000000000001ff3684f28c67538d4d072c22734` (selector `0x2213bc0b`) instead of fomo's swap contract, so fomo booked them as transfers in. Txs `0x928a64358403e70df0fc515db83d85611e7e62eeffae46d72568a25f419588b7`, `0xc379eef0432c78fa0e7f44a42a42fcaedde8ca2edbbe2308e30336c1c29c588a`, `0xbbc7c1fb883c890437fae56197aac26e9c8d41b41cf2fcc6a160d1d2cd3b3e3a`, paid in WETH (25 + 10 + 2). Pass-through contract `0xaa61254627b7392b0bc922097b10eb0587db2be7` nets to zero.
- **Real wallet: `0xb8f305F27cCC406373De0082CC06Cb1D065504eA`** on Robinhood Chain (EIP-7702 delegated code `0xef0100…`, like every real fomo EVM wallet). Proven by exact amount match: #2 SCHIFFY holder with the same 20,262,442.23 the fomo book shows. fomo's printed ids for him (`0x5caab41d…`, Solana `ATuYTDdW6jTgor6bNLKkgxq4uRDnT7h8ZUvLZ8b1fNEj`) are internal, not on chain.
- SCHIFFY contract `0x42afa2124ca5a2b83898e46b2da9a190995b1e18` (Robinhood Chain, fomo networkId 4663).
- His Solana positions on fomo are tiny; real Solana wallet not hunted.
- **Rule confirmed again: a fomo "Received" row is not proof of another wallet. Check the tx `from` first; router buys show as Received.**

## salemwatch, live 19 Sep 2026 19:20 Bangkok
- `/opt/salemwatch/` on the droplet (tracker.py etc. copied from chjokkawatch, an ubermwatch clone; CHJOKKA → SALEM), unit `salemwatch.service` enabled + active, tag SALEM, poll 2s, wallet label "SALEM FOMO", `alert_transfers` false, `ignore_unpriced_tokens` false, min $100. In watchdog UNITS and the droplet botctl registry. Mac `~/botctl/registry.json` NOT yet updated.
- **Telegram: on its own bot `@saleemalert_bot` since 19 Sep 19:32 BKK**, `commands_enabled` true; Mac registry row added. (The token reached the chat once; rotation via `/revoke` + stdin is offered, not done.)
- ⚠ **20-21 Sep: HELIX $143, FURN $199, ROIJIN $1,311, WISP AI $0.10 landing in this wallet were NOT his buys** even though fomo's cash vault paid and its settlement contract delivered them. fomo never listed them on his profile. Real fomo fills run through router `0x039ec98a76f111092d4751365ff09dd2aec301e8`; these did not. salemwatch (and the other 9 wallet bots) now drop settlement deliveries without that router as `gift-fill`. Detail in [[alert-bot-fleet-10]]. His real fomo trades so far: SCHIFFY, OPEN, AI buys of $900-$2,400, small sells.

## 3 Oct 2026 (phone chat). "fix this alert and all other alerts so that these fake buys don't show up anymore." PATCH NOT YET APPLIED, needs the Mac/Cowork session.
- [stated] Ben pasted two Saleem Bot alerts, BOUGHT $116,441 of SI (block 77,862,768) and BOUGHT $503.58 of SICAT (block 78,756,944), called them fake buys and asked for the fix across all bots.
- Checked on the RPC. **SI was REAL**: tx `0x8e8bd7c7bca28181203b25ce9aec4d94b0e675e7de5693f33cfd9a391808bb9a`, `from` is Salem's own wallet, selector `0x2213bc0b` via `0x0000000000001ff3684f28c67538d4d072c22734`, paid 75.37 WETH. Told Ben to keep it.
- **SICAT was FAKE, and the 21 Sep gift-fill rule missed it**: tx `0xd8d003ab436e02e71bca5827dd01301f03602351b475d1b7f2fbbb3f5801c306`, sender `0x2eeea2926f6a831238fd0bec6e30ec01a80cfc46` (a stranger) called plain DEX router `0x89e5db8b5aa49aa85ac63f691524311aeb649eba` with `swapExactETHForTokens` (`0x7ff36ab5`, 0.218 ETH) and set the recipient to Salem's wallet. No fomo settlement contract, no fomo router, so classify() rule 3 (settlement counterparty + no router log) never fired.
- **PATCH TO APPLY on all 10 wallet bots (alfiewatch, chjokkawatch, dougwatch, ghostwatch, grailwatch, neetwatch, pixelalert, salemwatch, ubermwatch, unicorn)**: an inbound leg is a BUY only if (a) `tx.from` == the tracked wallet, or (b) an address in `config.settlement_routers` (fomo router `0x039ec98a76f111092d4751365ff09dd2aec301e8`) emitted a log in the tx. Every other inbound-only tx is `("transfer","gift-fill")` regardless of counterparty. Sells untouched. Replay both txs above with tg stubbed before restart: SI classifies as trade, SICAT drops. Same transport as 21 Sep (`/root/patch_gift.py`, `/root/test_gift.py`, base64 over ssh, `.bak-*` kept).
- Could not be applied from the phone chat (no droplet key in the cloud container). Ben was told to open Cowork and say "apply the gift-fill signer patch to the wallet bots".
- [stated] Ben: "make it a learning so that it never happens again." Done: standing signer rule in preferences, `isbuy.py` plus the numbered pre-delivery gate in [[wallet-bot-buy-gate]], verified on SI (his trade), SICAT (gift), SCHIFFY (his trade). The Cowork patch must pass that gate.