monzero-core.git/src/cryptonote_basic/cryptonote_basic.h, branch v0.14.1.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.14.1.12019-06-14T08:48:19Zserialization: check stream good flag at the end2019-06-14T08:48:19Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-04-16T18:48:40Zurn:sha1:756773e5fe79f970a36615cc178be09aedf4a915
just in case
cryptonote: rework block blob size sanity check2019-04-05T09:35:19Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-04-04T00:15:57Zurn:sha1:089c7637a64652c8bcf6c437065237c23266d4a9
Use the actual block weight limit, assuming that weight is always
greater or equal to size
Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6db: 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 #49462018-12-31T22:06:50Zluigi1111luigi1111w@gmail.com2018-12-31T22:06:50Zurn: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)
cryptonote: set tx hash on newly parsed txes when known2018-12-05T21:13:29Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-12-05T20:34:10Zurn:sha1:d1efe3d91c4b1bbb8178a67b445733f5560df1bbcryptonote: add a set_null for transaction_prefix2018-11-30T15:11:43Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-30T14:54:46Zurn:sha1:0c5dd3161b0f8c962a77cd27cff58043d85e509c
Since it's all inline, I suspect the compiler will merge the
duplicate stores anyway.
cryptonote: sort tx_extra fields2018-10-07T11:13:22Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-08-03T10:21:08Zurn:sha1:9907ea0694ecf025258fd1b28e3dcc8c2c1b54d0
This removes some small amount of fingerprinting entropy.
There is no consensus rule to require this since this field
is technically free form, and a transaction is free to have
custom data in it.
keypair::generate: always require hw::device to avoid possible mistake2018-03-14T12:00:16Zstoffustoffu@protonmail.ch2018-03-05T08:02:17Zurn:sha1:8705beaf51c12d7eab5f56f615ec529a2a8efc27