fetch_relay_dms connected to all three CLAIM_RELAY_URLS (the Minibits relay
plus the two public fallbacks, relay.damus.io and nos.lol) on every 8s poll,
even though the module's own docs already described RELAY_URL as the
primary with the public relays meant only as a fallback. In practice this
meant 3 fresh WebSocket connections every poll and broadcasting the wallet's
derived Nostr pubkey's DM activity to two public relays it didn't need to
touch.
- Query RELAY_URL alone first; only add and query the public fallbacks when
it's unreachable (via try_connect_relay). Happy path is now one connection
per poll instead of three, and the public relays only see this pubkey's
traffic when the primary is actually down.
- Page through the DM filter instead of a single limit(200) fetch: a relay
returns the newest `limit` events for a filter, so a backlog of more than
200 DMs since the last poll (e.g. a long-offline node) silently skipped the
older ones forever, since `since` never advanced past them. Capped at 5
pages so a relay that never stops returning full pages can't hang the poll.
- Moved the ensure_mint_accepted doc comment back above its own function —
it had been glued onto fetch_relay_dms by an earlier edit.
- Timestamp::as_u64() -> as_secs() to clear the deprecation warning.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EZnFgeUBKY5UAfyJFsYccS
ssmithxandClaude Sonnet 5
489995ced0