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-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-03T12:31:04Z Riccardo Spagni ric@spagni.net 2017-03-03T12:31:04Z urn:sha1:d35d6261810bea652e526b4c93e6dcf063c498eb 2c468dd4 allow user I/O in millinero, micronero, nanonero, piconero (moneromooo-monero) 2017-03-02T19:02:41Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-03-01T22:27:27Z urn:sha1:2c468dd42989d429ae2ebcd696332a4092b4b4cc 2017-02-27T22:29:00Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-27T20:26:17Z urn:sha1:7a44f38a7f34f0a01785d0f8c2f53a8d0f98619a 2017-02-21T17:38:18Z Riccardo Spagni ric@spagni.net 2017-02-21T17:38:18Z urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359 2017-02-10T22:35:25Z Riccardo Spagni ric@spagni.net 2017-02-10T22:35:25Z urn:sha1:eacf2124b6822d088199179b18d4587404408e0f ce7fcbb4 Add server auth to monerod, and client auth to wallet-cli and wallet-rpc (Lee Clagett) 2017-02-08T13:45:15Z kenshi84 kenshi84@protonmail.ch 2017-01-26T15:07:23Z urn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96 2017-02-06T06:15:41Z Lee Clagett code@leeclagett.com 2017-02-05T22:48:03Z urn:sha1:ce7fcbb4aea884bb4bf433cf419ffa267f859c87 2017-02-04T15:18:38Z Riccardo Spagni ric@spagni.net 2017-02-04T15:18:38Z urn:sha1:31cf4e736203d687be97d3f65425fcdbcbe77ac6 f97526e6 simplewallet: option to always ask password for any crytical operations (kenshi84)