| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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()
|
|
small main.h cleanup (no code changes)
|
|
- 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.
|
|
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
|
|
update ThreadSafeMessageBox function to use strCaption
|
|
|
|
|
|
- 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
|
|
translations update (bitcoinstrings.cpp + bitcoin_en.ts)
|
|
|
|
- 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
|
|
-checklevel gets a new meaning:
0: verify blocks can be read from disk (like before)
1: verify (contextless) block validity (like before)
2: verify undo files can be read and have good checksums
3: verify coin database is consistent with the last few blocks
(close to level 6 before)
4: verify all validity rules of the last few blocks
Level 3 is the new default, as it's reasonably fast. As level 3 and
4 are implemented using an in-memory rollback of the database, they
are limited to as many blocks as possible without exceeding the
limits set by -dbcache. The default of -dbcache=25 allows for some
150-200 blocks to be rolled back.
In case an error is found, the application quits with a message
instructing the user to restart with -reindex. Better instructions,
and automatic recovery (when possible) or automatic reindexing are
left as future work.
|
|
|
|
This should be compatible with older code that didn't write checksums.
|
