slackcoder/bitcoin - Bitcoin Code integration/staging tree

Age	Commit message (Collapse)	Author
2017-03-09	Remove manual debug settings in qa tests.	John Newbery
	-debug and -logtimemicros are now set by default. Individual test cases no longer need to set these parameters manually.
2017-03-03	Define 7200 second timestamp window constant	Russell Yanofsky

2017-02-27	Merge #9839: [qa] Make import-rescan.py watchonly check reliable	Wladimir J. van der Laan
	864890a [qa] Make import-rescan.py watchonly check reliable (Russell Yanofsky) Tree-SHA512: ea0e2b1d4fc8f35174c3d575fb751b428daf6ad3aa944fad4e3ddcc9195e4f17051473acabc54203b1d27cca64cf911b737ab92e986c40ef384410652e2dbea1
2017-02-23	[qa] Make import-rescan.py watchonly check reliable	Russell Yanofsky
	Send payments during the test from a different node than the node generating keys to be imported, so the spending node doesn't create transactions that inadvertently involve (spend funds from) the imported keys. Fixes #9826
2017-02-23	Fix docstrings in qa tests	John Newbery
	This commit fixes the module-level docstrings for the tests and helper modules in qa. Many of these tests were uncommented previously - this commit ensures that every test case has at least a minimum level of commenting.
2017-02-16	Use 2 hour grace period for key timestamps in importmulti rescans	Russell Yanofsky
	Gregory Maxwell <greg@xiph.org> pointed out the lack of grace period in https://github.com/bitcoin/bitcoin/pull/9490#issue-199407998. The importwallet RPC which uses key timestamps in a similar way already has a 2 hour grace period.
2017-02-16	[qa] Extend import-rescan.py to test imports on pruned nodes.	Russell Yanofsky

2017-02-16	[qa] Extend import-rescan.py to test specific key timestamps	Russell Yanofsky

2017-02-16	[qa] Simplify import-rescan.py	Russell Yanofsky
	Get rid of partial functions so the test can be more easily extended to add more variants of imports with options that affect rescanning (e.g. different key timestamps). Also change the second half of the test to send /to/ the imported addresses, instead of /from/ the imported addresses. The goal of this part of the test was to confirm that the wallet would pick up new transactions after an import regardless of whether or not a rescan happened during the import. But because the wallet can only do this reliably for incoming transactions and not outgoing transactions (which require the wallet to look up transaction inputs) the test previously was less meaningful than it should have been.
2017-02-10	Require timestamps for importmulti keys	Russell Yanofsky
	Additionally, accept a "now" timestamp, to allow avoiding rescans for keys which are known never to have been used. Note that the behavior when "now" is specified is slightly different than the previous behavior when no timestamp was specified at all. Previously, when no timestamp was specified, it would avoid rescanning during the importmulti call, but set the key's nCreateTime value to 1, which would not prevent future block reads in later ScanForWalletTransactions calls. With this change, passing a "now" timestamp will set the key's nCreateTime to the current block time instead of 1. Fixes #9491
2016-12-12	[qa] Add test for rescan feature of wallet key import RPCs	Russell Yanofsky
	Covers importaddress, importpubkey, importprivkey, and importmulti RPCs.