monzero-core.git/src/cryptonote_protocol/block_queue.cpp, branch v0.18.4.3

Some cleanup in span/connection_context + few more checks

2025-02-03T17:04:45Z

build: fix build with Boost 1.85 and remove instances of viewkey logging [RELEASE]

2024-09-10T21:07:36Z

1. Use std::is_standard_layout and std::is_trivially_copyable instead of std::is_pod for KV byte-wise serialization, which fixes compile issue for Boost UUIDs 2. Removed reimplementation of std::hash for boost::uuids::uuid 3. Removed << operator overload for crypto::secret_key 4. Removed instances in code where private view key was dumped to the log in plaintext Release version of #9450, containing C++14 modified assertions

Copyright: Update to 2022

2022-03-04T05:59:20Z

protocol: drop origin IP if a block fails to verify in sync mode

2020-12-10T21:59:18Z

It would otherwise be possible for a peer to send bad blocks, then disconnect and reconnect again, escaping bans

Update copyright year to 2020

2020-05-07T02:36:54Z

Update copyright year to 2020

monerod can now sync from pruned blocks

2019-09-27T00:10:37Z

If the peer (whether pruned or not itself) supports sending pruned blocks to syncing nodes, the pruned version will be sent along with the hash of the pruned data and the block weight. The original tx hashes can be reconstructed from the pruned txes and theur prunable data hash. Those hashes and the block weights are hashes and checked against the set of precompiled hashes, ensuring the data we received is the original data. It is currently not possible to use this system when not using the set of precompiled hashes, since block weights can not otherwise be checked for validity. This is off by default for now, and is enabled by --sync-pruned-blocks

Update 2019 copyright

2019-03-05T21:05:34Z

block_queue: fix late sanity check off by one

2019-01-28T22:17:43Z

Pruning

2019-01-22T20:30:51Z

The blockchain prunes seven eighths of prunable tx data. This saves about two thirds of the blockchain size, while keeping the node useful as a sync source for an eighth of the blockchain. No other data is currently pruned. There are three ways to prune a blockchain: - run monerod with --prune-blockchain - run "prune_blockchain" in the monerod console - run the monero-blockchain-prune utility The first two will prune in place. Due to how LMDB works, this will not reduce the blockchain size on disk. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. The third way will create a second database, a pruned copy of the original one. Since this is a new file, this one will be smaller than the original one. Once the database is pruned, it will stay pruned as it syncs. That is, there is no need to use --prune-blockchain again, etc.

Remove boost::lexical_cast for uuid and unused uuid function

2018-12-23T11:11:30Z