Transaction

5a5a525950d9cb0293184fddb036bb1dcf48e91baff8084ff8e40fb1bebfe29f
Timestamp (utc)
2024-03-22 01:24:37
Fee Paid
0.00000018 BSV
(
0.00210907 BSV
-
0.00210889 BSV
)
Fee Rate
10.14 sat/KB
Version
1
Confirmations
93,721
Size Stats
1,775 B

2 Outputs

Total Output:
0.00210889 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMò<div class="post">Anyone notice, that for Windows Clients anyway, when you connect a bunch of other clients to it manually (through the -connect option) that if you go over 8, the windows client ends up cutting out the "outside world" connections and stick with the original 8 or more internal machines thinking that it's the entire network?<br/><br/>I never noticed this since I use a Linux client to funnel all my PCs to the outside world, but I tried it with a Windows client and noticed that at first, it had about 10 connections, then after adding another 50 clients internally that connect directly to it, the number would eventually drop down to just "internal clients" only.<br/><br/>When this happens, the block count doesn't increment anymore, basically the Windows client has separated itself from "the network" and all the other clients all think that they are the entire network now. If I do a "netstat -a -n" on the windows client, I can see it's only connected to the Internal clients and the IRC bootstrap channel and basically doesn't to connect to anyone else on the outside world. You know it's happening because the block count starts to fall behind of what is really going on outside of your local network (Internet for the rest of the world)<br/><br/>It's kind of a self-collapsing loop? Doesn't seem to affect Linux clients though, they will happily connect to and be connected to about as many as it can handle. I could see this is kind of a DoS on windows clients if someone was evil enough.</div> text/html
    https://whatsonchain.com/tx/5a5a525950d9cb0293184fddb036bb1dcf48e91baff8084ff8e40fb1bebfe29f