| Age | Commit message (Collapse) | Author |
|---|
|
add InitMessage() to noui and use debug.log for GUI
|
|
Make output of gettxout RPC more consistent
|
|
Parallel script verification
|
|
Bloom filters
|
|
update bitcoinstrings.cpp and bitcoin_en.ts (2013-01-14)
|
|
|
|
|
|
|
|
This adds a compact representation for a subset of a merkle tree's
nodes.
|
|
|
|
Note that the default value for fRelayTxes is false, meaning we
now no longer relay tx inv messages before receiving the remote
peer's version message.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
make database init messages more valuable
|
|
Display tx nLockTime correctly when set to block #
|
|
If the prio. will be enough after the next block don't force fees. [wallet]
|
|
Remove fClient
|
|
Upgrading to 0.8: re-use blkNNNN.dat files.
|
|
OutputDebugStringF code cleanup
|
|
- it was bad, that quite some messages were just talking about a database,
I think a user should know, if we are talking about wallet db or
block/coin db
- also adds a new init message for "Verifying block database integrity..."
|
|
Bitcoin-Qt: use reference in setAddress_SM() and setAddress_VM()
|
|
- this pull adds an InitMessage() function to noui.cpp, which outputs init
messages to debug.log (this allows to remove some printf() calls from
init.cpp)
- change InitMessage() in bitcoin.cpp to also write init messages to
debug.log to ensure nothting is missing in the log because of the
removal of printf() calls in init.cpp
|
|
- removes some obsolete comments about CTransaction::FetchInputs(), a
space and a few new-lines
|
|
Coin database checks
|
|
Provide fee data for all txs in RPC getblocktemplate response
|
|
|
|
Client (SPV) mode never got implemented entirely, and whatever part was already
working, is likely not been tested (or even executed at all) for the past two
years. This removes it entirely.
If we want an SPV implementation, I think we should first get the block chain
data structures to be encapsulated in a class implementing a standard interface,
and then writing an alternate implementation with SPV semantics.
|
|
Previously when a transaction was set to lock at a specific block the
calculation was reversed, returning a negative number. This broke the UI
and caused it to display %n in place of the actual number.
In addition the previous calculation would display "Open for 0 blocks"
when the block height was such that the next block created would
finalize the transaction. Inserted the word "more" and changed the
calculation so that the last message would be "Open for 1 more block" to
better match user expectations.
|
|
Since block validation happens in parallel, multiple threads may be
accessing the signature cache simultaneously. To prevent contention:
* Turn the signature cache lock into a shared mutex
* Make reading from the cache only acquire a shared lock
* Let block validations not store their results in the cache
|
|
* 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
|
