Conversation
…ull resync via an arg instead of hunting down files to delete
…ocal blockchain to a specific height thereby hopefully allowing people to avoid a FULL resync when local blockchain corruption is detected. Updated the error message presented when corruption is detected in the local copy of the blockchain to provide directions on how to attempt to recover from the error.
…into development # Conflicts: # README.md # src/config/CryptoNoteConfig.h # src/zedwallet++/CommandImplementations.cpp
# src/zedwallet++/CommandImplementations.cpp
# src/zedwallet++/CommandImplementations.cpp
…using issues after rewinding the blockchain cache as the autoincrement field wasn't updated to reflect the removal of blocks.
Update internal checkpoints
Fixes failing build when enabling ssl
Local Blockchain Cache Enhancements
Fix locked transactions getting double added when load from file
Prune spent inputs
MSVC 2019 Support
…nsactions" to avoid confusion
- Re-factors the code a bit to make it a bit more readable
…into development # Conflicts: # README.md # src/CMakeLists.txt # src/CryptoNoteCore/Core.cpp # src/CryptoNoteCore/Currency.cpp # src/CryptoNoteCore/Currency.h # src/CryptoNoteProtocol/CryptoNoteProtocolHandler.cpp # src/WalletService/main.cpp # src/config/Ascii.h # src/config/CryptoNoteCheckpoints.h # src/config/CryptoNoteConfig.h # src/config/version.h.in # src/walletbackend/Utilities.cpp # src/walletbackend/Utilities.h # src/zedwallet++/CommandImplementations.cpp # src/zedwallet++/CommandImplementations.h # src/zedwallet++/Commands.cpp
Fixing GCC+Clang compile warnings
Backend tweaks
Fix a couple of incorrect return codes
now that VS2017 is behind a login - much easier to use VS 2019 standalone build tools. also updated AppVeyor to the same
simplify Windows build instructions
Correcting Transaction Validation Error Message
… /sendrawtransaction to provide feedback on why a transaction was rejected
Bubble the error message from isTransactionValidForPool up to the node RPC call
…into development # Conflicts: # .appveyor.yml # README.md # src/config/version.h.in
production config for algo switch at block 394000
Thanks to: https://github.com/bobbieltd/derogold/commit/81f11906fc78116c442c402b6fa827ec5ce0509a - Exchanges will delist or refuse to list small coins if this shit keeps to be applied - No impact on performance (even quicker better on low end hardware nodes) 256 Mb write is enough. Read buffer is unimportant (it shares with OS cache). Opening files : few hundreds is enough. Back threads 4 (well 4 cores already enough) The original dev put 10 Mb (he was not stupid because it is idiot to put big number there) Turtle dev applied that commit in hurry without much consideration From outside dev Background threads = 10 —> assumption people run CPU with 16 cores or what ? Normally, daemon won’t use many threads but in the worst scenario it will use 10 cores Those config numbers are for worst case. In normal circumstances, daemon utilizes less.
fix: performance tweak.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.