| Age | Commit message (Collapse) | Author |
|---|
|
* During block verification (when parallelism is requested), script
check actions are stored instead of being executed immediately.
* After every processed transactions, its signature actions are
pushed to a CScriptCheckQueue, which maintains a queue and some
synchronization mechanism.
* Two or more threads (if enabled) start processing elements from
this queue,
* When the block connection code is finished processing transactions,
it joins the worker pool until the queue is empty.
As cs_main is held the entire time, and all verification must be
finished before the block continues processing, this does not reach
the best possible performance. It is a less drastic change than
some more advanced mechanisms (like doing verification out-of-band
entirely, and rolling back blocks when a failure is detected).
The -par=N flag controls the number of threads (1-16). 0 means auto,
and is the default.
|
|
|
|
|
|
|
|
Bitcoin-Qt: fix small stylesheet glitch in overviewpage.ui
|
|
Bitcoin-Qt: add a Signature label on sign message page
|
|
Bitcoin-Qt: give testnet a unique IPC message queue name
|
|
|
|
|
|
- ensure we use strCaption for printf and fprintf, as before it could
happen to have an error message in the debug.log, which had no "Error"
(or whatever) in front
|
|
- this prevents an interference with the IPC message queue (which is used
for URI processing) when running a testnet and mainnet instance in
parallel
- to check for testnet, I had to raise the ParseParameters() call in
main() to the topmost position
|
|
Bitcoin-Qt: comment out unused parameter in addressbookpage
|
|
Bitcoin-Qt: never display own block count > estimated block count
|
|
Bitcoin-Qt: add a Reset button to the options dialog
|
|
|
|
- a click on "Reset Options" sets all options to the default values by
removing all stored settings (QSettings), loading the defaults and
saving them as the new settings
- before the reset is executed the user is presented a confirmation dialog
- special casing was needed for StartAtStartup
|
|
- some users reported it as weird, that the estimated block count could be
lower than our own nodes block number (which is indeed true and not good)
- this pull adds a new default behaviour, which displays our own block
number as estimated block number, if own >= est. block count
- the pull raises space for nodes block counts in cPeerBlockCounts to 8 to
be more accurate
- also removes a reduntant setNumBlocks() call in RPCConsole and moves
initialisation of numBlocksAtStartup in ClientModel, where it belongs
|
|
|
|
|
|
Fix duplicate shortcut usage in sign/verify message dialog.
|
|
update 2 command-line parameter help messages
|
|
Space separation between major fields is easier for human eyes and
libs to parse.
|
|
- -checkpoints is now much more understandable and should be way easier
to translate
- -loadblock uses the same format (blk000??.dat) as -reindex
|
|
Convert fRescan argument to importprivkey to bool
|
|
|
|
|
|
Break one long comment down into 3 lines so it's readable.
|
|
|
|
Checkpoint at first 25-btc-reward block (210,000)
|
|
Change timestamps to use ISO8601 formatting
|
|
use new message() function in BitcoinGUI
|
|
- fix some indentation issues
|
|
add rescan bool to importprivkey to control whether to do a rescan after import
|
|
OptionsModel now has MapPortUPnP=false if UPNP is not supported
|
|
Documented locking part 1+2
|
|
Bignum2
|
|
Add NATIVE_WINDOWS
|
|
Update src/makefile.mingw
|
|
Add "checkpoints" option, to permit disabling of checkpoint logic.
|
|
Add new RPC "lockunspent", to prevent spending of selected outputs
|
|
Add -benchmark for reporting block processing times
|
|
Reconstruct coins/ database when missing
|
|
Two minor inconvenience fixes
|
|
|
|
|
|
|
|
some CheckDiskSpace() related changes
|
|
|
|
When the coin database is out of date with the block database, the
best block in it is automatically switched to. This reconnection
process can take time, so allow it to be interrupted.
This also stops block connection as soon as shutdown is requested,
leading to a faster shutdown.
|
|
This problem is like earth (mostly harmless). After/during a
-reindex, it means the statistics about the last block file
reported in debug.log are always of blk00000.dat instead of the
last file. Apart from that, it means a few more database entries
need to be read when finding a file to append to the first time.
|
