monzero-core.git/src/rpc/core_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.
rpc: send global indices along with blocks/transacions on refresh2016-08-28T20:29:38Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-13T18:26:11Zurn:sha1:3cb2edec6623e1a6b10d67c7335b55ccb410b336
This plugs a privacy leak, where the wallet tells the daemon
which transactions contain outputs for the wallet by asking
for additional information for that particular transaction.
As a nice bonus, this actually makes refresh slightly faster.
mixable transactions must be rct for v32016-08-28T20:29:07Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-02T09:02:12Zurn:sha1:c2ec6d35b9a8130fe1253d4933741506fee504cfcore: new /getrandom_rctouts.bin binary RPC call2016-08-28T20:28:16Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-06-05T09:46:18Zurn:sha1:4258dab4d6dcbf563daa054c7e05e8a0027290b8
to get random ringct outputs to mix with
remove original Cryptonote blockchain_storage blockchain format2016-08-28T20:27:32Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-05-26T20:48:18Zurn:sha1:9e82b694da120708652871b55f639d1ef306a7ecdaemon: print time to next fork2016-08-12T19:32:23Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-12T18:19:25Zurn:sha1:7e4e0021f422eec55fb0417b1d6e86ceddc1934fFake outs set is now decided by the wallet2016-08-11T13:35:27Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-02T20:48:09Zurn:sha1:11dc091464a6cef41434a0bb9f8604f6151c8dc5
This plugs a privacy leak from the wallet to the daemon,
as the daemon could previously see what input is included
as a transaction input, which the daemon hadn't previously
supplied. Now, the wallet requests a particular set of
outputs, including the real one.
This can result in transactions that can't be accepted if
the wallet happens to select too many outputs with non standard
unlock times. The daemon could know this and select another
output, but the wallet is blind to it. It's currently very
unlikely since I don't think anything uses non default
unlock times. The wallet requests more outputs than necessary
so it can use spares if any of the returns outputs are still
locked. If there are not enough spares to reach the desired
mixin, the transaction will fail.
new unlocked parameter to output_histogram2016-08-01T21:16:00Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-01T21:16:00Zurn:sha1:1593553e03aef8d44621aaf79a33ba25f69a2bd7
This constrains the number of instances of any amount
to the unlocked ones (as defined by the default unlock time
setting: outputs with non default unlock time are not
considered, so may be counted as unlocked even if they are
not actually unlocked).
core_rpc_server: fix gray/white peer list mixup2016-07-26T19:02:43Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-26T19:02:43Zurn:sha1:22d8344cb5f3338a87230e1832301417cbabdeafAdd a daemon RPC version, and make simplewallet check it2016-07-10T15:49:40Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-07-10T15:49:40Zurn:sha1:014f3a0d39e5314c13ae7420283b1ea5eb593517
If the version is different, simplewallet will refuse to use that
daemon, unless --allow-mismatched-daemon-version is used.