monzero-core.git/tests/core_tests/chaingen.cpp, branch crash-plMonzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=crash-pl2018-03-14T12:00:16Zkeypair::generate: always require hw::device to avoid possible mistake2018-03-14T12:00:16Zstoffustoffu@protonmail.ch2018-03-05T08:02:17Zurn:sha1:8705beaf51c12d7eab5f56f615ec529a2a8efc27Code 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:18216f19dd479466cb7fd38f52d23bddfcfd4880remove "using namespace std" from headers2017-11-14T16:56:10Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2017-10-10T14:47:08Zurn:sha1:383ff4f68943c5d998fba8caa20aee481583f214
It's nasty, and actually breaks on Solaris, where if.h fails to
build due to:
struct map *if_memmap;
core_tests: fix for subaddress patch2017-10-17T13:29:01Zkenshi84kenshi84@protonmail.ch2017-10-16T23:45:00Zurn:sha1:88ebfd646a5e75de0544958e88d152df86e310ecSubaddresses2017-10-07T04:06:21Zkenshi84kenshi84@protonmail.ch2017-02-19T02:42:10Zurn:sha1:53ad5a0f42174bca57e24485ef3d40e4b9cf5599update copyright year, fix occasional lack of newline at line end2017-02-21T17:38:18ZRiccardo Spagniric@spagni.net2017-02-21T17:38:18Zurn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359extract some basic code from libcryptonote_core into libcryptonote_basic2017-02-08T13:45:15Zkenshi84kenshi84@protonmail.ch2017-01-26T15:07:23Zurn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96New "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.
Add rct core tests2016-08-28T20:28:53Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-06-27T17:56:19Zurn:sha1:106e3dc3d4151ff2b9836ead3177892de92df2ce