I have updated the public ZERO node with IP 94.176.235.178 that accepts incoming connections. It is now based on the latest ZERO code-base at https://github.com/zerocurrency/zero - updated by the original Zero developer.

Everyone interested may add it to their config. file ~/.zero/zero.conf:
addnode=94.176.235.178

I have no tool to explore the network node numbers. I only tried to analyze how many nodes my node could connect to, and after discovering peers how many of them accepted connections (log shows connect failures). So what I wrote about the network was not 100% certain but it looks that way...

On the topic of the ZERO network, two things are apparent:

1. There are very few running ZERO nodes
2. Very few of those few ZERO nodes accept incoming connections

In fact my own node constantly has only one peer connected. The only node that (seems to) readily accepts connections is 35.164.216.74 (put up by the ZERO creator). In this condition the ZERO network is not really decentralized and resilient at all...

So let us try to fix this! I have started a ZERO node to the "benefit of the community" - IP 94.176.235.178  It accepts incoming connections. Everyone interested may add it to their config. file ~/.zero/zero.conf:

addnode=94.176.235.178

This node is based on the ZERO code-base at: https://github.com/zerodev2/zero
I would ask all those interested in having a strong ZERO network to either run a node that accepts connections or help me run this one (at least) The node costs approx 0.8 USD per day - at the current rate this is 5 ZER. All ZER contributions I receive to this ZERO address

t1L7TfvTQb9B78sLxH9cfx65aBVKfrFJMBQ

will be used to pay for the node... If enough people help with a few pennies - we can keep it running. This should be just a start - one extra node does not make a network ;-)

Yep. The ZERO Desktop GUI Wallet  https://github.com/vaklinov/zero-swing-wallet-ui works for me too... much better than a command line.

I did not get your mail. Could you send it again or post the log on some shared service (dropbox) and send me a private forum message with the link...

Could I ask you to ZIP and send me your log ~/.zero/debug.log to check (my mail is zerodev2@mail.ru). I do not have this disconnect problem...

To move ZERO forward I think we all need to realize that “we are in it together”. We may be selfish in our own ways: developers/miners etc. but if the currency dies off, due to not being pushed forward we will all suffer. If more community members become more active I think we can push it forward together…

The main problem to tackle at this stage is indeed the lack of further code base development. Like many I hope the ZERO creator will return to active development. But even if he does not, this is no reason to close shop. Bitcoin did not die when Satoshi disappeared, ZERO can also live on supported by a community. Perhaps one or two developers like @tearodactyl could undertake to continue to develop the code-base and the miners could support them in some way … e.g. developer bounties.

At this difficult time (security issue) I wish to offer my own contribution to ZERO development: I have back-ported the Zcash 1.0.8-1 security fix to the codebase of ZERO (which is based on Zcash 1.0.6). The code is now available on the following alternative ZERO GitHub site:

https://github.com/zerodev2/zero

I wish to ask for help by 2-3 community members who understand code, to review the change and confirm it is OK with them (and write on this forum thread). The security fix is the only change. Then a few other volunteers may run it on their ZERO nodes for a few days to make sure it works for them (works for me locally). After that I will send a pull request to the ZERO creator to incorporate the change… but even if he does not, this will not stop us… if an attack is started by malicious actors we will have a fix to deploy.

For now the question of long term development remains...

Regards to all,
   zerodev2 ;-)