monzero-core.git/src/rpc, branch v0.9.4Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.42016-04-02T03:05:07ZMerge pull request #7772016-04-02T03:05:07ZRiccardo Spagniric@spagni.net2016-04-02T03:05:07Zurn:sha1:ab43e803311c6f42b7ff50f7bfa02eb6bf4c42f9
8757e46 add blockhashing blob to getblocktemplate (Howard Chu)
Merge pull request #7672016-04-02T03:02:07ZRiccardo Spagniric@spagni.net2016-04-02T03:02:07Zurn:sha1:a38ad63f8f0c9941ea964519f8e9d25db5e594b2
24b3e90 Convey tx verification failure reasons to the RPC client (moneromooo-monero)
add blockhashing blob to getblocktemplate2016-03-30T15:54:36ZHoward Chuhyc@symas.com2016-03-30T01:50:51Zurn:sha1:8757e46b78f2778261dd7b047666b3d8ccc86ae6Convey tx verification failure reasons to the RPC client2016-03-27T11:37:18Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-03-27T11:35:36Zurn:sha1:24b3e9007a8ad0684edcee51df444b21a033e4ba
This allows appropriate action to be taken, like displaying
the reason to the user.
Do just that in simplewallet, which should help a lot in
determining why users fail to send.
Also make it so a tx which is accepted but not relayed is
seen as a success rather than a failure.
New RPC and daemon command to get output histogram2016-03-26T21:10:43Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-03-26T14:30:23Zurn:sha1:600a3cf0c0ca0a99dbdc91d32138db3c8aa4165c
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.
Fix typo on bitmonerod rpc method error.2016-03-15T05:09:21ZMike Cmicro-machine@users.noreply.github.com2016-03-15T05:09:21Zurn:sha1:ee71946cdcfc114d2ce62affa64b9593b6c2ee19rpc: do not return bans if they're effectively spent2016-03-12T13:49:08Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-03-12T13:44:55Zurn:sha1:789e2755f75dbd2b297b3588404f283568cd8eec
The blocked ip list will still hold them till next time
a connection attempt is made with that IP, so the effective
length of the ban may be negative.
new flush_txpool command, and associated RPC call2016-01-30T13:28:26Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-01-30T13:28:26Zurn:sha1:bf6d1474c097ee0affe827fe2e3dac489b290f40
It can flush a particular tx, or the whole pool (the RPC command
can flush a list of transactions too)
rpc: add missing return on error when getting a tx2016-01-30T13:28:12Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-01-30T13:28:12Zurn:sha1:6288295f8e4c7807dba73cbdddd375f105ea5af6Fix V1/V2 use of hard fork related parameters2016-01-29T17:21:11Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-01-29T15:09:17Zurn:sha1:3b1d7e03fcc1caa8898ced33e127f6ba09d66df8
Some of it uses hardcoded height, which will need some thinking
for next (voted upon) fork.