monzero-core.git/contrib/epee/include/string_tools.h, branch main

epee: partially revert c56ee140 to fix linking errors

2024-12-09T20:34:34Z

On Linux Mint 21.3, g++ Ubuntu 11.4.0-1ubuntu1~22.04, I get linking error for an undefined reference to `epee::string_tools::trim_right`. This PR reverts the changes to epee_readline.cpp in commit c56ee140, which turns a `boost::trim_right` callsite into an `epee::string_tools::trim_right` callsite.

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

Cleanup string_tools.

2024-03-15T15:49:39Z

1. Use boost::filesystem for already available operations. 2. Use boost::string for already available operations.

Split epee/string_tools.h and encapsulate boost::lexical_cast

2021-04-16T18:54:20Z

Move hex->bin conversion to monero copyright files and with less includes

2020-03-09T05:23:59Z

Remove temporary std::string creation in some hex->bin calls

2020-03-09T05:23:59Z

epee: fix peer ids being truncated on display

2019-11-14T18:27:12Z

epee: support unicode in parsed strings

2019-08-16T17:06:03Z

epee: some more minor JSON parsing speedup

2019-03-25T14:29:29Z

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.