aboutsummaryrefslogtreecommitdiff
path: root/src/ringct (follow)
AgeCommit message (Collapse)AuthorFilesLines
2018-08-23add and use constant time 32 byte equality functionmoneromooo-monero1-7/+8
2018-08-22Merge pull request #4210luigi11111-0/+10
4616cf2 Fixed ZMQ-RPC for transactions and GET_BLOCKS_FAST (vtnerd)
2018-08-02Fixed ZMQ-RPC for transactions and GET_BLOCKS_FASTLee Clagett1-0/+10
2018-07-27Merge pull request #4097luigi11111-6/+4
61caab8 crypto: remove slight bias in key generation due to modulo (moneromooo-monero)
2018-07-19Merge pull request #4045luigi11113-14/+14
7cdd147 Changed URLs to HTTPS (einsteinsfool)
2018-07-05crypto: remove slight bias in key generation due to modulomoneromooo-monero1-6/+4
2018-06-26threadpool: allow leaf functions to run concurrentlymoneromooo-monero1-6/+6
Decrease the number of worker threads by one to account for the fact the calling thread acts as a worker thread now
2018-06-23Changed URLs to HTTPSeinsteinsfool3-14/+14
2018-06-06ringct: remove an unnecessary scalarmultBase in zeroCommitmoneromooo-monero2-4/+2
2018-05-04ringct: do not show verification errors with default settingsmoneromooo-monero1-4/+6
2018-03-14Merge pull request #3372Riccardo Spagni1-9/+36
c3e23b2d ringct: 17% improvement in Borromean signature verification (moneromooo-monero)
2018-03-14device: untangle cyclic depenencystoffu5-87/+31
When #3303 was merged, a cyclic dependency chain was generated: libdevice <- libcncrypto <- libringct <- libdevice This was because libdevice needs access to a set of basic crypto operations implemented in libringct such as scalarmultBase(), while libringct also needs access to abstracted crypto operations implemented in libdevice such as ecdhEncode(). To untangle this cyclic dependency chain, this patch splits libringct into libringct_basic and libringct, where the basic crypto ops previously in libringct are moved into libringct_basic. The cyclic dependency is now resolved thanks to this separation: libcncrypto <- libringct_basic <- libdevice <- libcryptonote_basic <- libringct This eliminates the need for crypto_device.cpp and rctOps_device.cpp. Also, many abstracted interfaces of hw::device such as encrypt_payment_id() and get_subaddress_secret_key() were previously implemented in libcryptonote_basic (cryptonote_format_utils.cpp) and were then called from hw::core::device_default, which is odd because libdevice is supposed to be independent of libcryptonote_basic. Therefore, those functions were moved to device_default.cpp.
2018-03-08ringct: 17% improvement in Borromean signature verificationmoneromooo-monero1-9/+36
2018-03-05Merge pull request #3348Riccardo Spagni2-20/+0
c95dddd2 remove unused function keyImageV (h908714124)
2018-03-05Merge pull request #3301Riccardo Spagni1-2/+3
34a2a085 rctSigs - loop invariant code removed from the loop (Dusan Klinec)
2018-03-05remove unused function keyImageVh9087141242-20/+0
2018-03-04Code modifications to integrate Ledger HW device into monero-wallet-cli.cslashm5-48/+124
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.
2018-02-21rctSigs - loop invariant code removed from the loopDusan Klinec1-2/+3
2018-02-16Merge pull request #3226Riccardo Spagni1-0/+1
e4646379 keccak: fix mdlen bounds sanity checking (moneromooo-monero) 2e3e90ac pass large parameters by const ref, not value (moneromooo-monero) 61defd89 blockchain: sanity check number of precomputed hash of hash blocks (moneromooo-monero) 9af6b2d1 ringct: fix infinite loop in unused h2b function (moneromooo-monero) 8cea8d0c simplewallet: double check a new multisig wallet is multisig (moneromooo-monero) 9b98a6ac threadpool: catch exceptions in dtor, to avoid terminate (moneromooo-monero) 24803ed9 blockchain_export: fix buffer overflow in exporter (moneromooo-monero) f3f7da62 perf_timer: rewrite to make it clear there is no division by zero (moneromooo-monero) c6ea3df0 performance_tests: remove add_arg call stray extra param (moneromooo-monero) fa6b4566 fuzz_tests: fix an uninitialized var in setup (moneromooo-monero) 03887f11 keccak: fix sanity check bounds test (moneromooo-monero) ad11db91 blockchain_db: initialize m_open in base class ctor (moneromooo-monero) bece67f9 miner: restore std::cout precision after modification (moneromooo-monero) 1aabd14c db_lmdb: check hard fork info drop succeeded (moneromooo-monero)
2018-02-14Merge pull request #2959Riccardo Spagni1-56/+47
3f1a3fac bulletproofs: more robust challenge computation (moneromooo-monero)
2018-02-02ringct: fix infinite loop in unused h2b functionmoneromooo-monero1-0/+1
Coverity 146775
2018-01-31bulletproofs: more robust challenge computationmoneromooo-monero1-56/+47
Changes from sarang, from a recommendation by an anonymous reviewer
2018-01-31ringct: pseudoOuts moved to prunable in the simple bulletproof casemoneromooo-monero2-12/+66
Saves 64 bytes non prunable data per typical tx This breaks v7 consensus, will require a testnet reorg from v6
2018-01-26Readd copyright starting datexmr-eric3-3/+3
2018-01-26Update 2018 copyrightxmr-eric5-5/+5
2018-01-15ringct: handle exceptions verifying bulletproofs in worker threadsmoneromooo-monero1-4/+11
2018-01-10Merge pull request #2990Riccardo Spagni1-1/+1
2d17feb0 factor STL container serialization (moneromooo-monero)
2017-12-22factor STL container serializationmoneromooo-monero1-1/+1
2017-12-18check accessing an element past the end of a containermoneromooo-monero1-0/+3
2017-12-17N-1/N multisigmoneromooo-monero1-0/+5
2017-12-17Add N/N multisig tx generation and signingmoneromooo-monero3-29/+116
Scheme by luigi1111: Multisig for RingCT on Monero 2 of 2 User A (coordinator): Spendkey b,B Viewkey a,A (shared) User B: Spendkey c,C Viewkey a,A (shared) Public Address: C+B, A Both have their own watch only wallet via C+B, a A will coordinate spending process (though B could easily as well, coordinator is more needed for more participants) A and B watch for incoming outputs B creates "half" key images for discovered output D: I2_D = (Hs(aR)+c) * Hp(D) B also creates 1.5 random keypairs (one scalar and 2 pubkeys; one on base G and one on base Hp(D)) for each output, storing the scalar(k) (linked to D), and sending the pubkeys with I2_D. A also creates "half" key images: I1_D = (Hs(aR)+b) * Hp(D) Then I_D = I1_D + I2_D Having I_D allows A to check spent status of course, but more importantly allows A to actually build a transaction prefix (and thus transaction). A builds the transaction until most of the way through MLSAG_Gen, adding the 2 pubkeys (per input) provided with I2_D to his own generated ones where they are needed (secret row L, R). At this point, A has a mostly completed transaction (but with an invalid/incomplete signature). A sends over the tx and includes r, which allows B (with the recipient's address) to verify the destination and amount (by reconstructing the stealth address and decoding ecdhInfo). B then finishes the signature by computing ss[secret_index][0] = ss[secret_index][0] + k - cc[secret_index]*c (secret indices need to be passed as well). B can then broadcast the tx, or send it back to A for broadcasting. Once B has completed the signing (and verified the tx to be valid), he can add the full I_D to his cache, allowing him to verify spent status as well. NOTE: A and B *must* present key A and B to each other with a valid signature proving they know a and b respectively. Otherwise, trickery like the following becomes possible: A creates viewkey a,A, spendkey b,B, and sends a,A,B to B. B creates a fake key C = zG - B. B sends C back to A. The combined spendkey C+B then equals zG, allowing B to spend funds at any time! The signature fixes this, because B does not know a c corresponding to C (and thus can't produce a signature). 2 of 3 User A (coordinator) Shared viewkey a,A "spendkey" j,J User B "spendkey" k,K User C "spendkey" m,M A collects K and M from B and C B collects J and M from A and C C collects J and K from A and B A computes N = nG, n = Hs(jK) A computes O = oG, o = Hs(jM) B anc C compute P = pG, p = Hs(kM) || Hs(mK) B and C can also compute N and O respectively if they wish to be able to coordinate Address: N+O+P, A The rest follows as above. The coordinator possesses 2 of 3 needed keys; he can get the other needed part of the signature/key images from either of the other two. Alternatively, if secure communication exists between parties: A gives j to B B gives k to C C gives m to A Address: J+K+M, A 3 of 3 Identical to 2 of 2, except the coordinator must collect the key images from both of the others. The transaction must also be passed an additional hop: A -> B -> C (or A -> C -> B), who can then broadcast it or send it back to A. N-1 of N Generally the same as 2 of 3, except participants need to be arranged in a ring to pass their keys around (using either the secure or insecure method). For example (ignoring viewkey so letters line up): [4 of 5] User: spendkey A: a B: b C: c D: d E: e a -> B, b -> C, c -> D, d -> E, e -> A Order of signing does not matter, it just must reach n-1 users. A "remaining keys" list must be passed around with the transaction so the signers know if they should use 1 or both keys. Collecting key image parts becomes a little messy, but basically every wallet sends over both of their parts with a tag for each. Thia way the coordinating wallet can keep track of which images have been added and which wallet they come from. Reasoning: 1. The key images must be added only once (coordinator will get key images for key a from both A and B, he must add only one to get the proper key actual key image) 2. The coordinator must keep track of which helper pubkeys came from which wallet (discussed in 2 of 2 section). The coordinator must choose only one set to use, then include his choice in the "remaining keys" list so the other wallets know which of their keys to use. You can generalize it further to N-2 of N or even M of N, but I'm not sure there's legitimate demand to justify the complexity. It might also be straightforward enough to support with minimal changes from N-1 format. You basically just give each user additional keys for each additional "-1" you desire. N-2 would be 3 keys per user, N-3 4 keys, etc. The process is somewhat cumbersome: To create a N/N multisig wallet: - each participant creates a normal wallet - each participant runs "prepare_multisig", and sends the resulting string to every other participant - each participant runs "make_multisig N A B C D...", with N being the threshold and A B C D... being the strings received from other participants (the threshold must currently equal N) As txes are received, participants' wallets will need to synchronize so that those new outputs may be spent: - each participant runs "export_multisig FILENAME", and sends the FILENAME file to every other participant - each participant runs "import_multisig A B C D...", with A B C D... being the filenames received from other participants Then, a transaction may be initiated: - one of the participants runs "transfer ADDRESS AMOUNT" - this partly signed transaction will be written to the "multisig_monero_tx" file - the initiator sends this file to another participant - that other participant runs "sign_multisig multisig_monero_tx" - the resulting transaction is written to the "multisig_monero_tx" file again - if the threshold was not reached, the file must be sent to another participant, until enough have signed - the last participant to sign runs "submit_multisig multisig_monero_tx" to relay the transaction to the Monero network
2017-12-16move includes around to lessen overall loadmoneromooo-monero1-0/+1
2017-12-09ringct: always use outPk.mask to decode amountsmoneromooo-monero1-19/+3
2017-12-09ringct: do not include bulletproof commitments in signed messagemoneromooo-monero1-3/+3
Those are not serialized, but are restored from the outPk masks, so depending on what tries to validate the tx, those commitments may or may not be filled with valid data at the time. The outPk masks are already hashed as part of the rctSigBase field.
2017-12-08add bulletproofs from v7 on testnetmoneromooo-monero2-41/+90
2017-12-08bulletproofs: switch H/G in Pedersen commitments to match rctmoneromooo-monero1-13/+14
Changes from sarang
2017-12-08integrate bulletproofs into moneromoneromooo-monero4-55/+113
2017-12-08add bulletproofs to the build, with basic unit testsmoneromooo-monero3-2/+843
Based on Java code from Sarang Noether
2017-12-07add a version of ge_double_scalarmult_precomp_vartime with A precompmoneromooo-monero2-0/+10
2017-12-07ringct: add a version of addKeys which returns the resultmoneromooo-monero2-0/+6
2017-11-14remove "using namespace std" from headersmoneromooo-monero3-29/+15
It's nasty, and actually breaks on Solaris, where if.h fails to build due to: struct map *if_memmap;
2017-10-07Subaddresseskenshi841-0/+2
2017-09-14Use a threadpoolHoward Chu1-26/+23
Instead of constantly creating and destroying threads
2017-05-23changed crypto to cncrypto so it generated libcncryptoGentian1-1/+1
fix a cmakelist
2017-04-11Simplified the implementation and features of spanLee Clagett1-1/+4
2017-04-11Improvements for epee binary to hex functions:Lee Clagett1-2/+2
- Performance improvements - Added `span` for zero-copy pointer+length arguments - Added `std::ostream` overload for direct writing to output buffers - Removal of unused `string_tools::buff_to_hex`
2017-03-22ringct: move ge_frombytes_vartime failure error to warningmoneromooo-monero1-11/+13
Avoids scaring people when seeing some invalid txes
2017-02-27ringct: do not require range proof in decodeRct/decodeRctSimplemoneromooo-monero1-4/+2
These fields aren't used, and they'll actually be pruned in some cases
2017-02-21update copyright year, fix occasional lack of newline at line endRiccardo Spagni2-2/+2
2017-02-20core: test key images against validity domainmoneromooo-monero1-0/+4
2017-02-08extract some basic code from libcryptonote_core into libcryptonote_basickenshi842-1/+2
2017-01-26Fix clang build failure, caused by mixing C and C++Timothy D. Prime1-1/+1
Easily fixed by moving a C++ header out of 'extern "C" {...}'. When building with CC=clang CXX=clang++ make, [ 21%] Building CXX object src/ringct/CMakeFiles/obj_ringct.dir/rctTypes.cpp.o In file included from /home/tdprime/bitmonero/src/ringct/rctTypes.cpp:31: In file included from /home/tdprime/bitmonero/src/ringct/rctTypes.h:43: In file included from /home/tdprime/bitmonero/src/crypto/generic-ops.h:34: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0/cstring:100:3: error: conflicting types for 'memchr' memchr(void* __s, int __c, size_t __n) ^ /usr/include/string.h:92:14: note: previous declaration is here extern void *memchr (const void *__s, int __c, size_t __n) ^ ... and 4 more similar errors
2017-01-21ringct: reorder a bit to check quicker tests firstmoneromooo-monero1-17/+17
2017-01-16Change logging to easylogging++moneromooo-monero3-0/+9
This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels.
2017-01-15Merge pull request #1561Riccardo Spagni1-64/+64
d561f4ad enable clang checks that were disabled (Chris Vickio) 0aefb2f6 remove std::move from return statements (pessimizing-move warning) (Chris Vickio) 629d5b76 change counter from bool to int (deprecated-increment-bool warning) (Chris Vickio) fb76d439 add extra braces around subobjects (missing-braces warning) (Chris Vickio) 3b6d5f25 make struct/class declarations consistent (mismatched-tags warning) (Chris Vickio) fcf66925 remove unused fields from network_throttle (unused-private-field warning) (Chris Vickio) 296f8c16 inline unused function (for unused-function warning) (Chris Vickio)
2017-01-14rct: split rct checks between semantics and othermoneromooo-monero2-78/+101
Semantics can be checked early
2017-01-14add extra braces around subobjects (missing-braces warning)Chris Vickio1-64/+64
2016-12-19Removed unused functionsLee Clagett1-16/+0
2016-12-14fix MGs jsonmoneroexamples1-3/+3
2016-12-12Tx verification failing is not an errorluigi11111-5/+5
And rangeProofs are on outputs...
2016-12-08Merge pull request #1414Riccardo Spagni1-0/+19
3b005275 ringct: add sc_check calls in MLSAG_Ver for ss and cc (moneromooo-monero) 2f1732a7 ringct: guard against bad data exceptions in worker threads (moneromooo-monero)
2016-12-07ringct: add sc_check calls in MLSAG_Ver for ss and ccmoneromooo-monero1-0/+5
luigi1111's recommendation
2016-12-07ringct: guard against bad data exceptions in worker threadsmoneromooo-monero1-0/+14
If purported pubkeys aren't actually valid pubkeys, exceptions will fly. These will terminate if thrown in a worker thread. Guard against this.
2016-12-04ringct: luigi1111's changes to fix and speedup Borromean sigsluigi11111-16/+15
2016-12-04ringct: switch to Borromean signaturesShen Noether5-114/+88
2016-12-02ringct: fix MGs serialization to JSONmoneromooo-monero1-1/+5
2016-11-23Added task_region - a fork/join task implementationLee Clagett1-60/+45
2016-11-02adding thread_group for managing async tasksLee Clagett1-98/+50
2016-11-01Merge pull request #1272Riccardo Spagni1-3/+5
48b57d8 monero.supp: valgrind suppressions file (moneromooo-monero) ffd8c41 ringct: check the size of amount_keys is the same as destinations (moneromooo-monero) 836669d ringct: always shutdown the boost io service (moneromooo-monero)
2016-10-29ringct: check the size of amount_keys is the same as destinationsmoneromooo-monero1-0/+2
2016-10-29ringct: always shutdown the boost io servicemoneromooo-monero1-3/+3
Even if no worker threads were started, it needs shutting down or it will cause an invalid access in the io service thread
2016-10-23ringct: some more small optimizationsmoneromooo-monero2-58/+25
2016-10-15ringct: thread verRct and verRctSimplemoneromooo-monero1-17/+119
2016-10-15ringct: remove unneeded type conversionsmoneromooo-monero2-3/+3
2016-10-15ringct: reserve space in vectors to avoid excessive reallocationmoneromooo-monero1-0/+2
2016-10-15ringct: avoid unnecessary memcpymoneromooo-monero1-16/+3
2016-10-15ringct: add a few consts where possiblemoneromooo-monero1-4/+4
2016-10-15ringct: pass vectors by const ref where possiblemoneromooo-monero2-4/+4
2016-10-10Add performance timers for ringct tx verificationmoneromooo-monero1-0/+7
2016-10-08ringct: use const refs as parameters where appropriatemoneromooo-monero3-5/+5
2016-09-26Dropped "bit" from bitmonero.Randi Joseph1-2/+2
2016-09-18cmake: transitive deps and remove deprecated LINK_*redfish1-8/+2
Keep the immediate direct deps at the library that depends on them, declare deps as PUBLIC so that targets that link against that library get the library's deps as transitive deps. Break dep cycle between blockchain_db <-> crytonote_core. No code refactoring, just hide cycle from cmake so that it doesn't complain (cycles are allowed only between static libs, not shared libs). This is in preparation for supproting BUILD_SHARED_LIBS cmake built-in option for building internal libs as shared.
2016-09-14rct: rework serialization to avoid storing vector sizesmoneromooo-monero2-36/+130
2016-08-28ringct: remove unused codemoneromooo-monero1-245/+0
2016-08-28ringct: pass structure by const ref, not valuemoneromooo-monero2-2/+2
2016-08-28ringct: use memcpy/memset instead of handwritten loop where appropriatemoneromooo-monero1-29/+11
2016-08-28ringct: remove spurious copiesmoneromooo-monero1-24/+4
2016-08-28rct: faster Cryptonote/rct conversionsmoneromooo-monero1-8/+8
2016-08-28rct: early out on failure on verRangemoneromooo-monero1-3/+5
2016-08-28ringct: use Cryptonote serialization to hash non prunable datamoneromooo-monero1-21/+9
2016-08-28New "Halfway RingCT" outputs for coinbase transactionsmoneromooo-monero1-2/+7
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.
2016-08-28rct: log why verification failsmoneromooo-monero1-9/+13
and remove some unnecessary variables in the checking code
2016-08-28rct: serialize txnFee as varintmoneromooo-monero1-1/+1
2016-08-28rct amount key modified as per luigi1111's recommendationsmoneromooo-monero4-42/+12
This allows the key to be not the same for two outputs sent to the same address (eg, if you pay yourself, and also get change back). Also remove the key amounts lists and return parameters since we don't actually generate random ones, so we don't need to save them as we can recalculate them when needed if we have the correct keys.
2016-08-28rct: rework v2 txes into prunable and non prunable datamoneromooo-monero2-31/+43
Nothing is pruned, but this allows easier changes later.
2016-08-28rct: rework the verification preparation processmoneromooo-monero2-63/+77
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.
2016-08-28rct: change the simple flag to a typemoneromooo-monero2-10/+14
for future expansion
2016-08-28rct: avoid the need for the last II elementShen Noether3-33/+44
This element is used in the generation of the MLSAG, but isn't needed in verification. Also misc changes in the cryptonote code to match, by mooo.
2016-08-28rct: do not serialize senderPk - it is not used anymoremoneromooo-monero1-1/+1
2016-08-28rct: make the amount key derivable by a third party with the tx keymoneromooo-monero5-24/+52
Scheme design from luigi1114.
2016-08-28rct: do not serialize public keys in outPkmoneromooo-monero3-17/+29
They can be reconstructed from vout
2016-08-28rct: use the already defined H where possiblemoneromooo-monero1-2/+1
Found by luigi1111w
2016-08-28port get_tx_key/check_tx_key to rctmoneromooo-monero2-8/+10
2016-08-28integrate simple rct apimoneromooo-monero3-67/+76
2016-08-28ringct: optimization/cleanup of hash functionsShen Noether3-22/+45
2016-08-28ringct: "simple" ringct variantShen Noether5-3/+249
Allows the fake outs to be in different positions for each ring. For rct inputs only.
2016-08-28ringct: fix size unit mismatch calling keccakmoneromooo-monero1-1/+1
2016-08-28ringct: do not serialize what can be reconstructedmoneromooo-monero3-21/+43
The mixRing (output keys and commitments) and II fields (key images) can be reconstructed from vin data. This saves some modest amount of space in the tx.
2016-08-28ringct: catch errors from ge_frombytes_vartimemoneromooo-monero1-11/+12
2016-08-28ringct: add missing size check for ecdhInfomoneromooo-monero1-0/+1
2016-08-28ringct: change asserts to return false for boolean functionsmoneromooo-monero1-10/+10
2016-08-28add rct to the protocolmoneromooo-monero1-15/+23
It is not yet constrained to a fork, so don't use on the real network or you'll be orphaned or rejected.
2016-08-28ringct: add functions to commit to an amountmoneromooo-monero2-0/+21
One to commit to an amount with zero key (for use with fake commitments for pre-rct outputs), and one with an arbitrary key (for rct outputs).
2016-08-28make rct tx serialization workmoneromooo-monero1-0/+48
It may be suboptimal, but it's a pain to have to rebuild everything when some of this changes. Also, no clue why there seems to be two different code paths for serializing a tx...
2016-08-28ringct: allow no outputs, and add tests for this and feesmoneromooo-monero1-2/+0
2016-08-28ringct: make fee optionalmoneromooo-monero1-2/+9
2016-08-28ringct: txn fee stuffShen Noether3-13/+24
2016-08-28ringct: new {gen,decode}Rct APIs for conveniencemoneromooo-monero2-11/+27
A new version of genRct takes the mixRing as parameter, instead of the inPk. inPk are part of the mixRing, and it is cleaner to pass the mixRing data than to fetch it from the RingCT code. A new version of decodeRct also returns the mask. Also, failure to decode throws, so errors are properly detected.
2016-08-28ringct: add more convenience functionsmoneromooo-monero1-4/+14
2016-08-28ringct: add convenience functions to bridge ringct and cryptonotemoneromooo-monero1-0/+5
2016-08-28ringct: restore verRange check in debug modemoneromooo-monero1-1/+1
2016-08-28ringct: add check for destinations/amount size being equalmoneromooo-monero1-0/+1
2016-08-28ringct: fix off by 1 in mixin usagemoneromooo-monero1-3/+3
2016-08-28ringct: simplify random key generationmoneromooo-monero1-7/+2
2016-08-28ringct: cosmetic fixesShen Noether4-46/+9
Ported from Shen's RingCT repo
2016-08-28ringct: changes to hashToPointSimple to calcualte H2 valuesShen Noether1-0/+5
Ported from Shen's RingCT repo
2016-08-28ringct: compare keys with bitwise equality, not crypto opsShen Noether1-7/+6
Ported from Shen's RingCT repo
2016-08-28ringct: fix size argument to cn_fast_hashShen Noether1-1/+1
Ported from Shen's RingCT repo
2016-08-28Fix sc_0 to skGen in ProveRangeShen Noether1-1/+1
2016-08-28ringct: add a few consts where appropriatemoneromooo-monero2-6/+6
2016-08-28tests: more ringct range proof testsmoneromooo-monero1-1/+1
2016-08-28rct: add serialization machinery to rct typesmoneromooo-monero1-10/+32
2016-08-28serialization: declare do_serialize specializations before usemoneromooo-monero1-1/+1
This lets my gcc picks those instead of the generic template where appropriate (and then fail since std::vector<something> does not have a serialize method.
2016-08-28Added note on generating H2Shen Noether1-1/+2
2016-08-28Fixed missing last index H2Shen Noether1-1/+2
2016-08-28ringct: lock access to the PRNGmoneromooo-monero1-2/+2
2016-08-28ringct: add simple input validationmoneromooo-monero2-32/+74
Throw when inputs aren't the expected size.
2016-08-28ringct: add convenience operators to keymoneromooo-monero1-0/+4
2016-08-28ringct: import of Shen Noether's ring confidential transactionsmoneromooo-monero9-0/+2374