monzero-core.git/src/cryptonote_core/blockchain.h, branch v0.10.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.10.12016-12-04T12:27:45ZFix delayed exit when syncing2016-12-04T12:27:45Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-04T12:27:45Zurn:sha1:3f7d6fb57d1bfb5ee806d3facc1261efe3ad14a0Add a get_outs (fully text based) version of get_outs.bin2016-11-22T20:00:40Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-11-22T20:00:40Zurn:sha1:2c0173c722af7a6dc1f30c3423d97247a4fd1ad7rpc: add a dynamic fee estimation RPC call2016-10-31T08:38:00Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-10-28T20:19:40Zurn:sha1:e6deb8abda0b6560c8691f376d8a86aab163dd77core: dynamic fee algorithm from ArticMine2016-10-31T08:37:08Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-10-27T22:43:44Zurn:sha1:82dbba10d467e28e56929e2e7f3b1f04d4635da4
The fee will vary based on the base reward and the current
block size limit:
fee = (R/R0) * (M0/M) * F0
R: base reward
R0: reference base reward (10 monero)
M: block size limit
M0: minimum block size limit (60000)
F0: 0.002 monero
Starts applying at v4
wallet: select part of the fake outs from recent outputs2016-10-15T17:17:16Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-09-17T14:45:51Zurn:sha1:88faec75fe768a5702c3f8d9384c0913e4af22aa
25% of the outputs are selected from the last 5 days (if possible),
in order to avoid the common case of sending recently received
outputs again. 25% and 5 days are subject to review later, since
it's just a wallet level change.
rct: 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.