Agreed...
Before fireduck's this script (which also resides at http://foundry.electrum.org/server-peer-hashes.txt) was the only check.
The main point was not the failure of those connections but the "error" hash.
Topic: Electrum public servers with an incorrect hash (Read 1618 times)
Code:
Contacting 47 servers
39 servers could be reached
Connection failed: electrum.sky-ip.org:50002:s
Connection failed: 74m.de:40002:s
Connection failed: electrumaay7a3lc.onion:50002:s
Connection failed: gkn5ly5ytz2ekpdv.onion:50002:s
Connection failed: electrum.ofloo.net:50002:s
Connection failed: fdkbwjykvl2f3hup.onion:50002:s
Connection failed: electrum.dragonzone.net:50002:s
Connection failed: node.electrum.cz:50002:s
39 answers
blockchain.fh-biergarten.de:50002:s 392479 42a17f653f0312da5a7de164f3fb783d80250baf42ee087998c489122df51e7e error
39 servers could be reached
Connection failed: electrum.sky-ip.org:50002:s
Connection failed: 74m.de:40002:s
Connection failed: electrumaay7a3lc.onion:50002:s
Connection failed: gkn5ly5ytz2ekpdv.onion:50002:s
Connection failed: electrum.ofloo.net:50002:s
Connection failed: fdkbwjykvl2f3hup.onion:50002:s
Connection failed: electrum.dragonzone.net:50002:s
Connection failed: node.electrum.cz:50002:s
39 answers
blockchain.fh-biergarten.de:50002:s 392479 42a17f653f0312da5a7de164f3fb783d80250baf42ee087998c489122df51e7e error
The server checking doesn't seem to have a tor connection. The .onion ones are up.
Code:
Contacting 47 servers
39 servers could be reached
Connection failed: electrum.sky-ip.org:50002:s
Connection failed: 74m.de:40002:s
Connection failed: electrumaay7a3lc.onion:50002:s
Connection failed: gkn5ly5ytz2ekpdv.onion:50002:s
Connection failed: electrum.ofloo.net:50002:s
Connection failed: fdkbwjykvl2f3hup.onion:50002:s
Connection failed: electrum.dragonzone.net:50002:s
Connection failed: node.electrum.cz:50002:s
39 answers
blockchain.fh-biergarten.de:50002:s 392479 42a17f653f0312da5a7de164f3fb783d80250baf42ee087998c489122df51e7e error
39 servers could be reached
Connection failed: electrum.sky-ip.org:50002:s
Connection failed: 74m.de:40002:s
Connection failed: electrumaay7a3lc.onion:50002:s
Connection failed: gkn5ly5ytz2ekpdv.onion:50002:s
Connection failed: electrum.ofloo.net:50002:s
Connection failed: fdkbwjykvl2f3hup.onion:50002:s
Connection failed: electrum.dragonzone.net:50002:s
Connection failed: node.electrum.cz:50002:s
39 answers
blockchain.fh-biergarten.de:50002:s 392479 42a17f653f0312da5a7de164f3fb783d80250baf42ee087998c489122df51e7e error
blockchain.fh-biergarten.de
electrum.mindspot.org
are showing incorrect
electrum.mindspot.org
are showing incorrect
Updated...
dashoernchen.de
ulrichard.ch
dashoernchen.de
ulrichard.ch
Updated...
electrum-btc.ddns.net
electrum-btc.ddns.net
Now it is arunelec.cloudapp.net that has a bad hash...
@JWU42
So... over the past week muon.electrum.silvenga.com was rebuilt twice (Docker container), on both occasions I downloaded from Foundry and checked the hashes. The server receives connections from clients and there are no errors in the logs. I personally use that server and all functions appear to work.
Is the absence of the hostname in the below list evidence that there is an incorrect hash? How would I manually check it for consistency?
So... over the past week muon.electrum.silvenga.com was rebuilt twice (Docker container), on both occasions I downloaded from Foundry and checked the hashes. The server receives connections from clients and there are no errors in the logs. I personally use that server and all functions appear to work.
Is the absence of the hostname in the below list evidence that there is an incorrect hash? How would I manually check it for consistency?
Code:
Contacting 34 servers
Connection failed: electrum.drollette.com:50002:s
Connection failed: electrum.thwg.org:50002:s
Connection failed: electrum-server.ninja:50002:s
Connection failed: scytale.row33.com:50002:s
Connection failed: btc.medoix.com:50002:s
timeout
27 servers could be reached
27 answers
kirsche.emzy.de:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.hoodquarters.com:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
erbium1.sytes.net:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum3.hachre.de:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.plutusnode.com:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.netpros.co:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
us.electrum.be:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.no-ip.org:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
Electrum.hsmiths.com:995:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
elec.luggs.co:443:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
wirerocks.infoha.us:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
ecdsa.net:110:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
188.165.218.18:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
green-gold.cloudapp.net:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.badass.sx:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.mindspot.org:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
btc1.electrum-servers.us:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.kltrst.se:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.dragonzone.net:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
jwu42.hopto.org:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.0x0000.de:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
VPS.hsmiths.com:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.freeplayed.com:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum0.electricnewyear.net:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.bitfuzz.nl:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.sky-ip.org:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
ELECTRUM.jdubya.info:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
Connection failed: electrum.drollette.com:50002:s
Connection failed: electrum.thwg.org:50002:s
Connection failed: electrum-server.ninja:50002:s
Connection failed: scytale.row33.com:50002:s
Connection failed: btc.medoix.com:50002:s
timeout
27 servers could be reached
27 answers
kirsche.emzy.de:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.hoodquarters.com:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
erbium1.sytes.net:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum3.hachre.de:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.plutusnode.com:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.netpros.co:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
us.electrum.be:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.no-ip.org:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
Electrum.hsmiths.com:995:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
elec.luggs.co:443:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
wirerocks.infoha.us:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
ecdsa.net:110:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
188.165.218.18:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
green-gold.cloudapp.net:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.badass.sx:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.mindspot.org:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
btc1.electrum-servers.us:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.kltrst.se:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.dragonzone.net:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
jwu42.hopto.org:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.0x0000.de:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
VPS.hsmiths.com:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.freeplayed.com:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum0.electricnewyear.net:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.bitfuzz.nl:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
electrum.sky-ip.org:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
ELECTRUM.jdubya.info:50002:s 366842 d8f42e2f064ee2d01948749becc46c8d5aa58c96899d291f84ddb5294359cca2 ok
Thomas had a bot that would kick off servers from IRC with an incorrect hash (this would then remove them from the public server list). That bot has been down for a few weeks and I am unsure of its status.
Thanks for your quick reply. Now that I know how to verify a server, I don't need the "kicking" bot now. This "peer hash" file is already so useful, and it updates every 10 minutes. More Electrum users should know about this.
medUSA,
The script is in the linux client. I can't recall the name but think it is called "peers"
Thomas had a bot that would kick off servers from IRC with an incorrect hash (this would then remove them from the public server list). That bot has been down for a few weeks and I am unsure of its status.
The script is in the linux client. I can't recall the name but think it is called "peers"
Thomas had a bot that would kick off servers from IRC with an incorrect hash (this would then remove them from the public server list). That bot has been down for a few weeks and I am unsure of its status.
http://foundry.electrum.org/server-peer-hashes.txt
EagleTM runs a cron job that uses a script that looks for hash errors.
EagleTM runs a cron job that uses a script that looks for hash errors.
When I run electrum, I can't tell which server is trustworthy. I have always wanted to know how to check the validity of the Electrum servers. This "foundry" bot seek out discrepancies between the servers!
If any servers are found to have incorrect hash, does that imply transaction data from that server could be wrong? If so, should the server be automatically removed from the server list in Electrum? I still see "muon.electrum.silvenga.com" server on my list.
muon.electrum.silvenga.com still shows an incorrect hash 
I generated the muon.electrum.silvenga.com DB from scratch and see no issues in the logs. How did you check for the hash mismatch?
http://foundry.electrum.org/server-peer-hashes.txt
EagleTM runs a cron job that uses a script that looks for hash errors. Your will see your site still listed with an incorrect hash.
The DB corruption happens during an ungraceful shutdown (normally). You will need to grab a DB dump from the foundry.
Updated list just shows the following with an incorrect hash...
bitcoin.epicinet.net
I generated the muon.electrum.silvenga.com DB from scratch and see no issues in the logs. How did you check for the hash mismatch?
The following servers all have an incorrect hash (i.e., DB corruption of some sort). Please download a new DB from https://foundry.electrum.org
UPDATED - September 3, 2015
electrum-btc.ddns.net
dashoernchen.de
ulrichard.ch
UPDATED - September 3, 2015
electrum-btc.ddns.net
dashoernchen.de
ulrichard.ch
Jump to: