GitLab

Prune provably-unspendable outputs

Use 'low S' as malleability breaker rather than 'even S'

Add michagogo to gitian download scripts

[raw] reject insanely high fees by default in sendrawtransaction

Following a discussion in #bitcoin-dev, around
19:00 UTC, 20132209

Bitcoin-Qt: BitcoinGUI::message() updates/fixes

fix some printf -> LogPrintf leftovers

fix extract_strings_qt.py

- a recent pull changed xgettext to gettext, this is reverted here

Bugfix: nHeightLast instead of nHeightFirst

Gitian fixups

Fix minor unit test memory leaks

bitcoin incorrectly linked against the dll after the configure changes, so
ensure that only the static lib is installed.

configure.ac: remove debug/release concept, prefer autotools default CXXFLAGS

Remove #define printf, replace OutputDebugStringf with LogPrint(f)

Embedded test data in bitcoin_test

This change moves test data into the binaries rather than reading them from
the disk at runtime.

Advantages:
- Tests become distributable
- Cross-compile friendly. Build on one machine and execute in an arbitrary
  location on another.
- Easier testing for backports. Users can verify that tests pass without having
  to track down corresponding test data.
- More trustworthy test results and easier quality assurance as tests make
  fewer assumptions about their environment.
- Tests could theoretically run at client/daemon startup and exit on failure.

Disadvantages:
- Required 'hexdump' build-dependency. This is a standard bsd tool that should
  be usable everywhere. It is likely already installed on all build-machines.
- Tests can no longer be fudged after build by altering test-data.

More fixes for blockchain corruption on OSX.

autotools: fix a parallel build race condition spotted by the pull-tester

libleveldb.a and libmemenv.a should be able to build in parallel, but in
practice calling the leveldb makefile ends up rewriting build_config.mk. If
one target tries to build while the other is halfway through writing the
.mk, the make ends up in an undefined state.

Fix that by making one depend on the other. This also reorders the variables
to be passed by param rather than via the environment, and combines the targets
into a single rule to avoid needless duplication.

As we'd previously learned, OSX's fsync is a data eating lie.

Since 0.8.4 we're still getting some reports of disk corruption on
 OSX but now all of it looks like the block files have gotten out of
 sync with the database. It turns out that we were still using fsync()
 on the block files, so this isn't surprising.

Update translation process for autotools