monzero-core.git/src/cryptonote_core/tx_pool.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-22T15:06:10ZMerge pull request #59192019-10-22T15:06:10Zluigi1111luigi1111w@gmail.com2019-10-22T15:06:10Zurn:sha1:6f202844b5550b28674b27998cd2edc23c9735fe
01f660f blockchain: fill in cumulative block weight for alt blocks (moneromooo-monero)
Merge pull request #59622019-10-16T18:51:34Zluigi1111luigi1111w@gmail.com2019-10-16T18:51:34Zurn:sha1:461a25e1b5d41fe65c46f27426fd883efd664574
ec14abd tx_pool: make spent return-by-reference as intended (stoffu)
blockchain: fill in cumulative block weight for alt blocks2019-10-10T20:26:40Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-09-17T17:03:28Zurn:sha1:01f660f60fc95449130f0b6ffdb3931a6173c838tx_pool: make spent return-by-reference as intended2019-10-06T03:28:30Zstoffustoffu@protonmail.ch2019-10-06T03:28:30Zurn:sha1:ec14abdbe880f5986fd2096fc3991f1fd2d217bdmonerod 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
Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6Avoid repeated (de)serialization when syncing2019-03-05T11:57:55Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-11-11T14:51:03Zurn:sha1:b044d03a51e1dc64bebe2461813e0cfc50f71b0dcryptonote: Add const-qualifier on comparison functor2019-02-01T15:44:56ZTom Smedingtom.smeding@gmail.com2019-02-01T14:02:39Zurn:sha1:9bf0e5375134a0d230bc966f439f69a09c1556cb
The original code did not compile with GCC 8.2.1 in C++17 mode, since
comparison functions for std::set's must be invocable as const.
Merge pull request #47652018-11-16T08:58:42ZRiccardo Spagniric@spagni.net2018-11-16T08:58:41Zurn:sha1:e90ee7548c5685b988941f7a92549f0a57fcfe9f
09dbd9cb tx_pool: fix comment about transaction_prefix (moneromooo-monero)
tx_pool: speed up take_tx for transactions from blocks2018-11-01T15:51:28Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-10-31T13:52:16Zurn:sha1:bf31447e9bd9e424538abc8f4cb57bd133f439ed
This happens for every historical tx when syncing, and the
unnecessary parsing is actually showing up on profile.
Since these are kept cached for just one block, this does
not increase memory usage after syncing.