search

forknote / cryptonote-generator

Generate Cryptonote coin with 1 command
104 stars 211 forks source link

How to disable all nodes from old compilation #63

Open servc4 opened 6 years ago

servc4 commented 6 years ago

Hi I have a question, in last update I add diff algorithm zawy. But I notice then old nods are able to connect as wall, how I can disable or ban connection with old build nods ??? other wise there is no point to make update like that when old nods are able to mess with your network.

Regards

fengshuicoin commented 6 years ago

Let me know if u solve i have same issue forced to use "./coind --add-peer" but for some reason still wants to connect to original seed. I had to downgrade server to work with pool code and ips chnaged. We might nees to make new daemon command --forget-peer

pmitchev commented 6 years ago

We can port the ban strategy from Monero, but someone has to do it.

3ch0elite commented 6 years ago

Looks like a bit of an under taking. First step "grep -ri "ban" Anyone up for it? Must be another simple fix though seems like somewhere in cryptonote-generator it default add exclusive node...? I can do quick fix with --add-peer as stated. But others less experienced wont have any idea of how to fix letalone find config file with seed nodes ip. Im testing fixes by recompiling. Not sure why daemon wouldnt just use nodes from cryptonoteconfig.h let me know if you guys find a fix or work around. Not sure doing complete overhaul with monero ban is required. Also looks like some dir are different than ones currently with c-g.

servc4 commented 6 years ago

Hi guys Now I have a bigger problem .... https://github.com/forknote/cryptonote-generator/issues/66

Regards

servc4 commented 6 years ago

Hi I have question, because someone mine around 50 blocks on non zawy nods on alternative blockchain where he use nicehash attack I think, because speed was in ph/s and very height diff. And now what ever I will do all nods are switching on this block chain, ban or add peer maybe will work on nods but GUI wallets have the same issue. They sync with correct blockchain but on the end they switch on wrong blockchain again and again witch is now around 10K block behind...

Do you have any suggestion ??? Regards

pmitchev commented 6 years ago

The current work in progress is here: https://github.com/forknote/cryptonote-generator/blob/master/extensions/block-hosts.json

It still needs to add the cases for banning nodes