-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Several patches #100
Several patches #100
Conversation
This introduces the concept of the 'sync node', which is the one we asked for missing blocks. In case the sync node goes away, a new one will be selected. For now, the heuristic is very simple, but it can easily be extended later to add better policies.
I added "using pthread_create instead CreateThread on Windows". Not sure that it is somehow connected with the problem, but it's the only thing that I did Windows only.(for compatibility with mingw 4.9.2) |
Maybe #6 fixed. Need additional tests... |
OpenSSL Fix = bitcoin/bitcoin#5634 and bitcoin/bitcoin#5640 |
Make lsn_reset ("detach databases") optional and off by default = bitcoin/bitcoin#1119 |
Thanks for the pull request! In general, please don't submit "several patches" but split them into logical units (for the future). Also, without having reviewed the code in full, I have at least some suggestions right now:
|
Fourth Octet: 185 | ||
(67 * 16777216) + (225 * 65536) + (171 * 256) + (185) = 1138863033 | ||
*/ | ||
unsigned int pnSeed[] = {2990412266, 1138863033 }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why add the comment and not just #define a macro that does the calculation for you?
(Besides, I don't think we should hardcode the nodes.)
Sure. Added to the last commit(Automatic creation huntercoin.conf) I do not know how to edit an arbitrary commit, only the last. Let me know if you know how to edit an any commit.
Without adding nodes, huntercoin does not start synchronization from scratch. Although it works, if user downloads the database from your site( http://chain.huntercoin.org/ )(because your database has addr.dat with node IPs) |
Just add another commit which cleans up everything. (This is not perfect, but I think it is good enough for now.) Actually, Huntercoin should discover nodes via IRC (as Bitcoin did back in the day). Is this broken? If so, then we should indeed try to fix it. If not, I don't think we should be adding the hardcoded nodes. |
IRC code is good, but IRC servers often is offline(or maybe they blocked some IPs, not sure) For example, classic namecoin has 3 hardcoded nodes: https://github.com/namecoin/namecoin/blob/b043fba28018721b68c90edfc81b9eacb070b47d/src/namecoin.cpp#L2702 |
Yes, we have. User can't synchronize. The official advices were:
Snailbrain:
So I added 67.225.171.185 and 178.62.17.234 in the code. |
…re the last blockchain checkpoint" This reverts commit 79490f4.
Ok, I see. In that case, if IRC is down sometimes (wasn't aware of that), I think adding the nodes makes sense. Please just use a macro like #define CONVERT_IP4(a, b, c, d) instead of the manual computation. |
Done, https://github.com/fsb4000/huntercoin/commit/6b7eed1d458ea9d17fbbcc2823cd1f71cb777834
Done, https://github.com/fsb4000/huntercoin/commit/057a64ed87a1a0e3261bf7ef60784375ca041a7b |
done, https://github.com/fsb4000/huntercoin/commit/1ea795dd5055c331793686a6f155c6a5c2ebb2b5 Snailbrain, please,in the next release which will include the pull request, provide details about command line command -detachdb=0 which really speeds up the client shutdown |
"Automatic creation huntercoin.conf" is similar to jl777/btcd@be2f732 (the first time where I saw the auto creation .conf file) |
Same as novacoin-project/novacoin@28f9882
Similar to bitcoin/bitcoin@6ed71b5
(I don't delete old sync code because it does conflict with nothing and that's OK "Ask the first connected node for block updates" before this node can be selected for block updates in net.cpp)
(Although I can remove old sync code if necessary.)
Issue description: bitcoin/bitcoin#1234