monzero-core.git/tests/unit_tests/ban.cpp, branch mainMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=main2019-10-13T13:27:46Zp2p+rpc: don't skip p2p or rpc port bind failure by default2019-10-13T13:27:46Zxiphonxiphon@protonmail.com2019-10-13T13:27:46Zurn:sha1:d4d2b5c79a04858cd47ceae58401dacf8fb59836Merge pull request #59152019-10-08T20:55:03Zluigi1111luigi1111w@gmail.com2019-10-08T20:55:03Zurn:sha1:bf525793c724f62d4716aaca59345ba2e13a2c3c
8330e77 monerod can now sync from pruned blocks (moneromooo-monero)
monerod can now sync from pruned blocks2019-09-27T00:10:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-09-16T12:18:34Zurn: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
p2p: fix bans taking port into account2019-09-16T22:45:45Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-09-16T19:20:23Zurn:sha1:7b076d5170f3299b1933f990e8b35777083c1809allow blocking whole subnets2019-07-16T11:35:53Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-03-29T10:47:53Zurn:sha1:65c40049633f0c5db3c24af8716bb683520f368cunit_tests: undo is_blocked implementation factoring2019-04-16T22:23:15Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-04-16T22:23:15Zurn:sha1:e3dea478594a202e2d90826c768a23c3d5b95f57
The is_host_blocked method is not on master yet
p2p: fix integer overflow in host bans2019-04-11T21:59:27Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-04-11T21:57:51Zurn:sha1:5858598604c511ff57a434196d27acf2f49cf23fUpdate 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6cryptonote: avoid double parsing blocks when syncing2019-03-05T11:58:18Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-23T13:05:48Zurn:sha1:88c85c18e0173f479470842fbe49626cdc86e7d1Pruning2019-01-22T20:30:51Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-29T22:30:51Zurn: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.