Regenerate addresses at the end of the loop so that the shown wallet is the first to print.
Elaborating on the message after paper wallets are printed about ensuring print quality.
Prevent denial-of-service attacks by banning
peers that send us invalid orphan transactions
and only storing orphan transactions given to
us by a peer while the peer is connected.
Rebased-From: c74332c67806ed92e6e18de174671a7c30608780
Conflicts:
src/main.cpp
There is no reason to store thousands of orphan transactions;
normally an orphan's parents will either be broadcast or
mined reasonably quickly.
This pull drops the maximum number of orphans from 10,000 down
to 100, and adds a command-line option (-maxorphantx) that is
just like -maxorphanblocks to override the default.
Conflicts:
src/main.h
Used the new update-translations.py script to clean up all
locale files. Unlike bitcoin/bitcoin, we're keeping the
unfinished translation tags in place as long as we have
manual translations (whereas bitcoin uses transifex)
Some translations had non-matching formats, the update-translations
script would normally remove those and set it to "unfinished".
However, since those are fairly trivial to fix, those have been
manually corrected before doing a cleanup run with the update script.
Fix wrong capitalization in wallet encryption warning message:
"If you encrypt your wallet and lose your passphrase, you will
LOSE ALL OF YOUR DOGECOINS"
50,000 entries. Tested by temporarily constraining MAPASKFOR_MAX_SZ to 1 entry and observing return behavior in AskFor(const CInv& inv). Passed all Boost tests.
- Catch problems such as mismatched formatting characters. Remove
messages that can give problems at runtime.
- Also remove unfinished/untranslated messages, they just take up space
in the ts and waste parsing time.
Fixes bitcoin issue 4774.
cherry-picked from: bitcoin b62172a
It's only confusing people into thinking that they should mess with
boost versions, which should not be necessary to get bitcoind to work.
If there is a bug in the build system with autodetecting boost it needs
to be solved not worked around.
Rebased-From: 539abc4729ea16039d148cfa3b771929f7d37584
Bitcoin core should work with any remotely recent boost version
if a proper build environment is present. Remove a confusing comment
from the build documentation.
Rebased-From: bd45b1a
Conflicts:
doc/build-unix.md
Previously if bitcoind is linked with an OpenSSL which is compiled
without EC support, this is seen as an assertion failure "pKey !=
NULL" at key.cpp:134, which occurs after several seconds. It is an
esoteric piece of knowledge to interpret this as "oops, I linked
with the wrong OpenSSL", and because of the delay it may not even
be noticed.
The new output is
: OpenSSL appears to lack support for elliptic curve cryptography. For
more information, visit
https://en.bitcoin.it/wiki/OpenSSL_and_EC_Libraries
: Initialization sanity check failed. Bitcoin Core is shutting down.
which occurs immediately after attempted startup.
This also blocks in an InitSanityCheck() function which currently only
checks for EC support but should eventually do more. See #4081.
