aboutsummaryrefslogtreecommitdiff
path: root/src/cryptonote_core
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | Merge pull request #6050Alexander Blair2020-02-061-2/+3
|\ \ \ \ | | | | | | | | | | | | | | | 65301c40 core: point out when we hit the block rate visibility limit (moneromooo-monero)
| * | | | core: point out when we hit the block rate visibility limitmoneromooo-monero2019-10-281-2/+3
| | | | |
* | | | | Merge pull request #6233luigi11112020-02-041-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | 8a27645 blockchain: fix flushing txes from the txpool (moneromooo-monero)
| * | | | | blockchain: fix flushing txes from the txpoolmoneromooo-monero2019-12-141-1/+1
| | |_|_|/ | |/| | |
* | | | | Merge pull request #6140Alexander Blair2020-01-251-3/+10
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | 08635a08 blockchain: speedup fetching pruned contiguous tx blobs (moneromooo-monero)
| * | | | | blockchain: speedup fetching pruned contiguous tx blobsmoneromooo-monero2019-11-151-3/+10
| | |_|_|/ | |/| | | | | | | | | | | | | About twice as fast, very roughly
* | | | | Merge pull request #6146Alexander Blair2020-01-242-18/+2
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | 70c9cd3c Change to Tx diffusion (Dandelion++ fluff) instead of flooding (Lee Clagett)
| * | | | | Change to Tx diffusion (Dandelion++ fluff) instead of floodingLee Clagett2019-11-042-18/+2
| | |/ / / | |/| | |
* | | | | Merge pull request #6124Alexander Blair2020-01-161-1/+6
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | 21d4c216 blockchain: error out if the builtin hashes data size is wrong (moneromooo-monero)
| * | | | blockchain: error out if the builtin hashes data size is wrongmoneromooo-monero2019-11-121-1/+6
| |/ / /
* | | | Merge pull request #6055luigi11112019-12-121-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | 886ed25 blockchain: fix comment wrongly refering to SHA-3 rather than Keccak (moneromooo-monero)
| * | | | blockchain: fix comment wrongly refering to SHA-3 rather than Keccakmoneromooo-monero2019-10-291-1/+1
| | |_|/ | |/| |
* | | | Merge pull request #6052luigi11112019-12-121-2/+2
|\ \ \ \ | | | | | | | | | | | | | | | c96b7ee tx_pool: fix error message assuming incorrectly (moneromooo-monero)
| * | | | tx_pool: fix error message assuming incorrectlymoneromooo-monero2019-10-291-2/+2
| |/ / /
* | / / Adding support for hidden (anonymity) txpoolLee Clagett2019-11-027-205/+334
| |/ / |/| |
* | | Merge pull request #6079Riccardo Spagni2019-11-021-1/+1
|\ \ \ | | | | | | | | | | | | e4d1674e8 0.15.0.0 release engineering (Riccardo Spagni)
| * | | 0.15.0.0 release engineeringRiccardo Spagni2019-11-021-1/+1
| |/ /
* / / cryptonote: untangle dependency from miner to blockchainmoneromooo-monero2019-10-312-2/+6
|/ / | | | | | | It causes link errors at least on mac
* / blockchain: fix unwanted error when probing the pool for a txmoneromooo-monero2019-10-271-2/+11
|/
* Merge pull request #5958luigi11112019-10-251-15/+19
|\ | | | | | | | | | | | | d25acd7 Add hmac over encrypted value during transaction (clashm) 34f28a7 Add display address (clashm) 235b94e Revert PR #5835 (export view key) (clashm) 32febd2 Fix debug feature (clashm)
| * Add hmac over encrypted value during transactioncslashm2019-10-031-15/+19
| |
* | Merge pull request #6028luigi11112019-10-251-1/+1
|\ \ | | | | | | | | | 174a6ac tx_pool: fix divide by 0 in log (moneromooo-monero)
| * | tx_pool: fix divide by 0 in logmoneromooo-monero2019-10-251-1/+1
| | | | | | | | | | | | Coverity 205394
* | | rpc: add a flush_cache RPCmoneromooo-monero2019-10-252-0/+13
|/ / | | | | | | | | | | | | This allows flushing internal caches (for now, the bad tx cache, which will allow debugging a stuck monerod after it has failed to verify a transaction in a block, since it would otherwise not try again, making subsequent log changes pointless)
* | Merge pull request #5973luigi11112019-10-221-5/+1
|\ \ | | | | | | | | | abd3763 cryptonote: fill in tx weight when syncing from pruned blocks (moneromooo-monero)
| * | cryptonote: fill in tx weight when syncing from pruned blocksmoneromooo-monero2019-10-101-5/+1
| | |
* | | Merge pull request #5981luigi11112019-10-222-2/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | 88c9d90 protocol: initialize block_weight in block_complete_entry ctor (moneromooo-monero) fe443bb cryptonote: don't leave block_weight uninitialized (moneromooo-monero) 1ba9baf tx_pool: do not divide by 0 (moneromooo-monero)
| * | | tx_pool: do not divide by 0moneromooo-monero2019-10-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case of a 0 tx weight, we use a placeholder value to insert in the fee-per-byte set. This is used for pruning and mining, and those txes are pruned, so will not be too large, nor added to the block template if mining, so this is safe. CID 204465
| * | | cryptonote: don't leave block_weight uninitializedmoneromooo-monero2019-10-111-0/+1
| |/ / | | | | | | | | | CID 204467
* | | Merge pull request #5974luigi11112019-10-221-2/+4
|\ \ \ | | | | | | | | | | | | 7fcd0b5 blockchain: initialize pow to ff..ff (moneromooo-monero)
| * | | blockchain: initialize pow to ff..ffmoneromooo-monero2019-10-161-2/+4
| |/ / | | | | | | | | | as a safety to reject if it somehow does not get initialised
* | | Merge pull request #5970luigi11112019-10-221-3/+12
|\ \ \ | | | | | | | | | | | | ab96181 blockchain: use effective median block weight for penalty from v12 (moneromooo-monero)
| * | | blockchain: use effective median block weight for penalty from v12moneromooo-monero2019-10-111-3/+12
| |/ / | | | | | | | | | | | | It was using the raw block weight median, which was not what was intended in ArticMine's design
* | | Merge pull request #5966luigi11112019-10-221-8/+3
|\ \ \ | | | | | | | | | | | | be82c40 Support median block size > 4 GB (moneromooo-monero)
| * | | Support median block size > 4 GBmoneromooo-monero2019-10-211-8/+3
| | | | | | | | | | | | | | | | | | | | add a 128/64 division routine so we can use a > 32 bit median block size in calculations
* | | | Merge pull request #5919luigi11112019-10-223-0/+86
|\ \ \ \ | | | | | | | | | | | | | | | 01f660f blockchain: fill in cumulative block weight for alt blocks (moneromooo-monero)
| * | | | blockchain: fill in cumulative block weight for alt blocksmoneromooo-monero2019-10-103-0/+86
| | | | |
* | | | | Merge pull request #5962luigi11112019-10-162-2/+2
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | ec14abd tx_pool: make spent return-by-reference as intended (stoffu)
| * | | | | tx_pool: make spent return-by-reference as intendedstoffu2019-10-062-2/+2
| | |/ / / | |/| | |
* | | | | Merge pull request #5941luigi11112019-10-141-1/+2
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | d37d30f blockchain: tweak fee as a function of median values (moneromooo-monero)
| * | | | | blockchain: tweak fee as a function of median valuesmoneromooo-monero2019-09-281-1/+2
| | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the lesser of the short and long terms medians, rather then the long term median alone From ArticMine: I found a bug in the new fee calculation formula with using only the long term median It actually needs to be the lesser of the long term median and the old (modified short term median) short term median with the last 10 blocks calculated as empty Yes the issue occurs if there is a large long term median and, the short term median then falls and tries to then rise again The fees are could be not high enough for example LTM and STM rise to say 2000000 bytes STM falls back to 300000 bytes Fees are now based on 2000000 bytes until LTM also falls So the STM is could prevented from rising back up STM short term median LTM long term median
* | | | | Merge pull request #5933luigi11112019-10-141-0/+2
|\ \ \ \ \ | |_|_|_|/ |/| | | | | | | | | 3455efa ban peers sending bad pow outright (moneromooo-monero)
| * | | | ban peers sending bad pow outrightmoneromooo-monero2019-09-251-0/+2
| | | | | | | | | | | | | | | | | | | | PoW is expensive to verify, so be strict
* | | | | Merge pull request #5915luigi11112019-10-086-89/+314
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | 8330e77 monerod can now sync from pruned blocks (moneromooo-monero)
| * | | | monerod can now sync from pruned blocksmoneromooo-monero2019-09-276-89/+314
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | | Merge pull request #5902luigi11112019-09-301-1/+3
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | b9da023 blockchain: keep block template timestamp not below recent median (moneromooo-monero)
| * | | | | blockchain: keep block template timestamp not below recent medianmoneromooo-monero2019-09-111-1/+3
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Such a template would yield an invalid block, though would require an attacker to have mined a long blockchain with drifting times (assuming the miner's clock is roughly correct) Fixed by crCr62U0
* | | | | Merge pull request #5900luigi11112019-09-301-3/+10
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | 6bbc646 Fix bug in mempool get_transaction_stats histogram calculation (tomsmeding)
| * | | | Fix bug in mempool get_transaction_stats histogram calculationTom Smeding2019-08-281-3/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The 98th percentile position in the agebytes map was incorrectly calculated: it assumed the transactions in the mempool all have unique timestamps at second-granularity. This commit fixes this by correctly finding the right cumulative number of transactions in the map suffix. This bug could lead to an out-of-bounds write in the rare case that all transactions in the mempool were received (and added to the mempool) at a rate of at least 50 transactions per second. (More specifically, the number of *unique* receive_time values, which have second- granularity, must be at most 2% of the number of transactions in the mempool for this crash to trigger.) If this condition is satisfied, 'it' points to *before* the agebytes map, 'delta' gets a nonsense value, and the value of 'i' in the first stats.histo-filling loop will be out of bounds of stats.histo.
* | | | | RandomX integrationHoward Chu2019-09-255-6/+119
| |_|/ / |/| | | | | | | | | | | Support RandomX PoW algorithm
generated by cgit v1.2.3 (git 2.51.0) at 2026-08-16 13:11:53 +0000