Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.17.1.1 2020-08-17T16:23:58Z 2020-08-17T16:23:58Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2020-06-24T23:26:58Z urn:sha1:7175dcb1078abbdaa130a8c5f5fd2b93fa7b3086 This reduces the attack surface for data that can come from malicious sources (exported output and key images, multisig transactions...) since the monero serialization is already exposed to the outside, and the boost lib we were using had a few known crashers. For interoperability, a new load-deprecated-formats wallet setting is added (off by default). This allows loading boost format data if there is no alternative. It will likely go at some point, along with the ability to load those. Notably, the peer lists file still uses the boost serialization code, as the data it stores is define in epee, while the new serialization code is in monero, and migrating it was fairly hairy. Since this file is local and not obtained from anyone else, the marginal risk is minimal, but it could be migrated later if needed. Some tests and tools also do, this will stay as is for now. 2020-05-07T02:36:54Z SomaticFanatic afdlkajdlfkj@aldkfjf.com 2020-05-07T02:36:54Z urn:sha1:5ef0607da6042df51a57703bd223c5c8024741f6 Update copyright year to 2020 2019-09-27T00:10:37Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-09-16T12:18:34Z urn:sha1:8330e772f1ed680a54833d25c4d17d09a99ab8d6 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 2019-06-14T08:47:23Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-04-16T18:48:40Z urn:sha1:1387549e905fc206426d3099b069bd28df0aad71 just in case 2019-04-05T09:35:19Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-04-04T00:15:57Z urn:sha1:089c7637a64652c8bcf6c437065237c23266d4a9 Use the actual block weight limit, assuming that weight is always greater or equal to size 2019-03-05T21:05:34Z binaryFate binaryfate@users.noreply.github.com 2019-03-05T21:05:34Z urn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6 2019-03-05T10:28:52Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-11-11T13:39:00Z urn:sha1:e69477bf25630c94a5aff666433f3da9ab29298c by avoiding repeated (de)serialization 2019-01-22T20:30:51Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-04-29T22:30:51Z urn:sha1:b750fb27b0f20e9443827732b69a504a76036430 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. 2018-12-31T22:06:50Z luigi1111 luigi1111w@gmail.com 2018-12-31T22:06:50Z urn:sha1:69e8567c0e803dfc69e5b6f61be6e94d555ada21 6644b9b blockchain_db: remove a couple unused functions (moneromooo-monero) ce594f5 blockchain_db: allocate known size vector only once (moneromooo-monero) 8332698 db_lmdb: inline check_open, it's trivial and called everywhere (moneromooo-monero) 5511563 db_lmdb: avoid pointless division (moneromooo-monero) d1efe3d cryptonote: set tx hash on newly parsed txes when known (moneromooo-monero) 9cc68a2 tx_pool: add a few std::move where it can make a difference (moneromooo-monero) 2018-12-05T21:13:29Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-12-05T20:34:10Z urn:sha1:d1efe3d91c4b1bbb8178a67b445733f5560df1bb