12018-05-22T00:00:12 *** Victorsueca has quit IRC
22018-05-22T00:01:25 *** justan0theruser has quit IRC
32018-05-22T00:01:26 *** justanotheruser has joined #bitcoin-core-dev
42018-05-22T00:01:28 *** Victorsueca has joined #bitcoin-core-dev
52018-05-22T00:11:54 *** nman999_ has quit IRC
62018-05-22T00:14:02 *** cryptojanitor has joined #bitcoin-core-dev
72018-05-22T00:21:01 *** sipa has quit IRC
82018-05-22T00:21:01 *** sipa has joined #bitcoin-core-dev
92018-05-22T00:23:49 *** satwo has quit IRC
102018-05-22T00:30:56 *** honeybadgerdgaf has joined #bitcoin-core-dev
112018-05-22T00:40:45 *** drexl has quit IRC
122018-05-22T00:51:55 *** Randolf has quit IRC
132018-05-22T00:53:42 *** Randolf has joined #bitcoin-core-dev
142018-05-22T00:54:38 *** Randolf has quit IRC
152018-05-22T00:55:56 *** Randolf has joined #bitcoin-core-dev
162018-05-22T01:04:24 *** contrapumpkin has joined #bitcoin-core-dev
172018-05-22T01:28:59 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #13300: qa: Initialize lockstack to prevent null pointer deref (master...Mf1805-qaLockDebug) https://github.com/bitcoin/bitcoin/pull/13300
182018-05-22T01:40:58 <kallewoof> Is it just me, or didn't bitcoind use to write to debug.log even with -printtoconsole=0?
192018-05-22T01:41:26 <kallewoof> Running tests now doesn't create a debug.log file at all. Unless it was moved somewhere outside of -datadir...
202018-05-22T01:41:54 <kallewoof> Oh wait, nevermind, it was in regtest/.
212018-05-22T01:58:18 *** honeybadgerdgaf has quit IRC
222018-05-22T02:00:15 *** honeybadgerdgaf has joined #bitcoin-core-dev
232018-05-22T02:01:25 *** honeybadgerdgaf has quit IRC
242018-05-22T02:28:07 *** Randolf has quit IRC
252018-05-22T02:29:02 *** Randolf has joined #bitcoin-core-dev
262018-05-22T02:43:06 *** honeybadgerdgaf has joined #bitcoin-core-dev
272018-05-22T02:45:19 *** Krellan has quit IRC
282018-05-22T02:57:25 *** honeybadgerdgaf has quit IRC
292018-05-22T03:23:03 <bitcoin-git> [bitcoin] Empact opened pull request #13301: lint: Add linter to error on #include <*.cpp> (master...lint-include-cpp) https://github.com/bitcoin/bitcoin/pull/13301
302018-05-22T03:42:00 *** honeybadgerdgaf has joined #bitcoin-core-dev
312018-05-22T03:47:32 *** rex4539 has joined #bitcoin-core-dev
322018-05-22T03:56:01 *** glaksmono has joined #bitcoin-core-dev
332018-05-22T03:57:17 *** glaksmon_ has joined #bitcoin-core-dev
342018-05-22T04:00:12 *** glaksmono has quit IRC
352018-05-22T04:12:21 *** glaksmon_ has quit IRC
362018-05-22T04:12:53 *** glaksmono has joined #bitcoin-core-dev
372018-05-22T04:17:26 *** glaksmono has quit IRC
382018-05-22T04:26:48 *** honeybadgerdgaf has quit IRC
392018-05-22T04:28:30 *** rex4539 has quit IRC
402018-05-22T04:29:07 *** rex4539 has joined #bitcoin-core-dev
412018-05-22T04:34:11 *** glaksmono has joined #bitcoin-core-dev
422018-05-22T04:35:48 *** honeybadgerdgaf has joined #bitcoin-core-dev
432018-05-22T04:38:53 *** honeybadgerdgaf has quit IRC
442018-05-22T04:39:36 *** satwo has joined #bitcoin-core-dev
452018-05-22T04:43:41 *** honeybadgerdgaf has joined #bitcoin-core-dev
462018-05-22T04:58:39 *** Victorsueca has quit IRC
472018-05-22T04:59:57 *** Victorsueca has joined #bitcoin-core-dev
482018-05-22T05:05:50 *** satwo has quit IRC
492018-05-22T05:14:36 *** glaksmono has quit IRC
502018-05-22T05:21:09 *** glaksmono has joined #bitcoin-core-dev
512018-05-22T05:23:36 *** cryptojanitor has quit IRC
522018-05-22T05:25:33 *** glaksmono has quit IRC
532018-05-22T05:28:12 *** honeybadgerdgaf has quit IRC
542018-05-22T05:30:58 *** tripleslash has quit IRC
552018-05-22T05:36:11 *** setpill has quit IRC
562018-05-22T05:37:14 *** tripleslash has joined #bitcoin-core-dev
572018-05-22T05:51:55 *** Giszmo has quit IRC
582018-05-22T05:58:42 *** glaksmono has joined #bitcoin-core-dev
592018-05-22T05:59:07 *** glaksmono has joined #bitcoin-core-dev
602018-05-22T06:10:08 *** Giszmo has joined #bitcoin-core-dev
612018-05-22T06:12:39 *** glaksmono has quit IRC
622018-05-22T06:27:28 *** DougieBot5000_ has joined #bitcoin-core-dev
632018-05-22T06:30:40 *** DougieBot5000 has quit IRC
642018-05-22T06:45:57 *** glaksmono has joined #bitcoin-core-dev
652018-05-22T06:47:13 *** Krellan has joined #bitcoin-core-dev
662018-05-22T06:49:26 *** fanquake has joined #bitcoin-core-dev
672018-05-22T06:50:28 <fanquake> Chris_Stewart_5 Looks like you need to swap to using posix threads
682018-05-22T06:50:31 <fanquake> sudo update-alternatives --config x86_64-w64-mingw32-g++
692018-05-22T06:50:43 <fanquake> From memory you need to pick option (1)
702018-05-22T06:51:30 *** JackH has quit IRC
712018-05-22T06:51:54 *** Krellan has quit IRC
722018-05-22T06:52:00 <fanquake> Also, if your not using Ubuntu 18.04, which recently became available in the Windows Store, I'd suggest swapping to that. We have a WIP PR #13246, with simplified build instructions.
732018-05-22T06:52:03 <gribble> https://github.com/bitcoin/bitcoin/issues/13246 | doc: Bump to Ubuntu Bionic 18.04 in build-windows.md by ken2812221 · Pull Request #13246 · bitcoin/bitcoin · GitHub
742018-05-22T06:54:50 *** MisterPaz has quit IRC
752018-05-22T06:58:37 *** MrPaz has joined #bitcoin-core-dev
762018-05-22T07:03:49 *** JackH has joined #bitcoin-core-dev
772018-05-22T07:07:55 <jonasschnelli> sipa: we once talked about a similar error correction format (more tolerant) for private keys/seeds. Are you still exploring that field?
782018-05-22T07:08:03 <jonasschnelli> (similar to bech32)
792018-05-22T07:08:12 <sipa> i haven't followed up on that
802018-05-22T07:08:41 <sipa> but i can send a mail with the possible trade-offs or os
812018-05-22T07:08:48 <jonasschnelli> sipa: Do you think it makes sense to introduce a bip32 equivalent for xpriv in bech32 with seed birthday?
822018-05-22T07:10:39 <sipa> jonasschnelli: i don't think that the path of trying to encode all of the possible metadata around a key and derivation paths into one string is feasible
832018-05-22T07:10:41 <jonasschnelli> I guess there is a lot of blockchain scans (bandwidth and CPU consumption) due to the fact that seeds have no birthday
842018-05-22T07:10:46 <sipa> perhaps birthdate can be added
852018-05-22T07:11:01 <sipa> but what about subranges
862018-05-22T07:11:08 <jonasschnelli> subranges?
872018-05-22T07:11:14 <sipa> or whether hardened or nonhardened derivation is supposed to be used
882018-05-22T07:11:28 <sipa> or if it's a multisig key, the other chains to combine it with
892018-05-22T07:11:48 <luke-jr> there's too many possible variants to even try to include it IMO
902018-05-22T07:11:59 <gmaxwell> even just versioning so such things could be added later in a compatible way...
912018-05-22T07:12:00 <sipa> or if it's a nonstandard script, do you include some template into the string too?
922018-05-22T07:12:20 <gmaxwell> luke-jr: there is a subset which is much easier, known needed, etc.
932018-05-22T07:12:54 <jonasschnelli> Yes. Maybe a version bit and a birthday is a way to start. Other metadata is also interesting but birthday is most imortant and uses almost no bytes.
942018-05-22T07:12:54 <luke-jr> perhaps just an generic id field of some sort that can include a wallet format/name
952018-05-22T07:13:10 <gmaxwell> e.g. we _know_ a birth epoch is very useful, virtually always.
962018-05-22T07:13:29 <gmaxwell> it would be kinda sad to omit that just because we're not sure on all the other fields we might want to include. :)
972018-05-22T07:13:31 <luke-jr> I'm certainly not arguing against birth epoch
982018-05-22T07:13:45 <jonasschnelli> I'd say the birthday week from 2009-01-01 would be sufficient
992018-05-22T07:14:05 <sipa> to me, eventually these things will be some standard json like description of keys/addresses/templating/...
1002018-05-22T07:14:21 <luke-jr> jonasschnelli: year+week might be easier to handle in code
1012018-05-22T07:14:35 <sipa> and there may be "optimizations" to it which e.g. pack the private key into the same string as the derivation path (like xprv)
1022018-05-22T07:14:40 <gmaxwell> jonasschnelli: I think there was some list post where I gave some figures on resoltion vs size tradeoff.
1032018-05-22T07:14:47 <sipa> and perhaps pack the derivation type along with it (bip 158)
1042018-05-22T07:14:53 <sipa> and perhaps the date/time too
1052018-05-22T07:15:05 <jonasschnelli> gmaxwell: Okay. I'll search for it
1062018-05-22T07:15:28 <gmaxwell> luke-jr: (datetime-spec_provided_offset)/number_of_seconds_in_a_week -- it's trivial
1072018-05-22T07:15:29 <sipa> but i don't like the current thinking... which is essentially that the private key "string" is all you have
1082018-05-22T07:15:39 <sipa> and that everything *must* be inside of it, or it doesn't exist
1092018-05-22T07:15:44 <gmaxwell> sipa: that does reflect common backup practices.
1102018-05-22T07:16:24 <luke-jr> sipa: agreed
1112018-05-22T07:16:45 <sipa> well it could be a single string still - but not all of it needs to be encoded into an opaque blob
1122018-05-22T07:16:56 <sipa> you could have something URI like that adds extra data
1132018-05-22T07:17:18 <gmaxwell> I cerantly agree with your on that point though-- some things like metadata about your txn _cannot_ be encoded in any string set upfront regardless of how long it is... and that data can be pretty critical.
1142018-05-22T07:17:21 <jonasschnelli> I guess one of the problems is, that users have the idea with 24 words they have a complete backup.
1152018-05-22T07:17:34 <sipa> that's just silly
1162018-05-22T07:17:47 <jonasschnelli> But it is sadly the reality...
1172018-05-22T07:17:52 <sipa> there's not even a way to have an version number in it
1182018-05-22T07:17:56 <gmaxwell> it's also what e.g. electrum and basically claims.
1192018-05-22T07:17:58 <luke-jr> jonasschnelli: we don't have to encourage bad ideas
1202018-05-22T07:18:33 <gmaxwell> (I mean claims as a feature)
1212018-05-22T07:18:43 <sipa> jonasschnelli: well, i think what i'm thinking is a lower level than a whole wallet
1222018-05-22T07:18:47 <jonasschnelli> The Bitbox approach to backup to an SDCard seems to be accepted but people still prefer to "write down words to a paper" for backup.
1232018-05-22T07:19:25 <gmaxwell> Not just to a paper, it's relatively easy to make a fire durable backup of a short string.
1242018-05-22T07:19:31 <luke-jr> ideally, one would have metadata fully encrypted with a key derived from the seed, and automatically make remote backups of the metadata
1252018-05-22T07:20:00 <luke-jr> then one can use the seed to recover the full metadata, assuming it's widely backed up
1262018-05-22T07:21:12 <gmaxwell> right I think a better model in general would be some nice integration where your seed also lets you derrive and ID and encryption key for an encrypted backup that could be stored insecurely... and it would have all that metadata other than the most limited needed for a recovery.
1272018-05-22T07:21:50 <gmaxwell> and enough data so that if your metadata is lost it's still possible to recover things, though perhaps expensive.
1282018-05-22T07:22:27 <sipa> see the "future design" section here: https://gist.github.com/sipa/125cfa1615946d0c3f3eec2ad7f250a2
1292018-05-22T07:22:30 <gmaxwell> such a process would let backups store things like transaction notes and whatnot that could never be captured otherwise.
1302018-05-22T07:22:47 <sipa> that's effectively all the non-volatile metadata you need to describe a (part of) a wallet
1312018-05-22T07:22:52 <gmaxwell> and would still let users have a short key to stick in a fire safe.
1322018-05-22T07:28:00 *** Ishtv4n has joined #bitcoin-core-dev
1332018-05-22T07:28:20 <gmaxwell> in any case if "store the metadata elsewhere" were the path, basically the seed would only need versioning and maybe a hint about the kind of derrivation paths that were used.
1342018-05-22T07:28:56 <gmaxwell> sipa: one thing that isn't included in your lists, is that user really often want to protect their seeds with passwords, and doing that potentially has some overheads.
1352018-05-22T07:29:03 <luke-jr> well, so long as you can derive the backup key(s), you can put the rest of the derivation in the metadata
1362018-05-22T07:29:14 <gmaxwell> (alternatively or inaddition to they want to do secret sharing.)
1372018-05-22T07:29:17 *** str4d has joined #bitcoin-core-dev
1382018-05-22T07:29:44 <sipa> gmaxwell: well this is just describing the part that it's inside the wallet; not how it is to be encoded for exporting/importing
1392018-05-22T07:29:54 <gmaxwell> luke-jr: I think the idea I was thinking about there would still admit recovery from only the seed but perhaps only in a very costly manner, e.g. lots of brute force path searching or forensics to figure out what software you used.
1402018-05-22T07:30:02 *** d9b4bef9 has quit IRC
1412018-05-22T07:30:17 <gmaxwell> sipa: I know, just pointing that serializing that stuff still probably isn't enough.
1422018-05-22T07:30:50 <sipa> well this doesn't describe seeds at all
1432018-05-22T07:31:12 *** d9b4bef9 has joined #bitcoin-core-dev
1442018-05-22T07:31:13 <sipa> if you want a seed, you'll have some short string and a determinstic way to derive all of this from it
1452018-05-22T07:31:13 <gmaxwell> yep not faulting your document.
1462018-05-22T07:31:32 <sipa> but i don't expect an ability to encode a seed _from_ that data
1472018-05-22T07:32:34 <gmaxwell> luke-jr: if you can (even at some expense) recover without the 'backup' it makes the backup solution much more usable. e.g. don't have to worry much about your backup being randsomed for 50% of your funds.
1482018-05-22T07:33:58 <luke-jr> gmaxwell: true
1492018-05-22T07:37:27 <jonasschnelli> what alternatives for PBKDF2 with silly static 2048 rounds for seed passphrase derivation would make sense?
1502018-05-22T07:37:51 <jonasschnelli> Or are passphrase protected seed just a footgun?
1512018-05-22T07:37:56 <jonasschnelli> *seeds
1522018-05-22T07:38:38 <gmaxwell> 2048 rounds of PBKDF2 really reeks of snake oil. It's not a meaningful amount of hardening.
1532018-05-22T07:39:08 <gmaxwell> I think passphrase protected seeds are a footgun, at least if there isn't a recovery mechenism... but people want them anyways.
1542018-05-22T07:39:30 <gmaxwell> And a recovery mechenism could be provided totally seperately.
1552018-05-22T07:40:27 <jonasschnelli> gmaxwell: with "recovery mechanism" you mean an expensive forensic like approach to recover a lost seed-passphrase?
1562018-05-22T07:40:34 <gmaxwell> I'm still fond of offloadable KDFs, which we know how to do. But when I talked to the trezor folks about that they wanted an additional property that they be (cheaply) verifyable, which seems possible but moves it more towards being a research problem.
1572018-05-22T07:42:56 <gmaxwell> jonasschnelli: I mean, like, for example, your backup could contain the an encrypted copy of the passphrase in a section accessable with the seed alone, which you could decrypt with the help of a recovery service. E.g. to recover your wallet you need seed+passphrase OR seed + bob's help. (e.g. your backup has an encrypted message to bob, saying that he should give the content to anyone who pr
1582018-05-22T07:42:57 <gmaxwell> esents him with a passport with your name on it, and not otherwise).
1592018-05-22T07:43:14 <gmaxwell> exactly how password recovery works is a huge rathole, unfortunately.
1602018-05-22T07:44:04 <gmaxwell> Which is why I was making the point that even though I think it's unsafe design to prompt users for a password without having one, ... it's fine to design a scheme that allows for passwords, since recovery can be provided by something else.
1612018-05-22T07:45:14 <jonasschnelli> Indeed
1622018-05-22T07:47:18 <gmaxwell> the problem for passphrases is that they're really kinda dumb without a KDF, if the user provides the password (and if the user doesn't come up with the password they are even more likely to forget it).
1632018-05-22T07:47:50 <gmaxwell> but people also want to use these schemes with hardware wallets, which don't have the CPU power to do a KDF that a GPU wouldn't laugh at.
1642018-05-22T08:16:20 *** intcat has quit IRC
1652018-05-22T08:17:30 *** ccdle12 has joined #bitcoin-core-dev
1662018-05-22T08:23:51 *** intcat has joined #bitcoin-core-dev
1672018-05-22T08:25:32 *** zarez has joined #bitcoin-core-dev
1682018-05-22T08:26:18 *** promag has joined #bitcoin-core-dev
1692018-05-22T08:31:50 *** glaksmono has quit IRC
1702018-05-22T08:32:22 *** glaksmono has joined #bitcoin-core-dev
1712018-05-22T08:36:30 *** glaksmono has quit IRC
1722018-05-22T08:36:55 *** justanotheruser has quit IRC
1732018-05-22T08:38:18 *** goofie has quit IRC
1742018-05-22T08:46:11 *** timothy has joined #bitcoin-core-dev
1752018-05-22T08:46:45 *** vicenteH has joined #bitcoin-core-dev
1762018-05-22T08:49:25 *** Victorsueca has quit IRC
1772018-05-22T08:50:40 *** drizztbsd has joined #bitcoin-core-dev
1782018-05-22T08:50:41 *** timothy has quit IRC
1792018-05-22T08:50:43 *** Victorsueca has joined #bitcoin-core-dev
1802018-05-22T09:10:40 *** str4d has quit IRC
1812018-05-22T09:24:07 *** Randolf has quit IRC
1822018-05-22T09:24:31 *** Randolf has joined #bitcoin-core-dev
1832018-05-22T09:34:17 *** glaksmono has joined #bitcoin-core-dev
1842018-05-22T09:34:33 *** si has joined #bitcoin-core-dev
1852018-05-22T09:34:51 <si> hello world
1862018-05-22T09:34:55 *** si is now known as Guest72611
1872018-05-22T09:37:21 <Guest72611> hi
1882018-05-22T09:37:28 *** Guest72611 has quit IRC
1892018-05-22T10:19:22 *** belcher has quit IRC
1902018-05-22T10:20:14 *** belcher has joined #bitcoin-core-dev
1912018-05-22T10:20:41 *** Emcy has quit IRC
1922018-05-22T10:30:45 *** Emcy has joined #bitcoin-core-dev
1932018-05-22T10:43:19 *** Chris_Stewart_5 has joined #bitcoin-core-dev
1942018-05-22T10:43:27 *** AaronvanW has joined #bitcoin-core-dev
1952018-05-22T10:45:29 *** Aaronvan_ has joined #bitcoin-core-dev
1962018-05-22T10:46:44 *** Krellan has joined #bitcoin-core-dev
1972018-05-22T10:48:00 <bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/d82c5d15c504...6916024768ec
1982018-05-22T10:48:01 <bitcoin-git> bitcoin/master 60ebc7d Daniel Kraft: trivial: Mark overrides as such....
1992018-05-22T10:48:01 <bitcoin-git> bitcoin/master 6916024 MarcoFalke: Merge #13282: trivial: Mark overrides as such....
2002018-05-22T10:48:50 <bitcoin-git> [bitcoin] MarcoFalke closed pull request #13282: trivial: Mark overrides as such. (master...mark-override) https://github.com/bitcoin/bitcoin/pull/13282
2012018-05-22T10:48:57 *** AaronvanW has quit IRC
2022018-05-22T10:51:05 *** Krellan has quit IRC
2032018-05-22T11:18:46 *** goofie has joined #bitcoin-core-dev
2042018-05-22T11:19:57 *** owowo has quit IRC
2052018-05-22T11:23:35 *** Chris_Stewart_5 has quit IRC
2062018-05-22T11:23:35 *** Randolf has quit IRC
2072018-05-22T11:23:42 *** glaksmono has quit IRC
2082018-05-22T11:24:21 *** Guyver2 has joined #bitcoin-core-dev
2092018-05-22T11:25:01 *** Randolf has joined #bitcoin-core-dev
2102018-05-22T11:25:44 *** glaksmono has joined #bitcoin-core-dev
2112018-05-22T11:26:10 *** Emcy has quit IRC
2122018-05-22T11:27:32 *** satwo has joined #bitcoin-core-dev
2132018-05-22T11:29:56 *** Emcy has joined #bitcoin-core-dev
2142018-05-22T11:30:10 *** glaksmono has quit IRC
2152018-05-22T11:30:34 *** Aaronvan_ is now known as AaronvanW
2162018-05-22T11:32:02 *** d9b4bef9 has quit IRC
2172018-05-22T11:33:08 *** d9b4bef9 has joined #bitcoin-core-dev
2182018-05-22T11:35:46 *** Emcy has quit IRC
2192018-05-22T11:36:36 *** Emcy has joined #bitcoin-core-dev
2202018-05-22T11:43:14 *** goatpig has joined #bitcoin-core-dev
2212018-05-22T12:00:23 *** Chris_Stewart_5 has joined #bitcoin-core-dev
2222018-05-22T12:05:45 *** AaronvanW has quit IRC
2232018-05-22T12:07:23 *** promag has quit IRC
2242018-05-22T12:15:00 *** glaksmono has joined #bitcoin-core-dev
2252018-05-22T12:19:40 *** glaksmono has quit IRC
2262018-05-22T12:23:08 *** AaronvanW has joined #bitcoin-core-dev
2272018-05-22T12:25:17 *** AaronvanW has quit IRC
2282018-05-22T12:25:55 *** AaronvanW has joined #bitcoin-core-dev
2292018-05-22T12:30:15 *** AaronvanW has quit IRC
2302018-05-22T12:30:34 *** justanotheruser has joined #bitcoin-core-dev
2312018-05-22T12:36:50 *** ula has joined #bitcoin-core-dev
2322018-05-22T12:38:18 *** glaksmono has joined #bitcoin-core-dev
2332018-05-22T12:45:08 *** tryphe_ has quit IRC
2342018-05-22T12:45:32 *** tryphe_ has joined #bitcoin-core-dev
2352018-05-22T12:49:23 *** fanquake has quit IRC
2362018-05-22T12:53:18 *** SopaXorzTaker has joined #bitcoin-core-dev
2372018-05-22T12:54:57 *** glaksmono has quit IRC
2382018-05-22T13:00:46 *** glaksmono has joined #bitcoin-core-dev
2392018-05-22T13:05:12 *** glaksmono has quit IRC
2402018-05-22T13:06:33 *** AaronvanW has joined #bitcoin-core-dev
2412018-05-22T13:16:38 *** promag has joined #bitcoin-core-dev
2422018-05-22T13:38:34 *** AaronvanW has quit IRC
2432018-05-22T13:48:55 *** Aaronvan_ has joined #bitcoin-core-dev
2442018-05-22T13:49:27 *** glaksmono has joined #bitcoin-core-dev
2452018-05-22T13:50:37 *** Randolf has quit IRC
2462018-05-22T13:53:46 *** glaksmono has quit IRC
2472018-05-22T13:54:45 *** Emcy has quit IRC
2482018-05-22T14:03:22 *** Aaronvan_ has quit IRC
2492018-05-22T14:03:51 *** owowo has joined #bitcoin-core-dev
2502018-05-22T14:04:00 *** AaronvanW has joined #bitcoin-core-dev
2512018-05-22T14:05:22 *** instagibbs_ has quit IRC
2522018-05-22T14:08:00 *** instagibbs has joined #bitcoin-core-dev
2532018-05-22T14:08:12 *** AaronvanW has quit IRC
2542018-05-22T14:08:35 *** laurentmt has joined #bitcoin-core-dev
2552018-05-22T14:12:17 *** laurentmt has quit IRC
2562018-05-22T14:12:38 *** Aliencorpse has quit IRC
2572018-05-22T14:23:39 *** windsok has joined #bitcoin-core-dev
2582018-05-22T14:23:39 *** windsok has joined #bitcoin-core-dev
2592018-05-22T14:24:27 *** Aliencorpse has joined #bitcoin-core-dev
2602018-05-22T14:25:02 *** Giszmo has quit IRC
2612018-05-22T14:30:17 *** Samdney has joined #bitcoin-core-dev
2622018-05-22T14:31:17 *** promag has quit IRC
2632018-05-22T14:33:36 *** promag has joined #bitcoin-core-dev
2642018-05-22T14:34:03 *** promag has quit IRC
2652018-05-22T14:34:17 *** promag has joined #bitcoin-core-dev
2662018-05-22T14:37:48 *** glaksmono has joined #bitcoin-core-dev
2672018-05-22T14:42:20 *** Krellan has joined #bitcoin-core-dev
2682018-05-22T14:43:34 *** Giszmo has joined #bitcoin-core-dev
2692018-05-22T14:46:58 *** Krellan has quit IRC
2702018-05-22T14:48:43 *** AaronvanW has joined #bitcoin-core-dev
2712018-05-22T15:09:52 *** Randolf has joined #bitcoin-core-dev
2722018-05-22T15:18:57 *** Randolf has quit IRC
2732018-05-22T15:19:01 *** d9b4bef9 has quit IRC
2742018-05-22T15:19:43 *** tryphe_ has quit IRC
2752018-05-22T15:20:08 *** tryphe_ has joined #bitcoin-core-dev
2762018-05-22T15:20:09 *** d9b4bef9 has joined #bitcoin-core-dev
2772018-05-22T15:21:49 <jnewbery> wumpus: #13011 definitely seems ready for merge
2782018-05-22T15:21:52 <gribble> https://github.com/bitcoin/bitcoin/issues/13011 | Cache witness hash in CTransaction by MarcoFalke · Pull Request #13011 · bitcoin/bitcoin · GitHub
2792018-05-22T15:23:00 *** promag has quit IRC
2802018-05-22T15:23:05 *** tryphe_000 has joined #bitcoin-core-dev
2812018-05-22T15:23:54 *** zarez has quit IRC
2822018-05-22T15:25:13 *** tryphe_ has quit IRC
2832018-05-22T15:31:05 *** Randolf has joined #bitcoin-core-dev
2842018-05-22T15:31:24 *** zarez has joined #bitcoin-core-dev
2852018-05-22T15:31:34 *** glaksmono has quit IRC
2862018-05-22T15:43:27 *** Randolf has quit IRC
2872018-05-22T15:43:32 *** JackH has quit IRC
2882018-05-22T15:46:41 *** promag has joined #bitcoin-core-dev
2892018-05-22T15:49:32 *** dtm_ has joined #bitcoin-core-dev
2902018-05-22T15:55:35 *** Guyver2 has quit IRC
2912018-05-22T15:55:39 *** Giszmo has quit IRC
2922018-05-22T15:56:47 <promag> jnewbery: +1 ^
2932018-05-22T16:00:58 *** vicenteH has quit IRC
2942018-05-22T16:04:41 *** Ishtv4n has quit IRC
2952018-05-22T16:07:14 *** Victorsueca has quit IRC
2962018-05-22T16:08:28 *** Victorsueca has joined #bitcoin-core-dev
2972018-05-22T16:09:28 *** promag has quit IRC
2982018-05-22T16:11:21 *** Giszmo has joined #bitcoin-core-dev
2992018-05-22T16:16:12 *** zarez has quit IRC
3002018-05-22T16:28:14 *** Giszmo has quit IRC
3012018-05-22T16:30:00 *** ccdle12 has quit IRC
3022018-05-22T16:31:33 *** Giszmo has joined #bitcoin-core-dev
3032018-05-22T16:42:40 *** SopaXorzTaker has quit IRC
3042018-05-22T16:53:27 *** Giszmo has quit IRC
3052018-05-22T16:56:13 *** Giszmo has joined #bitcoin-core-dev
3062018-05-22T17:02:03 *** Randolf has joined #bitcoin-core-dev
3072018-05-22T17:10:06 *** ExtraCrispy has quit IRC
3082018-05-22T17:21:47 *** adiabat has quit IRC
3092018-05-22T17:22:25 *** adiabat has joined #bitcoin-core-dev
3102018-05-22T17:26:56 *** drexl has joined #bitcoin-core-dev
3112018-05-22T17:27:06 *** drizztbsd has quit IRC
3122018-05-22T17:31:10 *** promag has joined #bitcoin-core-dev
3132018-05-22T17:40:22 *** prototype has joined #bitcoin-core-dev
3142018-05-22T17:46:58 *** ccdle12 has joined #bitcoin-core-dev
3152018-05-22T17:51:40 *** ccdle12 has quit IRC
3162018-05-22T17:56:46 *** owowo has quit IRC
3172018-05-22T18:01:09 *** owowo has joined #bitcoin-core-dev
3182018-05-22T18:14:52 *** tryphe has joined #bitcoin-core-dev
3192018-05-22T18:17:46 *** tryphe_000 has quit IRC
3202018-05-22T18:23:14 *** promag has quit IRC
3212018-05-22T18:23:19 *** CubicEarths has joined #bitcoin-core-dev
3222018-05-22T18:33:09 *** Victorsueca has quit IRC
3232018-05-22T18:34:28 *** Victorsueca has joined #bitcoin-core-dev
3242018-05-22T18:45:07 *** ccdle12 has joined #bitcoin-core-dev
3252018-05-22T18:46:30 *** Chris_Stewart_5 has quit IRC
3262018-05-22T18:51:41 *** rex4539 has joined #bitcoin-core-dev
3272018-05-22T18:59:22 *** CubicEarths has quit IRC
3282018-05-22T19:00:47 *** CubicEarths has joined #bitcoin-core-dev
3292018-05-22T19:03:25 *** ccdle12 has quit IRC
3302018-05-22T19:14:57 *** promag has joined #bitcoin-core-dev
3312018-05-22T19:49:54 *** Chris_Stewart_5 has joined #bitcoin-core-dev
3322018-05-22T19:50:22 *** Aaronvan_ has joined #bitcoin-core-dev
3332018-05-22T19:51:03 *** AaronvanW has quit IRC
3342018-05-22T19:52:57 *** owowo has quit IRC
3352018-05-22T19:54:36 *** promag has quit IRC
3362018-05-22T19:57:52 *** owowo has joined #bitcoin-core-dev
3372018-05-22T19:59:07 *** satwo has quit IRC
3382018-05-22T20:07:15 *** satwo has joined #bitcoin-core-dev
3392018-05-22T20:11:57 *** owowo has quit IRC
3402018-05-22T20:12:06 *** tryphe has quit IRC
3412018-05-22T20:12:29 *** tryphe has joined #bitcoin-core-dev
3422018-05-22T20:16:54 *** owowo has joined #bitcoin-core-dev
3432018-05-22T20:17:43 *** Krellan has joined #bitcoin-core-dev
3442018-05-22T20:17:44 <sdaftuar> kallewoof: if you're around i was wondering if you could explain how the refactoring in #12634 relates to #12257?
3452018-05-22T20:17:47 <gribble> https://github.com/bitcoin/bitcoin/issues/12634 | [refactor] Make TransactionWithinChainLimit more flexible by kallewoof · Pull Request #12634 · bitcoin/bitcoin · GitHub
3462018-05-22T20:17:50 <gribble> https://github.com/bitcoin/bitcoin/issues/12257 | [wallet] Use destination groups instead of coins in coin select by kallewoof · Pull Request #12257 · bitcoin/bitcoin · GitHub
3472018-05-22T20:18:58 *** satwo has quit IRC
3482018-05-22T20:19:29 *** satwo has joined #bitcoin-core-dev
3492018-05-22T20:20:27 *** satwo has quit IRC
3502018-05-22T20:24:35 *** a5m0 has quit IRC
3512018-05-22T20:33:54 *** jtimon has joined #bitcoin-core-dev
3522018-05-22T20:33:57 *** a5m0 has joined #bitcoin-core-dev
3532018-05-22T20:51:17 *** Victorsueca has quit IRC
3542018-05-22T20:52:04 *** a5m0 has quit IRC
3552018-05-22T20:52:29 *** Victorsueca has joined #bitcoin-core-dev
3562018-05-22T20:55:29 *** Randolf has quit IRC
3572018-05-22T20:56:39 *** a5m0 has joined #bitcoin-core-dev
3582018-05-22T20:57:10 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #13304: qa: Fix wallet_listreceivedby race (master...Mf1805-qaWalletRace) https://github.com/bitcoin/bitcoin/pull/13304
3592018-05-22T21:02:19 <bitcoin-git> [bitcoin] jimpo opened pull request #13305: Refactor: encapsulate mapBlockIndex within validation.cpp (master...validation-globals) https://github.com/bitcoin/bitcoin/pull/13305
3602018-05-22T21:02:49 *** nickler has quit IRC
3612018-05-22T21:04:02 *** LeMiner has joined #bitcoin-core-dev
3622018-05-22T21:10:51 <bitcoin-git> [bitcoin] jimpo closed pull request #13305: Refactor: encapsulate mapBlockIndex within validation.cpp (master...validation-globals) https://github.com/bitcoin/bitcoin/pull/13305
3632018-05-22T21:19:02 *** honeybadgerdgaf has joined #bitcoin-core-dev
3642018-05-22T21:20:53 *** honeybadgerdgaf has quit IRC
3652018-05-22T21:22:44 *** honeybadgerdgaf has joined #bitcoin-core-dev
3662018-05-22T21:30:45 *** LeMiner has quit IRC
3672018-05-22T21:31:10 *** Giszmo has quit IRC
3682018-05-22T21:45:17 *** Giszmo has joined #bitcoin-core-dev
3692018-05-22T21:51:01 *** d9b4bef9 has quit IRC
3702018-05-22T21:51:03 *** Aaronvan_ has quit IRC
3712018-05-22T21:51:41 *** AaronvanW has joined #bitcoin-core-dev
3722018-05-22T21:52:08 *** d9b4bef9 has joined #bitcoin-core-dev
3732018-05-22T21:55:43 *** Randolf has joined #bitcoin-core-dev
3742018-05-22T21:56:02 *** AaronvanW has quit IRC
3752018-05-22T22:00:55 *** Randolf has quit IRC
3762018-05-22T22:12:51 *** jtimon has quit IRC
3772018-05-22T22:16:15 *** honeybadgerdgaf has quit IRC
3782018-05-22T22:18:53 <bitcoin-git> [bitcoin] theuni opened pull request #13306: build: split warnings out of CXXFLAGS (master...debug_flags) https://github.com/bitcoin/bitcoin/pull/13306
3792018-05-22T22:23:42 *** Giszmo has quit IRC
3802018-05-22T22:26:27 *** honeybadgerdgaf has joined #bitcoin-core-dev
3812018-05-22T22:30:18 *** Giszmo has joined #bitcoin-core-dev
3822018-05-22T22:33:15 *** prototype has quit IRC
3832018-05-22T22:33:56 *** ula has quit IRC
3842018-05-22T22:38:52 *** AaronvanW has joined #bitcoin-core-dev
3852018-05-22T22:40:20 *** honeybadgerdgaf has quit IRC
3862018-05-22T22:55:43 *** CubicEarths has quit IRC
3872018-05-22T22:56:21 *** CubicEarths has joined #bitcoin-core-dev
3882018-05-22T22:57:10 <roasbeef> jonasschnelli: re-seed stuff, have y'all seen what we made for lnd? it has all the features one would desire in a seed format: reversible mapping between seed+phrase (uses an arbitrary length tweakable block cipher), a versioning scheme (for the encryption and also the internal wallet payload), if you use a passphrase we can detect invalid attempts, and also we have a "birthdate" which is offset from the genesis block in days -- good till 2189 (iir
3892018-05-22T22:57:54 <roasbeef> uses proper key derivation (no like 2k rounds of sha2 or w/e lol)
3902018-05-22T22:58:30 <sipa> roasbeef: does proper imply variable number of rounds? :)
3912018-05-22T22:59:19 <roasbeef> well woudl be able to have diff versions with higher/lower number of rounds to make it easier for say hardware wallets if that's what you mean
3922018-05-22T23:00:36 *** CubicEarths has quit IRC
3932018-05-22T23:01:10 *** rex4539 has quit IRC
3942018-05-22T23:04:52 *** honeybadgerdgaf has joined #bitcoin-core-dev
3952018-05-22T23:05:15 *** Chris_Stewart_5 has quit IRC
3962018-05-22T23:09:53 *** nickler has joined #bitcoin-core-dev
3972018-05-22T23:13:23 *** satwo has joined #bitcoin-core-dev
3982018-05-22T23:16:32 <kallewoof> sdaftuar: When doing coin selection on groups rather than individual outputs, the ancestor/descendant stuff becomes rather messy if you don't unify them to their corresponding maximums. In order to do that, you need the values, since they are tested against multiple limits.
3992018-05-22T23:19:08 *** honeybadgerdgaf has quit IRC
4002018-05-22T23:29:24 *** honeybadgerdgaf has joined #bitcoin-core-dev
4012018-05-22T23:34:00 *** Randolf has joined #bitcoin-core-dev
4022018-05-22T23:41:09 *** drexl has quit IRC
4032018-05-22T23:51:26 *** honeybadgerdgaf has quit IRC
4042018-05-22T23:53:13 *** honeybadgerdgaf has joined #bitcoin-core-dev