monzero-core.git/src/cryptonote_protocol, branch v0.16.0.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.16.0.12020-05-19T22:51:03ZMerge pull request #65542020-05-19T22:51:03Zluigi1111luigi1111w@gmail.com2020-05-19T22:51:03Zurn:sha1:eed8a4e8a65a7ed96d9aa21b3661a1f206685fec
f01d529 cryptonote_protocol: reject requests/notifications before handshake (moneromooo-monero)
bbab044 cryptonote_protocol: stricter limit to number of objects requested (moneromooo-monero)
Merge pull request #65672020-05-19T22:38:34Zluigi1111luigi1111w@gmail.com2020-05-19T22:38:34Zurn:sha1:b82af557f50c68b86b18cd2a87d069908159c1d3
cef39dc protocol: move the 'peer claims higher version' warning to debug (moneromooo-monero)
Merge pull request #65432020-05-19T22:29:46Zluigi1111luigi1111w@gmail.com2020-05-19T22:29:46Zurn:sha1:8fb0d7e0b4edd1b10600f6f921d14eb3bb2e7a3a
44e3782 protocol: don't drop a connection if we can't get a compatible chain (moneromooo-monero)
protocol: move the "peer claims higher version" warning to debug2020-05-19T16:15:08Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-05-19T16:13:49Zurn:sha1:cef39dc3138a2556c796c7fde6b3a41584665679
Because there's a neverending supply of cunts claiming a wrong
version just to say "look at me" I guess
cryptonote_protocol: stricter limit to number of objects requested2020-05-19T10:34:05Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-05-17T14:01:28Zurn:sha1:bbab044c929ce1a690873c185b24c00708914831
Reported by xnbya
cryptonote_protocol: reject requests/notifications before handshake2020-05-19T10:34:04Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-05-17T13:48:40Zurn:sha1:f01d529bdb3910fdb5b0472571707199cdd66502
Reported by xnbya
protocol: don't drop a connection if we can't get a compatible chain2020-05-16T20:25:29Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-05-16T19:54:55Zurn:sha1:44e3782b4d30d396060a02e9dc3d706eb993c2ef
This can now happen if:
- we have a pruned db
- we have not connected to the monero network for a while
- we connect to a node
- that node asks us for history
- we only have a pruned version of the most recent common block
In that case, it's better to not reply but keep the connection alive,
so we can sync off it.
Revert "simplewallet: noob-friendly help menu"2020-05-16T19:26:11Zselstaselsta@sent.at2020-05-16T19:26:11Zurn:sha1:4a9c3aca0374afe292dfc6f70fd5aa4c4cc7a4d2
This reverts commit 67b4a19edf7b9d6a407a79eca5c57819863bfd71.
cryptonote_protocol: do not request pruned borromean sig txes2020-05-06T12:44:00Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2020-05-04T15:08:35Zurn:sha1:f80ab3edde12015ce5d642dc541282e6612262c1
We don't have a function to calculate their weight from a pruned
version (yet).
Merge pull request #62782020-04-21T13:19:02Zluigi1111luigi1111w@gmail.com2020-04-21T13:19:02Zurn:sha1:9c660e159ee2d9e2f7c7b7f766193792706f90a3
387fd66 Daemon: Print estimates for time until fully synced (rbrunner7)