monzero-core.git/src/cryptonote_basic/cryptonote_format_utils.h, 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-11T12:08:36Zcryptonote: add function to get weight from a pruned tx2019-10-11T12:08:36Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-10-10T10:45:49Zurn:sha1:9447e7276dbcaf37e5fe81738db3d62b5a443839
The weight of the prunable data is deterministic from the
unpruned data, so it can be determined from a pruned tx
RandomX integration2019-09-25T20:29:42ZHoward Chuhyc@symas.com2019-04-23T19:32:27Zurn:sha1:81c2ad6d5b17cf280a4a55fd6159e8dde423f5a8
Support RandomX PoW algorithm
functional_tests: add more blockchain related tests2019-04-11T11:07:58Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-03-23T16:20:08Zurn:sha1:064ab123401814b755c776d8e53f132f6a151657
Related to emission, reorgs, getting tx data back, output
distribution and histogram
cryptonote: block parsing + hash calculation speedup2019-03-25T13:43:17Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-12-13T19:47:47Zurn:sha1:547a9708de91c175ceab0ddde93785ba93c9efca
This saves a duplicate serialization step
Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6core: avoid calculating tx prefix hash when we don't need it2019-03-05T11:57:57Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-12T23:22:20Zurn:sha1:f75d51abda4c83ef58236bdc217f5a4c967084d2db: speedup block addition2019-03-05T10:28:52Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-11T13:39:00Zurn:sha1:e69477bf25630c94a5aff666433f3da9ab29298c
by avoiding repeated (de)serialization
Pruning2019-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.
Merge pull request #43082018-10-26T20:18:28ZRiccardo Spagniric@spagni.net2018-10-26T20:18:28Zurn:sha1:1c91963dcd95871b294f2c9411a90b0a8eaa6f20
9907ea06 cryptonote: sort tx_extra fields (moneromooo-monero)
tx_pool: avoid parsing a whole tx if only the prefix is needed2018-10-08T10:18:01Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-09-16T18:30:39Zurn:sha1:6844ae1b8d6b9fcbe4fda5ac5cb0e5a4242d850a