monzero-core.git/src/wallet/wallet_rpc_server.cpp, branch v0.10.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.10.02016-09-18T19:32:02Zepee: optionally restrict HTTP service to a configurable user agent2016-09-18T19:32:02Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-09-07T20:38:41Zurn:sha1:eeb2bbc0fcc9c5afa2c3aa12915b4d3f31115e56
This is intended to catch traffic coming from a web browser,
so we avoid issues with a web page sending a transfer RPC to
the wallet. Requiring a particular user agent can act as a
simple password scheme, while we wait for 0MQ and proper
authentication to be merged.
wallet: change priority/fee to ArticMine's recommendation2016-09-16T10:50:52Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-09-16T10:50:52Zurn:sha1:9c7b0cb28e015f5f7542932e0edcade748c1a67d
We keep 1, 2, 3 multipliers till the fee decrase from 0.01/kB
to 0.002/kB, where we start using 1, 20, 166 multipliers.
This ensures the higher multiplier will compensate for the
block reward penalty when pushing past 100% of the past median.
The fee-multiplier wallet setting is now rename to priority,
since it keeps its [0..3] range, but maps to different multiplier
values.
wallet_rpc_server: return payment id in make_integrated_address RPC2016-08-29T11:18:22Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-29T11:18:22Zurn:sha1:adca9035899532902b78b20a593a6c70018b7004
It is useful, especially when requesting a random one
rct amount key modified as per luigi1111's recommendations2016-08-28T20:30:19Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-10T11:48:20Zurn:sha1:d4b62a1e295a7fb19de6081733b1d8e0610cbf08
This allows the key to be not the same for two outputs sent to
the same address (eg, if you pay yourself, and also get change
back). Also remove the key amounts lists and return parameters
since we don't actually generate random ones, so we don't need
to save them as we can recalculate them when needed if we have
the correct keys.
wallet: do not store signatures in the wallet cache2016-08-28T20:30:10Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-06T18:19:25Zurn:sha1:a47ceee83b0e04a3c440d9ca5a75cf0ac1d9256e
Saves some substantial space.
Also avoid calculating tx hashes we don't need.
wallet: always use new algorithm for RPC transfers2016-08-28T20:30:03Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-30T08:37:22Zurn:sha1:1303cda646848450986b73ef66449cc4eea2cc0c
This ensures we get rct transactions when appropriate
wallet: do not try to use rct txes a few blocks before the fork2016-08-28T20:29:53Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-27T20:18:08Zurn:sha1:c27194a44426ee680fd6a3992685637b8431be39port get_tx_key/check_tx_key to rct2016-08-28T20:29:24Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-11T22:14:58Zurn:sha1:e81a2b2cfabfb1ad9aaade752a863f1448fc89cdadd rct to the protocol2016-08-28T20:28:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-06-15T22:37:13Zurn:sha1:dc4aad7eb5fffa450d4c5eb094cf962e45b2f43a
It is not yet constrained to a fork, so don't use on the real network
or you'll be orphaned or rejected.
wallet: new {ex,im}port_key_images commands and RPC calls2016-07-24T08:23:30Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-15T11:11:55Zurn:sha1:ebf97d76f0020eb027175818ebbdafd6d578aa77
They are used to export a signed set of key images from a wallet
with a private spend key, so an auditor with the matching view key
may see which of those are spent, and which are not.