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-24T12:34:55Z Riccardo Spagni ric@spagni.net 2017-03-24T12:34:55Z urn:sha1:92c2d79d1071800885b551e58b2048497fbd01ae a8646b09 Wallet API: add hard fork info functions (Jaquee) 2017-03-24T12:33:47Z Riccardo Spagni ric@spagni.net 2017-03-24T12:33:46Z urn:sha1:f54337778975adb18b698b41003e13a2587df777 8bbcbcfb wallet rpc: enable solo mining (stoffu) 2017-03-24T08:59:26Z Jaquee jaquee.monero@gmail.com 2017-03-24T08:59:26Z urn:sha1:a8646b0957aa60ffb8f3c2db820db16e40398c4e 2017-03-23T09:25:22Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-03-22T18:03:23Z urn:sha1:558cfc31caeb88398fe5bab9292246739586374d Includes a new RPC to get tx pool hashes fast. 2017-03-21T12:09:42Z Riccardo Spagni ric@spagni.net 2017-03-21T12:09:42Z urn:sha1:70e71a18450aa8e69971ad29793b0b409ffcef22 995969b1 wallet: fix set_log not handling 0,xxx style settings (moneromooo-monero) 2017-03-21T12:09:19Z Riccardo Spagni ric@spagni.net 2017-03-21T12:09:19Z urn:sha1:7769a6e7573e6975aded2f6e156a71d73fcac23c 350e99ae wallet2: cache which pool txes were scanned already (moneromooo-monero) 2017-03-21T12:08:36Z Riccardo Spagni ric@spagni.net 2017-03-21T12:08:36Z urn:sha1:9d157b519de6e2d73b1c695c6e6d22ecea37d365 c1e9ccc7 wallet2: speed up transactions using remote nodes (moneromooo-monero) 2017-03-21T11:17:05Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-03-21T11:17:05Z urn:sha1:995969b1907ee2d55c31ec9a40c39d5518e0ed87