monzero-core.git/src/cryptonote_core/cryptonote_core.h, branch v0.9.3Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.32016-03-21T10:12:23ZRevert "Print stack trace upon exceptions"2016-03-21T10:12:23Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-03-21T10:12:12Zurn:sha1:f7301c3563e7ae19b8d7c65d8bc88f3c42eefc09
Ain't nobody got time for link/cmake skullduggery.
This reverts commit fff238ec94ac6d45fc18c315d7bc590ddfaad63d.
Print stack trace upon exceptions2016-03-19T21:48:36Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-03-19T21:48:36Zurn:sha1:fff238ec94ac6d45fc18c315d7bc590ddfaad63d
Useful for debugging users' logs
core: check whether an update is needed straight away2016-02-17T22:57:38Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-02-17T22:57:38Zurn:sha1:27d4e50dfac5ca48104a87eddaa974d8cbffae63core_tests: add tests for hard fork behaviors (MRL-0004)2016-02-08T18:52:00Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-02-08T18:47:56Zurn:sha1:a333c42cdeab4675c22df25255313752d81a2d4e
We also replace the --fakechain option with an optional structure
containing details about configuration for the core/blockchain,
for test purposes. This seems more future friendly.
core: prevent the database from being used by multiple daemons2016-01-31T12:58:08Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-01-31T12:58:08Zurn:sha1:8b3539bc11639f2feaebdbb2fcbc9578806f5702
A boost lock is used to determine whether more than one process
wants to access the database. The boost file_lock doesn't seem
to like locking directories, so we use an arbitrary file in it.
This allows to still run two daemons if they have different
database directories (ie, LMDB/BDB, different data directories).
updated copyright year2015-12-31T06:39:56ZRiccardo Spagniric@spagni.net2015-12-31T06:39:56Zurn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51aReplace tabs with two spaces for consistency with rest of codebase2015-12-15T14:22:06Zwarptangentwarptangent@tutanota.com2015-12-14T04:54:39Zurn:sha1:725acc7f17e47e0ea0e7e690f241ee8a286411ea
Remove trailing whitespace in same files.
add a --fakechain argument for tests2015-12-13T11:38:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-13T11:38:37Zurn:sha1:10da0a0b7cc70fad0ffde60bdd04926484fb043a
The core tests use the blockchain, and reset it to be able
to add test data to it. This does not play nice with the
databases, since those will save that data without an explicit
save call.
We add a fakechain flag that the tests will set, which tells
the core and blockchain code to use a separate database, as
well as skip a few things like checkpoints and fixup, which
only make sense for real data.
Relay transactions when they linger too long in the pool2015-11-21T00:56:21Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-11-21T00:26:48Zurn:sha1:932994c0cb25d21ccc5795c23b0e342427260625
The last relayed time of a transaction is maintained, and
transactions will be relayed again if they are still in the
pool after a certain amount of time, which increases with
the transaction's age. All such transactions are resent,
whether or not they originated on the local node.
core: add consts where appropriate2015-09-19T15:47:35Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-09-19T10:25:57Zurn:sha1:a7177610b31a32fde7975af00f0d2c4cfee9ba67