Bitsharestalk forum is supported by Bitsapphire
Join the chat
Distancing my code from nxtcrypto.org is exactly what I am working on now. First, I am removing the hardcoded logic to use *.nxtcrypto.org nodes if no well-known peers are set in the properties file. Second, I am adding database support for storing all peers, so that we are not dependent on just a few centrally controlled well-known nodes. I will seed the database with all nodes (minus the nxtcrypto.org ones) that my node is currently aware of, and will update this list at every release. Finally, if the nas*.nxtcrypto.org aliases are still not removed, I will hardcode *.nxtcrypto.org as a default blacklist. Those insisting on using such nodes will have to edit the NRS source to remove this blacklist and compile it themselves. Most users won't bother. Needless to say, the next releases will be hosted at bitbucket.org, and I will not use any nxtcrypto.org services.
Page created in 0.598 seconds with 21 queries.