monzero-core.git/tests/core_proxy, branch v0.15.0.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.15.0.12019-10-08T20:55:03ZMerge 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
RandomX integration2019-09-25T20:29:42ZHoward Chuhyc@symas.com2019-04-23T19:32:27Zurn:sha1:81c2ad6d5b17cf280a4a55fd6159e8dde423f5a8
Support RandomX PoW algorithm
Update 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.
protocol: option to pad transaction relay to the next kB2018-11-06T15:47:05Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-02T22:27:25Zurn:sha1:3dba7f252e080ca9ce9c86dca033e6b0b00ee21d
To help protect one's privacy from traffic volume analysis
for people using Tor or I2P. This will really fly once we
relay txes on a timer rather than on demand, though.
Off by default for now since it's wasteful and doesn't bring
anything until I2P's in.
replace std::list with std::vector on some hot paths2018-06-26T21:14:21Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-04-15T23:16:02Zurn:sha1:ed2c81ed95be71bace897e62a0c241068cfde7be
also use reserve where appropriate
Merge pull request #34502018-06-08T19:31:49Zluigi1111luigi1111w@gmail.com2018-06-08T19:31:49Zurn:sha1:22c87302618fccee0de2affc9a0c689ba8aea268
3b941be core: add get_earliest_ideal_height_for_version() (stoffu)
Only log an error if fork version is higher AND is not known.2018-04-23T00:26:44ZThaer Khawajathaer.khawaja@gmail.com2018-04-16T02:02:26Zurn:sha1:dad10775778ef5e4f7ab99d1cda653728f438540