There are still several of the old clients running in the wild. We are trying to contact anyone who maybe working with an old client to get them shut down or updated to the latest version. EMD is 15 months old, so there are a lot of old clients out there on sites who are blissfully unaware that there have been any changes.
And many more changes are coming... for the better!
I'm constantly checking my peers so that I can update the addnode list in the OP with good peers... Matter of fact, getting ready to do that right now. If anyone notices any nodes that are updated and not in the OP, post them or send a PM and I will get them added.
To pick out good nodes - In the wallet console type: getpeerinfo Then, in the peer list, look for peers with: "addr": "xxx.xxx.xx.x:12128", "version" : "6002", "subver" : "8.2.1" or "subver" : "8.3.1"
We are working on banning older versions of the client in the next update. I tried in 8.3.1, but could never get the wallet to find any peers. I was running on fumes at the time... Since I have somewhat recovered and regained a bit of my energy (and sanity); after giving the code a fresh look, we should get things ironed out in the next client update.
Yeah, I've been fooling with it all damned day.. I'm setting up iptables rules to drop the bad nodes.. So far I've seen a digitalcoin and a worldcoin node connected, as well as some others that didn't have any identifying info. I played with the source a little bit and changed it to accept connections from 60001 minimum, but I don't think that had the desired effect since other interfering nodes are showing differently formatted version info. I'm going on fumes as well man, don't feel bad
Anyway, I've just left it alone to try and resync for several hours, using these as my added nodes (threw in the multipool's address as well).
connect=188.134.72.213
connect=107.170.99.188
connect=92.238.186.27
connect=62.44.226.18
connect=70.180.113.106
I thought using "connect" would limit it to only using those nodes to sync, without fetching their connected nodes and connecting with them as well, but I have 20 connections, but now seems to actually be syncing (slowly). Earlier, it'd sync a while, then stop, then load some more and stop, the multipool didn't seem to be suffering though I haven't mined blocks yet to confirm, it has been in sync with the block explorer the entire time. I was kind of suspecting maybe some DDoS mischief going on, but if it is I don't think it's hitting my server directly or my iptables would have been fishy. So IDK.
Ok, before I went on much further I decided to have a better look since I've kinda left it alone the last couple hours.... getpeerinfo is now showing me ONLY 0.8.3.1 clients now, which is strange because I've mixed and matched addnodes, -noirc, connect, etc. for hours and hours and always ended up seeing connected peers that very obviously weren't EMD. I'm nearly brain dead right now so I may just be imagining things, but I'm thinking that some sort of shenanigans may have been afoot, possibly some sort of DDoS or clusterfuck naughty node attack against our blockchain, or just a horrible accident with misbehaving nodes going completely awry. Feel free to tell me I'm wrong, or stupid, or both. I'd definitely recommend for a future version a complete protocol overhaul, paying careful attention to all the bits that'll keep our blockchain from mingling with any others. Some dns seed nodes would definitely be helpful as well as phasing out the old IRC peering stuff (didn't even bother poking my head into the IRC stuff to see if anything was amiss).
I just find it very strange that earlier, no matter what settings I was using, I still ended up with all sorts of crazy nodes connected but all of a sudden I only have current version nodes connected. I deleted the entire blockchain several times and kept getting all kinds of crazy stuff in the log, though I didn't have the presence of mind to snip some of it, I'll definitely hold on to the newest log in case it'll be of any use later on.
So far on the multipool, we're running about 1MH on EMD, got 2 confirmed blocks and no orphans, so that's a good sign. I'll be keeping an eye on it and will have the MPOS pool back up and running as soon as humanly possible, but it's syncing very slowly so not sure if I can stay awake long enough, lol.
Let me know if there's anything I can do to help out, and it shall be done!
Anyone having issues with naughty nodes, use this to drop all packets to/from bad nodes (make sure you replace the IP in both the input and output rules):
sudo iptables -A OUTPUT -d 104.131.142.198 -j DROP
sudo iptables -A INPUT -d 104.131.142.198 -j DROP
sudo apt-get install iptables-persistent
/etc/init.d/iptables-persistent save
