monzero-core.git/tests/core_tests/rct.cpp, branch v0.13.0.2Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.13.0.22018-09-11T13:37:37ZBulletproof aggregated verification and tests2018-09-11T13:37:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-30T19:29:42Zurn:sha1:2a8fcb421bc41eb254f95379dd73238915dd509d
Also constrains bulletproofs to simple rct, for simplicity
Code modifications to integrate Ledger HW device into monero-wallet-cli.2018-03-04T11:54:53Zcslashmcslashm@gmail.com2018-02-20T16:01:27Zurn:sha1:e745c1e38da8e54032660894bb2db0e9a49cccf2
The basic approach it to delegate all sensitive data (master key, secret
ephemeral key, key derivation, ....) and related operations to the device.
As device has low memory, it does not keep itself the values
(except for view/spend keys) but once computed there are encrypted (with AES
are equivalent) and return back to monero-wallet-cli. When they need to be
manipulated by the device, they are decrypted on receive.
Moreover, using the client for storing the value in encrypted form limits
the modification in the client code. Those values are transfered from one
C-structure to another one as previously.
The code modification has been done with the wishes to be open to any
other hardware wallet. To achieve that a C++ class hw::Device has been
introduced. Two initial implementations are provided: the "default", which
remaps all calls to initial Monero code, and the "Ledger", which delegates
all calls to Ledger device.
Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880add bulletproofs from v7 on testnet2017-12-08T13:50:45Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-12-02T21:17:42Zurn:sha1:c83d0b3ee2776d42ad27845534fd82f43cf5c083core_tests: do not include chaingen_tests_list.h in all tests2017-10-20T17:53:43Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-10-20T17:53:43Zurn:sha1:f92f1606748b987efb743649ff9b4ea0df78104b
This fixes all tests being annoyingly rebuilt when one changes
Subaddresses2017-10-07T04:06:21Zkenshi84kenshi84@protonmail.ch2017-02-19T02:42:10Zurn:sha1:53ad5a0f42174bca57e24485ef3d40e4b9cf5599move checkpoints in a separate library2017-09-25T20:16:26Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-09-10T16:35:59Zurn:sha1:5d65a75b69e0e83e69384461f26111666d6bf9aecore_tests: catch (impossible in practice) tx extra api failure2017-09-25T14:48:51Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-09-10T11:39:21Zurn:sha1:50a629b2e6071466c0807084c470b733ef96ca0a
CID 175301
update copyright year, fix occasional lack of newline at line end2017-02-21T17:38:18ZRiccardo Spagniric@spagni.net2017-02-21T17:38:18Zurn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359New "Halfway RingCT" outputs for coinbase transactions2016-08-28T20:30:26Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-12T17:45:07Zurn:sha1:c3b3260ae5b5acde445fa88a6f0909f582903754
When RingCT is enabled, outputs from coinbase transactions
are created as a single output, and stored as RingCT output,
with a fake mask. Their amount is not hidden on the blockchain
itself, but they are then able to be used as fake inputs in
a RingCT ring. Since the output amounts are hidden, their
"dustiness" is not an obstacle anymore to mixing, and this
makes the coinbase transactions a lot smaller, as well as
helping the TXO set to grow more slowly.
Also add a new "Null" type of rct signature, which decreases
the size required when no signatures are to be stored, as
in a coinbase tx.