Kudos!

Issue #21 resolved
Former user created an issue

Hello

0.5.9 works very well, it is a noticable improvement over previous NXT version especially those prior to 0.5.0 but now it seems that those older peers are "killing" the newer ones. For example, if I'm registering aliases it happens that if my node is connected to even 1 older node (0.5.7 or older) there will be issues with submitting aliases. Server does not respond, it respond but with noticable delay, it simply does not register alias (server response comes back in an instant after I attempt to register alias but no transaction is broadcast to network) and many other problems. So I have decided to check active peers every few minutes and manually "kill" any peer using 0.5.7 or older NXT. It is a boring and time consuming job especially because not only I must "kill" mentioned peers at "Active peers" but also at "Known peers" else they keep on coming back.

There is a minor bug related to "killing" peers, if user "kills" some peer, it reconnects quickly and user "kills" it again than it can happen that icon used to "kill" peers become unresponsive, e.g. it is no longer possible to "kill" a peer unless user reload the page.

TLDR Some way of automatic filter-out older nodes would be totally welcomed!

Keep up with the great job!

subSTRATA

Comments (2)

  1. Jean-Luc Picard repo owner

    Automated killing based only on version is not such a good idea, but peers that submit invalid blocks or transactions are automatically blacklisted in 0.6.0, so this will also catch zombies that display a fake version.

  2. Log in to comment