monzero-core.git/src/cryptonote_protocol, 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.32023-06-27T11:06:14Zprotocol: drop peers sending duplicate txes2023-06-27T11:06:14Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2023-05-16T22:31:31Zurn:sha1:1924c170d48f144eafd04694bbcda1f319abb51fcryptonote core/protocol: don't drop peers for soft offenses2023-03-29T07:07:15Zjeffro256jeffro256@tutanota.com2023-03-27T21:32:47Zurn:sha1:059b975388f346a4243273a75d86c16fd8e6990d
Also: txs with tx_extra which is too large will not get published to ZMQ
Co-authored-by: SChernykh <sergey.v.chernykh@gmail.com>
Fix dandelion++ fluff/stem bug with local txes2022-10-25T20:01:09ZLee Clagettcode@leeclagett.com2022-10-25T19:37:45Zurn:sha1:1bb5d25e313c1da23969b950b991a4051804c66bMove update_checkpoints() to a later stage2022-09-22T11:06:39ZSChernykhsergey.v.chernykh@gmail.com2022-09-22T11:06:39Zurn:sha1:802c4bb0e4e7a94c07e5c06a3e993e104b529e52
update_checkpoints() makes a few DNS requests and can take up to 20-30 seconds to complete (3-6 seconds on average). It is currently called from core::handle_incoming_block() which holds m_incoming_tx_lock, so it blocks all incoming transactions and blocks processing while update_checkpoints() is running. This PR moves it to until after a new block has been processed and relayed, to avoid full monerod locking.
Don't exclusively drop tor/i2p outgoing cxns in idle loop2022-05-18T16:54:21Zj-bermanjustinberman@protonmail.com2022-05-15T03:11:53Zurn:sha1:2dab31f62f3e7aff14afd7897848143456b0c47dTrimming Fat2022-04-18T14:55:20ZJeffreyjeffryan@tamu.edu2022-03-08T00:27:28Zurn:sha1:12b1b74d322f9933bb5d2ccbccd2566ee44cd3fc
Remove unused include statements or unused definitions.
Merge pull request #82232022-04-06T04:19:59Zluigi1111luigi1111w@gmail.com2022-04-06T04:19:59Zurn:sha1:bb093ec9a8087bba0e8f6e8769dbb336a6a0aedd
17772ef Eliminate dependence on boost::interprocess #8223 (Jeffrey)
Eliminate dependence on boost::interprocess #82232022-03-30T18:18:32ZJeffreyjeffryan@tamu.edu2022-03-30T18:18:32Zurn:sha1:17772ef53e57620f47c426fa4557671a86f1b3ae
In this repo, `boost::interprocess` was being used soley to make `uint32_t` operations atomic. So I replaced each instance of
`boost::interprocess::ipcdetail::atomic(...)32` with `std::atomic` methods. I replaced member declarations as applicable. For example,
when I needed to change a `volatile uint32_t` into a `std::atomic<uint32_t>`. Sometimes, a member was being used a boolean flag, so
I replaced it with `std::atomic<bool>`.
You may notice that I didn't touch `levin_client_async.h`. That is because this file is entirely unused and will be deleted in PR monero-project#8211.
Additional changes from review:
* Make some local variables const
* Change postfix operators to prefix operators where value was not need
Copyright: Update to 20222022-03-04T05:59:20Zmj-xmrmjxmr@protonmail.com2022-03-01T11:16:17Zurn:sha1:da9aa1f7f802552b9de459f331a2f39c84898009protocol: fix spurious rejection of downloaded blocks2021-10-21T20:34:06Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2021-10-21T20:34:06Zurn:sha1:1f81f5f5c1e65581ec66207e763df13efc2cad12
when kicking a peer for inactivity, clear the set of requested blocks,
or next time we requests blocks from it, we'll probably reject the
incoming blocks due to missing the previous requested blocks