< GitHub30>
[bitcoin] laanwj opened pull request #8453: Bring secp256k1 subtree up to date with master (master...2016_08_update_secp256k1) https://github.com/bitcoin/bitcoin/pull/8453
< sipa>
there are certainly no regressions known that would make the current master less appropriate than the subtree in bitcoin currently
< GitHub139>
[bitcoin] paveljanik opened pull request #8449: [Trivial] Do not shadow local variable, cleanup (master...20160803_shadow_blockencodings) https://github.com/bitcoin/bitcoin/pull/8449
< GitHub43>
[bitcoin] MarcoFalke closed pull request #8316: [qa] feefilter: Clear mempool after each check (master...Mf1607-qafeefilter) https://github.com/bitcoin/bitcoin/pull/8316
< GitHub193>
[bitcoin] laanwj closed pull request #8331: Fix three 'comparison between signed and unsigned integer expressions' warnings. (master...fix-compilation-warnings) https://github.com/bitcoin/bitcoin/pull/8331
< GitHub141>
bitcoin/master 115265b Pavel Janík: Trivial: bip -> BIP in help text and comment
< GitHub71>
bitcoin/0.13 6c083ac Wladimir J. van der Laan: Merge #8441: doc: Rewrite shell example to not leave secrets in the history file...
< GitHub53>
[bitcoin] laanwj closed pull request #8441: doc: Rewrite shell example to not leave secrets in the history file (0.13...patch-17) https://github.com/bitcoin/bitcoin/pull/8441
< GitHub71>
bitcoin/0.13 719208c paveljanik: Rewrite shell example to not leave secrets in the history file
< wumpus>
cfields: I don't get it, I don't manage to compile master for ARM anymore: https://github.com/bitcoin/bitcoin/issues/8447 however, in travis it's working. What could be the difference, that I'm compiling my own toolchain?
< GitHub103>
[bitcoin] paveljanik opened pull request #8446: BIP9 parameters on regtest cleanup (master...20160802_shadow_bip9params) https://github.com/bitcoin/bitcoin/pull/8446
< GitHub179>
[bitcoin] dexX7 opened pull request #8438: [0.13] Treat high-sigop transactions as larger rather than rejecting them (0.13...btc-13-sigops) https://github.com/bitcoin/bitcoin/pull/8438
< GitHub72>
[bitcoin] laanwj closed pull request #8403: Process "notfound" messages, and safeguard against unreasonably long … (master...ProcessNotfound) https://github.com/bitcoin/bitcoin/pull/8403
< GitHub88>
bitcoin/0.13 c3c82c4 Wladimir J. van der Laan: Merge #8389: [0.13] Create a new HD seed after encrypting the wallet...
< GitHub88>
bitcoin/0.13 de45c06 Jonas Schnelli: [Wallet] Add CKeyMetadata record for HDMasterKey(s), factor out HD key generation
< GitHub88>
bitcoin/0.13 f142c11 Jonas Schnelli: [0.13] Create a new HD seed after encrypting the wallet
< GitHub76>
[bitcoin] laanwj closed pull request #8389: [0.13] Create a new HD seed after encrypting the wallet (0.13...2016/07/hd_enc) https://github.com/bitcoin/bitcoin/pull/8389
< GitHub132>
[bitcoin] jtimon opened pull request #8413: Trivial: pass Consensus::Params& instead of CChainParams& in ContextualCheckBlock (master...0.13-consensus-last-params) https://github.com/bitcoin/bitcoin/pull/8413
< GitHub48>
[bitcoin] jtimon opened pull request #8412: libconsensus: Expose a flag for BIP112 (master...0.13-consensus-bip112-flag) https://github.com/bitcoin/bitcoin/pull/8412
< GitHub191>
bitcoin/0.13 0179a39 Wladimir J. van der Laan: qt: periodic translations update
< wumpus>
jonasschnelli: did you see my remark here: https://github.com/bitcoin/bitcoin/pull/8407/files#r72257114 ... I'm not sure what settings.value(strSettingsVersionKey) returns in the case !settings.contains(strSettingsVersionKey), but if it's garbage or raises an exception this may be problematic
< GitHub42>
bitcoin/0.13 18b8ee1 Jonas Schnelli: [Wallet] add HD xpriv to dumpwallet...
< jonasschnelli>
https://github.com/bitcoin/bitcoin/pull/8206 is featureish and I think we only backport it to 0.13 because of possible complains because of lack of exporting the xpriv
< * gmaxwell>
goes to find the old bitcoin wiki page.
< GitHub182>
[bitcoin] laanwj closed pull request #8365: Treat high-sigop transactions as larger rather than rejecting them (master...unifysigopcost) https://github.com/bitcoin/bitcoin/pull/8365
< GitHub176>
bitcoin/master 618c9dd Wladimir J. van der Laan: Merge #8365: Treat high-sigop transactions as larger rather than rejecting them...
< GitHub176>
bitcoin/master ab942c1 Pieter Wuille: Treat high-sigop transactions as larger rather than rejecting them
< gmaxwell>
By blocking I just meant bitcoin core wouldn't open multiple processes.
< gmaxwell>
well I suggested before a general design, where bitcoin-core wallet just has a simple interface to call another process to ask it to get signatures, providing it with the relevant data... and then that external process can implement the approrpiate call out to whatever is in use.
< da2ce7_mobile>
You could import these seeds into your Bitcoin Core to act as hot-wallets.
< gmaxwell>
or we could implement some version of the block bloom indexing that was posted about on bitcoin-dev.
< gmaxwell>
wumpus: wallet.dat encryption also gives you an authorization hook. A user doesn't have to worry when screwing around with bitcoin-qt that they're acidentally going to send funds.
< DongSwanson>
so bitcoin-core cannot create CSV escrows but can sign it's outgoing transactions if you provide the correct redeemscript?
< Chris_Stewart_5>
through bitcoin core's wallet UI?
< Chris_Stewart_5>
You can use something like peter todd's python bitcoin library or whatever library there is for your favorite language
< Chris_Stewart_5>
DongSwanson: Bitcoin Core doesn't expose functionality to create custom contracts through a user interface (that I know of...) You need to manually construct the contract
< DongSwanson>
sipa: oh. so if I wanted to create a escrow with timeout for a real world scenario, we cannot use bitcoin-core?
< DongSwanson>
can somebody help me with utilizing CHECKSEQUENCEVERIFY with bitcoin-core? I want to create a "escrow with timeout" with bitcoin-core