monzero-core.git/src/blockchain_utilities, branch v0.9.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.02015-12-31T21:12:13Zupdate version2015-12-31T21:12:13ZRiccardo Spagniric@spagni.net2015-12-31T21:12:13Zurn:sha1:5c71f5d13ebb5db5743f81161382a831f9fa8450updated copyright year2015-12-31T06:39:56ZRiccardo Spagniric@spagni.net2015-12-31T06:39:56Zurn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51aAdd missing semicolons after log statements2015-12-19T14:47:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-19T14:47:37Zurn:sha1:3f2970fadbe2d4dc7057d0c3b83faa93b8622bdeblockchain_db: make the indexing base a BlockchainDB virtual function2015-12-05T18:41:29Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-05T18:41:29Zurn:sha1:a3c5ca077c27b7a8fe5ee0a7afdc1d30b6f8ffe8blockchain_dump: fix output key dump for BDB 1-based indices2015-12-05T12:40:01Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-05T12:40:01Zurn:sha1:a70211842693f00f81c2374b7999eda9e184efce
Berkeley DB uses 1 based indices for RECNO databases, and the
implementation of BlockchainDB for Berkeley DB assumes 1 based
indices are passed to the API, whereas the LMDB one assumes
0 based indices. This is all internally consisteny, but since
the BDB code stores 1 based indices in the database, external
users have to be aware of this, as the indices will be off by
one depending on which DB is used.
cn_deserialize: a new tool to decode blocks and transactions2015-11-22T21:52:14Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-11-22T21:52:14Zurn:sha1:410c6cf3bd1d46c5cf030b0d1daff9362a0e6ae6Merge pull request #4932015-11-21T11:08:42ZRiccardo Spagniric@spagni.net2015-11-21T11:08:39Zurn:sha1:9276233b9ea58a19a5c1490b70cbec90ebcc3147
f3724ae Fix startup crash when using a locale boost does not like (moneromooo-monero)
0c1dae3 i18n: allow language to be passed as a parameter (moneromooo-monero)
Fix startup crash when using a locale boost does not like2015-11-21T10:13:10Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-11-21T10:13:10Zurn:sha1:f3724aef881ff2fdada98eddc792059e4e18c1c8
There are various locale related bugs in various versions of boost,
where exceptions are thrown in boost::filesystem APIs when the
current locale is not to boost's liking. It's not clear what "not
to boost's liking" means in detail, though "en" and "en_US.UTF-8"
are not to its liking.
Fix it by running a test function that's known to throw in such
a case, and resetting LANG and LC_ALL to C if an exception is
thrown. In simplewallet, the locale is queried before that so the
correct translations will still be used.
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.
blockchain_dump: fix build without berkeley db2015-10-30T22:48:04Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-10-30T22:48:04Zurn:sha1:b1d0c8a049c9b59c54ef2babc7aa9f2ca721e405