--- Log opened Mon Sep 03 00:00:58 2018
00:01 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has joined #bitcoin-core-dev
00:06 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has quit [Ping timeout: 252 seconds]
00:33 -!- profmac [~ProfMac@2001:470:1f0f:226:18f4:2632:4ae3:d66e] has quit [Ping timeout: 240 seconds]
01:00 -!- dcousens [~dcousens@110.140.174.10] has joined #bitcoin-core-dev
01:03 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev
01:06 -!- profmac [~ProfMac@2001:470:1f0f:226:9887:b7f:9ab6:d7aa] has joined #bitcoin-core-dev
01:22 -!- setpill [~setpill@unaffiliated/setpill] has quit [Ping timeout: 250 seconds]
01:24 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev
01:33 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev
01:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds]
02:03 < provoostenator> I put a few bounties on Bountysource a while ago, that seems the right way to coordinate these kinds of things, although I've only had limited success.
02:04 < provoostenator> And it doesn't help that they were eaten up by some ICO with too much money.
02:10 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has quit [Ping timeout: 272 seconds]
02:18 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev
02:29 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
02:39 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev
02:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
02:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
03:06 < wumpus> bountysource supports bitcoin? TIL
03:25 -!- grubles_ [~grubles@gateway/tor-sasl/grubles] has joined #bitcoin-core-dev
03:26 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 250 seconds]
03:26 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev
03:27 -!- grubles [~grubles@gateway/tor-sasl/grubles] has quit [Ping timeout: 250 seconds]
03:54 -!- kallewoof [~quassel@240d:1a:759:6000:a7b1:451a:8874:e1ac] has quit [Ping timeout: 250 seconds]
04:09 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
04:25 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Quit: Leaving.]
04:28 -!- hebasto [~hebasto@195.60.70.234] has quit [Remote host closed the connection]
04:30 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Read error: Connection timed out]
04:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
04:37 -!- hebasto [~hebasto@195.60.70.234] has joined #bitcoin-core-dev
04:42 -!- setpill [~setpill@unaffiliated/setpill] has quit [Ping timeout: 240 seconds]
04:42 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev
04:45 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection]
04:47 -!- setpill [~setpill@unaffiliated/setpill] has quit [Ping timeout: 240 seconds]
04:48 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev
04:52 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
05:03 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection]
05:04 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev
05:09 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has joined #bitcoin-core-dev
05:09 -!- Deacydal [~Deacyde@unaffiliated/deacyde] has joined #bitcoin-core-dev
05:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
05:38 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
05:39 -!- miknotauro_ [~miknotaur@187.207.79.62] has joined #bitcoin-core-dev
05:40 -!- miknotauro_ [~miknotaur@187.207.79.62] has quit [Client Quit]
05:41 -!- miknotauro [~miknotaur@187.207.79.62] has joined #bitcoin-core-dev
05:41 -!- Linrono [~androirc@pool-108-31-147-152.washdc.fios.verizon.net] has quit [Read error: Connection reset by peer]
05:53 -!- Linrono [~androirc@pool-108-31-147-152.washdc.fios.verizon.net] has joined #bitcoin-core-dev
05:54 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
06:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds]
06:30 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
06:31 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
06:32 -!- setpill [~setpill@unaffiliated/setpill] has quit [Ping timeout: 250 seconds]
06:34 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev
06:34 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 250 seconds]
06:34 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev
06:35 -!- Linrono [~androirc@pool-108-31-147-152.washdc.fios.verizon.net] has quit [Read error: Connection reset by peer]
06:37 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev
06:38 -!- setpill [~setpill@unaffiliated/setpill] has quit [Client Quit]
06:50 -!- Linrono [~androirc@pool-108-31-147-152.washdc.fios.verizon.net] has joined #bitcoin-core-dev
07:06 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev
07:13 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Excess Flood]
07:13 -!- miknotauro [~miknotaur@187.207.79.62] has quit [Ping timeout: 245 seconds]
07:13 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev
07:26 -!- itaseski [~itaseski@213.135.176.254] has joined #bitcoin-core-dev
07:28 -!- promag [~promag@119.70.114.89.rev.vodafone.pt] has joined #bitcoin-core-dev
07:42 < wumpus> oh, through coinbase...
08:16 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection]
08:17 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev
08:20 -!- itaseski [~itaseski@213.135.176.254] has quit [Quit: Leaving]
08:27 -!- Tennis [~Tennis@unaffiliated/tennis] has joined #bitcoin-core-dev
08:49 -!- maitra [~voltron@59.153.120.164] has joined #bitcoin-core-dev
08:49 -!- Krellan [~Krellan@2601:640:4000:9258:ed79:3217:ecfd:9f89] has joined #bitcoin-core-dev
09:08 -!- promag [~promag@119.70.114.89.rev.vodafone.pt] has quit [Remote host closed the connection]
09:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
10:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
10:17 -!- jhfrontz [~Adium@cpe-184-57-118-36.columbus.res.rr.com] has joined #bitcoin-core-dev
10:21 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds]
10:22 -!- hebasto [~hebasto@195.60.70.234] has quit [Remote host closed the connection]
10:24 -!- Guest79908 [~GAit@unaffiliated/gait] has quit [Quit: WeeChat 1.0.1]
10:24 -!- GAit [~GAit@unaffiliated/gait] has joined #bitcoin-core-dev
10:24 -!- Salve [~salve@139.60.181.221] has joined #bitcoin-core-dev
10:24 < Salve> Why does bitcoin use sha-512? 
10:24 < Salve> o.O
10:33 -!- Salve [~salve@139.60.181.221] has quit []
10:34 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 245 seconds]
10:35 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 272 seconds]
10:38 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 252 seconds]
10:39 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
10:44 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
10:56 -!- Krellan [~Krellan@2601:640:4000:9258:ed79:3217:ecfd:9f89] has quit [Read error: Connection reset by peer]
10:57 -!- Krellan [~Krellan@2601:640:4000:9258:ed79:3217:ecfd:9f89] has joined #bitcoin-core-dev
10:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]
11:04 < rafalcpp> sipa: seems parts of his code disappeared from git? or is github acting up. following parts of that discussion re 14090 and getting into places like https://github.com/bitcoin/bitcoin/pull/14090/files/9cc9bd700e92486189695ea1cb6edafd714cb33b and github says not found 
11:06 < maitra> bitcoind in regtest mode giving out empty responses to libbitcoinrpc RPC calls. Can someone help mw out here??
11:07 < maitra> while switching back to testnet works fine. Valid JSONs are returned. 
11:09 -!- Linrono [~androirc@pool-108-31-147-152.washdc.fios.verizon.net] has quit [Read error: Connection reset by peer]
11:12 -!- grubles_ is now known as grubles
11:17 -!- maitra [~voltron@59.153.120.164] has quit [Quit: WeeChat 1.9.1]
11:28 -!- maitra [~voltron@59.153.120.164] has joined #bitcoin-core-dev
11:47 -!- Deacydal [~Deacyde@unaffiliated/deacyde] has quit [Quit: May the Shwartz be with you]
11:48 -!- maitra [~voltron@59.153.120.164] has quit [Quit: WeeChat 1.9.1]
11:56 -!- miknotauro [~miknotaur@187.207.79.62] has joined #bitcoin-core-dev
11:58 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]
12:05 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
12:05 -!- miknotauro [~miknotaur@187.207.79.62] has quit [Ping timeout: 252 seconds]
12:10 -!- Netsplit *.net <-> *.split quits: moneyball, Jackielove4u, fronti, rubensayshi_, nsh, takinbo, provoostenator, emzy, skeees, ChrisMorrisOrg,  (+2 more, use /NETSPLIT to show all of them)
12:10 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has joined #bitcoin-core-dev
12:10 -!- Netsplit *.net <-> *.split quits: eragmus, arubi, aspect_, grubles, Guest8683, ghost43, sipa, intcat
12:14 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #bitcoin-core-dev
12:14 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev
12:15 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev
12:20 -!- nsh [~lol@wikipedia/nsh] has joined #bitcoin-core-dev
12:21 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-core-dev
12:24 < sipa> rafalcpp: if there were force pushes it's possible the code is no longer there
12:25 < gmaxwell> achow101: Is it really the case that there is no way in the rpc to take the scriptpubkey and amount from scantxoutset and use that to create/populate a PSBT?
12:26 < achow101> probably not. I haven't looked at scantxoutset yet
12:26 < gmaxwell> it returns output that looks like listunspent
12:27 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev
12:27 < sipa> createpsbt ?
12:27 < gmaxwell> but what I mean is that the createpsbt ignores scriptpubkey and amount, even if you provide them.
12:27 < sipa> oh, i see
12:27 < achow101> right now it only updates from the wallet
12:28 < achow101> there's an open pr to update from the node
12:28 < achow101> I can add to that updating from user provided data
12:28 < gmaxwell> yea, at least just make it so create doesn't ignore them would be nice.
12:28 < sipa> gmaxwell: it would lead to hard to analyse problems if it was a non-witness output being spent
12:29 < gmaxwell> sipa: how so?
12:29 < sipa> gmaxwell: for those it needs the full tx being spent, not just amount and sPK
12:29 < gmaxwell> There is no way to bypass that?
12:29 < sipa> no
12:29 < sipa> signers need that information
12:29 < achow101> gmaxwell: no, otherwise you could be tricked into signing something else
12:30 < gmaxwell> oh jesus. I am not going to be tricked into signing something else.
12:30 < gmaxwell> I understand how the bitcoin protocol works. I'm surprised that there isn't any way to bypass checking the inputs.
12:31 < gmaxwell> esp since the existing raw transaction flow provides no way to do that at all.
12:31 < sipa> heh, i guess there could be a "yes_i_verified_things_myself" option that skips the check in signing
12:31 < gmaxwell> (no way for the offline signer to check the fee)
12:31 < sipa> but you still need an updator first that understands the script being spent from
12:31 < sipa> so just adding amount/sPK isn't enough
12:31 < achow101> gmaxwell: sipa and I concluded that it was always safe to produce a segwit signature. so the problem is really with non-segwit
12:32 < achow101> so if all of your inputs were segwit, you could bypass that check
12:33 < sipa> my idea was to add an RPC that takes a list of descriptors, and updates using those from the UTXO set
12:33 < sipa> which would only work for segwit inputs still
12:33 < gmaxwell> Thats a good idea. You should still update non-segwit. Its up to the signer to decide if it has enough information.
12:34 < achow101> gmaxwell: we can't because we cant always fetch full transactions
12:34 < gmaxwell> ...
12:34 < gmaxwell> If you are updating from the UTXO set you can't provide full transactions. Absolutely. So don't.
12:34 < sipa> gmaxwell: if you want to sign without checking, you don't need any information at all in the psby
12:35 < gmaxwell> you need the scriptpubkeys.
12:35 < sipa> righr
12:35 < gmaxwell> I was hoping that this would replace an existing raw transaction workflow, but it not only doesn't but it seems not what you and achow are arguing with me.
12:35 < sipa> but there is no way to add that information in the psbt without providing a full tx
12:36 < sipa> there is a field for input data to a non-segwit input
12:36 < sipa> and one for input to a segwit input
12:36 < sipa> tbe first is a full tx, the second is amount/sPK
12:36 < gmaxwell> Then PSBT as they are today cannot replace raw transactions.
12:37 < sipa> you could fill segwit info from utxo data, even for non-segwit inputs
12:37 < sipa> but i expect various pieces of software will break
12:37 < gmaxwell> hm. it could correctly distinguish segwit from not based on the spk.
12:37 < gmaxwell> Thats ugly.
12:38 < gmaxwell> Better would be to just add a field type for non-sw utxo information, I think.
12:38 < sipa> no
12:38 < sipa> with a p2sh embedded segwit you can't tell
12:38 -!- ryanofsky [russ@jumpy.yanofsky.org] has quit [Quit: ZNC 1.7.0 - https://znc.in]
12:38 < gmaxwell> oh, indeed.
12:39 < sipa> i'm really scared about workflows that rely on unverifiable data
12:39 < gmaxwell> In any case, for what I'm doing for the moment, my choices now are: download 200GB of blockchain OR give up on using PSBT and just use a plain raw tx workflow.
12:39 < gmaxwell> So obviously I'm going to do the latter.
12:40 < sipa> i'm sure there is another way
12:40 < gmaxwell> I suppose I could also go to the system that already has the blockchain and do a 6 hour rescan to add the relevant inputs to the wallet.
12:40 -!- ryanofsky [~russ@jumpy.yanofsky.org] has joined #bitcoin-core-dev
12:41 < achow101> gmaxwell: I don't quite follow what you are trying to do
12:42 < gmaxwell> achow101: sweep a key that is on an offline machine.  There isn't any risk of 'send the coins to fees' because I know apriori how much coins are there.
12:42 < sipa> gmaxwell: well, right now, the implementation in bitcoin core isn't sufficient for non-wallet operation
12:42 < sipa> just having utxo data isn't enough; you also meed an updator which knows the pubkeys used, the redeemscripts, ...
12:43 < sipa> that could be provided by a descriptor, but isn't implemented yet
12:43 < gmaxwell> this is easy to do with rawtx + scantxoutset  (or rawtx + a block explorer), I was expect PSBT to simpify it at least slightly.
12:44 < sipa> i'm sure it will, once there are a few extra RPCs
12:44 < achow101> gmaxwell: it's only easy to do since you verified that the spk and amounts are correct. that's not something we can easily generalize
12:44 < gmaxwell> I don't see how based on the above conversation? 
12:44 < sipa> gmaxwell: for segwit inputs, at least
12:45 < sipa> there could also be a signer that lets you bypass safety checks
12:45 < sipa> but i'm scared about that
12:46 < gmaxwell> you managed to fail to be scared about that for years with that being the only way to use signrawtransaction. :)
12:48 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev
12:49 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has quit [Quit: May the Shwartz be with you]
12:50 < sipa> gmaxwell: fair
12:51 < sipa> though i think psbt aims at being convenient for slightly less sophisticated users
12:52 < gmaxwell> well the alternative is implement stuff to take the uxto data and then go fetch pruned blocks from the network to get the inputs.
12:52 < gmaxwell> so then at least there is a way to easily get the inputs.
12:52 < achow101> ew
12:53 < sipa> i don't think there is any harm in letting createpsbt take the amount/sPK and pass them through and create a segwit tx input field with those
12:53 < sipa> which would be enough for an unsafe signer with knowledge of scripts/pubkeys to sign
12:54 < gmaxwell> but as I'm saying, because of limitations in PSBT, even with being willing to modify the software to remove a check there is no way for this to replace raw tx in my existing workflow.  I wouldn't _mind_ it putting the inputs in there, but there is no efficent way to get them on a pruned node. 
12:55 < sipa> gmaxwell: if the checks are dropped, it would work fine, no?
12:55 < sipa> you wouldn't expect it to work in other software, though
12:56 < gmaxwell> Yes, if you could pass along the data and bypass the checks it would work fine.  Though a way of fetching the information on a pruned node would be more general (e.g. would work with hardware wallets that don't have a bypass)
12:57 < andytoshi> i think PSBT should have an extension to support gmaxwell's workflow .. even if the new field names have "unsafe" in them or something
12:57 < andytoshi> or maybe this is purely about core RPC, and not PSBT itself
12:57 < gmaxwell> sadly it sounds like PSBT needs an extension if its to accomidate this.
12:58 < gmaxwell> ('this' being unchecked signing)
12:58 < andytoshi> right .. it would be good if there was an "amount_unsafe" field or something that you could fill in, and if signers had good reason to trust it, they could use it
12:58 < sipa> there is no need for amount data
12:58 < sipa> only scriptPubKey
12:58 < jonasschnelli> kanzure: is there an issue with the bitcoin-dev mailing? I sent an email 7h, but got nothing back from the list
12:58 < gmaxwell> they can use the amount_unsafe data to display/check fees.
12:58 < sipa> gmaxwell: that seems unwise
12:59 < sipa> the only reason the data is there is so it can be verified
12:59 < sipa> if you bypass that, and are willing to vouch you yourself did sufficient checking, that doesn't seem needed
12:59 < andytoshi> sipa: it does if you want a hardware wallet that does fee-checking, and its only means of communication is by PSBT
13:00 < andytoshi> otherwise you need an extra transport to pass it pre-verified daa
13:00 < andytoshi> data
13:00 < sipa> andytoshi: it can't fee check if the amount isn't verified
13:00 < gmaxwell> sipa: the 'checking' of that part was done at an earlier stage.
13:00 < andytoshi> it sounds like gmax verified it when he made the transactions, and then didn't keep the transactions around..
13:00 < sipa> i'm confused
13:00 -!- polydin [~delphi@ip-69-80-248-129.wireless.static.fire2wire.com] has joined #bitcoin-core-dev
13:01 < sipa> if you verified the fee data outside the hsm already, why do you need to tell it the amount?
13:01 < gmaxwell> sipa: only UI convience wise.
13:01 < sipa> gmaxwell: again, that seems unwise if it's unverified
13:02 < sipa> i think the hw signer should just say "unverifiable data, agree to sign anyway?"
13:02 < andytoshi> and the user can use a pocket calculator for the fee?
13:02 < gmaxwell> In any case, I don't have a specific need for an unverifyed sign. I just need EITHER an unverfied sign, or a easy way to provide using a pruned node input tx for arbritary scriptpubkey that exist in the utxo set.
13:03 < sipa> andytoshi: the user must have checked the fee already outside, before passing it to the signer anyway
13:03 < sipa> andytoshi: so no, not a pocket calculator; just trusting himself which he's already doing in an unverified setting
13:03 < gmaxwell> e.g. the 'security upgrade' of getting the inputs is fine, so long as it doesn't cost an N hour download the whole blockchain/recan.
13:04 < sipa> gmaxwell: how do you imagine that to work?
13:04 < gmaxwell> sipa: the utxo has heights. get the inputs from the blocks, if we have them, otherwise go fetch the blocks.
13:05 < andytoshi> sipa: i don't feel strongly about this, but it's annoying that the user is being forced to compute the fee herself and verify this when she has a hw signer that is perfectly capable of addition
13:05 < sipa> ah, i see
13:06 < gmaxwell> Aside, AFAICT walletprocesspsbt  doesn't even show the fees. nor does decodepsbt... so using bitcoin core rpc as your HSM doesn't even provide any security improvement from having the inputs present? or am I missing it?
13:06 < achow101> gmaxwell: decodepsbt does if all inputs are there
13:06 < sipa> andytoshi: in this setting the user must have done far more complex things already
13:07 < gmaxwell> achow101: oh okay, still nothing forces you to call decode on it.
13:07 < achow101> walletcreatefundedpsbt also gives you the fee.
13:08 < gmaxwell> achow101: yes, and? that is something that I'm running on the online host... 
13:08 < andytoshi> sipa: ok, fair enough
13:09 < sipa> in any case, the only way to exploit the file format right now to do this is to create a segwit inout field (even for non-segwit inputs), which also stores the amount
13:10 < sipa> i just think it's a bad idea to show a user information which is not verifiable - it's fine if they're willing to do verification elsewhere and let them override security checks
13:10 < gmaxwell> well one could also set the amount to the max value.
13:11 < gmaxwell> AFAIK there would never need to be a reason to override if we could reliably provide the inputs without absurd burdens, but right now we can't do that.
13:11 < sipa> but that also means you don't need to shwow it again:; they analysed it and trust it already
13:24 < gmaxwell> why did signrawtransactionwithkey permute the arguments.
13:25 -!- grubles [~grubles@gateway/tor-sasl/grubles] has joined #bitcoin-core-dev
13:27 < achow101> permute?
13:28 < gmaxwell> signrawtransaction took  <tx> <inputs> <privkeys>   withkey takes <tx> <privkeys> <inputs>
13:28 < achow101> withkey requires keys, but not inputs
13:28 < achow101> inputs are optional for with key, but were optional in signraw
13:29 < achow101> keys were optional in signraw
13:29 < gmaxwell> just resulted in a couple minutes of confusion dealing with uninformative "JSON value is not a string as expected" after changing a script due to deprication.
13:29 < gmaxwell> Okay, makes sense I guess.
13:35 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 272 seconds]
13:36 -!- ryanofsky [~russ@jumpy.yanofsky.org] has quit [Remote host closed the connection]
13:40 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
13:49 -!- unholymachine [~quassel@2601:8c:c003:9f16:95f8:5e7e:9504:7929] has quit [Ping timeout: 240 seconds]
13:53 -!- bosma [sid103570@gateway/web/irccloud.com/x-gpkciklfvchaubui] has joined #bitcoin-core-dev
13:55 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Quit: <                            ~~<   K1lr0y w4s h3R3   >~~                           >]
14:02 -!- polydin [~delphi@ip-69-80-248-129.wireless.static.fire2wire.com] has quit [Ping timeout: 245 seconds]
14:03 -!- promag [~promag@a89-153-198-202.cpe.netcabo.pt] has joined #bitcoin-core-dev
14:15 -!- Emzy [~quassel@unaffiliated/emzy] has joined #bitcoin-core-dev
14:18 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
14:20 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev
14:33 -!- timothy [~tredaelli@redhat/timothy] has quit [Ping timeout: 252 seconds]
14:36 -!- miknotauro [~miknotaur@187.207.79.62] has joined #bitcoin-core-dev
14:37 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds]
14:38 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
14:44 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 246 seconds]
14:46 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
14:47 -!- profmac [~ProfMac@2001:470:1f0f:226:9887:b7f:9ab6:d7aa] has quit [Ping timeout: 250 seconds]
14:50 -!- unholymachine [~quassel@2601:8c:c003:9f16:408f:1b81:8604:dd0b] has joined #bitcoin-core-dev
14:52 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
15:07 -!- profmac [~ProfMac@72-48-98-98.dyn.grandenetworks.net] has joined #bitcoin-core-dev
15:16 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
15:21 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds]
15:22 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
15:42 -!- promag [~promag@a89-153-198-202.cpe.netcabo.pt] has quit [Remote host closed the connection]
15:43 -!- profmac [~ProfMac@72-48-98-98.dyn.grandenetworks.net] has quit [Read error: Connection reset by peer]
15:50 -!- profmac [~ProfMac@72-48-98-98.dyn.grandenetworks.net] has joined #bitcoin-core-dev
15:55 -!- profmac [~ProfMac@72-48-98-98.dyn.grandenetworks.net] has quit [Read error: Connection reset by peer]
16:00 -!- profmac [~ProfMac@2001:470:1f0f:226:9887:b7f:9ab6:d7aa] has joined #bitcoin-core-dev
16:16 -!- spinza [~spin@155.93.246.187] has quit [Ping timeout: 245 seconds]
16:23 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
16:31 < kanzure> sipa: apologies. mailing list is in moderation mode since someone figured out how to spoof emails from bitcoin developers. emails were delayed due to my travel.
16:35 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
16:49 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has joined #bitcoin-core-dev
16:53 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has quit [Ping timeout: 245 seconds]
16:56 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 272 seconds]
16:56 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has joined #bitcoin-core-dev
16:57 -!- lnostdal [~lnostdal@77.70.119.51] has joined #bitcoin-core-dev
16:58 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl]
17:01 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has quit [Ping timeout: 240 seconds]
17:04 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 240 seconds]
17:10 -!- lnostdal [~lnostdal@77.70.119.51] has joined #bitcoin-core-dev
17:17 -!- Tennis [~Tennis@unaffiliated/tennis] has quit [Quit: Leaving]
17:19 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]
17:22 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Disconnected by services]
17:22 -!- Krellan [~Krellan@2601:640:4000:9258:ed79:3217:ecfd:9f89] has quit [Read error: Connection reset by peer]
17:22 -!- Krellan [~Krellan@2601:640:4000:9258:ed79:3217:ecfd:9f89] has joined #bitcoin-core-dev
17:24 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 256 seconds]
17:29 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev
17:42 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has joined #bitcoin-core-dev
17:47 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has quit [Ping timeout: 244 seconds]
17:49 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Ping timeout: 252 seconds]
17:50 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #bitcoin-core-dev
18:12 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit []
18:15 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has joined #bitcoin-core-dev
18:25 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has quit [Ping timeout: 244 seconds]
19:13 -!- unholymachine [~quassel@2601:8c:c003:9f16:408f:1b81:8604:dd0b] has quit [Remote host closed the connection]
19:16 < da2ce7> kanzure, is it possible for to fix the headers of the emails so that regular email clients show the original author? -  Or could it be policy that people can put their name/nym at the end of the email. I find it a frustration to work out the author of many of the mails now.
19:25 < kanzure> has this changed recently?
19:25 < achow101> da2ce7: the original author is usually in the reply-to field
19:26 < achow101> both gmail and protonmail show me "from: X via bitcoin-dev"
19:32 < da2ce7> achow101, kanzure, I worked it out, my computer had a contact card for the mailing list and then just showing than instead of the real-name. :)
19:32 < da2ce7> thankyou anyway.
19:35 < kanzure> now that we have solved the email protocol, let's move on to coinjoin
20:56 -!- hebasto [~hebasto@195.60.70.234] has joined #bitcoin-core-dev
21:00 -!- Sinclair6 [~sinclair6@108-75-18-87.lightspeed.clmboh.sbcglobal.net] has joined #bitcoin-core-dev
21:02 -!- maitra [~voltron@59.153.120.164] has joined #bitcoin-core-dev
21:18 -!- miknotauro [~miknotaur@187.207.79.62] has quit [Ping timeout: 252 seconds]
21:31 -!- polydin [~delphi@ip-69-80-248-129.wireless.static.fire2wire.com] has joined #bitcoin-core-dev
21:41 -!- Urgo [~Urgo@cpe-107-15-142-254.nc.res.rr.com] has joined #bitcoin-core-dev
21:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
21:49 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
21:52 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 252 seconds]
22:00 -!- profmac [~ProfMac@2001:470:1f0f:226:9887:b7f:9ab6:d7aa] has quit [Read error: Connection reset by peer]
22:01 -!- profmac [~ProfMac@2001:470:1f0f:226:9887:b7f:9ab6:d7aa] has joined #bitcoin-core-dev
22:08 -!- profmac [~ProfMac@2001:470:1f0f:226:9887:b7f:9ab6:d7aa] has quit [Read error: Connection reset by peer]
22:08 -!- profmac [~ProfMac@2001:470:1f0f:226:9887:b7f:9ab6:d7aa] has joined #bitcoin-core-dev
22:40 -!- hebasto [~hebasto@195.60.70.234] has quit [Remote host closed the connection]
22:48 -!- felco [~felco@unaffiliated/felco] has quit [Ping timeout: 260 seconds]
22:50 -!- felco [~felco@unaffiliated/felco] has joined #bitcoin-core-dev
22:50 -!- _flow_ [~none@2001:638:a000:4140::ff10:844c] has quit [Ping timeout: 260 seconds]
22:51 -!- _flow_ [~none@2001:638:a000:4140::ff10:844c] has joined #bitcoin-core-dev
23:41 -!- miknotauro [~miknotaur@187.207.79.62] has joined #bitcoin-core-dev
--- Log closed Tue Sep 04 00:00:59 2018