monzero-core.git/src/cryptonote_core, branch v0.18.3.3Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.18.3.32024-03-11T14:20:10Zbuild: prepare v0.18.3.32024-03-11T14:20:10Zselstaselsta@sent.at2024-03-11T14:13:49Zurn:sha1:97e3ce5f1838459969121287f53fd48724312004Fixed mempool pruning2024-03-08T20:03:41ZSChernykh15806605+SChernykh@users.noreply.github.com2024-03-08T19:58:21Zurn:sha1:b5b72ae05c5b47b76e57d565de0bac5706530c6a
- Fixed undefined behavior after a call to `remove_tx_from_transient_lists` (it used an invalid iterator)
- Fixed `txCompare` (it wasn't strictly weak ordered)
Merge pull request #92232024-03-08T18:46:09Zluigi1111luigi1111w@gmail.com2024-03-08T18:46:09Zurn:sha1:5eb3fc29bbeef95c133d18a34c52aecb9f449b60
36ee12b get_block_template_backlog: better sorting logic (SChernykh)
tx_memory_pool: make double spends a no-drop offense2024-03-08T14:14:06Zjeffro256jeffro256@tutanota.com2024-03-07T15:23:41Zurn:sha1:eeb7c7c5467dae9c72e4dde11cbd51dab3b448f9
Nodes who see different txs in a double spend attack will drop each other, splitting the network.
Issue found by @boog900.
get_block_template_backlog: better sorting logic2024-03-08T13:51:33ZSChernykh15806605+SChernykh@users.noreply.github.com2024-03-08T13:50:01Zurn:sha1:36ee12bd8d20aecf67fbfe5387749b1562732528
std::sort is unstable, so it can return random sets of transactions when mempool has many transactions with the same fee/byte. It can result in p2pool mining empty blocks sometimes because it doesn't pick up "new" transactions immediately.
Merge pull request #91362024-02-24T15:18:40Zluigi1111luigi1111w@gmail.com2024-02-24T15:18:40Zurn:sha1:c6ff0d38207d30a90dba72767ef7ca63098d6a79
f2360a7 build: prepare v0.18.3.2 (selsta)
build: prepare v0.18.3.22024-02-20T14:37:47Zselstaselsta@sent.at2024-01-27T19:08:59Zurn:sha1:f2360a725e9e8649a0be6e34801a40e03097b7f8cryptonote_core: early out on out of bounds scaling parameter2024-02-20T14:21:27Zselstaselsta@sent.at2024-02-20T14:20:38Zurn:sha1:0cc8f7aaa3d00765b96028658b2bc8decd078e8aMerge pull request #90142023-10-02T19:28:11Zluigi1111luigi1111w@gmail.com2023-10-02T19:28:11Zurn:sha1:2656cdf5056c07684741c4425a051760b97025b0
69de381 add a test for the long term weight cache (Boog900)
810f6a6 Fix: long term block weight cache The long term block weight cache was doing a wrong calculation when adding a new block to the cache. (Boog900)
Fix: long term block weight cache2023-10-02T14:27:31ZBoog90054e72d8a-345f-4599-bd90-c6b9bc7d0ec5@aleeas.com2023-10-01T12:40:06Zurn:sha1:810f6a6cd2431988b6d349444aa3359ae90b2778
The long term block weight cache was doing a wrong calculation when
adding a new block to the cache.