19:00:13 <wumpus> #startmeeting
19:00:13 <lightningbot> Meeting started Thu Jul  5 19:00:13 2018 UTC.  The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:13 <lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:00:24 <provoostenator> Hi
19:00:47 <gmaxwell> Hi.
19:00:51 <wumpus> can someone else paste the name list I don't have it handy
19:01:07 <wumpus> proposed topics?
19:01:19 <provoostenator> Topic suggestion: alternating meeting time
19:01:47 <wumpus> #topic High priority for review
19:01:50 <provoostenator> And maybe topic suggestion: Min relay fee
19:01:52 <aj> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr btcdrak sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag provoostenator
19:02:05 <wumpus> looks like there is only one thing left: #12196
19:02:08 <cfields> hi
19:02:11 <gribble> https://github.com/bitcoin/bitcoin/issues/12196 | Add scantxoutset RPC method by jonasschnelli · Pull Request #12196 · bitcoin/bitcoin · GitHub
19:02:17 <wumpus> any suggestions?
19:03:12 <wumpus> reminder that the 0.17 feature freeze is 2018-07-16, so in roughly a week
19:03:20 <wumpus> #link 0.17 release schedule https://github.com/bitcoin/bitcoin/issues/12624
19:03:20 <sipa> oh wow
19:03:28 <sipa> thanks for reminding us
19:03:42 <promag_> §shi
19:03:55 <wumpus> so if there are features that still need to make it in, we certainly have to make them high prio for review
19:04:21 <gmaxwell> sipa: Is #12196 'compatible' in what it matches with your new work on wallet scanning?   I haven't looked at that PR for a while, but I recall that at one point it expected you to provide pubkeys as the thing you scan for.
19:04:26 <gribble> https://github.com/bitcoin/bitcoin/issues/12196 | Add scantxoutset RPC method by jonasschnelli · Pull Request #12196 · bitcoin/bitcoin · GitHub
19:04:31 <aj> wumpus: #13547 or #12458 would be nice to have for 0.17, as would #13072 (though that needs a rebase now)
19:04:32 <gribble> https://github.com/bitcoin/bitcoin/issues/13547 | Make signrawtransaction* give an error when amount is needed but missing by ajtowns · Pull Request #13547 · bitcoin/bitcoin · GitHub
19:04:34 <gribble> https://github.com/bitcoin/bitcoin/issues/13072 | Update createmultisig RPC to support segwit by ajtowns · Pull Request #13072 · bitcoin/bitcoin · GitHub
19:04:35 <provoostenator> I'd like to get #11658
19:04:36 <gribble> https://github.com/bitcoin/bitcoin/issues/12458 | Enforce that amount is provided for signrawtransaction prevtxs by Empact · Pull Request #12458 · bitcoin/bitcoin · GitHub
19:04:39 <gribble> https://github.com/bitcoin/bitcoin/issues/11658 | During IBD, when doing pruning, prune 10% extra to avoid pruning again soon after by luke-jr · Pull Request #11658 · bitcoin/bitcoin · GitHub
19:04:41 <wumpus> gmaxwell: the xpub stuff was removed for that reason
19:04:43 <sipa> gmaxwell: yes, discussed in previous meeting
19:04:47 <gmaxwell> sipa: Thanks!
19:04:59 <wumpus> so that when it gets added it's compatible with sipa's proposal
19:05:10 <sipa> i'm almost done with an implementation for "output descriptors" which we'll just be able to plug into scantxoutset
19:05:24 <wumpus> nice!
19:05:41 <sipa> i'd very much like to see PSBT in 0.17
19:05:42 <wumpus> aj: ok, thanks
19:05:49 <wumpus> me too
19:05:52 <wumpus> I'll add that to high priority
19:06:07 <achow101> wumpus: #13557 for high prio please (psbt)
19:06:14 <gribble> https://github.com/bitcoin/bitcoin/issues/13557 | BIP 174 PSBT Serializations and RPCs by achow101 · Pull Request #13557 · bitcoin/bitcoin · GitHub
19:06:32 <gmaxwell> +1
19:06:56 <nmnkgl> #13298
19:06:58 <gribble> https://github.com/bitcoin/bitcoin/issues/13298 | Net: Random delays *per network group* to obfuscate transaction time by naumenkogs · Pull Request #13298 · bitcoin/bitcoin · GitHub
19:07:02 <wumpus> achow101: done
19:07:28 <nmnkgl> This is probably for high prio.
19:07:30 <wumpus> so does aeveryone agree with the PRs that aj proposes?
19:07:44 <wumpus> nmnkgl: I think that needs a lot of discussion still
19:07:50 <wumpus> nmnkgl: there's some security worries
19:08:13 <wumpus> nmnkgl: agree it's important, but not something to rush for 0.17
19:08:39 <wumpus> though if other people think so I'm happy to concede
19:08:53 <sipa> i think sdaftuar and nmnkgl have worked it out pretty much
19:09:02 <gmaxwell> I think that 13298 is basically done? no?
19:09:24 <nmnkgl> I think it is.
19:09:33 <wumpus> ok
19:09:37 <gmaxwell> I'm always happy to see stuff like that get out sooner rather than later, since it'll take months for its effects on the network to be observed.
19:09:41 <wumpus> adding it for review then
19:10:40 <sipa> nmnkgl: rebase it though
19:10:51 <Randolf> Hello.
19:11:16 <r-f> hello. any chance for #13414 gitlab support, it's like 2 screens of python only (plus comments)
19:11:18 <gribble> https://github.com/bitcoin/bitcoin/issues/13414 | Support gitlab API in github-merge.py by rfree-d · Pull Request #13414 · bitcoin/bitcoin · GitHub
19:13:28 <wumpus> r-f: yes, makes sense, but not relevant to 0.17 I think
19:13:39 <sipa> yeah, that seems independent of releases
19:13:53 <wumpus> ok added al the PRs mentioned by aj too
19:14:06 <wumpus> that means he now has two things on the high priority list though
19:14:20 <wumpus> sipa: right
19:14:21 <sipa> i'll do an effort to review all of them
19:14:31 <sipa> (so ack from me on that)
19:14:35 <wumpus> ok :)
19:15:12 <wumpus> #topic Alternating meeting time
19:15:23 <wumpus> (provoostenator)
19:15:41 <provoostenator> My suggestino would be something trivial, e.g. alternate by 12 hours every week
19:16:08 <provoostenator> e.g. 9:00 and 19:00 UTC
19:16:20 <provoostenator> (uhh, 7:00 UTC and 19:00 UTC)
19:16:49 <wumpus> sgtm
19:17:19 <provoostenator> With the day such that it is thursday morning Asia
19:17:47 <sipa> 7 UTC is pretty bad for eastcoast, though any time will hurt someone
19:17:49 <aj> thursday evening asia?
19:17:58 <provoostenator> Sorry, yes, what aj says.
19:18:13 <aj> (it's friday morning australia/asia now, 700 utc thursday is thursday afternoon)
19:18:20 <wumpus> sipa: yes, it would be alternatingly bad for asia and eastcoast then
19:18:26 <achow101> I tend to nack alternating meeting times as that will confuse people and result in probably less attendance as people either forget or get the meeting time switched
19:19:25 <gmaxwell> unfortunately there is no alternating scheme where a large group of regulars aren't impacted.
19:19:27 <luke-jr> sipa: depends on who would otherwise come
19:19:57 <achow101> 7 UTC is bad for americas in general
19:20:08 <sipa> midnight westcoast, 3am eastcoast
19:20:20 <cfields> I'm ok with awkward east-coast times, but I assume I'm in the minority
19:20:52 <wumpus> the problem is that the people in favor of the time will likely not be here now
19:21:00 <wumpus> it's unfair :-)
19:21:00 <phantomcircuit> probably just need a list of everybody who is likely to attend and their timezone to figure this one out
19:21:07 <phantomcircuit> wumpus, lul
19:21:08 <gmaxwell> phantomcircuit: it's bad regardless.
19:21:34 <clarkmoody> Is there a way to have an Asia meeting prior to the Europe/USA meeting and review minutes prior to this one?
19:21:36 <gmaxwell> sdaftuar: morcos: I'm guessing you're not going to be showing up between 3am and 4am.
19:21:38 <gmaxwell> :P
19:21:40 <phantomcircuit> i more meant for figuring out the time rather than doing an alternating schedule
19:21:41 <aj> a 3-phase cycle of 8 hours ought to make everyone able to attend 2 of 3 meetings :-/
19:21:58 <wumpus> we're getting kicked out here
19:22:04 <wumpus> can someone else take the chair please
19:22:15 <sipa> endmeeting and i'll start a new one
19:22:21 <wumpus> #endmeeting