Quote from: anemol on November 04, 2019, 08:33:26 AM

Quote from: AltcoinBaggins on July 24, 2019, 01:47:33 PM

...
- I had no problems with nodes / connections while testing recent versions, but as Velecore said, you can always add more nodes using "addnode" option in config (or as an rpc command), for example, you can pick some from the masternode list ( http://explorer.veles.network/masternodes ), those don't change IP frequently.
...

https://i55.servimg.com/u/f55/19/28/27/85/blocke10.png

This information is not usable. The role of a block explorer is also to inform about active nodes (IP, version) as do most usual block explorers.

Quote from: virtuado on November 03, 2019, 09:25:06 PM

Let's 1st start with the useless part here....the only thing here which is useless is your comment. Roll Eyes

Before you run your mouth with negative bs, get your facts straight. There are currently not any problems which you mention, block explorer is functioning like it should and has all the information available, network is running smooth, masternodes dito.

I suggest you take a sneak peak in our Discord and see if there are any complaints like you just mention? I'm fully confident that you will find none, so i guess the problem is on your side and not ours...

By twice, before you run your mouth with negative comment instead of helping, have you some nodes to offer here? Thanks.

We have a reason that the layout of the blockexplorer is like it is, and all IPs from nodes are available in the wallet, which in general causes zero problems.

You belong to the very rare cases which somehow it doesn't work??

addnode=194.182.84.184:21337
addnode=81.2.239.169:21337

When the wallet is synced you will see a lot of status "watchdog_expired" nodes. This is a bug and will be addressed very soon, but the nodes are working fine and receive rewards.