| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Miners with MLSAG txes which they'd already verified included
a couple in that block, but the consensus rules had changed
in the meantime, so that block is technically invalid and any
node which did not already have those two txes in their txpool
could not sync. Grandfather them in, since it has no effect in
practice.
|
| | |
|
| | |
|
| |
|
|
| |
Based on a patch by TheCharlatan <seb.kung@gmail.com>
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| | |
d20ff4f64 functional_tests: add a large (many randomx epochs) p2p reorg test (moneromooo-monero)
6a0b3b1f8 functional_tests: add randomx tests (moneromooo-monero)
9d42649d5 core: fix mining from a block that's not the current top (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
6a37da8 threadpool: guard against exceptions in jobs, and armour plating (moneromooo-monero)
|
| | | |
| | |
| | |
| | |
| | | |
Those would, if uncaught, exit run and leave the waiter to wait
indefinitely for the number of active jobs to reach 0
|
| | |/
|/|
| |
| | |
They are allowed from v12, and MLSAGs are rejected from v13.
|
| |\ \
| | |
| | |
| | | |
844fb4e94 enforce claiming maximum coinbase amount (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
Claiming a slightly lesser amount does not yield the size gains
that were seen pre rct, so this closes a fingerprinting vector
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
13eee1d6a rpc: reject wrong sized txid (moneromooo-monero)
92e6b7df2 easylogging++: fix crash with reentrant logging (moneromooo-monero)
6dd95d530 epee: guard against exceptions in RPC handlers (moneromooo-monero)
90016ad74 blockchain: guard against exceptions in add_new_block/children (moneromooo-monero)
|
| | |/
| |
| |
| | |
Reporter requested credit to be given to Decred
|
| |\ \
| | |
| | |
| | | |
267ce5b71 avoid a couple needless copies (moneromooo-monero)
|
| | | | |
|
| | |/
|/| |
|
| |\ \
| | |
| | |
| | | |
7bd66b01b daemon: guard against rare 'difficulty drift' bug with checkpoints and recalculation (stoffu)
|
| | |/
| |
| |
| |
| |
| | |
recalculation
On startup, it checks against the difficulty checkpoints, and if any mismatch is found, recalculates all the blocks with wrong difficulties. Additionally, once a week it recalculates difficulties of blocks after the last difficulty checkpoint.
|
| |\ \
| | |
| | |
| | | |
5d882f4f1 blockchain: fix theoretical race getting bulk timestamps (moneromooo-monero)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
5ef0607da Update copyright year to 2020 (SomaticFanatic)
|
| | |/ /
| | |
| | |
| | | |
Update copyright year to 2020
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The cache is discarded when a block is popped, but then gets
rebuilt when the difficulty for next block is requested.
While this is all properly locked, it does not take into account
the delay caused by a database transaction being only committed
(and thus its effects made visible to other threads) later on,
which means another thread could request difficulty between
the pop and the commit, which would end up using stale database
view to build the cache, but that cache would not be invalidated
again when the transaction gets committed, which would cause the
cache to not match the new database data.
To fix this, we now keep track of when the cache is invalidated
so we can invalidate it again upon database transaction commit
to ensure it gets calculated again with fresh data next time it
is nedeed.
|
| |\ \ \
| | | |
| | | |
| | | | |
795e186 blockchain: fix total_height in getblocks.bin response (moneromooo-monero)
|
| | |/ / |
|
| |\ \ \
| |_|/
|/| |
| | | |
5741b4d blockchain: detect and log bad difficulty calculations (moneromooo-monero)
|
| | |/ |
|
| |/ |
|
| |\
| |
| |
| | |
8958b4e blockchain_db: faster fetching of consecutive txes (moneromooo-monero)
|
| | |
| |
| |
| | |
Useful for wallet refresh or node sync
|
| |\ \
| | |
| | |
| | | |
fcb06f7 cryptonote_core: skip block notify on blockchain switching rollback (xiphon)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
c61abf8 remove empty statements (shopglobal)
|
| | |/
| |
| |
| | |
Cleaning up a little around the code base.
|
| |\ \
| | |
| | |
| | | |
02224e71 Fix check_fee() discrepancy. (UkoeHB)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
M100 = max{300kb, min{100block_median, m_long_term_effective_median_block_weight}}
not
M100 = max{300kb, m_long_term_effective_median_block_weight}
Fix base reward in get_dynamic_base_fee_estimate().
get_dynamic_base_fee_estimate() should match check_fee()
Fee is calculated based on block reward, and the reward penalty takes into account 0.5*max_block_weight (both before and after HF_VERSION_EFFECTIVE_SHORT_TERM_MEDIAN_IN_PENALTY).
Moved median calculation according to best practice of 'keep definitions close to where they are used'.
|
| |\ \ \
| |_|/
|/| |
| | | |
5985c5af rpc: add bad-blocks to flush_cache RPC (moneromooo-monero)
|
| | | |
| | |
| | |
| | | |
Flushes m_invalid_blocks in Blockchain.
|
| |\ \ \
| | | |
| | | |
| | | | |
8a27645 blockchain: fix flushing txes from the txpool (moneromooo-monero)
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | | |
08635a08 blockchain: speedup fetching pruned contiguous tx blobs (moneromooo-monero)
|
| | | |/
| |/|
| | |
| | | |
About twice as fast, very roughly
|
| |\ \ \
| |_|/
|/| |
| | | |
21d4c216 blockchain: error out if the builtin hashes data size is wrong (moneromooo-monero)
|