HUGE problem with anyone new wanting to use darkcoin... and needs to be addressed.

LittleFinger

LittleFinger

Member
Im going to keep this short, because I have already posted on it, and since have had more troubles with the issues that seem to not be getting fixed.

I introduced 2 new people to darkcoin, they downloaded the wallets, and had the same problem. Both could not find a block source until I gave them the node list to place in their conf files.

That is ridiculous, that this is still a problem. Something so small keeping new people from easily enjoying becoming part of the drk community.

This needs to get sorted immediately in my opinion, and i think all would agree. DRK's success is not only its features, but the ease of which someone can start using it.

Whatever the problem is, its not just local to my machines, and even though its such a small thing to anyone who can troubleshoot, its a HUGE problem in regards to a wide audience adoption.
 
I haven't got this problem whereas I'm IT noob.

I think your problem isn't due to darkcoin wallet but maybe cause by your isp (p2p traffic) or your firewall (windows or hardware).

Have you try updating wallet with another coin?
 
I know this problem too. It really depends on the Firewall/Router you are behind. I tried running several clients in many places. Sometimes it works sometime it does not. But you are right, that issue should be addressed. It think the easiest would be to provide a zip/tar.gz which holds (darkcoind, darkcoin-qt, darkcoin.conf and maybe the peers.dat ) and the best would be a debian (for most linuxes ) and exe for windows.
If more people think this is an severe issue and the core team has no resources to do it I could work on that.
 
LittleFinger said:
Im going to keep this short, because I have already posted on it, and since have had more troubles with the issues that seem to not be getting fixed.

I introduced 2 new people to darkcoin, they downloaded the wallets, and had the same problem. Both could not find a block source until I gave them the node list to place in their conf files.

That is ridiculous, that this is still a problem. Something so small keeping new people from easily enjoying becoming part of the drk community.

This needs to get sorted immediately in my opinion, and i think all would agree. DRK's success is not only its features, but the ease of which someone can start using it.

Whatever the problem is, its not just local to my machines, and even though its such a small thing to anyone who can troubleshoot, its a HUGE problem in regards to a wide audience adoption.
Click to expand...

Hi,

we are sorry you had issues downloading the blockchain - i worked on this with Evan and we resolved it. The next bugfix version we will be releasing will be able to bootstrap without any additional addnode-lines in the conf-file - just like you are used to from bitcoin and litecoin.

Sorry for the inconvenience.
 
vertoe said:
Just curious, why only adding 2 seednodes?
And arent .qa and .io both the same one?
Isnt that a single point of failure?
Click to expand...

Answer is simple: These are not 'nodes' - they are dnsseeder for the DNS-zones 'dnsseed.darkcoin.qa' and 'dnsseed.darkcoin.io'

(Note: darkcoin.io belongs to Evan, darkcoin.qa belongs to me - they are distinct)

Behind these zone-entries there is actually a cluster of 5 machines as per now (3 mainnet, 2 testnet - and Evan will add some more on his side too), answering queries for node-adresses.

You can test it with dig command

Code: 
$ dig +short dnsseed.darkcoin.qa
31.209.28.22
46.165.208.136
54.81.226.238
54.82.138.97
54.89.158.2
54.186.141.83
54.255.148.0
68.106.3.49
80.240.136.242
82.33.73.34
85.214.203.169
87.121.52.38
87.212.170.90
91.156.100.191
94.255.243.236
98.250.247.209
107.170.235.189
108.61.197.56
108.61.223.74
112.175.123.82
128.199.168.215
162.243.63.93
162.243.118.225
188.226.230.170
192.99.9.229
200.108.143.123
24.8.192.200

EDIT: BTW: Same applies to testnet, no addnode entry needed anymore :smile:

Code: 
$ dig +short testnet-seed.darkcoin.qa
54.178.159.204
85.23.41.89
85.23.45.36
112.175.123.82
112.175.123.94
184.73.179.148
188.226.243.116
198.50.148.87
 
Last edited by a moderator:
flare said:
Answer is simple: These are not 'nodes' - they are dnsseeder for the DNS-zones 'dnsseed.darkcoin.qa' and 'dnsseed.darkcoin.io'

(Note: darkcoin.io belongs to Evan, darkcoin.qa belongs to me - they are distinct)

Behind these zone-entries there is actually a cluster of 5 machines as per now (3 mainnet, 2 testnet - and Evan will add some more on his side too).

You can test it with dig command

Code: 
$ dig +short dnsseed.darkcoin.qa
31.209.28.22
46.165.208.136
54.81.226.238
54.82.138.97
54.89.158.2
54.186.141.83
54.255.148.0
68.106.3.49
80.240.136.242
82.33.73.34
85.214.203.169
87.121.52.38
87.212.170.90
91.156.100.191
94.255.243.236
98.250.247.209
107.170.235.189
108.61.197.56
108.61.223.74
112.175.123.82
128.199.168.215
162.243.63.93
162.243.118.225
188.226.230.170
192.99.9.229
200.108.143.123
24.8.192.200

EDIT: BTW: Same applies to testnet, no addnode entry needed anymore :smile:

Code: 
$ dig +short testnet-seed.darkcoin.qa
54.178.159.204
85.23.41.89
85.23.45.36
112.175.123.82
112.175.123.94
184.73.179.148
188.226.243.116
198.50.148.87
Click to expand...

Excellent news. I realize the issue is simple to resolve, but for the general public, this may have cost us some potential users already.

I am glad you guys have resolved it though. I wouldnt want this issue to be a persons first encounter with the wallet.
 
LittleFinger said:
Excellent news. I realize the issue is simple to resolve, but for the general public, this may have cost us some potential users already.

I am glad you guys have resolved it though. I wouldnt want this issue to be a persons first encounter with the wallet.
Click to expand...

I absolutely agree: Nothing worse for the perception than a wallet which is not running out-of-the-box.
 
flare said:
Dynamic dnsseeder is returning a list of 20 nodes (out of known pool) in a round robin fashion. So the peers are not overloaded by "getblockchain"-requests anymore.
Click to expand...
Damn, I love technology, everything is possible :)
 
mattmct said:
I run http://x11p2p.com:7903/ . How can I strengthen the network? :)
Click to expand...

Start off with adding two entries to your DNS-zone

one NS record
Code: 
dnsseed.x11p2p.com.    7200    IN      NS      seed1.x11p2p.com.
one A record
Code: 
seed1.x11p2p.com.       1800    IN      A       23.23.186.131     <--- replace with IP of machine you want to run the seeder on, port 53/UDP needs to be open

As we don't want to run services as root, you will need the following iptables-rule on your seeder machine to redirect port 53/UDP to port 5353/UDP
Code: 
dnsseed@ip-10-65-166-48:~$ sudo iptables -t nat -A PREROUTING -p udp --dport 53 -j REDIRECT --to-port 5353

After you managed DNS and iptables setup, checkout the darkcoin-seeder from https://github.com/nightlydarkcoin/darkcoin-seeder
Code: 
dnsseed@ip-10-65-166-48:~$ git clone https://github.com/nightlydarkcoin/darkcoin-seeder.git

compile
Code: 
dnsseed@ip-10-65-166-48:~$ cd darkcoin-seeder ; make ; strip dnsseed

and run
Code: 
dnsseed@ip-10-65-166-48:~/darkcoin-seeder$ ./dnsseed -h dnsseed.x11p2p.com -n seed1.x11p2p.com -p 5353

You will get this type of output from dnsseed
Code: 
[14-07-08 05:01:03] 910/12392 available (11861 tried in 998s, 4 new, 527 active), 431 banned; 146 DNS requests, 37 db queries

You can test if your seeder is working properly and reachable from remote, with dig command from another machine
Code: 
dnsseed@ip-10-xx-xxx-xx:~$ dig +short @seed1.x11p2p.com dnsseed.x11p2p.com

This should return a different list of node IPs each time.

If you are done i will let you run the service for some days, and if proven reliable we will add your seeder to the official seeder list in the client :)
 
Last edited by a moderator:
flare said:
BTW: If you are in control of the DNS of your domain (qhor.net) you are free to join and run a dnsseeder - will strengthen the network :)
Click to expand...
Apprently I'm not, using this as a dummy domain and have to pay $5 per dns change at some really crappy hoster.
I'm usually working with IPs only lol....
 
flare said:
Never mind, maybe mattmct will jump in :)
Click to expand...

Would love to! Cheers for the detailed instructions, much appreciated flare. I'll see if I can do this, unfortunately I think I might currently be in the same situation pf vertoe, I'm not currently running my own dns server / bind on that VPS, as I do with most of my business servers. I'll look into it though! Cheers
 
You must log in or register to reply here.
Back
Top