Ack/dev contribution - #348
Closed
Acktarius wants to merge 59 commits into
Closed
Conversation
Acktarius
commented
Apr 30, 2026
Member
- includes fireice-uk checkpoint work (including DNS checkpoints logic)
- P2P checkpoint consensus to cover in period of lack of hardcoded checkpoints
- update of checkpoints (mainnet + testnet)
- improve ui message in context of wallet reset as per nullcryptodev suggestions
- fix memory leak at exit from logger
- adapt CMakeList in regards of libboost version warning for macOS
- adapt workflows actions version to satisfy nodejs24
* strategy with priority order and validation of checkpoint hashes
* rollback only after second concesus failed twice with the same hash
* combo config + dns + p2p
* append only new chunk to checkpoint.dat
…or chaingen Introduce a unique temporary directory for each chaingen test run using boost::filesystem. This ensures that test environments are isolated from production checkpoint files and prevents blockchain file contamination between consecutive tests. A TempDirGuard RAII object is used to automatically clean up the directory upon test completion.
* Call clear_targets_for_test() after init_targets() to isolate the test state * Compute the real cn_fast_hash of the zero-hash vector and use it as the target (instead of "00...00") * Actually call set_checkpoint_list() to load m_points, mirroring how old checkpoint.dat was loaded * Restore ASSERT_EQ(greatest, N) sanity checks — they now pass because the state is controlled
remove confusing log message
* at init make sure conversion from old format to new format is only done once, avoiding edge cases where we would try to convert new format.
* windows: logging fixes * mingw: build fixes phmap.h improv: * At cache rebuild: verify chain linkage between blocks
* windows: undef ERROR in CheckpointList.h * MinGW: main.cpp, use static char[] for service name
* in order to fix macOs build errors
* new boost version, probably 1.90.0 and base on our use should not break...TBC
… 1.90.0 for macOS build
Update success message for wallet reset process.
* bump to 6.7.4-beta.1 in order to propose on upstream/development * update contributing flow
* store it in memory = allow in check zone * at checkpoit height confirm the prefetched with the locally computed hash, and rollback if needed
|
Member
Author
|
PR closed, contribution will be sequence differently. |
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.


