<feed xmlns='http://www.w3.org/2005/Atom'>
<title>monzero-core.git/src/rpc/core_rpc_server.h, branch v0.10.0</title>
<subtitle>Monzero core node, command-line wallet, consensus code, and release tooling.
</subtitle>
<id>https://code.monzero.org/monzero-core.git/atom?h=v0.10.0</id>
<link rel='self' href='https://code.monzero.org/monzero-core.git/atom?h=v0.10.0'/>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/'/>
<updated>2016-09-18T19:32:02Z</updated>
<entry>
<title>epee: optionally restrict HTTP service to a configurable user agent</title>
<updated>2016-09-18T19:32:02Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2016-09-07T20:38:41Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=eeb2bbc0fcc9c5afa2c3aa12915b4d3f31115e56'/>
<id>urn:sha1:eeb2bbc0fcc9c5afa2c3aa12915b4d3f31115e56</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>core: new /getrandom_rctouts.bin binary RPC call</title>
<updated>2016-08-28T20:28:16Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2016-06-05T09:46:18Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=4258dab4d6dcbf563daa054c7e05e8a0027290b8'/>
<id>urn:sha1:4258dab4d6dcbf563daa054c7e05e8a0027290b8</id>
<content type='text'>
to get random ringct outputs to mix with
</content>
</entry>
<entry>
<title>Fake outs set is now decided by the wallet</title>
<updated>2016-08-11T13:35:27Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2016-08-02T20:48:09Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=11dc091464a6cef41434a0bb9f8604f6151c8dc5'/>
<id>urn:sha1:11dc091464a6cef41434a0bb9f8604f6151c8dc5</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Merge pull request #902</title>
<updated>2016-07-20T11:55:59Z</updated>
<author>
<name>Riccardo Spagni</name>
<email>ric@spagni.net</email>
</author>
<published>2016-07-20T11:55:59Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=fc3e135b8387b8aab2eb9917240e7d312c7b0c2f'/>
<id>urn:sha1:fc3e135b8387b8aab2eb9917240e7d312c7b0c2f</id>
<content type='text'>
014f3a0 Add a daemon RPC version, and make simplewallet check it (moneromooo-monero)
</content>
</entry>
<entry>
<title>Add a daemon RPC version, and make simplewallet check it</title>
<updated>2016-07-10T15:49:40Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2016-07-10T15:49:40Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=014f3a0d39e5314c13ae7420283b1ea5eb593517'/>
<id>urn:sha1:014f3a0d39e5314c13ae7420283b1ea5eb593517</id>
<content type='text'>
If the version is different, simplewallet will refuse to use that
daemon, unless --allow-mismatched-daemon-version is used.
</content>
</entry>
<entry>
<title>rpc: fix get_bans and set_bans RPC names, they were missing a _</title>
<updated>2016-07-10T14:10:51Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2016-07-10T14:10:51Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=34ecfdbf157fe780552dd9cb7f7b1122efe611f1'/>
<id>urn:sha1:34ecfdbf157fe780552dd9cb7f7b1122efe611f1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Restrict also 'get_connections' and 'getbans' APIs.</title>
<updated>2016-05-16T11:34:15Z</updated>
<author>
<name>osensei</name>
<email>admin@monerohash.com</email>
</author>
<published>2016-05-16T11:34:15Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=1c0bffb5f0c9b60a4314c22d6689e287227bd423'/>
<id>urn:sha1:1c0bffb5f0c9b60a4314c22d6689e287227bd423</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Don't allow 'flush_txpool' and 'setbans' JSON_RPC methods when running in restricted mode.</title>
<updated>2016-05-14T06:06:04Z</updated>
<author>
<name>osensei</name>
<email>admin@monerohash.com</email>
</author>
<published>2016-05-14T06:06:04Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=9f8bc4946b3993ad4437936dcae705d2c8f1116a'/>
<id>urn:sha1:9f8bc4946b3993ad4437936dcae705d2c8f1116a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add GET_HASHES_FAST rpc, use it in wallet</title>
<updated>2016-04-17T14:25:46Z</updated>
<author>
<name>Howard Chu</name>
<email>hyc@symas.com</email>
</author>
<published>2016-04-13T22:45:02Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=b7140daea2b33d03f65b852de7f1ce4b99661adf'/>
<id>urn:sha1:b7140daea2b33d03f65b852de7f1ce4b99661adf</id>
<content type='text'>
When m_refresh_from_block_height has been set, only hashes will be
retrieved up to that height, instead of full blocks. The same will
be done for "refresh &lt;height&gt;" when the specified height is beyond
the current local blockchain.
</content>
</entry>
<entry>
<title>New RPC and daemon command to get output histogram</title>
<updated>2016-03-26T21:10:43Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2016-03-26T14:30:23Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=600a3cf0c0ca0a99dbdc91d32138db3c8aa4165c'/>
<id>urn:sha1:600a3cf0c0ca0a99dbdc91d32138db3c8aa4165c</id>
<content type='text'>
This is a list of existing output amounts along with the number
of outputs of that amount in the blockchain.

The daemon command takes:
- no parameters: all outputs with at least 3 instances
- one parameter: all outputs with at least that many instances
- two parameters: all outputs within that many instances

The default starts at 3 to avoid massive spamming of all dust
outputs in the blockchain, and is the current minimum mixin
requirement.

An optional vector of amounts may be passed, to request
histogram only for those outputs.
</content>
</entry>
</feed>
