monzero-core.git/src/cryptonote_core/blockchain.h, 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-08-28T20:30:16Zrct: rework the verification preparation process2016-08-28T20:30:16Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-09T10:38:54Zurn:sha1:d93746b6d37dd5b99d16331ec8e24e8a1f7e4652
The whole rct data apart from the MLSAGs is now included in
the signed message, to avoid malleability issues.
Instead of passing the data that's not serialized as extra
parameters to the verification API, the transaction is modified
to fill all that information. This means the transaction can
not be const anymore, but it cleaner in other ways.
add 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.
core: 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
daemon: 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).
blockchain: remove the tx validation result cache2016-04-06T18:01:28Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-04-06T17:56:33Zurn:sha1:4cfb4dff3e8ae213cc87b2d0234a519d2e8674b7
As pointed out by smooth, a transaction's validity may change
over time as the blockchain changes.
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)
Merge pull request #7652016-03-27T12:09:53ZRiccardo Spagniric@spagni.net2016-03-27T12:09:53Zurn:sha1:2b57845766ee41fef14166219b9f3aa8ba3f68a2
d5d46e6 tests: obligatory hardfork unit build fix after interface change (moneromooo-monero)
25672d3 wallet: pass std::function by const ref, not value (moneromooo-monero)
0be6e08 wallet: do not leak owned amounts to the daemon unless --trusted-daemon (moneromooo-monero)
12146da wallet: change sweep_dust to sweep_unmixable (moneromooo-monero)
600a3cf New RPC and daemon command to get output histogram (moneromooo-monero)
f9a2fd2 wallet: handle rare case where fee adjustment can bump to the next kB (moneromooo-monero)
f26651a wallet: factor fee calculation (moneromooo-monero)
Convey 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.