Age | Commit message (Collapse) | Author |
|
This should make occurances of NodeId wrapping essentially impossible for
real-world usage.
Github-Pull: #10176
Rebased-From: c851be4b25905977ca471c42435dc590fd2ff2f5
|
|
Github-Pull: #10204
Rebased-From: 883154cbcb306dcc6205fe349c7056ced1f6c5fc
|
|
|
|
If prioritisetransaction was called for a tx with in-mempool
descendants, the modified ancestor fee values for those descendants was
incorrect.
Github-Pull: #10144
Rebased-From: 9bef02e36525d0eed4e2e31678b3ff04bbb0b8cb
|
|
Always leave a reasonable buffer of 50MB for usage from newly connected block (once over 50%) and increase the high water mark buffer to 200MB.
Github-Pull: #10133
Rebased-From: 1b55e07b7a61a9e6c299cf4c40fde80fa715d440
|
|
Github-Pull: #10133
Rebased-From: f33afd3b2be1bcabeb10168a53835359c9ff4a3e
|
|
Since we are more accurately measuring pcoinsTip peak usage at twice the current in dynamic usage, it makes sense to double the default (this will lead to the same effective usage and peak usage as previously).
We should also double the buffer used to avoid flushing if above 90% but still sufficient space remaining.
Github-Pull: #10133
Rebased-From: 5b95a190e8d7059039ce61e808d494dcf89ebb3b
|
|
There is no point in even hashing a submitted block which doesn't have
a coinbase transaction.
This also results in more useful error reporting on corrupted input.
Thanks to rawodb for the bug report.
Github-Pull: #10146
Rebased-From: 4f15ea102d15eb237b63464725508dc509e98819
|
|
This isn't actually needed anywhere, but it's less brittle.
Github-Pull: #10146
Rebased-From: ada0caa165905b50db351a56ec124518c922085a
|
|
Accidentally removed in 40b556d3742a1f65d67e2d4c760d0b13fe8be5b7
Github-Pull: #10139
Rebased-From: 4b87973c32bcaa5fa7509793e4f0c4f4f981f21b
|
|
Github-Pull: #10126
Rebased-From: 7228ce853de5670d559d752f04a7db79578990ea
|
|
large mempools
a296c60 Update benchmarking with package statistics (Suhas Daftuar)
10028fb Add benchmarking for CreateNewBlock (Suhas Daftuar)
b5c3440 Mining: return early when block is almost full (Suhas Daftuar)
Tree-SHA512: 7c39d03a778abe00412743958981a1a55d22fc1843c9a3aef7a56506622e6f5d6b8962c586a339b6031e1ee4815d6981351cf527e8fbe5b265824c81d6c7199d
|
|
glibc-specific: On 32-bit systems set the number of arenas to 1. By
default, since glibc 2.10, the C library will create up to two heap
arenas per core. This is known to cause excessive virtual address space
usage in our usage. Work around it by setting the maximum number of
arenas to 1.
Github-Pull: #10120
Rebased-From: 625488ace5c41ccba1b68323a72588000782f820
|
|
Github-Pull: #10130
Rebased-From: 19ecd1e2e13514c8a92a2a4337c2568c3d5d13e5
|
|
Github-Pull: #10130
Rebased-From: 21704f6334d2a4bd140c6e3260c4bfa3f3157bad
|
|
The number of arguments is not checked MutateTxAddOutAddr(..), meaning
that
> ./bitcoin-tx -create outaddr=
accessed the vStrInputParts vector beyond its bounds.
This also includes work by jnewbery to check the inputs for
MutateTxAddPubKey()
Github-Pull: #10130
Rebased-From: eb66bf9bdd5ae20c546314eb2c494ac09929970f
|
|
Github-Pull: #9959
Rebased-From: 011124a2b278c5a60bad5f1b0b4abbf7ebc95aa0
|
|
Github-Pull: #9959
Rebased-From: 42cd8c890fb2d65274f26edf95b6d52ac41fcab8
|
|
Github-Pull: #9959
Rebased-From: eed816af6c68c0c67f5fc05472a3927db62f8a18
|
|
Github-Pull: #10084
Rebased-From: fa558532192ca0bb519f811ee14df6037413b89f
|
|
Github-Pull: #9912
Rebased-From: 02c57b521a9e7afd4416cd027a8b397f202b08a8
|
|
Ensures that there is an item on the rpcconsole stack before adding something to the current stack so that a segmentation fault does not occur.
Github-Pull: #10060
Rebased-From: 4df76e270caa9d828179cae1c7a8918d6f91ec21
|
|
Github-Pull: #10037
Rebased-From: 05a9f22358be27c08f7e164d05eeeaf0386073cb
|
|
segwit signalling or mining
2cd2cd5 Test transaction selection when gbt called without segwit support (Suhas Daftuar)
569596c Don't require segwit in getblocktemplate for segwit signalling or mining (Suhas Daftuar)
Tree-SHA512: bf2672287713e5adc7e851791207e17490679f941d0b9ed38467ffede3aa3000d229151b8ae54323fc8037e0a8569b2fd910ec19f034fb85d9142289648793c3
|
|
Github-Pull: #9953
Rebased-From: 819b513a5415d1669b5440e214862cda6c2261f8
|
|
We previously would block waiting for a CSemaphoreGrant in
ThreadOpenAddedConnections, when we did not need to. This would
block as the posts in CConnman shutdown were both to the wrong
semaphore and in the wrong location.
Github-Pull: #9953
Rebased-From: e007b243c4840e44857b5ccf686ed35899e44af0
|
|
Segwit's version bit will be signalled for all invocations of CreateNewBlock,
and not specifying segwit only will cause CreateNewBlock to skip transactions
with witness from being selected.
Github-Pull: #9955
Rebased-From: abe7b3d3abe10e3554b770f40824174b3b217490
|
|
Bug was a missing ++i line in a new range for loop added in commit e2e2f4c
"Return errors from importmulti if complete rescans are not successful"
Github-Pull: #9829
Rebased-From: 306bd72157f089b962b9c537bbacf710a4158647
|
|
|
|
Github-Pull: #9791
Rebased-From: 5c8fd508112016c3821b71112270afe83e6949ac
|
|
don't accidentally send coins there (like I did).
Github-Pull: #9865
Rebased-From: 83ac719d34f98cc1d3efa6ece2b95145bcde8775
|
|
Github-Pull: #9840
Rebased-From: f81f0d003079b96b8c33d3dfe76f90e50344bcd8
|
|
Github-Pull: #9856
Rebased-From: d4ee7baef729da5e18b5e5c3d6ddb5b97df8d4e4
|
|
Github-Pull: #9856
Rebased-From: c5f008a4166bae4350881a74fc04a87d7a5c4ed5
|
|
Github-Pull: #9875
Rebased-From: 75a109338fbbe9a30c54d76010b538c8ac1080ac
|
|
|
|
This turns some compiler warnings into errors. Useful for c-i.
Github-Pull: #9789
Rebased-From: 205830a37b7ffa4f8fa306e5c9eafcee3777fa68
|
|
Github-Pull: #9711
Rebased-From: 9949ebfa6a548260858df429f4d0e716e0a26065
|
|
Github-Pull: #9773
Rebased-From: e2e2f4c856363bbb0e3b5ba4df225f3754c3db39
|
|
Github-Pull: #9817
Rebased-From: 312c4f10574ccf6dfe0d4ecb3ce928733d3a1e52
|
|
Github-Pull: #9798
Rebased-From: 40f11f8872c3e9f380f8278f984dfdabffe77539
|
|
mempool.dat is a binary file and thus it should be read/written as such.
Fixes #9810.
Github-Pull: #9813
Rebased-From: 171fc91f061d4a980eedfa522e302b8598408cc5
|
|
Github-Pull: #9619
Rebased-From: 9fc7f0bce94f1cea0239b1543227f22a3f3b9274
|
|
Remove "nLowestTimestamp <= chainActive.Tip()->GetBlockTimeMax()" check from
importmulti, which is always true because nLowestTimestamp is set to the
minimum of the most recent block time and all the imported key timestamps,
which is necessarily lower than the maximum block time.
Github-Pull: #9760
Rebased-From: ec1267f13b7d0b9b5058c6821cf8dbf74e02d17c
|
|
They're unused and produce nasty deprecation warnings
Github-Pull: #9786
Rebased-From: 3301587dc5c7937141282f3799592d1e398495fb
|
|
Github-Pull: #9785
Rebased-From: c801c82e253dc4956069b6110f65b43f538dd5a1
|
|
Github-Pull: #9785
Rebased-From: 914fad155d9fc76b42b3a0414dd14b5ebc36062f
|
|
|
|
|
|
e662af3 Use 2 hour grace period for key timestamps in importmulti rescans (Russell Yanofsky)
38d3e9e [qa] Extend import-rescan.py to test imports on pruned nodes. (Russell Yanofsky)
c28583d [qa] Extend import-rescan.py to test specific key timestamps (Russell Yanofsky)
8be0866 [qa] Simplify import-rescan.py (Russell Yanofsky)
|