monzero-core.git/tests/functional_tests/transactions_flow_test.cpp, branch v0.17.2.3 Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.17.2.3 2020-05-07T02:36:54Z Update copyright year to 2020 2020-05-07T02:36:54Z SomaticFanatic afdlkajdlfkj@aldkfjf.com 2020-05-07T02:36:54Z urn:sha1:5ef0607da6042df51a57703bd223c5c8024741f6 Update copyright year to 2020 Merge pull request #5877 2019-09-24T15:08:44Z luigi1111 luigi1111w@gmail.com 2019-09-24T15:08:44Z urn:sha1:ee6e84962721b0a47e2aea4f9cbdb6e796332441 2cd4fd8 Changed the use of boost:value_initialized for C++ list initializer (JesusRami) 4ad191f Removed unused boost/value_init header (whyamiroot) 928f4be Make null hash constants constexpr (whyamiroot) wallet: fix mismatch between two concepts of "balance" 2019-09-05T11:19:34Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-05-10T17:20:20Z urn:sha1:2ec455df1f82148733c4ac268d22e9c51a690b14 One considers the blockchain, while the other considers the blockchain and some recent actions, such as a recently created transaction which spend some outputs, but isn't yet mined. Typically, the "balance" command wants the latter, to reflect the recent action, but things like proving ownership wants the former. This fixes a crash in get_reserve_proof, where a preliminary check and the main code used two concepts of "balance". Changed the use of boost:value_initialized for C++ list initializer 2019-09-02T12:16:29Z Jesus Ramirez jesus.rami.serra@gmail.com 2019-06-26T14:39:41Z urn:sha1:2cd4fd8972620737956aeeb4262209f8a446e3ee Update 2019 copyright 2019-03-05T21:05:34Z binaryFate binaryfate@users.noreply.github.com 2019-03-05T21:05:34Z urn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6 Remove boost::lexical_cast for uuid and unused uuid function 2018-12-23T11:11:30Z Lee Clagett code@leeclagett.com 2018-12-18T00:05:27Z urn:sha1:a5ffc2d5ade4db49f31f169e8908065be8cdc0f2 api/wallet: properly disable key encryption 2018-09-17T13:15:29Z stoffu stoffu@protonmail.ch 2018-08-25T05:22:26Z urn:sha1:ba8dd3479d56ff084fbc4b631548ff8cf05f60d1 remove obsolete daemon selection of fake outs and old tx construction 2018-09-14T10:51:45Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-08-13T16:18:32Z urn:sha1:be001326d1baac0b00d79d2d0a7f42662dc1be1f wallet: store trusted-daemon flag in wallet2 2018-08-23T05:55:09Z stoffu stoffu@protonmail.ch 2018-08-10T12:15:40Z urn:sha1:8ca1215f25ad48a87c5445ffeed8896122343ad1 store secret keys encrypted where possible 2018-08-16T11:57:43Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-07-08T20:12:33Z urn:sha1:e9ffa91257b672009e8b8c84027378f3893a6d01 The secret spend key is kept encrypted in memory, and decrypted on the fly when needed. Both spend and view secret keys are kept encrypted in a JSON field in the keys file. This avoids leaving the keys in memory due to being manipulated by the JSON I/O API.