12019-02-15T00:15:04 *** schmidty has joined #bitcoin-core-dev
22019-02-15T00:16:52 *** Aequitas_ has quit IRC
32019-02-15T00:19:36 *** Zenton has quit IRC
42019-02-15T00:20:02 *** schmidty has quit IRC
52019-02-15T00:29:30 <meshcollider> The segwit project (https://github.com/bitcoin/bitcoin/projects/5) is now empty
62019-02-15T00:29:53 <meshcollider> Time to close it?
72019-02-15T00:35:04 *** schmidty has joined #bitcoin-core-dev
82019-02-15T00:38:02 <aj> meshcollider: makes sense to me
92019-02-15T00:39:02 <instagibbs> \o/
102019-02-15T00:39:33 <instagibbs> still would like descriptor checksums, one more day to get that more review
112019-02-15T00:39:53 <aj> instagibbs: PR?
122019-02-15T00:40:22 *** schmidty_ has joined #bitcoin-core-dev
132019-02-15T00:40:27 <sipa> #15368
142019-02-15T00:40:29 <gribble> https://github.com/bitcoin/bitcoin/issues/15368 | Descriptor checksums by sipa · Pull Request #15368 · bitcoin/bitcoin · GitHub
152019-02-15T00:41:01 *** holmes has joined #bitcoin-core-dev
162019-02-15T00:42:06 *** jarthur has joined #bitcoin-core-dev
172019-02-15T00:43:01 <jb55> sipa: what do I have to read to understand the math behind the bech32-style checksums you come up with? looks generally useful...
182019-02-15T00:43:41 <sipa> jb55: i learned most from https://en.wikipedia.org/wiki/BCH_code, plus latent algebra knowledge :)
192019-02-15T00:44:00 <jb55> sipa: thx
202019-02-15T00:44:13 <sipa> jb55: we came up with a bunch of algorithms to opimize searching for parameters, which we probably should make a writeup about
212019-02-15T00:44:18 *** schmidty has quit IRC
222019-02-15T00:44:36 *** schmidty has joined #bitcoin-core-dev
232019-02-15T00:44:47 *** schmidty_ has quit IRC
242019-02-15T00:45:00 *** holmes has quit IRC
252019-02-15T00:46:00 <jb55> sipa: why you chose this kinda of error correcting code in particular would be good to know as well. would be a great read if you get around to writing it up!
262019-02-15T00:46:07 <aj> https://travis-ci.org/bitcoin/bitcoin/builds/492869085?utm_source=github_status&utm_medium=notification # travis job needs a kick (or maybe two kicks by now)
272019-02-15T00:47:28 <sipa> aj: kicked
282019-02-15T00:48:43 <meshcollider> aj should be in the org so he can do it himself, I thought he was :)
292019-02-15T00:48:55 *** schmidty has quit IRC
302019-02-15T00:49:20 *** schmidty has joined #bitcoin-core-dev
312019-02-15T00:49:28 <gmaxwell> jb55: why 'this kind' is a pretty easy answer: we use a cyclic linear code because after extensive research, it's the only class of code we know of that can achieve good guarentees for the "user makes random single character errors" channel.
322019-02-15T00:49:29 <aj> meshcollider: curses, foiled again
332019-02-15T00:50:40 <gmaxwell> jb55: other kinds of codes, like a simple CRC don't operate at the 5-bit-character level, and so can't guarentee e.g. that a bad input with 3 character errors will be detected.
342019-02-15T00:53:23 <gmaxwell> jb55: and other kinds of codes (like ones constructed from arbritary non-linearities) are computationally intractable-- as far as anyone yet knows-- for detecting as many errors as bech32 does.
352019-02-15T00:54:02 *** schmidty has quit IRC
362019-02-15T00:54:35 <gmaxwell> (er, that was unclear, I mean -- for examples-- no one knows how to determine what the minimum distance of an arbritary quasigroup code is, except for the single error case other than by performing an test of all possible error patterns)
372019-02-15T00:55:37 *** schmidty has joined #bitcoin-core-dev
382019-02-15T01:00:25 *** schmidty has quit IRC
392019-02-15T01:02:11 *** zhangzf has joined #bitcoin-core-dev
402019-02-15T01:04:29 <jb55> gmaxwell: ah, interesting... thx.
412019-02-15T01:07:13 <jb55> was wondering why I was dealing with 5bit words when working on a bech32 lib...
422019-02-15T01:07:54 <jb55> gmaxwell: is there a particular reason it's 5 bits?
432019-02-15T01:11:06 <jb55> oh I see the extra 3 are for error correction
442019-02-15T01:12:51 <gmaxwell> jb55: it's 5 bits because log2(32) is 5. -- the number of bits per character is a product of the character set size. The character set size is chosen to be relatively small because it makes entering it easier. Mixed case in base58, for example, makes it really hard to read addresses out loud (e.g. over the phone).
452019-02-15T01:14:00 * jb55 slowly getting it
462019-02-15T01:14:18 <gmaxwell> The exact character set size could be another value, but (1) if it's a power of two its much easier to convert to and from bytes, since each character represents an integer number of bits. and (2) for it to be feasable to design a linear error detection code over it, the size must be a prime or a prime raised to some power. (so base58 is out)
472019-02-15T01:14:51 <sipa> jb55: there are no bytes involved anywhere
482019-02-15T01:15:07 <sipa> everything is 5-bit symbols; both the 'data' and the 'checksum' are 5-bit units
492019-02-15T01:15:14 <jb55> ahh
502019-02-15T01:15:40 <sipa> the reason for that is because we expect errors that are affecting groups of 5 bits simultaneously
512019-02-15T01:15:40 <gmaxwell> Of the character set sizes that allow for easy conversion two and from bytes... 16 characters is overly restrictive (bigger addresses), and 64 is too many (requires using characters that are hard to distinguish/hard to type).
522019-02-15T01:15:54 <sipa> jb55: because 1 character in base32 = 5 bits
532019-02-15T01:16:51 *** mistergold has joined #bitcoin-core-dev
542019-02-15T01:17:54 <gmaxwell> A pretty good case could have been made for base-31, base-29, or base-27-- which would allow excluding some more visually similar characters without being much longer, but the code to convert from binary data into those bases is somewhat irritating.
552019-02-15T01:20:27 *** mistergo1d has quit IRC
562019-02-15T01:21:24 <jb55> and 7 bits wouldn't work because the character set size would be too large... 3 would be too verbose. and the log of other bases are fractional so conversion is annoying, if I'm getting this right
572019-02-15T01:21:35 <sipa> indeed
582019-02-15T01:21:52 <sipa> 6 bits would work too; base64 is pretty common, but it means mixing upper and lowercase
592019-02-15T01:22:15 <sipa> there are only 94 printable ascii characters, so 7 bits is kinda out
602019-02-15T01:22:32 <sipa> unless you want to mix in things like poop emoji
612019-02-15T01:27:24 <jb55> gotta capture that millenial market, should have went with basemoji
622019-02-15T01:27:43 <gmaxwell> mixed case is hard to read, also irritating to type on mobile devices, also results in more similar character mistakes.
632019-02-15T01:27:51 *** jarthur has quit IRC
642019-02-15T01:28:31 *** jarthur has joined #bitcoin-core-dev
652019-02-15T01:29:09 <gmaxwell> if your metric is "how long does it take to successfully transfer 200 bits of data between two humans, where one reads and speaks the other hears and types" a base somewhere between 25 and 32 is likely optimum.
662019-02-15T01:30:16 <gmaxwell> more than 32 and you're forced to use easily confused characters (and/or prefixing every letter with "upper" "lower" and causing a 2x slowdown)
672019-02-15T01:31:28 <jb55> base32 is my go-to, although I use a modified variant that replaces o,i with 8,9. I always thought that choice was kind of odd in the standard base32 encoding.
682019-02-15T01:31:45 <gmaxwell> If your metric is copy and paste, the length/characters hardly matter except non-alphanum characters break the automatic copy boundary behavior in browsers.
692019-02-15T01:32:01 <gmaxwell> jb55: there are like a half dozen different base32s that replace different characters.
702019-02-15T01:32:36 <jb55> although it's not optimized phonetically, would be interesting to see a character set that is ideal for voice transcription instead of visual.
712019-02-15T01:32:37 *** mistergo1d has joined #bitcoin-core-dev
722019-02-15T01:33:00 *** Karyon has joined #bitcoin-core-dev
732019-02-15T01:33:10 <gmaxwell> Our ommited characters are basied on minimizing visual confusion according to some NIST data. Though later a research paper came out and had confusion data generated from millions of password entry attempts and it gave essentially the same results.
742019-02-15T01:34:30 <gmaxwell> At least my thinking was the the visual component is always there (for human based transcription), while speaking is not always used. Also, speaking errors depend a lot on your accient and/or if you're using something like the NATO phonetic alphabet (alpha bravo charley delta echo foxtrot..)
752019-02-15T01:35:08 <gmaxwell> I think if that password entry data were available we would have used it instead of the NIST data, but I reran the analysis using it and got essentially the same result.
762019-02-15T01:35:53 *** mistergold has quit IRC
772019-02-15T01:37:02 *** cubancorona has joined #bitcoin-core-dev
782019-02-15T01:40:19 * jb55 thinking about an address format encoded as poetry
792019-02-15T01:41:12 * sipa mentions https://github.com/sipa/gramtropy
802019-02-15T01:41:52 <jb55> sipa always with the one ups
812019-02-15T01:43:57 <gmaxwell> (I think also if we had the password data I would have spent more time exploring e.g. base-27, since we actually would have had a good criteria to use to exclude more characters)
822019-02-15T01:48:51 <gmaxwell> One thing we were able to do in base-32 was make it so that if you only made the most likely mistakes then we are guarenteed to detect one more error. (we did this by choosing a character permutation that mapped the most likely errors to single bit errors, and choosing the code to also support up to 6 one bit errors)... this would have likely worked even better in base-27
832019-02-15T01:49:09 *** mistergo1d has quit IRC
842019-02-15T01:49:45 <gmaxwell> (both because we could exclude more characters outright, and because the analog would be mapping them to a single-trit error out of three trits per symbol.)
852019-02-15T01:53:04 <jb55> gmaxwell: sounds kind of like compression wrt. most common symbols assigned to shorter prefix bit sequences? in this case instead of most common symbols you're describing most common human error symbols?
862019-02-15T01:53:17 <jb55> if I'm understanding correctly
872019-02-15T01:54:22 <gmaxwell> jb55: https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki#Bech32 no, look at the table there. Visually similar characters like q/g or q/p are arranged so that their value differes only by 1 bit.
882019-02-15T01:54:56 <jb55> ohh
892019-02-15T01:54:57 <gmaxwell> (the table is dimensioned so that it's relatively easy to see the 5 dimensional 1-bit-difference hypercube...)
902019-02-15T01:56:37 <gmaxwell> r/t r/y 8/0 c/e 8/h almost all of the easier mistakes map to one bit differences.
912019-02-15T01:58:13 <jb55> gmaxwell: so the smaller bit difference the less ambiguity in detecting which symbol has the error?
922019-02-15T01:58:43 <sipa> jb55: the checksum itself was optimized to be slightly better for low-bit-error
932019-02-15T01:58:54 <sipa> this is not an inherent property; it was selected for
942019-02-15T01:59:14 <gmaxwell> the bech32 checksum will always detect if there are no more than 5 characters wrong, ... or if there are no more than 6 bits wrong.
952019-02-15T01:59:25 <gmaxwell> we specifically designed it for this behavior.
962019-02-15T02:00:04 <jb55> and by designed you're referring to which symbol is assigned to which 5 bit number?
972019-02-15T02:00:16 <sipa> no, the BCH code
982019-02-15T02:00:19 <jb55> ah
992019-02-15T02:00:27 <sipa> the character set was designed so that common errors are 1 bit only
1002019-02-15T02:00:28 <gmaxwell> Picking the symbol ordering lets us map common mistakes to single bit errors.
1012019-02-15T02:00:40 <sipa> the BCH code was designed to that 1 bit errors are more frequently detected
1022019-02-15T02:00:41 <gmaxwell> Picking the error correcting code let us pick one that would detect 6-one bit errors.
1032019-02-15T02:01:01 <sipa> the two are designed for each other
1042019-02-15T02:01:37 <gmaxwell> there were many possible codes which have exactly equal performance for detecting whole character errors, but one of them also did better for bit errors.
1052019-02-15T02:01:53 <jb55> picking a BCH code involves what, picking constants?
1062019-02-15T02:02:06 <sipa> jb55: effectively, picking the generator
1072019-02-15T02:02:18 <sipa> every cyclic code is uniquely characterized by its field representation and generator
1082019-02-15T02:02:39 <gmaxwell> this line in the BIP:
1092019-02-15T02:02:41 <gmaxwell> GEN = [0x3b6a57b2, 0x26508e6d, 0x1ea119fa, 0x3d4233dd, 0x2a1462b3]
1102019-02-15T02:02:42 <gmaxwell> mostly
1112019-02-15T02:03:31 * jb55 goes to learn about galois fields
1122019-02-15T02:04:06 <jb55> thx guys this makes a lot more sense now
1132019-02-15T02:12:31 *** Mischa010 has joined #bitcoin-core-dev
1142019-02-15T02:13:09 <Mischa010> hi there, does anyone here know to how many peers bitcoin sends new blocks in general?
1152019-02-15T02:13:35 <sipa> all.
1162019-02-15T02:13:37 <Mischa010> i know 8 peers are connected to but how many can actually request and download a block at the same time?
1172019-02-15T02:13:59 <Mischa010> i forgot the 'at the same time' qualifier!
1182019-02-15T02:14:20 <gmaxwell> Mischa010: 8 peers are the number of outbound connections a node normally has, but they can have many more inbound. 70 inbound isn't uncommon.
1192019-02-15T02:14:25 <sipa> Mischa010: this sounds like a question for https://bitcoin.stackexchange.com
1202019-02-15T02:14:40 <gmaxwell> it's actually been answered in a number of forms on stack exchange before.
1212019-02-15T02:14:50 <Mischa010> so there could be 70 downloading a block from a node at the same time?
1222019-02-15T02:15:09 <gmaxwell> Mischa010: for the most part blocks aren't even transfered. because magic.
1232019-02-15T02:15:57 <Mischa010> yes compact blocks is great
1242019-02-15T02:16:11 <Mischa010> incidentally, thanks for all the great work!
1252019-02-15T02:16:16 <gmaxwell> but yes, 70... as many as 125 in the default config, in fact... could be transfered at the 'same time'.
1262019-02-15T02:16:49 <gmaxwell> because of how tcp works you cannot generally achieve capacity without many concurrent streams in any case.
1272019-02-15T02:17:00 <Mischa010> yes that's true
1282019-02-15T02:17:05 <gmaxwell> as each one will only send one rwin worth before having to wait for an ack.
1292019-02-15T02:17:25 <Mischa010> although couldn't you just determine and set some maximum mtu per connection?
1302019-02-15T02:17:37 <gmaxwell> fwiw, node here with uptime of a week has not send a single whole block to any peer.
1312019-02-15T02:17:59 <Mischa010> nice
1322019-02-15T02:18:42 <Mischa010> but i guess starting with a big mtu has its own problems
1332019-02-15T02:18:43 *** schmidty has joined #bitcoin-core-dev
1342019-02-15T02:18:50 <gmaxwell> Mischa010: depends on link speeds, packet loss rates, remote tcp stack rwin value, all of which aren't observable generally.
1352019-02-15T02:18:55 <Mischa010> yes
1362019-02-15T02:20:07 <gmaxwell> (or at least not very observable at the application layer without non-portable os specific code)
1372019-02-15T02:20:58 <gmaxwell> in any case, I know there is a stackexchange question on the "why doesn't it just send to one peer at a time?" question
1382019-02-15T02:21:08 <Mischa010> assuming an ideal network you should propagate to e nodes
1392019-02-15T02:21:18 <Mischa010> at a time
1402019-02-15T02:21:35 <Mischa010> i just came up with this so it might be very wrong
1412019-02-15T02:21:59 <Mischa010> so in practice 2
1422019-02-15T02:22:21 <sipa> https://bitcoin.stackexchange.com/questions/81531/did-bitcoin-core-relay-blocks-sequentially-or-in-parallel-to-peers-before-compac/81533#81533
1432019-02-15T02:22:22 <gribble> https://github.com/bitcoin/bitcoin/issues/81533 | HTTP Error 404: Not Found
1442019-02-15T02:22:30 <sipa> lol
1452019-02-15T02:23:44 <gmaxwell> thats too narrow thinking, e.g. assuming a homogeneous network (equal speeds, equal delays on all links), fibre shows that the optimal distribution pattern (shortest time to reach all nodes) is achieved by round robining packets one at a time equally to each peer.
1462019-02-15T02:24:34 <gmaxwell> because they'll each send the recieved packets to each of their peers. spreading more slowly than that fails to achieve the maximum bisection bandwidth of the network.
1472019-02-15T02:25:43 <gmaxwell> (on an inhomogeneous network it's more complicated)
1482019-02-15T02:26:11 <Mischa010> interesting, is there any literature on this?
1492019-02-15T02:27:40 <gmaxwell> bitcoin specific, not that I'm aware of. There is a lot of lit on 'network coding' though, which covers many of these things.
1502019-02-15T02:30:38 *** DeanGuss has joined #bitcoin-core-dev
1512019-02-15T02:30:51 <Mischa010> great, im reading up on fibre now
1522019-02-15T02:31:01 <Mischa010> thanks
1532019-02-15T02:31:06 <gmaxwell> the writeup I made on stack exchange is probably one of the better ones.
1542019-02-15T02:31:11 <Mischa010> link?
1552019-02-15T02:31:39 <gmaxwell> https://bitcoin.stackexchange.com/questions/56485/can-someone-please-explain-fibre-to-me-like-im-5-and-why-is-it-useful/56494
1562019-02-15T02:32:51 *** Murch has quit IRC
1572019-02-15T02:33:02 <gmaxwell> fibre gets pretty close to the best possible performance (consistently within a couple ms of the one way link delays between nodes)... there are a long list of potential improvements, but most of them end up making it work worse because they take more cpu time than they save. :(
1582019-02-15T02:44:44 <Mischa010> ah yes i wasnt thinking at the packet level
1592019-02-15T02:45:01 <Mischa010> an interface only sends one packet at a time right?
1602019-02-15T02:46:11 <Mischa010> then my point is moot :p
1612019-02-15T02:48:22 *** pinheadmz has quit IRC
1622019-02-15T02:49:00 *** skyikot has joined #bitcoin-core-dev
1632019-02-15T03:03:16 *** pinheadmz has joined #bitcoin-core-dev
1642019-02-15T03:03:51 *** schmidty has quit IRC
1652019-02-15T03:08:23 *** AaronvanW has quit IRC
1662019-02-15T03:10:33 *** bitcoin-git has joined #bitcoin-core-dev
1672019-02-15T03:10:34 <bitcoin-git> [bitcoin] yunchiri closed pull request #15396: docs: make it clearer that posix mode must be used in WSL (master...patch-1) https://github.com/bitcoin/bitcoin/pull/15396
1682019-02-15T03:10:39 *** bitcoin-git has left #bitcoin-core-dev
1692019-02-15T03:12:54 *** ap4lmtree has quit IRC
1702019-02-15T03:13:56 *** Mischa010 has quit IRC
1712019-02-15T03:18:42 *** AaronvanW has joined #bitcoin-core-dev
1722019-02-15T03:23:32 *** AaronvanW has quit IRC
1732019-02-15T03:25:21 *** Karyon has quit IRC
1742019-02-15T03:46:51 *** ap4lmtree has joined #bitcoin-core-dev
1752019-02-15T03:52:56 *** Guest36088 has joined #bitcoin-core-dev
1762019-02-15T03:56:59 *** Guest36088 has quit IRC
1772019-02-15T04:26:21 *** hebasto has joined #bitcoin-core-dev
1782019-02-15T04:28:53 *** spinza has quit IRC
1792019-02-15T04:37:39 *** AaronvanW has joined #bitcoin-core-dev
1802019-02-15T04:39:52 *** spinza has joined #bitcoin-core-dev
1812019-02-15T04:40:59 *** hebasto has quit IRC
1822019-02-15T04:47:37 *** skyikot has quit IRC
1832019-02-15T05:01:25 *** schmidty has joined #bitcoin-core-dev
1842019-02-15T05:12:08 *** AaronvanW has quit IRC
1852019-02-15T05:40:19 *** DeanGuss has quit IRC
1862019-02-15T05:51:53 *** schmidty has quit IRC
1872019-02-15T05:59:08 *** stepa[m] has joined #bitcoin-core-dev
1882019-02-15T06:24:35 *** AaronvanW has joined #bitcoin-core-dev
1892019-02-15T06:40:22 *** pinheadmz has quit IRC
1902019-02-15T06:57:22 *** AaronvanW has quit IRC
1912019-02-15T07:05:01 *** DeanGuss has joined #bitcoin-core-dev
1922019-02-15T07:45:32 *** TheHoliestRoger has quit IRC
1932019-02-15T07:46:41 *** TheHoliestRoger has joined #bitcoin-core-dev
1942019-02-15T07:48:49 *** schmidty has joined #bitcoin-core-dev
1952019-02-15T08:09:48 *** Klox has quit IRC
1962019-02-15T08:10:30 *** Klox has joined #bitcoin-core-dev
1972019-02-15T08:29:49 *** jtimon has quit IRC
1982019-02-15T08:30:14 *** ap4lmtree has quit IRC
1992019-02-15T08:30:33 *** ap4lmtree has joined #bitcoin-core-dev
2002019-02-15T08:31:55 *** csknk has joined #bitcoin-core-dev
2012019-02-15T08:37:52 *** schmidty has quit IRC
2022019-02-15T08:51:58 *** ap4lmtree has quit IRC
2032019-02-15T08:54:40 *** AaronvanW has joined #bitcoin-core-dev
2042019-02-15T08:56:03 *** trillhc has quit IRC
2052019-02-15T08:58:40 *** booyah has quit IRC
2062019-02-15T08:59:02 *** booyah has joined #bitcoin-core-dev
2072019-02-15T09:01:11 *** ap4lmtree has joined #bitcoin-core-dev
2082019-02-15T09:28:09 *** AaronvanW has quit IRC
2092019-02-15T09:39:02 *** timothy has joined #bitcoin-core-dev
2102019-02-15T09:45:53 *** bitcoin-git has joined #bitcoin-core-dev
2112019-02-15T09:45:53 <bitcoin-git> [bitcoin] practicalswift opened pull request #15413: tests: Add missing cs_main locks required when accessing pcoinsdbview, pcoinsTip or pblocktree (master...validation-cs_main-tests) https://github.com/bitcoin/bitcoin/pull/15413
2122019-02-15T09:46:05 *** bitcoin-git has left #bitcoin-core-dev
2132019-02-15T10:02:05 *** bitcoin-git has joined #bitcoin-core-dev
2142019-02-15T10:02:05 <bitcoin-git> [bitcoin] Sjors opened pull request #15414: [wallet] allow adding pubkeys from imported private keys to keypool (master...2019/02/keypool_import_private_keys) https://github.com/bitcoin/bitcoin/pull/15414
2152019-02-15T10:02:06 *** bitcoin-git has left #bitcoin-core-dev
2162019-02-15T10:02:12 *** setpill has joined #bitcoin-core-dev
2172019-02-15T10:06:09 *** setpill has quit IRC
2182019-02-15T10:07:41 *** setpill has joined #bitcoin-core-dev
2192019-02-15T10:16:10 *** spinza has quit IRC
2202019-02-15T10:17:48 *** jungly has joined #bitcoin-core-dev
2212019-02-15T10:22:39 *** spinza has joined #bitcoin-core-dev
2222019-02-15T10:30:37 *** AaronvanW has joined #bitcoin-core-dev
2232019-02-15T10:34:18 *** schmidty has joined #bitcoin-core-dev
2242019-02-15T10:34:20 *** AaronvanW has quit IRC
2252019-02-15T10:34:37 *** AaronvanW has joined #bitcoin-core-dev
2262019-02-15T10:36:42 *** fanquake has joined #bitcoin-core-dev
2272019-02-15T10:39:35 *** promag has joined #bitcoin-core-dev
2282019-02-15T10:43:52 *** Zenton has joined #bitcoin-core-dev
2292019-02-15T10:45:25 *** phwalkr has joined #bitcoin-core-dev
2302019-02-15T10:49:01 <fanquake> jonasschnelli FYI, if the intention of the red & green squares in 15412 is to indicated working or not, you could also use :white_check_mark: & :negative_squared_cross_mark:.
2312019-02-15T10:49:29 <fanquake> The names are a bit verbose.., but GH should also autocomplete for you
2322019-02-15T10:54:16 *** Karyon has joined #bitcoin-core-dev
2332019-02-15T11:04:53 *** zhangzf has quit IRC
2342019-02-15T11:05:11 *** zhangzf has joined #bitcoin-core-dev
2352019-02-15T11:15:41 *** laurentmt has joined #bitcoin-core-dev
2362019-02-15T11:26:27 *** schmidty has quit IRC
2372019-02-15T11:28:02 *** rh0nj has quit IRC
2382019-02-15T11:29:09 *** rh0nj has joined #bitcoin-core-dev
2392019-02-15T11:37:21 *** schmidty has joined #bitcoin-core-dev
2402019-02-15T11:40:37 *** csknk has quit IRC
2412019-02-15T11:42:06 *** schmidty has quit IRC
2422019-02-15T11:44:43 *** Karyon has quit IRC
2432019-02-15T11:46:46 *** schmidty has joined #bitcoin-core-dev
2442019-02-15T11:51:18 *** schmidty has quit IRC
2452019-02-15T11:51:41 *** schmidty has joined #bitcoin-core-dev
2462019-02-15T11:52:22 *** emilr has quit IRC
2472019-02-15T12:00:22 *** bitcoin-git has joined #bitcoin-core-dev
2482019-02-15T12:00:22 <bitcoin-git> [bitcoin] Sjors opened pull request #15415: [test] functional: set node cwd to datadir (master...2019/02/test_cwd) https://github.com/bitcoin/bitcoin/pull/15415
2492019-02-15T12:00:23 *** bitcoin-git has left #bitcoin-core-dev
2502019-02-15T12:03:21 *** bitcoin-git has joined #bitcoin-core-dev
2512019-02-15T12:03:21 <bitcoin-git> [bitcoin] fanquake opened pull request #15416: doc: update FreeBSD build guide for 12.0 (master...docs-freebsd-120) https://github.com/bitcoin/bitcoin/pull/15416
2522019-02-15T12:03:23 *** bitcoin-git has left #bitcoin-core-dev
2532019-02-15T12:04:06 <fanquake> No more ancient GDB as of FreeBSD 12.0 \o/
2542019-02-15T12:14:11 *** emilr has joined #bitcoin-core-dev
2552019-02-15T12:17:07 *** bitcoin-git has joined #bitcoin-core-dev
2562019-02-15T12:17:07 <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/c576979b78b5...4d2767c2287e
2572019-02-15T12:17:07 <bitcoin-git> bitcoin/master 543ef7d practicalswift: tests: Add missing cs_main locks required when accessing pcoinsdbview, pco...
2582019-02-15T12:17:08 <bitcoin-git> bitcoin/master 4d2767c MarcoFalke: Merge #15413: tests: Add missing cs_main locks required when accessing pco...
2592019-02-15T12:17:12 *** bitcoin-git has left #bitcoin-core-dev
2602019-02-15T12:17:58 *** bitcoin-git has joined #bitcoin-core-dev
2612019-02-15T12:17:59 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #15413: tests: Add missing cs_main locks required when accessing pcoinsdbview, pcoinsTip or pblocktree (master...validation-cs_main-tests) https://github.com/bitcoin/bitcoin/pull/15413
2622019-02-15T12:18:00 *** bitcoin-git has left #bitcoin-core-dev
2632019-02-15T12:18:09 *** darosior has joined #bitcoin-core-dev
2642019-02-15T12:19:45 *** bitcoin-git has joined #bitcoin-core-dev
2652019-02-15T12:19:45 <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/4d2767c2287e...bf3677a6bb48
2662019-02-15T12:19:45 <bitcoin-git> bitcoin/master 88a91e2 Sjors Provoost: [build] AppVeyor: clean cache when build configuration changes
2672019-02-15T12:19:46 <bitcoin-git> bitcoin/master bf3677a MarcoFalke: Merge #15405: [build] AppVeyor: clean cache when build configuration chang...
2682019-02-15T12:19:57 *** bitcoin-git has left #bitcoin-core-dev
2692019-02-15T12:20:36 *** bitcoin-git has joined #bitcoin-core-dev
2702019-02-15T12:20:36 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #15405: [build] AppVeyor: clean cache when build configuration changes (master...2019/02/appveyor_cache) https://github.com/bitcoin/bitcoin/pull/15405
2712019-02-15T12:20:44 *** bitcoin-git has left #bitcoin-core-dev
2722019-02-15T12:32:25 *** schmidty has quit IRC
2732019-02-15T12:32:48 *** schmidty has joined #bitcoin-core-dev
2742019-02-15T12:37:09 *** schmidty has quit IRC
2752019-02-15T12:37:52 *** ali has joined #bitcoin-core-dev
2762019-02-15T12:38:15 *** ali is now known as Guest19016
2772019-02-15T12:38:44 *** schmidty has joined #bitcoin-core-dev
2782019-02-15T12:41:16 *** schmidty has quit IRC
2792019-02-15T12:41:49 *** schmidty has joined #bitcoin-core-dev
2802019-02-15T12:46:22 *** schmidty has quit IRC
2812019-02-15T12:47:06 *** schmidty has joined #bitcoin-core-dev
2822019-02-15T12:51:26 *** schmidty has quit IRC
2832019-02-15T12:52:16 *** schmidty has joined #bitcoin-core-dev
2842019-02-15T12:53:57 *** schmidty has quit IRC
2852019-02-15T12:56:26 *** promag has quit IRC
2862019-02-15T12:57:03 *** promag has joined #bitcoin-core-dev
2872019-02-15T13:01:24 *** promag has quit IRC
2882019-02-15T13:03:10 *** schmidty has joined #bitcoin-core-dev
2892019-02-15T13:07:38 *** schmidty has quit IRC
2902019-02-15T13:15:07 *** schmidty has joined #bitcoin-core-dev
2912019-02-15T13:16:33 *** Guest19016 has quit IRC
2922019-02-15T13:18:42 *** schmidty_ has joined #bitcoin-core-dev
2932019-02-15T13:18:47 *** schmidty has quit IRC
2942019-02-15T13:22:14 *** schmidty_ has quit IRC
2952019-02-15T13:22:47 *** schmidty has joined #bitcoin-core-dev
2962019-02-15T13:27:17 *** schmidty has quit IRC
2972019-02-15T13:31:33 *** schmidty has joined #bitcoin-core-dev
2982019-02-15T13:36:07 *** schmidty has quit IRC
2992019-02-15T13:40:46 *** schmidty has joined #bitcoin-core-dev
3002019-02-15T13:45:08 *** dermoth has quit IRC
3012019-02-15T13:45:21 *** schmidty has quit IRC
3022019-02-15T13:45:32 *** dermoth has joined #bitcoin-core-dev
3032019-02-15T13:48:07 *** mistergold has joined #bitcoin-core-dev
3042019-02-15T13:48:23 *** schmidty has joined #bitcoin-core-dev
3052019-02-15T13:52:01 <provoostenator> Re bech32: I find the "l" annoying, because my handwriting can't distinguish between 1 and l without significant effort.
3062019-02-15T13:53:21 *** schmidty has quit IRC
3072019-02-15T13:53:22 <belcher> could you write in capitals? L vs 1 is clearer
3082019-02-15T13:55:02 *** mistergo1d has joined #bitcoin-core-dev
3092019-02-15T13:55:58 *** schmidty has joined #bitcoin-core-dev
3102019-02-15T13:58:43 *** bitcoin-git has joined #bitcoin-core-dev
3112019-02-15T13:58:43 <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/bf3677a6bb48...eca1273c3500
3122019-02-15T13:58:43 <bitcoin-git> bitcoin/master fa178a6 MarcoFalke: [rpc] mining: Omit uninitialized currentblockweight, currentblocktx
3132019-02-15T13:58:44 <bitcoin-git> bitcoin/master eca1273 MarcoFalke: Merge #15383: [rpc] mining: Omit uninitialized currentblockweight, current...
3142019-02-15T13:58:56 *** bitcoin-git has left #bitcoin-core-dev
3152019-02-15T13:59:31 *** bitcoin-git has joined #bitcoin-core-dev
3162019-02-15T13:59:31 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #15383: [rpc] mining: Omit uninitialized currentblockweight, currentblocktx (master...Mf1902-rpcMining) https://github.com/bitcoin/bitcoin/pull/15383
3172019-02-15T13:59:36 *** bitcoin-git has left #bitcoin-core-dev
3182019-02-15T13:59:48 *** mistergold has quit IRC
3192019-02-15T14:00:38 *** schmidty has quit IRC
3202019-02-15T14:02:08 *** laurentmt has quit IRC
3212019-02-15T14:03:14 *** Karyon has joined #bitcoin-core-dev
3222019-02-15T14:03:29 *** schmidty has joined #bitcoin-core-dev
3232019-02-15T14:07:55 *** schmidty has quit IRC
3242019-02-15T14:08:49 *** schmidty has joined #bitcoin-core-dev
3252019-02-15T14:09:24 *** mistergold has joined #bitcoin-core-dev
3262019-02-15T14:12:05 *** schmidty_ has joined #bitcoin-core-dev
3272019-02-15T14:12:18 *** schmidty has quit IRC
3282019-02-15T14:12:58 *** mistergo1d has quit IRC
3292019-02-15T14:13:03 *** Aaronvan_ has joined #bitcoin-core-dev
3302019-02-15T14:16:05 *** schmidty has joined #bitcoin-core-dev
3312019-02-15T14:16:21 *** AaronvanW has quit IRC
3322019-02-15T14:17:02 *** schmidty_ has quit IRC
3332019-02-15T14:20:31 *** schmidty has quit IRC
3342019-02-15T14:21:47 *** schmidty has joined #bitcoin-core-dev
3352019-02-15T14:26:20 *** schmidty has quit IRC
3362019-02-15T14:28:13 *** schmidty has joined #bitcoin-core-dev
3372019-02-15T14:28:54 *** schmidty has quit IRC
3382019-02-15T14:30:41 *** schmidty has joined #bitcoin-core-dev
3392019-02-15T14:30:54 *** spinza has quit IRC
3402019-02-15T14:34:32 *** schmidty_ has joined #bitcoin-core-dev
3412019-02-15T14:35:26 *** schmidty has quit IRC
3422019-02-15T14:38:50 *** schmidty has joined #bitcoin-core-dev
3432019-02-15T14:39:21 *** schmidty_ has quit IRC
3442019-02-15T14:40:29 *** Guyver2 has joined #bitcoin-core-dev
3452019-02-15T14:42:49 *** bitcoin-git has joined #bitcoin-core-dev
3462019-02-15T14:42:50 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #15419: qa: Always refresh rotten cache to be out of ibd (master...Mf1902-mocktime) https://github.com/bitcoin/bitcoin/pull/15419
3472019-02-15T14:42:54 *** bitcoin-git has left #bitcoin-core-dev
3482019-02-15T14:43:30 *** schmidty has quit IRC
3492019-02-15T14:43:38 *** schmidty has joined #bitcoin-core-dev
3502019-02-15T14:45:54 *** schmidty has quit IRC
3512019-02-15T14:46:08 *** schmidty has joined #bitcoin-core-dev
3522019-02-15T14:50:36 *** schmidty has quit IRC
3532019-02-15T14:51:23 *** spinza has joined #bitcoin-core-dev
3542019-02-15T14:52:16 *** Karyon has quit IRC
3552019-02-15T14:54:09 *** schmidty has joined #bitcoin-core-dev
3562019-02-15T14:56:31 *** Karyon has joined #bitcoin-core-dev
3572019-02-15T14:56:40 *** schmidty has quit IRC
3582019-02-15T14:56:57 *** schmidty has joined #bitcoin-core-dev
3592019-02-15T15:02:51 <achow101> provoostenator: write your 1's like sipa does. they look like upside down v's
3602019-02-15T15:06:11 *** bitcoin-git has joined #bitcoin-core-dev
3612019-02-15T15:06:11 <bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/eca1273c3500...95801902b987
3622019-02-15T15:06:11 <bitcoin-git> bitcoin/master 7cee858 practicalswift: Add compile time verification of assumptions we're currently making implic...
3632019-02-15T15:06:12 <bitcoin-git> bitcoin/master 9580190 Wladimir J. van der Laan: Merge #15391: Add compile time verification of assumptions we're currently...
3642019-02-15T15:06:13 *** bitcoin-git has left #bitcoin-core-dev
3652019-02-15T15:07:04 *** bitcoin-git has joined #bitcoin-core-dev
3662019-02-15T15:07:05 <bitcoin-git> [bitcoin] laanwj merged pull request #15391: Add compile time verification of assumptions we're currently making implicitly/tacitly (master...assumptions) https://github.com/bitcoin/bitcoin/pull/15391
3672019-02-15T15:07:13 *** bitcoin-git has left #bitcoin-core-dev
3682019-02-15T15:09:57 *** mistergo1d has joined #bitcoin-core-dev
3692019-02-15T15:13:01 *** mistergold has quit IRC
3702019-02-15T15:26:59 *** promag has joined #bitcoin-core-dev
3712019-02-15T15:28:28 <wumpus> PSA: dev.visucore.com will be offline for a while (transferring service to a new domai)
3722019-02-15T15:28:32 <wumpus> new server*
3732019-02-15T15:31:53 <promag> provoostenator: just rebased #15204
3742019-02-15T15:31:55 <gribble> https://github.com/bitcoin/bitcoin/issues/15204 | gui: Add Open External Wallet action by promag · Pull Request #15204 · bitcoin/bitcoin · GitHub
3752019-02-15T15:32:40 <promag> first commit is almost move-only
3762019-02-15T15:39:59 *** Aaronvan_ is now known as AaronvanW
3772019-02-15T15:41:07 *** Karyon has quit IRC
3782019-02-15T15:41:10 <fanquake> wumpus will it be running on a RISC-V pc :p
3792019-02-15T15:44:30 *** cubancorona has quit IRC
3802019-02-15T15:57:39 <wumpus> fanquake: no :-) another x86_64 server unfortunately
3812019-02-15T15:58:59 <wumpus> 1U risc-v servers would be pretty awesome, but given how hard it still is to get decent ARM servers I'm not holding my breath
3822019-02-15T16:07:06 *** setpill has quit IRC
3832019-02-15T16:07:52 *** jtimon has joined #bitcoin-core-dev
3842019-02-15T16:11:59 *** promag_ has joined #bitcoin-core-dev
3852019-02-15T16:15:21 *** jarthur has quit IRC
3862019-02-15T16:17:30 *** mistergo1d has quit IRC
3872019-02-15T16:26:53 *** hebasto has joined #bitcoin-core-dev
3882019-02-15T16:27:51 <wumpus> https://www.reddit.com/r/RISCV/comments/8lq97j/riscv_server_cpus_when/ I don't think anyone knows either
3892019-02-15T16:28:40 <wumpus> achow101: the travis error in #13932 is strange
3902019-02-15T16:28:43 <gribble> https://github.com/bitcoin/bitcoin/issues/13932 | Additional utility RPCs for PSBT by achow101 · Pull Request #13932 · bitcoin/bitcoin · GitHub
3912019-02-15T16:30:01 <wumpus> I don't understand why it could not be finding the test_bitcoin executable
3922019-02-15T16:30:44 <luke-jr> wumpus: POWER servers aren't so hard to get
3932019-02-15T16:31:11 <wumpus> luke-jr: yes they certainly are ahead there
3942019-02-15T16:32:49 <achow101> wumpus: maybe it wasn't compiled?
3952019-02-15T16:33:38 <achow101> i don't see a cxxld line for test/test_bitcoin
3962019-02-15T16:34:55 <midnightmagic> oo 1U RISCV servers?
3972019-02-15T16:34:59 <wumpus> I tried restarting that build but it ran into the same problem
3982019-02-15T16:35:06 <wumpus> midnightmagic: if only
3992019-02-15T16:35:07 <midnightmagic> HiFive runs ECC ram doesn't it?
4002019-02-15T16:35:15 *** mildly_risky has joined #bitcoin-core-dev
4012019-02-15T16:35:44 <midnightmagic> you might get away with embedding an unleashed into a 1U :-D but the addon board isn't available anymore
4022019-02-15T16:36:11 <luke-jr> wumpus: also ahead in freedom ;)
4032019-02-15T16:36:31 <achow101> wumpus: that's weird. maybe i need to rebase
4042019-02-15T16:37:11 <cjd> 16:34 < midnightmagic> oo 1U RISCV servers? <-- srsly ? link ?
4052019-02-15T16:37:18 *** mildly_risky has quit IRC
4062019-02-15T16:37:21 <midnightmagic> luke-jr: How so again? I think the HiFive board after the firmware deterministic build contest is all open isn't it?
4072019-02-15T16:37:27 <midnightmagic> cjd: :-) hah funny
4082019-02-15T16:37:31 *** Murch has joined #bitcoin-core-dev
4092019-02-15T16:37:59 <luke-jr> midnightmagic: doesn't it require non-free memory controller stuff?
4102019-02-15T16:38:11 <cjd> :D
4112019-02-15T16:39:23 *** mildly_risky has joined #bitcoin-core-dev
4122019-02-15T16:40:29 *** owowo has quit IRC
4132019-02-15T16:41:49 <midnightmagic> luke-jr: the dram controller. I read an update on that somewhere, I think as part of the firmware contest update/winner announcement. hang on I'm having trouble finding it.
4142019-02-15T16:45:53 *** owowo has joined #bitcoin-core-dev
4152019-02-15T16:48:41 *** zhangzf has joined #bitcoin-core-dev
4162019-02-15T16:50:51 *** promag_ has quit IRC
4172019-02-15T16:52:00 <midnightmagic> luke-jr: https://www.sifive.com/blog/an-open-source-release-of-the-freedom-u540-c000s-bootloader "There's been a lot of interest in the beta program, but now that the DDR code is public it's a good time to start in earnest porting bootloaders, so we'll try to find a way to give you a board!"
4182019-02-15T16:52:02 *** promag_ has joined #bitcoin-core-dev
4192019-02-15T16:52:05 *** jarthur has joined #bitcoin-core-dev
4202019-02-15T16:53:32 <midnightmagic> luke-jr: I think that's all of it?
4212019-02-15T16:54:51 *** echonaut has quit IRC
4222019-02-15T16:55:18 *** echonaut has joined #bitcoin-core-dev
4232019-02-15T16:56:11 *** promag_ has quit IRC
4242019-02-15T16:56:15 <midnightmagic> luke-jr: so I think atm without open-source firmware for the SAS chip (for those that have it onboard) and.. mm.. the ethernet controller (which I think is being worked on) and of course the default chassis they ship with, I think the risc-v people might have pulled slightly ahead in the FOSS race. I could be wrong.
4252019-02-15T16:56:41 *** promag_ has joined #bitcoin-core-dev
4262019-02-15T16:57:57 *** promag has quit IRC
4272019-02-15T16:58:13 *** phwalkr has quit IRC
4282019-02-15T16:58:40 <luke-jr> cool
4292019-02-15T16:59:11 *** schmidty has quit IRC
4302019-02-15T17:00:04 *** mildly_risky has quit IRC
4312019-02-15T17:00:34 *** zhangzf has quit IRC
4322019-02-15T17:00:41 *** schmidty has joined #bitcoin-core-dev
4332019-02-15T17:01:11 *** pinheadmz has joined #bitcoin-core-dev
4342019-02-15T17:02:46 *** schmidty has quit IRC
4352019-02-15T17:02:57 *** schmidty has joined #bitcoin-core-dev
4362019-02-15T17:03:56 *** echonaut has quit IRC
4372019-02-15T17:04:13 *** echonaut has joined #bitcoin-core-dev
4382019-02-15T17:07:42 *** schmidty has quit IRC
4392019-02-15T17:08:48 *** jungly has quit IRC
4402019-02-15T17:09:11 *** schmidty has joined #bitcoin-core-dev
4412019-02-15T17:11:59 *** schmidty_ has joined #bitcoin-core-dev
4422019-02-15T17:13:48 *** schmidty has quit IRC
4432019-02-15T17:17:06 *** schmidty_ has quit IRC
4442019-02-15T17:19:39 *** schmidty has joined #bitcoin-core-dev
4452019-02-15T17:20:53 *** Zenton has quit IRC
4462019-02-15T17:21:55 *** schmidty has quit IRC
4472019-02-15T17:22:11 *** schmidty has joined #bitcoin-core-dev
4482019-02-15T17:25:51 *** hebasto has quit IRC
4492019-02-15T17:30:27 *** mistergold has joined #bitcoin-core-dev
4502019-02-15T17:32:38 *** timothy has quit IRC
4512019-02-15T17:39:37 *** mistergo1d has joined #bitcoin-core-dev
4522019-02-15T17:41:34 *** mistergold has quit IRC
4532019-02-15T17:49:11 *** millerti has joined #bitcoin-core-dev
4542019-02-15T17:49:47 <luke-jr> whoa, RISC-V has fallen in price a lot :o https://hackaday.com/2019/02/14/new-part-day-a-risc-v-cpu-for-eight-dollars/
4552019-02-15T17:55:27 <luke-jr> only 8 MB RAM, so i guess it isn't going to run a node any time soon
4562019-02-15T17:57:05 <wumpus> huhh whoa gotta have one
4572019-02-15T17:58:27 <MarcoFalke> heh, the travis failure is due to a bug on their side (travis.yaml is taken from the branch, not from master)
4582019-02-15T17:58:39 <MarcoFalke> Only way to solve that is by close-open
4592019-02-15T17:59:00 *** bitcoin-git has joined #bitcoin-core-dev
4602019-02-15T17:59:00 <bitcoin-git> [bitcoin] MarcoFalke closed pull request #13932: Additional utility RPCs for PSBT (master...psbt-util-rpcs) https://github.com/bitcoin/bitcoin/pull/13932
4612019-02-15T17:59:01 *** bitcoin-git has left #bitcoin-core-dev
4622019-02-15T17:59:09 <MarcoFalke> fingers crossed
4632019-02-15T17:59:13 <wumpus> :o
4642019-02-15T17:59:17 *** bitcoin-git has joined #bitcoin-core-dev
4652019-02-15T17:59:18 <bitcoin-git> [bitcoin] MarcoFalke reopened pull request #13932: Additional utility RPCs for PSBT (master...psbt-util-rpcs) https://github.com/bitcoin/bitcoin/pull/13932
4662019-02-15T17:59:24 *** bitcoin-git has left #bitcoin-core-dev
4672019-02-15T18:00:42 <MarcoFalke> (The fuzzer won't build any binaries other than the fuzzers, so the test_bitcoin was missing)
4682019-02-15T18:00:54 <MarcoFalke> *fuzzer travis job
4692019-02-15T18:03:53 *** promag has joined #bitcoin-core-dev
4702019-02-15T18:08:12 *** promag has quit IRC
4712019-02-15T18:09:59 *** JackH has joined #bitcoin-core-dev
4722019-02-15T18:11:21 *** mistergo1d has quit IRC
4732019-02-15T18:12:16 *** mistergold has joined #bitcoin-core-dev
4742019-02-15T18:12:24 *** mistergo1d has joined #bitcoin-core-dev
4752019-02-15T18:15:24 *** bitcoin-git has joined #bitcoin-core-dev
4762019-02-15T18:15:25 <bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/95801902b987...743c2f461c0e
4772019-02-15T18:15:26 <bitcoin-git> bitcoin/master fabcfa5 MarcoFalke: fuzz: Move deserialize tests to test/fuzz/deserialize.cpp
4782019-02-15T18:15:26 <bitcoin-git> bitcoin/master fab15ff MarcoFalke: fuzz: Script validation flags
4792019-02-15T18:15:26 <bitcoin-git> bitcoin/master 743c2f4 MarcoFalke: Merge #15399: fuzz: Script validation flags
4802019-02-15T18:15:28 *** bitcoin-git has left #bitcoin-core-dev
4812019-02-15T18:15:40 <achow101> MarcoFalke: wouldn't it pick up an updated travis.yml from a rebase? or does it use the one from the time the pr was opened?
4822019-02-15T18:16:08 <MarcoFalke> Rebase also does it, but I wasn't sure if the pull was reviewed already
4832019-02-15T18:16:13 *** bitcoin-git has joined #bitcoin-core-dev
4842019-02-15T18:16:13 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #15399: fuzz: Script validation flags (master...Mf1902-fuzzSoft) https://github.com/bitcoin/bitcoin/pull/15399
4852019-02-15T18:16:18 *** bitcoin-git has left #bitcoin-core-dev
4862019-02-15T18:16:50 <MarcoFalke> Or generally a push would do it as well
4872019-02-15T18:18:14 <achow101> the latest version hadn't gotten reviewed yet so I was gonna rebase it when I got home later
4882019-02-15T18:18:29 <achow101> but if close-reopen works, then i'll just leave it as is
4892019-02-15T18:18:49 <MarcoFalke> Yeah, I hope that fixed it already
4902019-02-15T18:21:48 *** mistergo2d has joined #bitcoin-core-dev
4912019-02-15T18:41:11 *** DeanGuss has quit IRC
4922019-02-15T18:48:44 *** promag has joined #bitcoin-core-dev
4932019-02-15T18:49:48 *** promag_ has joined #bitcoin-core-dev
4942019-02-15T18:53:03 *** promag has quit IRC
4952019-02-15T18:54:07 *** promag_ has quit IRC
4962019-02-15T19:04:45 *** mmgen has joined #bitcoin-core-dev
4972019-02-15T19:05:09 *** promag has joined #bitcoin-core-dev
4982019-02-15T19:12:50 *** promag has quit IRC
4992019-02-15T19:18:00 *** promag has joined #bitcoin-core-dev
5002019-02-15T19:21:02 *** rh0nj has quit IRC
5012019-02-15T19:24:08 *** rh0nj has joined #bitcoin-core-dev
5022019-02-15T19:27:45 *** Zenton has joined #bitcoin-core-dev
5032019-02-15T19:42:27 *** darosior has quit IRC
5042019-02-15T19:56:16 *** promag has quit IRC
5052019-02-15T20:00:17 <wumpus> travis on #13932 passed now, appveyor takes a long time but that wasn't a problem
5062019-02-15T20:00:20 <gribble> https://github.com/bitcoin/bitcoin/issues/13932 | Additional utility RPCs for PSBT by achow101 · Pull Request #13932 · bitcoin/bitcoin · GitHub
5072019-02-15T20:00:35 <achow101> yay
5082019-02-15T20:25:30 *** promag has joined #bitcoin-core-dev
5092019-02-15T20:31:07 *** promag has quit IRC
5102019-02-15T20:33:38 *** DeanGuss has joined #bitcoin-core-dev
5112019-02-15T20:37:13 *** mistergo3d has joined #bitcoin-core-dev
5122019-02-15T20:37:14 *** mistergo4d has joined #bitcoin-core-dev
5132019-02-15T20:37:16 *** mistergo5d has joined #bitcoin-core-dev
5142019-02-15T20:40:47 *** mistergo2d has quit IRC
5152019-02-15T20:40:47 *** mistergold has quit IRC
5162019-02-15T20:41:13 *** mistergo1d has quit IRC
5172019-02-15T20:43:55 *** mistergo1d has joined #bitcoin-core-dev
5182019-02-15T20:43:55 *** mistergold has joined #bitcoin-core-dev
5192019-02-15T20:44:04 *** mistergo2d has joined #bitcoin-core-dev
5202019-02-15T20:44:30 *** mmgen has quit IRC
5212019-02-15T20:46:47 *** mistergo4d has quit IRC
5222019-02-15T20:47:07 *** mistergo5d has quit IRC
5232019-02-15T20:47:40 *** mistergo3d has quit IRC
5242019-02-15T20:51:44 *** drexl has quit IRC
5252019-02-15T20:52:46 *** dgenr8 has quit IRC
5262019-02-15T20:58:00 *** promag has joined #bitcoin-core-dev
5272019-02-15T21:02:24 <wumpus> ok https://dev.visucore.com/bitcoin/doxygen/ is back !
5282019-02-15T21:02:24 *** promag has quit IRC
5292019-02-15T21:03:11 <sipa> my dns seed is also back (was down for a few days)
5302019-02-15T21:10:52 <wumpus> sipa: great!
5312019-02-15T21:11:15 <wumpus> also made it update the version, apparently it was stuck at showing 0.15.99 (even though it was regenerating the docs from the correct branch)
5322019-02-15T21:11:36 *** bitcoin-git has joined #bitcoin-core-dev
5332019-02-15T21:11:37 <bitcoin-git> [bitcoin] luke-jr closed pull request #11803: Bugfix: RPC/Wallet: Include HD key metadata in dumpwallet (master...bugfix_dumpwallet_hdkeypath) https://github.com/bitcoin/bitcoin/pull/11803
5342019-02-15T21:11:38 *** bitcoin-git has left #bitcoin-core-dev
5352019-02-15T21:13:11 <gmaxwell> oh, should I (or someone) make a PR moving forward assumevalid / chainwork now? It seems like we forget to do that, because it really needs to be done at release-candidate minus two weeks or so.
5362019-02-15T21:17:55 <meshcollider> provoostenator: re https://github.com/bitcoin/bitcoin/pull/11803#issuecomment-464082302 I'm not sure the same thing Luke was changing has been done?
5372019-02-15T21:18:04 *** nullptr| has quit IRC
5382019-02-15T21:18:14 <meshcollider> I.e. the key metadata hasn't been moved out of the "comment" section
5392019-02-15T21:18:50 *** bitcoin-git has joined #bitcoin-core-dev
5402019-02-15T21:18:51 <bitcoin-git> [bitcoin] luke-jr opened pull request #15421: torcontrol: Launch a private Tor instance when not already running (master...tor_subprocess) https://github.com/bitcoin/bitcoin/pull/15421
5412019-02-15T21:18:55 *** bitcoin-git has left #bitcoin-core-dev
5422019-02-15T21:19:06 *** nullptr| has joined #bitcoin-core-dev
5432019-02-15T21:19:27 *** Karyon has joined #bitcoin-core-dev
5442019-02-15T21:22:39 *** AaronvanW has quit IRC
5452019-02-15T21:22:41 *** DeanGuss has quit IRC
5462019-02-15T21:33:19 *** AaronvanW has joined #bitcoin-core-dev
5472019-02-15T21:37:56 *** AaronvanW has quit IRC
5482019-02-15T21:42:02 <luke-jr> provoostenator: ^ are you already working on boost::process detection?
5492019-02-15T21:52:45 *** Karyon_ has joined #bitcoin-core-dev
5502019-02-15T21:52:45 *** Karyon has quit IRC
5512019-02-15T21:54:44 *** mistergo3d has joined #bitcoin-core-dev
5522019-02-15T21:54:45 *** mistergo4d has joined #bitcoin-core-dev
5532019-02-15T21:54:46 *** mistergo5d has joined #bitcoin-core-dev
5542019-02-15T21:57:58 *** mistergo2d has quit IRC
5552019-02-15T21:58:33 *** mistergo1d has quit IRC
5562019-02-15T21:58:33 *** mistergold has quit IRC
5572019-02-15T21:58:33 *** Skirmant has quit IRC
5582019-02-15T22:10:48 *** AaronvanW has joined #bitcoin-core-dev
5592019-02-15T22:15:12 *** AaronvanW has quit IRC
5602019-02-15T22:15:32 *** tenni has joined #bitcoin-core-dev
5612019-02-15T22:16:23 <tenni> anyone awake in here?
5622019-02-15T22:16:30 *** mistergo1d has joined #bitcoin-core-dev
5632019-02-15T22:16:30 *** mistergold has joined #bitcoin-core-dev
5642019-02-15T22:16:31 *** mistergo2d has joined #bitcoin-core-dev
5652019-02-15T22:16:40 <sipa> no
5662019-02-15T22:16:54 <tenni> looks like that
5672019-02-15T22:19:38 *** mistergo4d has quit IRC
5682019-02-15T22:19:38 *** mistergo3d has quit IRC
5692019-02-15T22:20:03 *** mistergo5d has quit IRC
5702019-02-15T22:21:04 *** tenni has left #bitcoin-core-dev
5712019-02-15T22:46:15 *** spinza has quit IRC
5722019-02-15T22:50:39 *** AaronvanW has joined #bitcoin-core-dev
5732019-02-15T22:52:34 *** owowo has quit IRC
5742019-02-15T22:57:31 *** owowo has joined #bitcoin-core-dev
5752019-02-15T23:04:55 *** Karyon_ has quit IRC
5762019-02-15T23:05:28 *** spinza has joined #bitcoin-core-dev
5772019-02-15T23:05:40 *** kexkey has joined #bitcoin-core-dev
5782019-02-15T23:13:58 *** jtimon has quit IRC
5792019-02-15T23:25:00 *** AaronvanW has quit IRC