1 2016-12-06 14:51:10 <earlz> Is there a bitcoin wallet that supports P2SH? Like for multisig and/or normal pubkeyhash, but encoded within a P2SH transaction?
 2 2016-12-06 14:59:01 <Chris_Stewart_5> for programming or with a UI?
 3 2016-12-06 15:00:10 <earlz> with a UI primarily
 4 2016-12-06 15:00:24 <earlz> console or graphical
 5 2016-12-06 15:00:56 <Chris_Stewart_5> Most wallets default to P2SH(multisig), I don't know of any that default to that for pubkeyhash though
 6 2016-12-06 15:01:45 <earlz> Well, sending and receiving. I don't think anything really works for receiving like a normal pubkeyhash would, but I can't find much info. I guess it's unusual
 7 2016-12-06 15:09:25 <BTCgame_> Hello everyone!
 8 2016-12-06 15:10:48 <BTCgame_> is there anyone who created or played lottery bitcoins games? I am full stack developer who making an application related to bitcoins payments and I have some questions related to payments
 9 2016-12-06 15:12:57 <BTCgame_> I mean how you deal with minimal fee when making transactions from system account to user account
10 2016-12-06 15:23:07 <afk11> earlz: blocktrail for personal 2-of-3 with recovery if they 'go away'. copay uses 1-of-1 multisig(p2sh) for your personal wallet, it also exposes a multi-party multisig UI
11 2016-12-06 15:47:21 <Chris_Stewart_5> How does the NULLFAIL policy flag help eliminate malleability?
12 2016-12-06 15:51:15 <Chris_Stewart_5> is the only difference that the script terminates immediately instead of continuing evaluation?
13 2016-12-06 16:53:09 <sipa> Chris_Stewart_5: the important part is that it is guaranteed to fail
14 2016-12-06 17:11:03 <Chris_Stewart_5> Thanks
15 2016-12-06 17:45:11 <BTCgame> Hi, what minimal amount should I sent with minimal fee to send money from first address to second address (and how much time will it take?)
16 2016-12-06 18:37:10 <moli> is there a document somewhere that explains how segwit solves malleability?
17 2016-12-06 18:38:03 <sipa> it makes the malleable part not contribute to the txid
18 2016-12-06 18:38:29 <abpa> signatures can't sign themselves, so people can change the signature, so remove signatures from the hashing algorithm that makes the txid, so the txid remains consistent even if you change the signature
19 2016-12-06 18:38:32 <sipa> so it can still be malleated, but it won't break unconfirmed transactions depending on it
20 2016-12-06 18:41:01 <moli> sipa, thanks for the explanation, it would be great if you could write up in technical detail a bit more for us ?
21 2016-12-06 18:42:13 <arubi> abpa, self-signed signature in a transaction on testnet: 0895e97e9c4ce7ebe04e15e0835bb0788053fbfdbbb2f3f25f81631687d7b857  :)
22 2016-12-06 18:43:39 <sipa> moli: watch my hong kong presentation or the transcript :)
23 2016-12-06 18:51:22 <moli> sipa, is segwit still the same as planned in the presentation?  it seems segwit doesn't save block space?
24 2016-12-06 18:53:32 <sipa> moli: it just accounts for the witness part 1/4
25 2016-12-06 18:56:08 <moli> ok, thanks, sipa
26 2016-12-06 18:56:42 <sipa> moli: https://bitcoincore.org/en/2016/01/26/segwit-benefits/