monzero-core.git/src/cryptonote_core/blockchain.cpp, 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:97e3ce5f1838459969121287f53fd48724312004Merge 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.
build: prepare v0.18.3.12023-10-02T10:59:37Zselstaselsta@sent.at2023-10-02T10:59:37Zurn:sha1:fbcd8da082fe9b7f4d1b771b392e6a0e8654e7fbbuild: prepare v0.18.3.02023-09-10T16:30:34Zselstaselsta@sent.at2023-09-10T13:55:30Zurn:sha1:64ed9385a204920499dd2b3f0c5f71030fdbe9f4Enforce restricted # pool txs served via RPC + optimize chunked reqs [release-v0.18]2023-07-09T06:38:18Zj-bermanjustinberman@protonmail.com2022-12-14T00:08:56Zurn:sha1:f137a35984985232a3aae50cd4c7b47634866594
- `/getblocks.bin` respects the `RESTRICTED_TX_COUNT` (=100) when
returning pool txs via a restricted RPC daemon.
- A restricted RPC daemon includes a max of `RESTRICTED_TX_COUNT` txs
in the `added_pool_txs` field, and returns any remaining pool hashes
in the `remaining_added_pool_txids` field. The client then requests
the remaining txs via `/gettransactions` in chunks.
- `/gettransactions` no longer does expensive no-ops for ALL pool txs
if the client requests a subset of pool txs. Instead it searches for
the txs the client explicitly requests.
- Reset `m_pool_info_query_time` when a user:
(1) rescans the chain (so the wallet re-requests the whole pool)
(2) changes the daemon their wallets points to (a new daemon would
have a different view of the pool)
- `/getblocks.bin` respects the `req.prune` field when returning
pool txs.
- Pool extension fields in response to `/getblocks.bin` are optional
with default 0'd values.
blockchain: ensure base fee cannot reach 02023-05-11T13:59:41ZCrypto Citycryptocity@example.com2023-05-11T11:43:09Zurn:sha1:1fad8cc919b2e309d306eedac009508e8fdd171f
reported by sech1