monzero-core.git/src/cryptonote_core/cryptonote_core.cpp, 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-31T01:25:07Zcryptonote: untangle dependency from miner to blockchain2019-10-31T01:25:07Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-10-31T01:05:58Zurn:sha1:d31024c2e1634d32cfbf750ce5713b52a1e67707
It causes link errors at least on mac
rpc: add a flush_cache RPC2019-10-25T18:41:54Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-10-22T15:28:08Zurn:sha1:a4dc575ccba8348886ed19594a16f5a7242f8fe6
This allows flushing internal caches (for now, the bad tx cache,
which will allow debugging a stuck monerod after it has failed to
verify a transaction in a block, since it would otherwise not try
again, making subsequent log changes pointless)
Merge pull request #59732019-10-22T15:54:46Zluigi1111luigi1111w@gmail.com2019-10-22T15:54:46Zurn:sha1:4233d88341a074450c38064807ed348fe4691019
abd3763 cryptonote: fill in tx weight when syncing from pruned blocks (moneromooo-monero)
cryptonote: don't leave block_weight uninitialized2019-10-11T14:09:31Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-10-11T10:42:57Zurn:sha1:fe443bbdec3ad6cdb7409f61a1e64eda6b32016b
CID 204467
cryptonote: fill in tx weight when syncing from pruned blocks2019-10-10T11:08:02Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-10-10T11:07:29Zurn:sha1:abd376313bb5fd82df622901b11adf1e1bccd03bMerge 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
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)
Merge pull request #58772019-09-24T15:08:44Zluigi1111luigi1111w@gmail.com2019-09-24T15:08:44Zurn:sha1:ee6e84962721b0a47e2aea4f9cbdb6e796332441
2cd4fd8 Changed the use of boost:value_initialized for C++ list initializer (JesusRami)
4ad191f Removed unused boost/value_init header (whyamiroot)
928f4be Make null hash constants constexpr (whyamiroot)