| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Conflicts:
src/bitcoinrpc.cpp
|
| |
|
|
|
|
|
|
|
| |
This reverts commits:
- 220de9aafbdb76fa620531fc5c0b01ffa6616d7b Qt: small header changes / fixes
- caeafd1bd1b217276005c6bb422136f379d881cf fix some double-spaces in strings
- deb9f100a04dbb9c25d6ba320eba4c653a2f5423 fix some double-spaces in strings
- 65cee0bbbdea49c08bc84be7824ab004cc19f57e don't use memset() in privacy/security relevant code parts
- ff31f1fa10e2062465520ad8a3ff846c23b7a96f don't use memset() in privacy/security relevant code parts
|
| |
|
|
|
| |
It seemed to create two CWalletDB objects that both grab the
database lock.
|
| |
|
|
|
|
|
|
|
|
| |
Conflicts:
src/bitcoinrpc.cpp
src/crypter.h
src/main.cpp
src/qt/bitcoin.cpp
src/qt/qtipcserver.cpp
src/util.cpp
|
| |\
| |
| | |
add LOCK() for proxy related data-structures
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
- fix #1560 by properly locking proxy related data-structures
- update GetProxy() and introduce GetNameProxy() to be able to use a
thread-safe local copy from proxyInfo and nameproxyInfo
- update usage of GetProxy() all over the source to match the new
behaviour, as it now fills a full proxyType object
- rename GetNameProxy() into HaveNameProxy() to be more clear
|
| |/
|
|
| |
Replace all "magic values" in RPCError(...) by constants.
|
| |\ |
|
| | | |
|
| |/ |
|
| |\ |
|
| | | |
|
| |\ \
| | |
| | | |
implement CreateThread with boost::thread
|
| | | |
| | |
| | |
| | | |
Prevent clash with win32 API symbol
|
| |\ \ \
| |/ /
|/| /
| |/ |
Bugfix: Require OrderedTxItems to provide properly scoped accounting entry list
|
| | |
| |
| |
| |
| |
| | |
OrderedTxItems returns a multimap of pointers, but needs a place to store the actual CAccountingEntries it points to.
It had been using a stack item, which was clobbered as soon as it returned, resulting in undefined behaviour.
This fixes at least bug #1768.
|
| |\ \
| | |
| | | |
Listunspent txout address filtering and listaddressgroupings
|
| | | |
| | |
| | |
| | |
| | | |
This is cleanup for the listaddressgroupings code. Also add some
real help text.
|
| | |/
| |
| |
| | |
Signed-off-by: Gregory Maxwell <[email protected]>
|
| | | |
|
| |/
|
|
|
| |
- Show address receiving the generation, and include it in the correct "account"
- Multiple entries in listtransactions output if the coinbase has multiple outputs to us
|
| |
|
|
|
|
|
|
|
| |
Logic:
- If sending a transaction, assign its timestamp to the current time.
- If receiving a transaction outside a block, assign its timestamp to the current time.
- If receiving a block with a future timestamp, assign all its (not already known) transactions' timestamps to the current time.
- If receiving a block with a past timestamp, before the most recent known transaction (that we care about), assign all its (not already known) transactions' timestamps to the same timestamp as that most-recent-known transaction.
- If receiving a block with a past timestamp, but after the most recent known transaction, assign all its (not already known) transactions' timestamps to the block time.
|
| |
|
|
| |
transaction Object outputs
|
| |
|
|
|
| |
For backward compatibility, new accounting data is stored after a \0 in the comment string.
This way, old versions and third-party software should load and store them, but all actual use (listtransactions, for example) ignores it.
|
| |
|
| |
One added space + one removed space.
|
| | |
|
| |
|