monero.git - Monero: the secure, private, untraceable cryptocurrency

Age	Commit message (Collapse)	Author	Files	Lines
2022-04-18	Add view tags to outputs to reduce wallet scanning time	j-berman	1	-0/+1
	Implements view tags as proposed by @UkoeHB in MRL issue https://github.com/monero-project/research-lab/issues/73 At tx construction, the sender adds a 1-byte view tag to each output. The view tag is derived from the sender-receiver shared secret. When scanning for outputs, the receiver can check the view tag for a match, in order to reduce scanning time. When the view tag does not match, the wallet avoids the more expensive EC operations when deriving the output public key using the shared secret.
2022-04-06	Merge pull request #8197	luigi1111	1	-1/+1
	da9aa1f Copyright: Update to 2022 (mj-xmr)
2022-04-04	Bulletproofs+	Sarang Noether	1	-0/+1

2022-03-04	Copyright: Update to 2022	mj-xmr	1	-1/+1

2020-10-28	Add RELINK_TARGETS, monero_add_target_no_relink and use ↵	mj-xmr	1	-1/+1
	monero_add_executable/monero_add_library where possible (mj-xmr) Add monero_add_minimal_executable and use in tests This is done in order not to have to relink targets, when just an .so changed, but not its interface.
2020-05-06	Update copyright year to 2020	SomaticFanatic	1	-1/+1
	Update copyright year to 2020
2019-03-24	Make difficulty 128 bit instead of 64 bit	moneromooo-monero	1	-0/+1
	Based on Boolberry work by: jahrsg <jahr@jahr.me> cr.zoidberg <crypto.zoidberg@gmail.com>
2019-03-05	Update 2019 copyright	binaryFate	1	-1/+1

2018-10-22	performance_tests: sc_check and ge_dsm_precomp	moneromooo-monero	1	-0/+2

2018-09-11	performance_tests: add signature generation/verification	moneromooo-monero	1	-0/+1

2018-09-11	add Straus multiexp	moneromooo-monero	1	-0/+1

2018-09-11	performance_tests: add crypto ops	moneromooo-monero	1	-0/+1

2018-09-11	performance_tests: add bulletproofs	moneromooo-monero	1	-0/+1

2018-09-11	performance_tests: add (Borromean) range proofs	moneromooo-monero	1	-0/+1

2018-01-26	Update 2018 copyright	xmr-eric	1	-1/+1

2017-12-18	performance_tests: add a test for subaddress expansion	moneromooo-monero	1	-0/+2

2017-05-23	changed crypto to cncrypto so it generated libcncrypto	Gentian	1	-1/+1
	fix a cmakelist
2017-02-21	update copyright year, fix occasional lack of newline at line end	Riccardo Spagni	1	-1/+1

2017-01-16	Change logging to easylogging++	moneromooo-monero	1	-0/+1
	This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=:FATAL This one is very verbose: MONERO_LOGS=:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net logs only at INFO: MONERO_LOGS=:ERROR,net:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels.
2016-10-26	tests: add performance test for keypair::generate	moneromooo-monero	1	-0/+1

2016-10-08	tests: add performance test for ge_frombytes_vartime	moneromooo-monero	1	-0/+1
	At luigi1111's request
2016-10-08	tests: add performance tests for rct signatures	moneromooo-monero	1	-1/+1

2016-09-18	cmake: transitive deps and remove deprecated LINK_*	redfish	1	-2/+1
	Keep the immediate direct deps at the library that depends on them, declare deps as PUBLIC so that targets that link against that library get the library's deps as transitive deps. Break dep cycle between blockchain_db <-> crytonote_core. No code refactoring, just hide cycle from cmake so that it doesn't complain (cycles are allowed only between static libs, not shared libs). This is in preparation for supproting BUILD_SHARED_LIBS cmake built-in option for building internal libs as shared.
2015-12-31	updated copyright year	Riccardo Spagni	1	-1/+1

2015-01-02	year updated in license	Riccardo Spagni	1	-1/+1

2014-10-24	cmake: fix up link lines	Ben Boeckel	1	-1/+2

2014-10-24	cmake: support 2.8.7	Ben Boeckel	1	-1/+1
	Older versions of CMake support LINK_{PUBLIC,PRIVATE} while newer versions prefer PUBLIC and PRIVATE instead, but still support the LINK_ prefix.
2014-10-23	cmake: put each test executable in its own directory	Ben Boeckel	1	-0/+60