Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.9.3 2016-02-08T18:52:00Z 2016-02-08T18:52:00Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-02-08T18:47:56Z urn: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. 2016-02-08T16:50:51Z warptangent warptangent@tutanota.com 2016-02-05T07:05:11Z urn:sha1:8f863e742d2cd6a959361ec232c4c93473914568 2016-02-02T18:58:39Z Thomas Winget tewinget@gmail.com 2015-10-08T02:28:11Z urn:sha1:1642be242d51c183532752bd482a04767c263740 - Blockchain should store if it's running on testnet or not - moved loading compiled-in block hashes to its own function for clarity - on handle_get_objects, should now correctly return false if a block's transactions are missing - replace instances of BOOST_FOREACH with C++11 for loops in Blockchain. 2016-01-30T13:28:26Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-01-30T13:28:26Z urn:sha1:bf6d1474c097ee0affe827fe2e3dac489b290f40 It can flush a particular tx, or the whole pool (the RPC command can flush a list of transactions too) 2015-12-31T06:39:56Z Riccardo Spagni ric@spagni.net 2015-12-31T06:39:56Z urn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51a 2015-12-26T18:01:24Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2015-12-26T18:01:24Z urn:sha1:b0541a56eb0f3b07eb482726c3d99310e476a9fa 2015-12-25T22:13:38Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2015-12-25T22:13:38Z urn:sha1:f33a88cfc17177e3a079ee2226df9674dfa2d138 If the block reward was too high, the verification failed flag was set, but the function continued. The code which was supposed to trap this flag and return failure failed to trap it, and, while the block was not added to the chain, the function would return success. The reason for avoiding returning when the block reward problem was detected was to be able to return any transactions to the pool if needed. This is now mooted by moving the transaction return code to a separate function, which is now called at all appropriate points, making the logic much simpler, and hopefully correct now. We also move the hard fork version check after the prev_id check, as block which does not go on the top of the chain might not have the expected version there, without being invalid just for this reason. Last, we trap the case where a block fails to be added due to using already spent key images, to set the verification failed flag. 2015-12-25T22:07:58Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2015-12-25T22:07:58Z urn:sha1:81cb0fcdccf08afd6f37d21ccfefb31131fd3950 Block reward may now be less than the full amount allowed. This was breaking the bitflipping test. We now keep track of whether a block which was accepted by the core has a lower than allowed block reward, and allow this in the test. 2015-12-19T14:52:30Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2015-12-19T14:52:30Z urn:sha1:8ea7af1ba3ea74be52893a38ab9c7d5afdc90926 And make it change behavior slightly when close/after first hard fork 2015-12-15T14:22:06Z warptangent warptangent@tutanota.com 2015-12-14T04:54:39Z urn:sha1:725acc7f17e47e0ea0e7e690f241ee8a286411ea Remove trailing whitespace in same files.