GitLab

Bugfix: ThreadSocketHandler creation error

Only GetAdjustedTime once for the retry loop

Python scripts demonstrating using RPC to keep passphrases out of shell history/etc.

Update release-process to point to gitian.sigs repo.

Added bitrpc.py which allows for sending of all standard Bitcoin commands via RPC rather than as command line args.
Signed-off-by: David Perry <enmaku@gmail.com>

Signed-off-by: David Perry <enmaku@gmail.com>

Remove possibility of 63 bit overflow in ParseMoney

Added RPC call 'getmemorypool' for p2p mining pools

Added RPC call 'getmemorypool' that provides everything needed to construct a block with a custom generation transaction and submit a solution

getmemorypool [data]
If [data] is not specified, returns data needed to construct a block to work on:
  "version" : block version
  "previousblockhash" : hash of current highest block
  "transactions" : contents of non-coinbase transactions that should be included in the next block
  "coinbasevalue" : maximum allowable input to coinbase transaction, including the generation award and transaction fees
  "time" : timestamp appropriate for next block
  "bits" : compressed target of next block
If [data] is specified, tries to solve the block and returns true if it was successful.

- also, add unit tests for various functions in util.cpp/util.h

Sign and verify message with bitcoin address

qmake build system improvements

- USE_SSL=1 to support RPC SSL
- BDB_LIB_SUFFIX= to link against specific BDB version
- Fix typo
- Start lrelease during qmake phase to prevent errors/warnings

Qt GUI updates

remove deprecated RPCs

deprecate midstate and hash1 in getwork

Conflicts:
	.gitignore (used upstream version)
	bitcoin-qt.pro

- fixes problem that one misconfigured or malicious node can mess up progress bar
- implementation in src/util.h
- testcase in src/test/util_tests.cpp

Update release-process.txt with gitian release instructions.

Updated readme file with timers.

- automatically build binary translation files in qmake/make
- roll translations into resource file and executable, to simply installation

Instead of encoding the public key inside the signature string, use
key recovery to do verification. This allows 88-character base64-encoded
signature strings instead of 188-character ones.

Introduce a new type of signatures that are only 65 bytes long, and allow
reconstruction of the public key that was used to create the signature.

Include the public key in the signature string, to allow verification
based on address.

Add padding to input (fixed string + address) before hashing