aboutsummaryrefslogtreecommitdiff
path: root/tests/core_tests
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Merge pull request #6146Alexander Blair2020-01-241-2/+2
|\ \ \ | |/ / |/| | | | | 70c9cd3c Change to Tx diffusion (Dandelion++ fluff) instead of flooding (Lee Clagett)
| * | Change to Tx diffusion (Dandelion++ fluff) instead of floodingLee Clagett2019-11-041-2/+2
| | |
* | | Merge pull request #6115Alexander Blair2020-01-161-0/+2
|\ \ \ | | | | | | | | | | | | 27522aaa core_tests: reset thread pool between tests (moneromooo-monero)
| * | | core_tests: reset thread pool between testsmoneromooo-monero2019-11-101-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Avoids a DB error (leading to an assert) where a thread uses a read txn previously created with an environment that was since closed and reopened. While this usually works since BlockchainLMDB renews txns if it detects the environment has changed, this will not work if objects end up being allocated at the same address as the previous instance, leading to stale data usage. Thanks hyc for the LMDB debugging.
* | | | Merge pull request #6110Alexander Blair2020-01-113-22/+180
|\ \ \ \ | |_|/ / |/| | | | | | | da6c807f tests: fix HF12 chaingen - construct bc object from events (Dusan Klinec)
| * | | tests: fix HF12 chaingen - construct bc object from eventsDusan Klinec2019-11-133-22/+180
| |/ /
* / / Adding support for hidden (anonymity) txpoolLee Clagett2019-11-027-22/+723
|/ /
* / cryptonote: untangle dependency from miner to blockchainmoneromooo-monero2019-10-311-2/+6
|/ | | | It causes link errors at least on mac
* Merge pull request #5915luigi11112019-10-081-5/+13
|\ | | | | | | 8330e77 monerod can now sync from pruned blocks (moneromooo-monero)
| * monerod can now sync from pruned blocksmoneromooo-monero2019-09-271-5/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | If the peer (whether pruned or not itself) supports sending pruned blocks to syncing nodes, the pruned version will be sent along with the hash of the pruned data and the block weight. The original tx hashes can be reconstructed from the pruned txes and theur prunable data hash. Those hashes and the block weights are hashes and checked against the set of precompiled hashes, ensuring the data we received is the original data. It is currently not possible to use this system when not using the set of precompiled hashes, since block weights can not otherwise be checked for validity. This is off by default for now, and is enabled by --sync-pruned-blocks
* | RandomX integrationHoward Chu2019-09-251-2/+2
| | | | | | | | Support RandomX PoW algorithm
* | Merge pull request #5882luigi11112019-09-243-6/+40
|\ \ | | | | | | | | | a444f06 blockchain: enforce 10 block age for spending outputs (moneromooo-monero)
| * | blockchain: enforce 10 block age for spending outputsmoneromooo-monero2019-09-173-6/+40
| | | | | | | | | | | | | | | Some custom wallet code apparently ignores this, which causes users of that code to be fingerprinted
* | | Merge pull request #5877luigi11112019-09-241-2/+2
|\ \ \ | |/ / |/| | | | | | | | | | | 2cd4fd8 Changed the use of boost:value_initialized for C++ list initializer (JesusRami) 4ad191f Removed unused boost/value_init header (whyamiroot) 928f4be Make null hash constants constexpr (whyamiroot)
| * | Changed the use of boost:value_initialized for C++ list initializerJesus Ramirez2019-09-021-2/+2
| |/
* / blockchain: forbid v1 coinbase from v12moneromooo-monero2019-08-193-0/+28
|/
* add a few checks where it seems appropriatemoneromooo-monero2019-04-292-0/+2
|
* Remove unneeded SFINAE on check_tx/block verification in core_testsDoyle2019-04-173-77/+28
|
* Merge pull request #5409Riccardo Spagni2019-04-164-5/+5
|\ | | | | | | ac874e2d tests: fix test_options initialization error (Dusan Klinec)
| * tests: fix test_options initialization errorDusan Klinec2019-04-074-5/+5
| |
* | Merge pull request #5400Riccardo Spagni2019-04-161-2/+17
|\ \ | | | | | | | | | 5e673c03 blockchain_db: fix db txn ending too early (moneromooo-monero)
| * | blockchain_db: fix db txn ending too earlymoneromooo-monero2019-04-141-2/+17
| |/ | | | | | | | | | | | | | | | | | | The db txn in add_block ending caused the entire overarching batch txn to stop. Also add a new guard class so a db txn can be stopped in the face of exceptions. Also use a read only db txn in init when the db itself is read only, and do not save the max tx size in that case.
* / tests: trezor tests fixes and improvementsDusan Klinec2019-04-101-1/+1
|/ | | | - configurable hardforks via env vars
* Merge pull request #5211Riccardo Spagni2019-03-212-6/+4
|\ | | | | | | | | | | c9b13fbb tests/trezor: HF9 and HF10 tests (Dusan Klinec) a1fd1d49 device/trezor: HF10 support added, wallet::API (Dusan Klinec) d74d26f2 crypto: hmac_keccak added (Dusan Klinec)
| * tests/trezor: HF9 and HF10 testsDusan Klinec2019-03-202-6/+4
| | | | | | | | | | | | | | | | | | - tests fixes for HF10, builder change, rct_config; fix_chain - get_tx_key test - proper testing after live refresh added - live refresh synthetic test - log available funds for easier test construction - wallet::API tests with mocked daemon
* | Merge pull request #5061Riccardo Spagni2019-03-1733-33/+33
|\ \ | |/ |/| | | 1f2930ce Update 2019 copyright (binaryFate)
| * Update 2019 copyrightbinaryFate2019-03-0533-33/+33
| |
* | Merge pull request #4977Riccardo Spagni2019-03-145-110/+1353
|\ \ | |/ |/| | | 5ea17909 device/trezor: debugging features, trezor tests (Dusan Klinec)
| * device/trezor: debugging features, trezor testsDusan Klinec2019-03-055-110/+1353
| |
* | cryptonote: avoid double parsing blocks when syncingmoneromooo-monero2019-03-051-2/+2
| |
* | ArticMine's new block weight algorithmmoneromooo-monero2019-03-041-1/+1
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | This curbs runaway growth while still allowing substantial spikes in block weight Original specification from ArticMine: here is the scaling proposal Define: LongTermBlockWeight Before fork: LongTermBlockWeight = BlockWeight At or after fork: LongTermBlockWeight = min(BlockWeight, 1.4*LongTermEffectiveMedianBlockWeight) Note: To avoid possible consensus issues over rounding the LongTermBlockWeight for a given block should be calculated to the nearest byte, and stored as a integer in the block itself. The stored LongTermBlockWeight is then used for future calculations of the LongTermEffectiveMedianBlockWeight and not recalculated each time. Define: LongTermEffectiveMedianBlockWeight LongTermEffectiveMedianBlockWeight = max(300000, MedianOverPrevious100000Blocks(LongTermBlockWeight)) Change Definition of EffectiveMedianBlockWeight From (current definition) EffectiveMedianBlockWeight = max(300000, MedianOverPrevious100Blocks(BlockWeight)) To (proposed definition) EffectiveMedianBlockWeight = min(max(300000, MedianOverPrevious100Blocks(BlockWeight)), 50*LongTermEffectiveMedianBlockWeight) Notes: 1) There are no other changes to the existing penalty formula, median calculation, fees etc. 2) There is the requirement to store the LongTermBlockWeight of a block unencrypted in the block itself. This is to avoid possible consensus issues over rounding and also to prevent the calculations from becoming unwieldy as we move away from the fork. 3) When the EffectiveMedianBlockWeight cap is reached it is still possible to mine blocks up to 2x the EffectiveMedianBlockWeight by paying the corresponding penalty. Note: the long term block weight is stored in the database, but not in the actual block itself, since it requires recalculating anyway for verification.
* ringct: encode 8 byte amount, saving 24 bytes per outputmoneromooo-monero2019-01-221-1/+1
| | | | Found by knaccc
* add a bulletproof version, new bulletproof type, and rct configmoneromooo-monero2019-01-224-45/+45
| | | | This makes it easier to modify the bulletproof format
* Merge pull request #5046Riccardo Spagni2019-01-182-5/+13
|\ | | | | | | 524bf750 core_tests: add a --list_tests command line switch (moneromooo-monero)
| * core_tests: add a --list_tests command line switchmoneromooo-monero2019-01-072-5/+13
| |
* | core_tests: rename invalid multisig tests to read "invalid"moneromooo-monero2018-12-223-16/+16
|/
* remove some unused codemoneromooo-monero2018-11-232-4/+1
| | | | Found by codacy.com
* Multisig M/N functionality core tests addednaughtyfox2018-10-014-42/+223
|
* Arbitrary M/N multisig schemes:naughtyfox2018-10-011-1/+1
| | | | | | | | | * support in wallet2 * support in monero-wallet-cli * support in monero-wallet-rpc * support in wallet api * support in monero-gen-trusted-multisig * unit tests for multisig wallets creation
* core_tests: add a test for 4-aggregated BP verificationmoneromooo-monero2018-09-113-0/+16
|
* core_tests: add a test for a tx with empty bulletproofmoneromooo-monero2018-09-113-0/+20
|
* v8: per byte fee, pad bulletproofs, fixed 11 ring sizemoneromooo-monero2018-09-117-163/+176
|
* require canonical multi output bulletproof layoutmoneromooo-monero2018-09-113-13/+13
|
* Bulletproof aggregated verification and testsmoneromooo-monero2018-09-117-4/+573
| | | | Also constrains bulletproofs to simple rct, for simplicity
* bulletproofs: add multi output bulletproofs to rctmoneromooo-monero2018-09-111-1/+1
|
* core_tests: add --filter to select which tests to runmoneromooo-monero2018-07-072-0/+7
|
* replace std::list with std::vector on some hot pathsmoneromooo-monero2018-06-267-18/+18
| | | | also use reserve where appropriate
* keypair::generate: always require hw::device to avoid possible mistakestoffu2018-03-142-3/+3
|
* Stagenetstoffu2018-03-051-2/+2
|
* Code modifications to integrate Ledger HW device into monero-wallet-cli.cslashm2018-03-045-7/+10
| | | | | | | | | | | | | | | | | | | 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.