Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.10.3.1 2017-03-25T11:44:04Z 2017-03-25T11:44:04Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-03-24T21:56:58Z urn:sha1:a50c4a4fad9856262638210091d7ce72c547d885 With the change from the original transfer method to the new algorithm, payments to the same destination were merged. It seemed like a good idea, optimizing space. However, it is a useful tool for people who want to split large outputs into several smaller ones (ie, service providers making frequent payments, and who do not like a large chunk of their balance being locked for 10 blocks after each payment). Default to off, which is a change from the previous behavior. 2017-03-25T11:29:11Z Riccardo Spagni ric@spagni.net 2017-03-25T11:29:11Z urn:sha1:119803f26e8c5ea0cfaf36cc3227f06159d25581 2bee92db Fixed typo in v5 hard fork finalized date (Derek Zhang) d17179d1 Fixed typo in CLI wallet help message (Derek Zhang) 2017-03-25T01:05:05Z Derek Zhang derekdyzhang@gmail.com 2017-03-25T01:05:05Z urn:sha1:d17179d14b6f408eb18a9fcc1313c50c9a4c5e80 2017-03-24T21:04:08Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-03-24T20:58:02Z urn:sha1:0ad87db01f19eff22ab9c3998826b7aa943975cf When a single input is enough to satisfy a transfer, the code would previously try to add a second input, to match the "canonical" makeup of a transaction with two inputs and two outputs. This would cause wallets to slowly merge outputs till all the monero ends up in a single output, which causes trouble when making two transactions one after the other, since change is locked for 10 blocks, and an increasing portion of the remaining balance would end up locked on each transaction. There are two new settings (min-output-count and min-output-value) which can control when to stop adding such unneeded second outputs. The idea is that small "dust" outputs will still get added, but larger ones will not. Enable with, eg: set min-output-count 10 set min-output-value 30 to avoid using an unneeded second output of 30 monero or more, if there would be less than 10 such outputs left. This does not invalidate any other reason why such outputs would be used (ie, when they're really needed to satisfy a transfer, or when randomly picked in the normal course of selection). This may be improved in the future. 2017-03-22T13:10:34Z Akademik Prokhor Zakharov woordenboer@planet.nl 2017-03-22T13:10:34Z urn:sha1:9bccf1b11efbf4f595c97cf8072acfab2eb31628 New pull request because I couldn't figure out how to change the previous one. 1. For clarity, I want to focus the help text for the 'transfer' command on the most typical use case (a single payment). 2. New users will prefer to use 'transfer', so the older method 'transfer_original' should refer to 'transfer' rather than the other way around. 2017-03-21T11:17:05Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-03-21T11:17:05Z urn:sha1:995969b1907ee2d55c31ec9a40c39d5518e0ed87 2017-03-18T18:31:37Z Riccardo Spagni ric@spagni.net 2017-03-18T18:31:37Z urn:sha1:82411cdf3a35cef0518a6431bed016977f5deb50 f9a2b527 simplewallet: allow setting tx priority in watch wallets (moneromooo-monero) 2017-03-18T18:30:19Z Riccardo Spagni ric@spagni.net 2017-03-18T18:30:19Z urn:sha1:f33a696ec7de8dbadcc65cbed4bcb1ef7b720609 d0238313 use const references in catch blocks (moneromooo-monero) 2017-03-18T18:07:54Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-03-18T18:07:54Z urn:sha1:f9a2b5279d6243fb1fc0f585516c6c79a8301962 Those can create unsigned transactions 2017-03-18T12:56:07Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-03-18T12:56:07Z urn:sha1:d0238313278206e505473cef4d4bed88b75b96fd