<lightlike>
so they would reject all blocks-only connections they have as inbounds quickly?! is this dependent on v2 transport (BIP324) being used?
Cory58 has quit [Quit: Client closed]
Cory58 has joined #bitcoin-core-dev
<eugenesiegel>
I wrote a light client so it doesn't have v2 transport yet and doesn't do blocks-only connections (so I can't be certain if blocks only connections would be rejected). I can look at the version messages and see if maybe there's a correlation with nServices
<lightlike>
i just mentioned those because with block-relay-only connections (pings every 2 minutes, blocks every 10 minutes, no addr or tx relay) there should be frequent intervals where no messages are exchanged for more than 30s.
zeropoint has quit [Quit: leaving]
eval-exec has joined #bitcoin-core-dev
<eugenesiegel>
I did a little more digging. Each node offers the exact same service flags of "SFNodeNetwork|SFNodeBloom|SFNodeNetworkLimited|0x800" and they all have the same block height of 882,161
<eugenesiegel>
I think the tip at measurement time was 882,199
<sipa>
0x800 = NODE_P2P_V2
<sipa>
Weird that they're offering NODE_BLOOM; that's not on in Bitcoin Core by default
Josemoe21 has joined #bitcoin-core-dev
Josemoe45 has joined #bitcoin-core-dev
Josemoe45 has quit [Client Quit]
Josemoe21 has quit [Client Quit]
agentcasey_ has joined #bitcoin-core-dev
agentcasey has quit [Ping timeout: 245 seconds]
agentcasey_ has quit [Remote host closed the connection]
agentcasey has joined #bitcoin-core-dev
<eugenesiegel>
I found the BLOOM weird, the addresses are grouped into about seven /16 blocks
jonatack has joined #bitcoin-core-dev
jarthur has joined #bitcoin-core-dev
jonatack has quit [Read error: Connection reset by peer]
jonatack has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 260 seconds]
jonatack has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 272 seconds]
jonatack has joined #bitcoin-core-dev
vasild has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 272 seconds]
<sipa>
is this linkinglion or some spy?
kevkevin has quit [Remote host closed the connection]
jarthur has quit [Ping timeout: 248 seconds]
jarthur has joined #bitcoin-core-dev
cmirror has quit [Remote host closed the connection]
cmirror has joined #bitcoin-core-dev
<eugenesiegel>
I don't think its linkinglion, but I do think they're probably all the same entity. I tested on my mainnet node and v2 handshakes to them fail and are downgraded to v1 handshakes and then fail 30s later. The nodes ignore the sent feefilter and send INV messages always with 50 items and duplicate some of the items in the set. They also have other
<eugenesiegel>
idiosyncrasies like not responding to GETDATA
<eugenesiegel>
They also duplicate hashes _across_ different INVs and waste bandwidth. The main IP ranges are 139.162.0.0/16, 172.104.0.0/16, 172.105.0.0/16, 172.232.0.0/16, 172.233.0.0/16, 172.234.0.0/16, and 172.236.0.0/16 if anybody is curious. I guess I answered my own question about these nodes since this behavior doesn't indicate a normal 27.0 satoshi
<eugenesiegel>
node
flow has quit [Ping timeout: 265 seconds]
Guest46 has joined #bitcoin-core-dev
Guest46 has quit [Client Quit]
<lightlike>
yes, probably not core nodes, but definitely interesting, 800 is not nothing!
flow has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 252 seconds]
mcey has quit [Remote host closed the connection]
robobub has quit [Quit: Connection closed for inactivity]
mcey has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 248 seconds]
robobub has joined #bitcoin-core-dev
S3RK_ has joined #bitcoin-core-dev
S3RK has quit [Ping timeout: 244 seconds]
<b10c>
seeing a few of these connections too with the same characteristics you mention
Guyver2 has joined #bitcoin-core-dev
jarthur has quit [Quit: jarthur]
BlockSmith has joined #bitcoin-core-dev
BlockSmith has quit [Client Quit]
BlockSmith has joined #bitcoin-core-dev
BlockSmith has quit [Quit: Ping timeout (120 seconds)]
BlockSmith has joined #bitcoin-core-dev
<Sjors[m]>
Seeing spam approvals from Armss9936 on Github.
<bitcoin-git>
[bitcoin] furszy opened pull request #31794: wallet: abandon orphan coinbase txs, and their descendants, during startup (master...2025_wallet_abandon_coinbase_during_startup) https://github.com/bitcoin/bitcoin/pull/31794
jonatack has joined #bitcoin-core-dev
BUSY has quit [Ping timeout: 276 seconds]
zeropoint has joined #bitcoin-core-dev
BUSY has joined #bitcoin-core-dev
jespada has joined #bitcoin-core-dev
jarthur has joined #bitcoin-core-dev
jonatack has quit [Read error: Connection reset by peer]
dongcarl6 has joined #bitcoin-core-dev
dongcarl has quit [Read error: Connection reset by peer]
<eugenesiegel>
> seeing a few of these connections too with the same characteristics you mention
<eugenesiegel>
They respond to GETADDR and respond with 256 addresses of all of their addresses, so I think all of their nodes are pretty easy to identify. I think it's some sort of tx broadcasting / relay infrastructure
<eugenesiegel>
* 256 of their addresses
eugenesiegel has quit [Quit: Client closed]
eugenesiegel has joined #bitcoin-core-dev
PaperSword1 has joined #bitcoin-core-dev
apex944 has quit [Quit: Client closed]
PaperSword has quit [Read error: Connection reset by peer]
PaperSword1 is now known as PaperSword
eugenesiegel has quit [Quit: Client closed]
eugenesiegel has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
preimage has joined #bitcoin-core-dev
Talkless has quit [Quit: Konversation terminated!]
Guest16 has joined #bitcoin-core-dev
Guest16 has quit [Client Quit]
jonatack has quit [Ping timeout: 244 seconds]
jonatack has joined #bitcoin-core-dev
pyth has quit [Ping timeout: 244 seconds]
pyth has joined #bitcoin-core-dev
<fjahr>
Can someone kick the CI in #31384? Multiple jobs have failed due to a docker.io issue (too many requests).
pyth has quit [Ping timeout: 260 seconds]
pyth has joined #bitcoin-core-dev
jespada has quit [Quit: My Mac has gone to sleep. ZZZzzz…]