Age | Commit message (Collapse) | Author |
|
|
|
small changes in init, main, checkpoints.h and bitcoin-qt.pro
|
|
Reimplement click-to-pay. Support OSX.
|
|
Various performance tweaks to CCoinsView
|
|
Native versions for AllocateFileRange()
|
|
Progressbar based on time-based estimation of transactions.
|
|
ApproximateBestSubset internal RNG to prevent degenerate behavior.
|
|
Enable dumpprivkey in safe mode
|
|
reformat OS X build instrcs, add 10.8 + Homebrew
|
|
Add adjustedtime to getinfo RPC call
|
|
Add -walletnotify to call an external script on wallet transactions
|
|
|
|
Shorten a startup message. It was getting truncated and looks ugly.
|
|
|
|
- remove an unneeded MODAL flag, as MSG_ERROR sets MODAL
- re-order an if-clause in main to have bool checks before a function call
- fix some log messages that used wrong function names
- make a log message use a correct ellipsis
- remove some unneded spaces, brackets and line-breaks
- fix style for adding files in the Qt project
|
|
* reformatted the entire document to look pretty in both standard text and
Markdown
* incorporated [my OS X 10.8 build instructions with Homebrew as the package
manager](http://bitcoin.stackexchange.com/questions/3672/trouble-compiling-bitcoind-on-osx-with-homebrew/5253#5253)
* incorporated @gavinandresen's MacPorts and release build instructions based on
an earlier revision of this commit
* added makefile patch necessary for Homebrew compilation to `contrib`
|
|
|
|
Pass compiler flags to leveldb make
|
|
Improve block database load error reporting
|
|
This fixes test_bitcoin failures on openbsd reported by dhill on IRC.
On some systems rand() is a simple LCG over 2^31 and so it produces
an even-odd sequence. ApproximateBestSubset was only using the least
significant bit and so every run of the iterative solver would be the
same for some inputs, resulting in some pretty dumb decisions.
Using something other than the least significant bit would paper over
the issue but who knows what other way a system's rand() might get us
here. Instead we use an internal RNG with a period of something like
2^60 which is well behaved. This also makes it possible to make the
selection deterministic for the tests, if we wanted to implement that.
|
|
|
|
|
|
|
|
remove outdated QT windows build instructions
|
|
|
|
translations update (bitcoinstrings.cpp + bitcoin_en.ts)
|
|
|
|
This is less confusing to most people, and doesn't rely on estimates
of the total number of blocks received from other nodes.
|
|
Two changes: make some linux-specific linker options linux and linker specific.
And in the cross-compile environment, prefer the $HOME/qt/bin tools to
whatever might be somewhere else in the path.
|
|
Fixes issue#2288. Includes cleanups from Luke's pull 2243.
|
|
|
|
Switch to using Qt's QLocalServer/QLocalSocket to handle bitcoin
payment links (bitcoin:... URIs)
Reason for switch: the boost::interprocess mechanism seemed flaky,
and doesn't mesh as well with "The Qt Way"
qtipcserver.cpp/h is replaced by paymentserver.cpp/h
Click-to-pay now also works on OSX, with a custom Info.plist
that registers Bitcoin-Qt as a handler for bitcoin: URLs and
an event listener on the main QApplication that handles
QFileOpenEvents (Qt translates 'url clicked' AppleEvents into
QFileOpenEvents automagically).
|
|
Do not use C++11 std::vector.data()
|
|
Add script to clean up datadirs
|
|
Some improvements to the release notes
|
|
|
|
|
|
Use QImage.bits instead of QImage.constBits to ease backporting
|
|
Image.constBits was introduced in Qt 4.7. Should be ok here to use
QImage.bits which allows linking against the Qt in Squeeze.
|
|
std::vector.data() is a C++11 feature that makes my OSX build machine unhappy.
|
|
|
|
|
|
Bugfix CValidationResult for BIP30 + add DoS
|
|
gmaxwell/signrawtransaction_for_regular_missing_txins
Signrawtransaction shouldn't require redeemScript for non-p2sh txins.
|
|
Do not call ResendWalletTransactions when reindexing or importing
|
|
|
|
Calling ResendWalletTransactions when reindexing, importing or on IBD spams
other nodes with our old transactions, because they become unconfirmed.
|
|
|
|
Make transactions larger than 100K non-standard
|
|
Extremely large transactions with lots of inputs can cost the network
almost as much to process as they cost the sender in fees.
We would never create transactions larger than 100K big; this change
makes transactions larger than 100K non-standard, so they are not
relayed/mined by default. This is most important for miners that might
create blocks larger than 250K big, who could be vulnerable to a
make-your-blocks-so-expensive-to-verify-they-get-orphaned attack.
|