Has anyone else problems with syncing the das wallet? I can't start my MN because of it :/. It can't find any blocksources.
Are there some addnode IPs to fix this?
NovaExchange lists the addnodes they use at the bottom of the DAS_BTC trading page:
https://novaexchange.com/market/BTC_DAS/Current addnodes listed:
addnode=104.207.145.22:9399
addnode=107.174.69.220:9399
addnode=137.74.157.36:9399
addnode=141.134.124.215:9399
addnode=154.16.7.191:9399
addnode=185.137.97.15:9399
addnode=185.81.167.100:9399
addnode=192.99.70.176:9399
addnode=195.181.241.86:9399
addnode=195.181.243.208:9399
addnode=212.47.243.63:9399
addnode=24.91.171.132:9399
addnode=35.184.44.214:9399
addnode=35.197.67.60:9399
addnode=45.32.169.164:9399
addnode=45.32.169.70:9399
addnode=45.32.235.64:9399
addnode=45.76.13.77:9399
addnode=45.77.115.157:9399
addnode=47.209.22.141:9399
addnode=5.79.97.229:9399
addnode=51.15.46.181:9399
addnode=52.23.180.74:9399
addnode=75.130.162.248:9399
addnode=78.106.135.194:9399
addnode=85.214.153.21:9399
addnode=89.239.193.68:9399
addnode=94.176.238.166:9399
addnode=98.172.83.52:9399
addnode=98.172.83.59:9399
addnode=98.226.11.139:9399
Using THESE addnodes as well as adding the longest ENABLED masternodes on the masternode tab (if not already listed above), I have had NO problems at all using this das.conf:
rpcuser=[username]
rpcpassword=[password]
externalip=[publicIP]
rpcport=9399
#listen=1
port=9399
server=1
daemon=1
logips=1
maxconnections=24
banscore=5000
bantime=86400
#
masternode=1
masternodeaddr=[publicIP]:9399
masternodeprivkey=[key]
I tend to have 20 connections (12 in/8 out) which is 20 peers (0 or very low ban score), average network speed at 3kB/s bursting up to 15kB/s with a daily average debug.log at 2-3 MB.
It took me about a week to tweak all these settings and setup my masternodes according to MY specific OS, machines and network setup. After that, I check once a day to make sure all is running well. Current MN rewards averaging 4.6 DAS daily this past week up to yesterday. Usually 2 rewards daily 12 hours apart, but sometimes a single reward if mining WAY down.
Hope this helps. IF your core is installed and compiled correctly AND your masternode is setup correctly incl applicable .conf files and you are connected to reliable peers on the MN network, you should not have any transaction problems, whether from/to internal wallet addresses or external addresses. Since I fixed my misbehaving peers problem, runs like a charm and EVERY transaction sees confirmations running at 3-5 mins per confirmation.
If you are getting unconfirmed transactions (ie, transaction never sent out on the network to be confirmed by anyone else), you have a connection and/or peer problem. There can be scores of reasons why and it's just a matter of analyzing the data from the Tools windows, debug.log and DAS block explorers to troubleshoot and correct.
Regards,
c_p