People who can use docker containers : here is the automated build for the daemon (node). I will help the network too. The trimmed image based on ubuntu 16.04 takes only 136MB. Running a node at this time need at least 2.2Go free on hard drive to store the blockchain but it will grow. For example, monero blockchain use today 33Go
Please allow 1 or 2 hours for the image to be automatically build. The full description will be automatically filled when build is done
For the records, my pool
https://ird.uvac.fr has been ddosed since 6 hours !!! LOL !!! (we lost 2 blocks - Orphaned) but we feel lucky now.
It's ok now.Thank you, nice guide.
But i should back to our question with seeds list(i ask in private).
Seed nodes, which builded in source code are not correct or works long time ago yet, this is my investigation:
./src/CryptoNoteConfig.h
const char* const SEED_NODES[] = {
"108.61.196.136:12007",
"45.32.71.24:12007",
"45.63.119.236:12007",
"13.92.140.240:12007",
"52.14.88.78:12007",
"66.42.209.128:12007",
"74.218.51.222:12007"
};
This looks like "default peers" which used automatically, but not one of this IP list actual right now, look this, i will check step by step.
My node works with --log-level=4, like i see this is maximum debug mode.
I collect some data into logfile and now cat operate with this info:
# cat iridiumd.log |grep -i 108.61.196.136
3bc09b4816649dad 108.61.196.136:12007 last_seen: d33.h03.m27.s46
3bc09b4816649dad 108.61.196.136:12007 last_seen: d17.h11.m59.s20
5201146fe62a0889 108.61.196.136:12007 last_seen: d52.h14.m06.s28
3bc09b4816649dad 108.61.196.136:12007 last_seen: d27.h14.m34.s27
3bc09b4816649dad 108.61.196.136:12007 last_seen: d17.h13.m45.s53
# cat iridiumd.log |grep -i 45.32.71.24
d7525d75268dfa36 45.32.71.24:12007 last_seen: d33.h01.m03.s52
6da4ab783fc6bac1 45.32.71.24:12007 last_seen: d52.h12.m32.s29
d7525d75268dfa36 45.32.71.24:12007 last_seen: d28.h04.m27.s06
d7525d75268dfa36 45.32.71.24:12007 last_seen: d17.h11.m59.s27
6da4ab783fc6bac1 45.32.71.24:12007 last_seen: d53.h14.m43.s55
# cat iridiumd.log |grep -i 45.63.119.236
d5ca329b33f56127 45.63.119.236:12007 last_seen: d33.h08.m03.s53
dd5a73c50e97aec9 45.63.119.236:12007 last_seen: d52.h14.m06.s28
dd5a73c50e97aec9 45.63.119.236:12007 last_seen: d53.h13.m54.s18
d5ca329b33f56127 45.63.119.236:12007 last_seen: d33.h08.m04.s53
d5ca329b33f56127 45.63.119.236:12007 last_seen: d35.h04.m51.s39
# cat iridiumd.log |grep -i 74.218.51.222
cce8bae311d2085c 74.218.51.222:12007 last_seen: d10.h13.m30.s28
cce8bae311d2085c 74.218.51.222:12007 last_seen: d10.h13.m30.s24
cce8bae311d2085c 74.218.51.222:12007 last_seen: d10.h12.m51.s06
cce8bae311d2085c 74.218.51.222:12007 last_seen: d10.h07.m37.s27
cce8bae311d2085c 74.218.51.222:12007 last_seen: d10.h07.m37.s04
Other 3 ips not matched yet in logs, this mean this nodes or never exist or die long time ago.
So, what this mean ? When you setup node your cant reach any of peer.

Sure, you can use option "--add-peer" when you start your node, but how new peoples who start nodes know IPs which need use? I just can get list of peers when
stevebrush take me IP of his own node and port, then i can connect to network, sync chains and get full list of current peers... but i have no idea how new peoples will do that.
Since today i will collect and analyze logfile for get list of most stable nodes which then developers need put into source code, i hope one week its good time, i found more then 60 nodes now, but part of this nodes can be "test node" or something else.... i will collect data and then check which ips used more time then rest... So, i hope this help.
If you want start node today, you can use my node as peer, just add this into your start cmd
--add-peer 104.234.216.118:12007.
Maybe someone who read this forum and have stable node will put his IP there.
Also, i done with node without docker, install into my OS, CentOS 7. If someone need this i can help.
Thanks,