monzero-core.git/src/wallet/wallet2.h, branch v0.9.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.12016-01-10T11:56:13Zwallet2: decide at runtime which upper tx size to use2016-01-10T11:56:13Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-01-10T11:56:13Zurn:sha1:67bbb56a6c577f3f1703a04b689896831afaa6e2
The value will be different depending on whether we've reached
the first hard fork, which allows a larger size, or not.
This fixes transactions being rejected by the daemon on mainnet
where the first hard fork is not yet active.
updated copyright year2015-12-31T06:39:56ZRiccardo Spagniric@spagni.net2015-12-31T06:39:56Zurn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51awallet: add a rescan_bc command and rescan_blockchain RPC2015-12-30T15:06:03Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-30T12:58:15Zurn:sha1:bc8a52efd8dcda4544856e724a17c9cba161d4a2
Blockchain hashes and key images are flushed, and blocks are
pulled anew from the daemon.
The console command is shortened to match bc_height.
This should make it a lot easier on users who are currently
told to remove this particular cache file but keep the keys
one, etc, etc.
wallet: protect against exceptions in the block pull thread2015-12-30T12:43:15Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-30T12:43:15Zurn:sha1:92ef6b54fe00d6b2e065b9a50884418ecaa76d93
This can happen when the daemon exits, which would also cause
the wallet to crash via unhandled exception
Merge pull request #5502015-12-22T08:27:44ZRiccardo Spagniric@spagni.net2015-12-22T08:26:58Zurn:sha1:c41f785d56e254780d15ad2bea2c170d371985b7
8c93608 wallet: fix load/save versioning bug for recently added tx data (moneromooo-monero)
wallet: fix load/save versioning bug for recently added tx data2015-12-20T14:03:15Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-20T13:51:55Zurn:sha1:8c93608f2faa6fe7fb2d90d0d48201b465a4441e
The version number passed to those data's serialize function
was always 0, not the wallet's version as I had expected.
A version number now exists for these structures so they're
versioned correctly.
Allow the wallet to access hard fork information2015-12-19T14:52:30Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-19T14:52:30Zurn:sha1:8ea7af1ba3ea74be52893a38ab9c7d5afdc90926
And make it change behavior slightly when close/after first hard fork
wallet: make the wallet refresh type a wallet setting2015-12-05T21:44:25Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-05T21:44:25Zurn:sha1:c6cfe0f26d51b8ef29ff3ecbcb651ef5e9b5b686
instead of a command line setting. It makes sense that is is
a long lived setting.
Merge pull request #5072015-11-29T22:19:47ZRiccardo Spagniric@spagni.net2015-11-29T22:19:44Zurn:sha1:bc1bc4adb246b08adee2144ce2c7e3784f7899f1
62e49a5 wallet: optional automatic refresh from the daemon (moneromooo-monero)
wallet: optional automatic refresh from the daemon2015-11-28T12:41:06Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-11-28T12:38:58Zurn:sha1:62e49a5f02da0963fb0303383626b2c86443d405
The daemon will be polled every 90 seconds for new blocks.
It is enabled by default, and can be turned on/off with
set auto-refresh 1 and set auto-refresh 0 in the wallet.