1 Commits (6c8d9ad2db649cd80f5d35d2428fa875e760f253)

Author	SHA1	Message	Date
Strycher	977af98069	fix(#250): refuse to block your own node ... Blocking yourself silently hid your own traffic with no visible cause, and because blocks are offloaded to the radio it was pushed there and could be pulled back by the connect-time union. BlockService gains a selfKeyHex, injected by the connector when the self key is learned and cleared on disconnect. Every add path refuses it (block, importKeys, maybePromote) — importKeys specifically, so a self-block already on the radio cannot be re-imported. setSelfKey also heals an existing self-block and pushes REMOVE, covering the case where the union pull lands before self-info arrives. Contacts and discovery sheets hide the Block option for your own node. Per Gemini review: heal on an unchanged key too (an early return would strand a self-block introduced after the key was known), and order setSelfKey so all in-memory state settles synchronously, keeping callers consistent even though the connector fires it unawaited. Adds test/services/block_service_test.dart — the first coverage for BlockService (10 tests). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 days ago