monzero-core.git/src/crypto/crypto.h, branch v0.11.0.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.11.0.02017-06-22T09:11:13ZSignature proving payment to destination by only revealing key derivation, not the actual tx secret key2017-06-22T09:11:13Zstoffustoffu@protonmail.ch2017-03-29T23:22:16Zurn:sha1:c9e0e944e900012b5789fd54bd8e455e399f94a0update copyright year, fix occasional lack of newline at line end2017-02-21T17:38:18ZRiccardo Spagniric@spagni.net2017-02-21T17:38:18Zurn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359wallet: fix output collision detection for view wallets2016-11-07T18:59:30Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-11-07T18:50:05Zurn:sha1:c80f4d416d2a392dbf7c61b500672a6156b4b77d
View wallets do not have the spend secret key, and are thus
unable to derive key images for incoming outputs. Moreover,
a previous patch set key images to zero as a means to mark
an output as having an unknown key image, so they could be
filled in when importing key images at a later time. That
later patch caused spurious collisions. We now use public
keys to detect duplicate outputs. Public keys obtained from
the blockchain are checked to be identical to the ones
derived locally, so can't be spoofed.
rct amount key modified as per luigi1111's recommendations2016-08-28T20:30:19Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-10T11:48:20Zurn:sha1:d4b62a1e295a7fb19de6081733b1d8e0610cbf08
This allows the key to be not the same for two outputs sent to
the same address (eg, if you pay yourself, and also get change
back). Also remove the key amounts lists and return parameters
since we don't actually generate random ones, so we don't need
to save them as we can recalculate them when needed if we have
the correct keys.
ringct: import of Shen Noether's ring confidential transactions2016-08-28T20:26:54Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-05-13T19:45:20Zurn:sha1:9b1afe5f2d488c64e3fb5e087055cf66d2165391crypto: make clear generate_random_bytes is not thread safe2016-05-14T23:05:59Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-05-14T21:08:10Zurn:sha1:d539be33590f7dfb0013187502744286f2959ee3
And add a thread safe version to encourage proper use
Use boost::thread instead of std::thread2016-03-11T15:09:50ZHoward Chuhyc@symas.com2016-03-11T12:25:28Zurn:sha1:b937a2c915861900d047d4d4a24af31c454e3540
and all other associated IPC
updated copyright year2015-12-31T06:39:56ZRiccardo Spagniric@spagni.net2015-12-31T06:39:56Zurn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51ayear updated in license2015-01-02T16:52:46ZRiccardo Spagniric@spagni.net2015-01-02T16:52:46Zurn:sha1:f4b69d553a249ace3694e3b4fd307ddffa156d7dLicense updated to BSD 3-clause2014-07-23T13:03:52Zfluffyponyric@spagni.net2014-07-23T13:03:52Zurn:sha1:6fc995fe5d5a9f5e74ed520b695d67159aa08b33