monzero-core.git/src/ringct, branch v0.11.0.0 Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.11.0.0 2017-05-23T11:45:40Z changed crypto to cncrypto so it generated libcncrypto 2017-05-23T11:45:40Z Gentian gkruja2@gmail.com 2017-05-21T06:21:17Z urn:sha1:4b932ff3148550fd3e9cf07fccb807a9cdde59ef fix a cmakelist Simplified the implementation and features of span 2017-04-11T20:35:14Z Lee Clagett code@leeclagett.com 2017-03-09T20:50:51Z urn:sha1:93e10f1cc40f31aa4fd10ed09a42cc9caa3bdd8c Improvements for epee binary to hex functions: 2017-04-11T20:35:00Z Lee Clagett code@leeclagett.com 2017-02-27T18:33:16Z urn:sha1:4a8f96f95da51e6b570a00ddcfefe100844d8f8b - Performance improvements - Added `span` for zero-copy pointer+length arguments - Added `std::ostream` overload for direct writing to output buffers - Removal of unused `string_tools::buff_to_hex` ringct: move ge_frombytes_vartime failure error to warning 2017-03-22T21:26:38Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-03-22T21:26:38Z urn:sha1:00cbf72064d3a7ffaeef3ba47d47d290bccea29c Avoids scaring people when seeing some invalid txes ringct: do not require range proof in decodeRct/decodeRctSimple 2017-02-27T22:28:45Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-27T22:03:31Z urn:sha1:da18898f0e64a9bec75e10230038759ccf95205e These fields aren't used, and they'll actually be pruned in some cases update copyright year, fix occasional lack of newline at line end 2017-02-21T17:38:18Z Riccardo Spagni ric@spagni.net 2017-02-21T17:38:18Z urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359 core: test key images against validity domain 2017-02-20T22:58:25Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-20T17:41:39Z urn:sha1:d282cfcc46d39dc49e97f9ec5cedf7425e74d71f extract some basic code from libcryptonote_core into libcryptonote_basic 2017-02-08T13:45:15Z kenshi84 kenshi84@protonmail.ch 2017-01-26T15:07:23Z urn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96 Fix clang build failure, caused by mixing C and C++ 2017-01-27T01:30:00Z Timothy D. Prime tdprime@teleosmedia.com 2017-01-27T01:30:00Z urn:sha1:6b145763f7cc7afa115b85df5827a4f46793738a Easily fixed by moving a C++ header out of 'extern "C" {...}'. When building with CC=clang CXX=clang++ make, [ 21%] Building CXX object src/ringct/CMakeFiles/obj_ringct.dir/rctTypes.cpp.o In file included from /home/tdprime/bitmonero/src/ringct/rctTypes.cpp:31: In file included from /home/tdprime/bitmonero/src/ringct/rctTypes.h:43: In file included from /home/tdprime/bitmonero/src/crypto/generic-ops.h:34: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0/cstring:100:3: error: conflicting types for 'memchr' memchr(void* __s, int __c, size_t __n) ^ /usr/include/string.h:92:14: note: previous declaration is here extern void *memchr (const void *__s, int __c, size_t __n) ^ ... and 4 more similar errors ringct: reorder a bit to check quicker tests first 2017-01-21T20:29:22Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-01-21T20:29:22Z urn:sha1:6cc7d261406ad38071065a79f66c4366f65b65ba