monzero-core.git/src/blockchain_db, 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-17T17:39:05Zdb_lmdb: an empty prunable data record means the tx is not pruned2019-10-17T17:39:05Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-10-17T17:34:01Zurn:sha1:37cccb8cfb5bce18d210febd30ce5bef6143acc3
as opposed to an absent record
Merge 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
Merge pull request #58782019-09-24T15:10:28Zluigi1111luigi1111w@gmail.com2019-09-24T15:10:28Zurn:sha1:06bee964a8989c3dcafdf8e665f74762814b43a2
f9b3f6e Removed Berkeley DB and db switching logic (JesusRami)
Removed Berkeley DB and db switching logic2019-09-16T14:18:05ZJesus Ramirezjesus.rami.serra@gmail.com2019-06-26T14:39:41Zurn:sha1:f9b3f6ef3b1ebde4dc9a1ef8e70b4ef7d807cededb_lmdb: print percentages as percentages, not ratios2019-09-04T14:53:59Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-05-14T18:07:02Zurn:sha1:4672b5cea99966d8fc27eedc1c655dfcc645762eIncrease max_dbs from 20 to 322019-08-18T16:10:45ZHoward Chuhyc@symas.com2019-08-18T16:10:45Zurn:sha1:50ec40ea16f281690aeded37973dc582ddf38843
We've added a lot of new indices recently, and 20 isn't enough for them plus
new DBs opened during format migrations.
Merge pull request #55242019-07-24T19:04:16Zluigi1111luigi1111w@gmail.com2019-07-24T19:04:16Zurn:sha1:4b76656f5caf7c37825c6db4b916f258fc8a0faf
06b8f29 blockchain: keep alternative blocks in LMDB (moneromooo-monero)
Merge pull request #55022019-07-24T18:57:06Zluigi1111luigi1111w@gmail.com2019-07-24T18:57:06Zurn:sha1:e3de4aa68bedf7a7adfaf53cc2c132a74dc7fb08
25a7cfd add a few checks where it seems appropriate (moneromooo-monero)
1a66a86 remove unused code (moneromooo-monero)
db_lmdb: commit pruning txn at checkpoints2019-06-15T09:50:54Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-06-15T09:49:28Zurn:sha1:2ff99fb47ff9feada77285f0ea4988c7b40e7cae
to avoid errors when the txn is too large