Bitcoin full node and query server

Sep 3, 2026

View in context in the libbitcoin Slack #general mirror.

evoskuil22:29

I'm seeing these types of messages now:

2026-09-03T22:00:45Z.5 Invalid headers payload from [74.138.71.14:8333] with bytes (000dfdd0070000032018fb3ddd3ac22973b6b9bb02e04323f15fc610f155da000000000000000000003a1d4f36eb09fe7700d59b90c0851e479fe7986c5f59d1cb6a63dd21adc72e0b514c746ad43a0217823085fa000020b426bec7d77c250698748e1e3e6f7d790941a2407ab58ef101000000000000000000a16b2dbc21347f5e6424c746d0b73c97a46f0d547ac2944315c9da209d22afddc34c746ad43a02178ccd50c10000c0a623fdb0cc955f1b0ab6d839a78f065c8299a19765fefe28000000000000000000004ae1b5ca5a763bd538d781ad0e51cf59f96b9ce97875a636d6fa42a259955313854d746ad43a02174298d2e50000c01429c9b776...)

This is another shitcoin operating on the bitcoin network. Fortunately it's identifying itself, so can be masked out using our shitcoin flags: 00010000000000000000000010110000

[peer]
invalid_services = 268435632 # 4 shitcoins

(edited)