--- Day changed Wed Dec 13 2017 00:02 -!- tattoovicious [~tattoovic@78.90.9.207] has joined #bitcoin-core-dev 00:08 -!- Kozuch [~Kozuch@81.0.198.168] has joined #bitcoin-core-dev 00:11 -!- go1111111 [~go1111111@gateway/vpn/privateinternetaccess/go1111111] has joined #bitcoin-core-dev 00:12 -!- Williiiiiii [65bd6e79@gateway/web/freenode/ip.101.189.110.121] has joined #bitcoin-core-dev 00:15 -!- Williiiiiii [65bd6e79@gateway/web/freenode/ip.101.189.110.121] has quit [Client Quit] 00:19 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 00:32 -!- tattoovicious [~tattoovic@78.90.9.207] has quit [Quit: This computer has gone to sleep] 00:34 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 00:43 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 00:49 < Provoostenator> There's a Github issue or PR about consolidating translation files, but I can't find it. Not even with Google... 00:49 -!- tattoovicious [~tattoovic@78.90.9.207] has joined #bitcoin-core-dev 00:53 < fanquake> There are various issues for translations open at the moment. Do you want to add discussion somewhere? 00:54 < fanquake> cfields did you end up sending the zeromq mingw64 patch upstream? 00:55 < Provoostenator> I want to link to it from #11875 because reducing the number of locales would probably be helpful for review. 00:55 < gribble> https://github.com/bitcoin/bitcoin/issues/11875 | Snoei: a.k.a. how to translate technical jargon · Issue #11875 · bitcoin/bitcoin · GitHub 00:56 < Provoostenator> I remember the issue was quite specific about whch language files could be combined. 01:12 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-asuukgnoghxecexx] has joined #bitcoin-core-dev 01:15 -!- tiagotrs [~tiago@p5DC47F60.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 01:15 -!- tiagotrs [~tiago@p5DC47F60.dip0.t-ipconnect.de] has quit [Changing host] 01:15 -!- tiagotrs [~tiago@unaffiliated/tiagotrs] has joined #bitcoin-core-dev 01:16 < wumpus> I don't think there's a hard rule for that; in some cases the same language for multiple countries is spurious, in some cases there's actually a language difference 01:17 -!- Ab_ [b4bcfb10@gateway/web/freenode/ip.180.188.251.16] has joined #bitcoin-core-dev 01:17 < wumpus> 'reducing the number of locales' is not a goal in itself, it means leaving people without translations for their language, though removing low-quality ones would be good (but this has to be judged on transifex somehow) 01:18 -!- Ab_ [b4bcfb10@gateway/web/freenode/ip.180.188.251.16] has quit [Client Quit] 01:19 < Provoostenator> I think the PR (which I can't find) was just combining (mostly) identical languages like Dutch and Flemish. 01:20 -!- aqeel [77a0605d@gateway/web/freenode/ip.119.160.96.93] has joined #bitcoin-core-dev 01:21 < sipa> jonasschnelli: my odroid iseems be having some trouble... i just had a block that took 12 hours to validate 01:21 < sipa> it looks like it's just insanely slow I/O (7.5s per txin), but it's much faster after a reboot 01:22 < Provoostenator> In transifex there's nl, nl_BE, and nl_NL, although in src/qt/locale there's only nl. So maybe this has already been done. 01:22 < wumpus> yes, I have already been selective which languages I include in the repository 01:23 < wumpus> also translations with too few messages don't get included 01:23 < wumpus> (although that threshold is at 10, should probably be higher with the huge volume of translatable strings we have these days) 01:24 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #bitcoin-core-dev 01:24 < Provoostenator> As long as the fallback is sane and the translations are reviewed, wouldn't 1 be a low enough threshold? 01:26 < Provoostenator> E.g. if Flemish falls back to Dutch and Dutch falls back to English. Similarly Latin american versions of Spanish should fall back to European Spanish, before falling back to English. 01:27 < Provoostenator> But if instead languages immedidately fall back to English then it's probably better to leave them out if they're seriously incomplete. 01:28 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 01:29 < sipa> Provoostenator: we've had issues in the past once where there was an austrian german translation which was apparently full of dialect that offended peoe 01:30 < Provoostenator> Without review even worse things could happen. 01:31 < sipa> oh yes. 01:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:31 < Provoostenator> So I think the amount / quality / trustworthyness of review is more important than the number of translated phrases (depdneing on fallback behavior). 01:32 < Provoostenator> Obviously it's not worth monitoring reviewers for a language with 5 words, so I guess it's the same outcome. 01:32 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:36 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 256 seconds] 01:36 -!- vicenteH [~user@195.235.96.150] has joined #bitcoin-core-dev 01:38 -!- aqeel [77a0605d@gateway/web/freenode/ip.119.160.96.93] has quit [Quit: Page closed] 01:40 < wumpus> what use would a translation with one translated phrase be? I don't see it 01:40 < wumpus> for translation to be useful the entire application needs to be translated, more or less, certainly the most visited parts 01:41 < sipa> i don't know how i'd translate anything dirrectly in dutch vs flemish 01:41 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:41 < wumpus> I do agree the threshold could be lower for XX_yy languages that just override some messages than for XX "top level" ones 01:42 < wumpus> but otherwise the number of message is a measure of compleness 01:43 < Provoostenator> There's probably no use for a translation with 10 words, but if someone believes it's useful (for whatever reason I can't think of) and it's reviewed, and the fallback behavior is correct, I don't see a downside. 01:43 < Provoostenator> But as a general rule I would agree the majority of the frequently used parts of the app should be translated and maintained. 01:44 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 01:45 < Provoostenator> There are some cases where XX_yy languages have subtle differences that are genenally not a problem, but can be very confusing in just one or two places. That's the only scenario I can think of and I doubt it's relevant with so much technical jargon. 01:45 < wumpus> another reason why a language with many translations is preferable is because, very likely, there is more translation activity for it 01:45 < wumpus> a language with 10 messages will likely have had 1 person type in some messages 01:46 < wumpus> but sure, in the end it's just a time-saving heuristic - I don't have time nor language skills to judge every translation separately 01:47 < wumpus> I like the idea of having a glossary of 'words to not translate' btw, though I'm not sure it works for every language 01:47 < wumpus> e.g. what about chinese or arabic? it just doesn't make sense t ohave english words interspersed there 01:48 -!- timothy [tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:49 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 01:49 < Provoostenator> The glossary for each language would contain the suggested translation, which in most cases would not be a translation. 01:50 < wumpus> you want to make one for every language? 01:50 < Provoostenator> Well, every language where it's useful. 01:50 < Provoostenator> Isn't that how it already works? 01:50 < wumpus> that's awesome 01:52 < wumpus> I mean we've never had anyone spend a lot of time on translations or helping translators, i've tried to do it on or off (usually by removing overly-technical messages from translation or rewording them) 01:54 < Provoostenator> It's seems problematic to have a process that nobody can focus enough on to prevent things from breaking. 01:55 < wumpus> it's not clear to me what kind of process works for translating open source software 01:56 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 01:56 < wumpus> though the current one works, more or less, it's certainly better than not translating at all 01:56 < Provoostenator> I think it's better to not translate when in doubt 01:56 < wumpus> whose doubt? 01:56 < wumpus> that's the problem really here, you'd have to mobilize lots of volunteers 01:56 < wumpus> unless you know all languages yourself :) 01:57 < wumpus> maybe it's realistic now that bitcoin is so well-known 01:57 < Provoostenator> There's a lot of websites and applications out there where the translation is worse than the original. 01:57 < wumpus> and still it helps some people 01:57 < Provoostenator> I think requiring review of translated strings would be a good improvement. 01:57 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has joined #bitcoin-core-dev 01:58 < wumpus> a large portion of the world doesn't know english at all, so even somewhat broken form of their own language is more understandable 01:58 < wumpus> by whom? 01:58 < Provoostenator> Not always, because if you google a word like "snoei" you won't find help in any language. 01:59 < wumpus> well it literally translates to prune 01:59 < Provoostenator> Same as with pull requests; anyone can review translations, don't merge unless it has enough review. 01:59 < wumpus> so does transifex have a process for that? 02:00 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 240 seconds] 02:00 < wumpus> I know you can make teams etc 02:00 < wumpus> and that messages can be flagged as 'reviewed' 02:00 < Provoostenator> Yes, when you download the strings, you can select that you only want reviewed strings. 02:00 < Provoostenator> At least in the UI. 02:00 < wumpus> yes, but what does that mean? 02:00 < wumpus> who clicked 'reviewed' in that case? 02:00 < Provoostenator> That part I'm still figuring out 02:00 < Provoostenator> Transifex is broken for me, I can't see some of the pages. 02:00 < wumpus> I guess that a language reviewr needs to be assigned for every language? 02:01 < wumpus> or review team 02:01 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Remote host closed the connection] 02:01 < Provoostenator> Every language has a team, feel free to add me to Dutch. 02:01 < wumpus> I think German has a review team, from back when diapolo was a contributor 02:01 < wumpus> oh they can choose their own team? 02:01 < wumpus> I really have no clue :) 02:02 < Provoostenator> I think you (or whoever has admin rights over transifex) can invite people to language teams. 02:03 < wumpus> I'll see if I can add you for dutch 02:03 < Provoostenator> So a process could be: 1) all translations need review by someone in the team 2) before or after merging the final version, remind people on Github to quickly skim through whichever language they know 3) if (2) leads to problems, fire the reviewers 02:03 < wumpus> but I can't coordinate this for every language 02:03 < Provoostenator> (3) could be less drastic :-) 02:04 < Provoostenator> So maybe we need a github issue for a translation coordinator? 02:05 < Provoostenator> Sounds like a good role for a non-technical person who wants to help out. 02:06 < wumpus> I can't even find where to add you, I can go to https://www.transifex.com/bitcoin/teams/159/nl_NL/ and see your name under "translators" but I don't see how to move you to coorindator or reviewer 02:08 < Provoostenator> I'll try to make an org for myself and see if I can figure out the UX. 02:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 02:09 < wumpus> https://docs.transifex.com/teams/managing-and-removing-collaborators I don't see any "Teams" tab 02:10 < Provoostenator> I've used half a dozen translation services in the past and they all have serious issues. 02:10 < wumpus> might be that I don't have the required permissions 02:10 < Provoostenator> Yeah, I was assuming you were the admin. 02:10 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 02:10 < Provoostenator> Maybe Satoshi is? :-) 02:10 < wumpus> I'm "project maintainer" 02:10 < wumpus> seone, apparently 02:11 < wumpus> haven't seen them in a long time... 02:12 < wumpus> on the other hand I have access to all the settings, even the "delete project" button, so I would find it slightly strange if I don't have access to teams 02:13 < Provoostenator> Projects are not the top lovel. 02:14 < Provoostenator> Organization is 02:14 < wumpus> ok 02:15 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 02:15 < Provoostenator> If you click on the dropdown next to Bitcoin at the top, you shoudl see Organization Settings. 02:15 < Provoostenator> (I don't see that for Bitcoin because I don't own that org, but I do see it for the org I just created) 02:15 < wumpus> https://www.transifex.com/bitcoin/public/ I can only access the public page, ok that's explained then 02:16 < Provoostenator> Yes, and I can add administrators, which is probably what you are. 02:17 < Provoostenator> There's also "Maintainers". So maybe you can be promoted to admin. 02:18 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 256 seconds] 02:18 < Provoostenator> SAAS Kafka 02:18 < gmaxwell> https://www.bloomberg.com/news/articles/2017-12-12/bitcoin-developer-behind-failed-fork-begins-another-offshoot < someone should contact them and advise them that jeff garzik has not been a bitcoin core developer for many years. 02:18 < wumpus> Provoostenator: trying to find contact info for them. At least the irc account mentioned hasn't logged on for 7 weeks. Yes indeed :( 02:19 < Provoostenator> gmaxwell: doesn't he have an ICO to work on? 02:22 < wumpus> gmaxwell: I don't think there's a way to get rid of that denomination even if you'd want to 02:23 < wumpus> once someone is a bitcoin core developer you'll never leave, so beware :) 02:23 < meshcollider> gmaxwell: here you go ;) https://twitter.com/MeshCollider/status/940889701640060928 02:24 < wumpus> the only solution is to call everyone bitcoin core developer that contributed one patch, or heck even a translation message 02:24 < meshcollider> yes all users on transifex are core developers too :) 02:24 < wumpus> yup! 02:25 < wumpus> in that regard I've been trying to get credit info from the API (for the release notes) but haven't been succesful 02:25 < Provoostenator> Yes, which would include the bitcoin diamonds(?) person whose gitian signature was recently added to a PR. 02:25 < gmaxwell> Nah, they media does this when people use it to promote themselves or at least don't say don't do that. 02:26 < gmaxwell> that new spinoff is especially scammy, in they they confiscate most of the coins; -- any coin that wasn't moved in the last 30 days. 02:29 < Provoostenator> Ah, that's where they get their "sizable reserve to stabilize its price relative to fiat currencies" 02:30 < wumpus> the confiscation part is extrememly scammy, I mean deleting coins after 30 days that's one way to *bludgeon* the utxo set down, a very ugly way, but moving that money into their pocket is simply criminal 02:30 < gmaxwell> (moved in the last 30 days before their fork, and their domain was only registered <12 days before the fork...) 02:30 < Provoostenator> I'm sure it will stabilize at 0. I personally don't find it very productive to try and get media to report bitcoin related thing correctly. 02:31 < gmaxwell> well they design the rules, so ... well the really misleading part is to claim it is really related to bitcoin at all, it's just a massively premined dumb altcoin, where they happened to give a small portion to people who generated excess tx volume in the last week. 02:31 < wumpus> right, just yet another fork, at some point people will start ignoring them like they do for new altcoins and icos 02:32 < Provoostenator> There will probalby be plenty of malware too, maybe even in the reference client. 02:32 < wumpus> yep, also waiting for the first fork with malware in their reference client, it has been done with altcoins 02:33 < Provoostenator> Let's see if they get it right "at block height: #498,777" 02:33 < gribble> https://github.com/bitcoin/bitcoin/issues/498 | Edited README.md via GitHub by paraipan · Pull Request #498 · bitcoin/bitcoin · GitHub 02:35 < wumpus> garzik is pretty just wasting everyones time 02:35 < wumpus> +much 02:35 < Provoostenator> On the bright side, some of these airdrop developers might end up contributing to Core in the long term. 02:36 < wumpus> at some point his reputation will go down enough he can't keep pulling these stunts off anymore 02:36 < Provoostenator> Whaha, you'd be surprised. 02:36 < Provoostenator> I can point you to some biographies... 02:37 < wumpus> I'm not sure we even want that, the forks don't really seem to attract much talent, just people full of themselves that think they can do everything better 02:37 < Provoostenator> Not always, not if they're hired developers. 02:37 < Provoostenator> Then it's just their boss telling them to work on X, which they might feel reluctant about. 02:41 < gmaxwell> Provoostenator: someone once said that about altcoins in 2011... so far it seems almost none have done so. 02:42 -!- Lauda [~quassel@unaffiliated/lauda] has quit [Remote host closed the connection] 02:42 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev 02:42 < Provoostenator> Were any of these altcoins run by companies though? I would not expect single founder coin devs to do this. But yeah, I'm probably too optimistic. 02:43 < fanquake> The altcoins were run in bitcointalk threads. And eventually "generators" just churned them out. 02:44 < Provoostenator> They have 12 devs: http://www.ub.com/about/team 02:47 < meshcollider> at least their website looks nice ;) 02:48 < wumpus> usually in the cryptocurrency space, the nicer the website looks the scammier something is 02:48 < meshcollider> yep they spend more time on the website appearance than on the actual coin 02:50 -!- Lauda [~quassel@unaffiliated/lauda] has quit [Remote host closed the connection] 02:50 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-iwtokgyjrxvesuwq] has joined #bitcoin-core-dev 02:51 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev 02:51 < Provoostenator> No checksums on the download page. Source code is offered as a zip file, so good luck reviewing that... 02:51 < Provoostenator> (oh no, they do have a Github repo as well) 02:52 < meshcollider> only as of a week ago according to their roadmap lol 02:54 < Provoostenator> The commit messages and user names are entertaining. 02:54 < meshcollider> BUG FIXED 02:55 < Provoostenator> They branched away from Core master on November 30 02:56 < Provoostenator> This should be the full div: https://github.com/UnitedBitcoin/UnitedBitcoin/compare/60d739e...v1.0.3 02:56 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 03:09 < Provoostenator> My favorite comment so far: "UnionBitcoin god mode block generator" (anyway, off topic I guess, unless there's a zero-day?) 03:11 < gmaxwell> Provoostenator: in 2011 no, but ripple... 03:12 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Remote host closed the connection] 03:13 < Provoostenator> Does Ripple have any code overlap with Core that would make it easy for their devs to help out here? 03:14 < wumpus> I don't think they have any code overlap 03:16 < meshcollider> certainly doesn't look like they do, from a quick browse at their repo 03:18 -!- tattoovicious [~tattoovic@78.90.9.207] has quit [Quit: This computer has gone to sleep] 03:18 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 03:19 < gmaxwell> generally companies won't have code overlap, paying people to rewrite the codebase (not necessarily well or with any originality :) ) is cheap to do and lots of people are eager to do it. 03:21 < Provoostenator> I created #bitcoin-airdrop-code-shenanigans if anyone is interested. Not sure how to log it. 03:27 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 03:32 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Ping timeout: 248 seconds] 03:36 -!- tattoovicious [~tattoovic@78.90.9.207] has joined #bitcoin-core-dev 03:39 -!- fronti [~fronti@irc.fh-biergarten.de] has quit [Ping timeout: 255 seconds] 03:49 -!- go1111111 [~go1111111@gateway/vpn/privateinternetaccess/go1111111] has quit [Quit: Leaving] 03:51 -!- promag [~promag@82.155.24.70] has joined #bitcoin-core-dev 03:52 -!- fronti [~fronti@irc.fh-biergarten.de] has joined #bitcoin-core-dev 03:55 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 04:02 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Ping timeout: 248 seconds] 04:03 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 04:03 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host] 04:03 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 04:08 -!- blackbaba [~blackbaba@137.59.252.172] has joined #bitcoin-core-dev 04:09 < cluelessperson> question, which flag indicates an RBF transaction? 04:10 < mryandao> nsequence 04:10 < cluelessperson> < some maximum? 04:11 < meshcollider> cluelessperson: yep RBF if any sequence value is less than 0xffffffff - 1 04:11 < cluelessperson> oh that's easy 04:11 < cluelessperson> I overlooked it in my code 04:11 * cluelessperson makes a comment 04:13 < cluelessperson> wait 04:13 < cluelessperson> my previous code looks at nsequence in all of the inputs 04:13 < cluelessperson> is that right? 04:14 < cluelessperson> should be nSequence of the current transaction, not inputs, right? 04:20 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 04:20 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 240 seconds] 04:20 < aj> cluelessperson: depends on if the inputs have confirmed already 04:20 < cluelessperson> aj: What depends? 04:21 < aj> cluelessperson: RBF inherits; if the ancestors have nSeq signalling RBF, current tx is RBF too 04:22 < aj> cluelessperson: (provided the ancestors haven't confirmed yet) 04:22 < meshcollider> cluelessperson: Depends what you are referring to by an input. If you mean the vin of the transaction, then yes, thats correct, sequence numbers are per-input 04:22 < meshcollider> that is different from looking back at the parent being spend 04:22 < meshcollider> spent* 04:23 < meshcollider> but yes aj is right, RBF also inherits 04:24 -!- blackbaba [~blackbaba@137.59.252.172] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 04:26 < cluelessperson> I see 04:26 < cluelessperson> for txin in tx.vin: if txin.nSequence < 0xfffffffe: return True 04:27 -!- promag [~promag@82.155.24.70] has quit [Remote host closed the connection] 04:29 < meshcollider> yes that sounds right 04:29 < meshcollider> its detailed in BIP 125 btw 04:34 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has joined #bitcoin-core-dev 04:35 -!- tattoovicious [~tattoovic@78.90.9.207] has quit [Quit: This computer has gone to sleep] 04:37 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 04:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:43 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Ping timeout: 248 seconds] 04:44 -!- StopAndDecrypt [~StopAndDe@73.248.248.9] has joined #bitcoin-core-dev 04:44 -!- StopAndDecrypt [~StopAndDe@73.248.248.9] has quit [Changing host] 04:44 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 04:48 -!- kabaum_ [~kalle@h-13-35.A163.priv.bahnhof.se] has joined #bitcoin-core-dev 04:54 -!- bityogi [~textual@208-104-132-26.brvd.dsl.dyn.comporium.net] has joined #bitcoin-core-dev 04:55 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 04:58 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Quit: Leaving.] 04:59 -!- cyber55 [~cyber55@unaffiliated/cyber55] has quit [Quit: Leaving] 05:01 -!- alfa [uid11513@gateway/web/irccloud.com/x-mplvkqilautnfmop] has joined #bitcoin-core-dev 05:02 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 05:03 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 05:06 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/ba2f19504c6b...68e021e3a35d 05:06 < bitcoin-git> bitcoin/master fbf327b Aaron Clauson: Minimal code changes to allow msvc compilation. 05:06 < bitcoin-git> bitcoin/master 68e021e Wladimir J. van der Laan: Merge #11558: Minimal code changes to allow msvc compilation... 05:12 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 05:17 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev 05:21 -!- DeadCode [~0xD3adC0d@37.172.166.41] has joined #bitcoin-core-dev 05:21 < DeadCode> hello world 05:22 < DeadCode> I would like to ask some questions to jonasschnelli but he seems offline, anyone would like to help regarding libbtc implementation, please? 05:27 -!- archaeal [62ce095e@gateway/web/freenode/ip.98.206.9.94] has quit [Ping timeout: 260 seconds] 05:35 -!- lnostdal [~lnostdal@62.90-149-73.nextgentel.com] has quit [Ping timeout: 272 seconds] 05:36 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 256 seconds] 05:36 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 05:38 -!- Deacydal [~Deacyde@unaffiliated/deacyde] has joined #bitcoin-core-dev 05:38 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has quit [Ping timeout: 276 seconds] 05:41 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has quit [Ping timeout: 255 seconds] 05:46 -!- lnostdal [~lnostdal@62.90-149-73.nextgentel.com] has joined #bitcoin-core-dev 05:50 -!- archaeal [62ce095e@gateway/web/freenode/ip.98.206.9.94] has joined #bitcoin-core-dev 06:04 -!- DeadCode [~0xD3adC0d@37.172.166.41] has quit [Quit: Leaving] 06:07 -!- quantbot [~quantbot@184.75.84.115] has joined #bitcoin-core-dev 06:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 06:13 -!- mrfrasha [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 06:14 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 06:14 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has joined #bitcoin-core-dev 06:19 -!- quantbot [~quantbot@184.75.84.115] has quit [Remote host closed the connection] 06:19 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 06:19 -!- quantbot [~quantbot@rrcs-184-75-84-115.nyc.biz.rr.com] has joined #bitcoin-core-dev 06:20 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 06:20 -!- arubi_ [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 06:21 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 06:23 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds] 06:23 -!- quantbot [~quantbot@rrcs-184-75-84-115.nyc.biz.rr.com] has quit [Ping timeout: 240 seconds] 06:24 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 06:32 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 06:33 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 06:33 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-iwtokgyjrxvesuwq] has quit [Quit: Connection closed for inactivity] 06:34 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 06:38 -!- harrymm [~harrymm@104.207.83.57] has joined #bitcoin-core-dev 06:39 -!- tiagotrs [~tiago@unaffiliated/tiagotrs] has quit [Ping timeout: 264 seconds] 06:45 -!- quantbot [~quantbot@rrcs-184-75-84-115.nyc.biz.rr.com] has joined #bitcoin-core-dev 06:46 -!- SopaXT [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 06:46 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Read error: Connection reset by peer] 06:49 -!- quantbot [~quantbot@rrcs-184-75-84-115.nyc.biz.rr.com] has quit [Ping timeout: 248 seconds] 06:50 -!- quantbot [~quantbot@rrcs-184-75-84-115.nyc.biz.rr.com] has joined #bitcoin-core-dev 06:52 < promag> MarcoFalke: ping 06:52 -!- mrfrasha_ [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 06:52 -!- mrfrasha [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Quit: mrfrasha] 06:53 -!- quantbot [~quantbot@rrcs-184-75-84-115.nyc.biz.rr.com] has quit [Remote host closed the connection] 06:53 -!- quantbot [~quantbot@rrcs-184-75-84-115.nyc.biz.rr.com] has joined #bitcoin-core-dev 06:53 < promag> wumpus: int64_t GetArg returns 0 if conversion fails 06:54 < promag> should it return default value? should it throw or signal some *bool? 06:54 < wumpus> I guess that has always been the case? 06:55 < promag> we have ParseInt64 that indicates success or not 06:55 < wumpus> no, if that's changed, I'd say make it use ParseInt64 instead of atoi and raise an actual error 06:55 < wumpus> yes 06:56 < promag> for instance, -prune=foo 06:56 < promag> atm it's the same as -prune=0 06:57 < wumpus> it should throw an error and exit imo 06:57 < promag> my opinion also 06:57 < wumpus> using the default value when parsing fails isn't better 06:57 < promag> right 06:57 < promag> it's bad configuration 06:57 < promag> should be fixed 06:57 -!- quantbot [~quantbot@rrcs-184-75-84-115.nyc.biz.rr.com] has quit [Ping timeout: 264 seconds] 07:00 < promag> the problem is that dealing with failed conversion will make the code ugly throughout, GetArg is used everywhere 07:03 < wumpus> yeah... 07:03 < wumpus> that's kind of the annoying thing about the current argument parsing code 07:03 < wumpus> that it's called from everywhere, not just init 07:04 < wumpus> also why I didn't fix this before, I did know of that use of atoi when I introduced ParseInt64 07:05 < wumpus> seems it's something better left for when there's more structured argument parsing 07:11 < promag> ok 07:16 -!- quantbot [~quantbot@38.101.106.141] has joined #bitcoin-core-dev 07:18 < promag> Is this comment still valid https://github.com/bitcoin/bitcoin/blob/68e021e3a35d1e88d6075ea8b05a8e3a40a64e29/src/wallet/wallet.cpp#L4125-L4129 ? 07:20 < promag> Reading #10286.. 07:20 < gribble> https://github.com/bitcoin/bitcoin/issues/10286 | Call wallet notify callbacks in scheduler thread (without cs_main) by TheBlueMatt · Pull Request #10286 · bitcoin/bitcoin · GitHub 07:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 07:28 -!- Amuza [~Amuza@85.159.207.5] has joined #bitcoin-core-dev 07:29 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 07:34 < promag> is validation.h the best place for LookupBlockIndex definition? 07:35 < promag> I guess so because extern BlockMap& mapBlockIndex; is in validation.h 07:38 < BlueMatt> yes, though tbh I'd like to quickly move to LookupBlockIndex being in validation.h and mapBlockIndex being validation.cpp-static, but thats more work so can be a separate pr 07:40 < promag> yes I thought of that too 07:40 < promag> https://github.com/bitcoin/bitcoin/pull/11041#issuecomment-349811860 07:41 < promag> but out of scope of 11041 07:42 < BlueMatt> yes, agreed 07:43 < BlueMatt> I just really want to get #10692 in, and #11041 should simplify it a bunch 07:43 < gribble> https://github.com/bitcoin/bitcoin/issues/10692 | Make mapBlockIndex and chainActive and all CBlockIndex*es const outside of validation/CChainState by TheBlueMatt · Pull Request #10692 · bitcoin/bitcoin · GitHub 07:43 < gribble> https://github.com/bitcoin/bitcoin/issues/11041 | Add LookupBlockIndex by promag · Pull Request #11041 · bitcoin/bitcoin · GitHub 07:43 < BlueMatt> and I can probably skip making mapBlockIndex const and just move it to validation.cpp, cause making it const is a stupid hack (that possible invokes ub? I'm not actually 100% sure) 07:44 < promag> haven't compiled locally to verify the annotation LookupBlockIndex(const uint256& hash) EXCLUSIVE_LOCKS_REQUIRED(cs_main), waiting for travis 07:44 < BlueMatt> you just have to compile with CXX=clang++ ./configure --enable-werror 07:47 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 07:49 -!- dabura667 [~dabura667@KD111103034253.ppp-bb.dion.ne.jp] has joined #bitcoin-core-dev 07:56 -!- tattoovicious [~tattoovic@95.111.59.133] has joined #bitcoin-core-dev 08:07 -!- pkx2 [~pkx@unaffiliated/pkx] has joined #bitcoin-core-dev 08:08 < promag> IMO #11877 is ready 08:08 < gribble> https://github.com/bitcoin/bitcoin/issues/11877 | Improve createrawtransaction functional tests by promag · Pull Request #11877 · bitcoin/bitcoin · GitHub 08:09 < promag> jnewbery: +1 for comment 08:18 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 272 seconds] 08:19 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-asuukgnoghxecexx] has quit [Quit: Connection closed for inactivity] 08:21 < bitcoin-git> [bitcoin] fridzema opened pull request #11885: Direct link to the freenode channel (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11885 08:22 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 08:24 -!- mitfree[m] [mitfreemat@gateway/shell/matrix.org/x-dsdadvhufjofqhrn] has joined #bitcoin-core-dev 08:25 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 08:26 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 08:33 -!- SopaXT [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Quit: Leaving] 08:33 -!- LeMiner [LeMiner@unaffiliated/leminer] has quit [Read error: Connection reset by peer] 08:33 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 08:34 < bitcoin-git> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/68e021e3a35d...d4991c0cbb8a 08:34 < bitcoin-git> bitcoin/master 320669a João Barbosa: rpc: Validate replaceable type in createrawtransaction 08:34 < bitcoin-git> bitcoin/master 27c6199 João Barbosa: test: Add multidict to support dictionary with duplicate key (laanwj) 08:34 < bitcoin-git> bitcoin/master 88af502 João Barbosa: test: Add createrawtransaction functional tests 08:35 < bitcoin-git> [bitcoin] laanwj closed pull request #11877: Improve createrawtransaction functional tests (master...2017-12-createrawtransaction) https://github.com/bitcoin/bitcoin/pull/11877 08:35 -!- dabura667 [~dabura667@KD111103034253.ppp-bb.dion.ne.jp] has quit [Remote host closed the connection] 08:41 -!- tattoovicious [~tattoovic@95.111.59.133] has quit [Quit: Leaving] 08:41 < bitcoin-git> [bitcoin] jimhashhq reopened pull request #10922: New file-partition.md doc describing how to partition files to ensure fast initial blockchain synchronization.. (master...master) https://github.com/bitcoin/bitcoin/pull/10922 08:47 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Ping timeout: 260 seconds] 08:50 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 264 seconds] 08:51 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 08:51 < bitcoin-git> [bitcoin] practicalswift closed pull request #11734: rpc: Work around Clang thread safety analysis quirks (master...clang-thread-safety-quirks) https://github.com/bitcoin/bitcoin/pull/11734 08:53 -!- mitfree[m] [mitfreemat@gateway/shell/matrix.org/x-dsdadvhufjofqhrn] has left #bitcoin-core-dev ["User left"] 08:54 -!- ThemoonMoth [80b17166@gateway/web/freenode/ip.128.177.113.102] has joined #bitcoin-core-dev 08:54 < ThemoonMoth> Thoughts about the upcoming FCC vote? 08:54 < ThemoonMoth> And it's effect on bitcoin development in the US 08:55 < kanzure> wrong channel 08:55 < ThemoonMoth> the appropriate one would be...? 09:00 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev 09:01 < BlueMatt> #bitcoin 09:01 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 09:01 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 09:02 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 09:05 -!- Kozuch [~Kozuch@81.0.198.168] has quit [Ping timeout: 248 seconds] 09:06 < BlueMatt> can remove 11363 from https://github.com/bitcoin/bitcoin/projects/8 =D 09:06 -!- rever5e [ac3a06b5@gateway/web/freenode/ip.172.58.6.181] has joined #bitcoin-core-dev 09:07 < rever5e> I'm trying to figure out if there is a way i can help core as a full-stack web developer. Anyone have any ideas? 09:07 -!- rafalcpp [~racalcppp@84.10.11.234] has joined #bitcoin-core-dev 09:07 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 09:08 < rever5e> Unfortunately not savvy enough to contribute to main repo i'd just end up Garzik'ing it 09:09 < wumpus> rever5e: you could help with documentation, or translations 09:10 < rever5e> wumpus: How? 09:10 < wumpus> documentation is mainly in https://github.com/bitcoin/bitcoin/tree/master/doc, translations on transifex https://www.transifex.com/bitcoin/bitcoin/ 09:10 -!- ThemoonMoth [80b17166@gateway/web/freenode/ip.128.177.113.102] has quit [Quit: Page closed] 09:14 -!- rever5e [ac3a06b5@gateway/web/freenode/ip.172.58.6.181] has quit [Quit: Page closed] 09:16 -!- Amuza [~Amuza@85.159.207.5] has quit [Quit: Leaving] 09:23 < bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11886: Clarify getbalance meaning a tiny bit in response to questions. (master...2017-12-getbalance-docs) https://github.com/bitcoin/bitcoin/pull/11886 09:25 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 09:25 < bitcoin-git> [bitcoin] laanwj closed pull request #11885: Direct link to the freenode channel (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11885 09:27 -!- Kozuch [~Kozuch@81.0.198.168] has joined #bitcoin-core-dev 09:29 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 09:34 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Ping timeout: 272 seconds] 09:41 -!- alfa [uid11513@gateway/web/irccloud.com/x-mplvkqilautnfmop] has quit [Quit: Connection closed for inactivity] 09:43 -!- Kozuch [~Kozuch@81.0.198.168] has quit [Ping timeout: 264 seconds] 09:44 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 09:47 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 09:59 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit [] 09:59 -!- timothy [tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 10:06 -!- arubi_ is now known as arubi 10:11 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt] 10:13 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 10:15 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 10:17 < cluelessperson> Bitcoin Core's "estimatefee" and "estimatesmartfee", what is the unit they're using? 10:17 < cluelessperson> 0.00356757 10:17 < cluelessperson> I think it's mbtc/kb? 10:17 < arubi> it's always been btc/kb 10:17 < arubi> maybe changed recently? that would be breaking for .confs 10:18 < arubi> *so I don't think it's changed :) 10:19 < arubi> yep, says btc/kb 10:19 -!- [b__b] [~b__b]@ec2-54-85-45-223.compute-1.amazonaws.com] has quit [Remote host closed the connection] 10:19 < wumpus> the help should show it, if not, it's a bug 10:19 -!- [b__b] [~b__b]@ec2-54-85-45-223.compute-1.amazonaws.com] has joined #bitcoin-core-dev 10:19 < wumpus> (e.g. bitcoin-cli help estimatefee) 10:19 < arubi> it does, actually I didn't see we're on #-core-dev 10:20 < arubi> on smartfee it does say btc/kb. estimatefee just says "fee-per-kb" 10:21 < wumpus> that could be clearer, though in general all amounts on the RPC interface are in BTC, never mbtc or mubtc 10:27 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-vabvxrinxehuevvt] has joined #bitcoin-core-dev 10:30 < achow101> estimatefee is deprecated anyways 10:31 < cluelessperson> help doesn't show it. 10:31 < cluelessperson> achow101: estimatesmartfee is good? 10:32 < sipa> yes 10:32 < achow101> yes 10:32 < sipa> estimatesmartfee orestimaterawfee 10:33 < achow101> estimatesmartfee replaces estimatefee 10:35 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 272 seconds] 10:43 -!- bityogi [~textual@208-104-132-26.brvd.dsl.dyn.comporium.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 10:46 -!- eck [~eck@fsf/member/eck] has quit [Quit: we out here] 10:50 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 256 seconds] 10:58 < jonasschnelli> sipa: re. "it looks like it's just insanely slow I/O (7.5s per txin), but it's much faster after a reboot" 10:58 < jonasschnelli> Is that the same problem we have reported on the github issue tracker? 10:58 < jonasschnelli> Do you know why it was caused? swap? 11:05 < sipa> jonasschnelli: trying to figure that out now 11:08 -!- sanada` [~bitktn@36-2-119-80.chiba.ap.gmo-isp.jp] has quit [] 11:09 < jonasschnelli> I really like to try Core on the Jetson TX1 board: https://www.nvidia.com/en-us/autonomous-machines/embedded-systems-dev-kits-modules/ 11:10 < GAit> when you say odroid do you mean hardkernel stuff? 11:10 < jonasschnelli> sipa: did anyone ever conceptually figured out if parts of the validation could be "outsourced" to GPU? 11:10 < jonasschnelli> (http://on-demand.gputechconf.com/gtc/2013/presentations/S3018-High-Performance-Cryptology-on-GPUs.pdf) 11:10 < jonasschnelli> GAit: yes. Hardkernel 11:11 < jonasschnelli> But for a "fullnode-in-a-box", I think you need more horsepower... that's why I think the Jetson TX1 would be a good choice. 11:11 < jonasschnelli> Also,... you don't pay for stuff you don't need (HDMI, 4USB, etc.) 11:12 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 11:15 < gmaxwell> the gpu is useless, and otherwise it's just an arm a57 and wouldn't be faster than other a57s 11:18 < wumpus> with modern GPUs you can certainly do cryptography, would'nt be surprised if you could port secp256k1 to opencl, but gpus are unreliable, even the high-end cloud computing ones, but especially customer ones. It'd be a mess. 11:19 < gmaxwell> well there have been gpu key generators, for example, that were a couple times faster than openssl, but significantly slower than libsecp256k1. 11:19 < wumpus> and as we already get a enough reports of errors due to overheating *CPUs*... 11:19 < gmaxwell> lack of 64,64->128 multiply is a big performance hit. 11:19 < wumpus> still, you could distribute over both the CPU and PGU 11:22 < gmaxwell> the pdf jonas linked to showed only a 6x speedup over naieve code on the cpu given arbritarily high parallelism, with a gpu using ~3x the power, and having a 21x hit in latency. Not especially attractive even if you ignore the historical stability issues. 11:22 < gmaxwell> (and the man power required to write and maintain the software, and the requirement for propritary drivers, etc.) 11:23 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...] 11:24 < wumpus> yes 11:25 < Provoostenator> wumpus: I can't find "snoei" in the nl_NL Transifex translations, maybe it's in the nl one? Can you add me there? 11:26 < wumpus> it's possible that it was removed since last update from transifex 11:27 < wumpus> but no, I can't add you to anything, I somehow don't have access to teams there 11:27 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 248 seconds] 11:28 < Provoostenator> But you were able to add me to nl_NL, or did I just social engineer Transifex staff? 11:28 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Quit: Leaving] 11:28 < wumpus> no, I didn't add you to anything 11:30 < wumpus> I can only delete stuff apparentlly, transifex access controls make no sense 11:31 < wumpus> oh that's not true I can also create new translations, and sub-projects, just not teams 11:31 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 11:31 < Provoostenator> Does the translation script only use nl_NL? Because then there's no need for me to have access to nl (or nl_be) 11:32 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has joined #bitcoin-core-dev 11:32 < wumpus> for the next major version I should probably create the transations in a new organization 11:33 < wumpus> $ find -name bitcoin_nl\* -> ./src/qt/locale/bitcoin_nl_NL.ts ./src/qt/locale/bitcoin_nl.ts 11:34 < Provoostenator> So that combines nl, nl_BE and nl_NL somehow? 11:34 < wumpus> no 11:34 < wumpus> that's literally nl_NL and nl, no nl_BE 11:35 < wumpus> it doesn't combine anything, it just copies the translation files 11:36 -!- dcousens [~dcousens@CPE-101-181-44-212.lnse4.cha.bigpond.net.au] has quit [Ping timeout: 246 seconds] 11:36 -!- jonas_ [cedd7f22@gateway/web/freenode/ip.206.221.127.34] has joined #bitcoin-core-dev 11:37 -!- dcousens [~dcousens@110.148.122.235] has joined #bitcoin-core-dev 11:37 -!- jonas_ is now known as Guest99398 11:37 < wumpus> nl_BE either falls below the threshold of 10 messages, or has been added since the last translations pull 11:37 -!- Guest99398 [cedd7f22@gateway/web/freenode/ip.206.221.127.34] has quit [Client Quit] 11:39 < Provoostenator> I'm reading the script now. Is it actually doing the downloading or do you do that manually? 11:39 < wumpus> yes, it does the downloading 11:39 < Provoostenator> update-translations.py? Where? 11:39 < wumpus> we talked about this before today? 11:40 < Provoostenator> I was referring to this: https://github.com/bitcoin/bitcoin/issues/11875#issuecomment-351331497 11:41 < Provoostenator> Ah wait, I see it now. TX is another command. I'll figure it out. 11:41 < wumpus> fetch_all_translations(), fetches the translations 11:41 -!- dcousens [~dcousens@110.148.122.235] has quit [Ping timeout: 256 seconds] 11:42 -!- dcousens [~dcousens@CPE-101-181-119-74.lnse5.cha.bigpond.net.au] has joined #bitcoin-core-dev 11:43 -!- m8tion01 [~m8tion@81-65-53-254.rev.numericable.fr] has joined #bitcoin-core-dev 11:46 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has quit [Ping timeout: 248 seconds] 11:50 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 272 seconds] 11:53 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev 11:54 -!- dcousens [~dcousens@CPE-101-181-119-74.lnse5.cha.bigpond.net.au] has quit [Ping timeout: 264 seconds] 11:54 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Max SendQ exceeded] 11:54 -!- bityogi [~textual@208-104-132-26.brvd.dsl.dyn.comporium.net] has joined #bitcoin-core-dev 11:54 -!- dcousens [~dcousens@CPE-101-181-119-74.lnse5.cha.bigpond.net.au] has joined #bitcoin-core-dev 11:54 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev 11:55 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Max SendQ exceeded] 11:56 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev 11:56 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Max SendQ exceeded] 11:57 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev 11:58 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Max SendQ exceeded] 11:58 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev 11:59 -!- tiagotrs [~tiago@p5DC47F60.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:59 -!- tiagotrs [~tiago@p5DC47F60.dip0.t-ipconnect.de] has quit [Changing host] 11:59 -!- tiagotrs [~tiago@unaffiliated/tiagotrs] has joined #bitcoin-core-dev 12:00 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Remote host closed the connection] 12:00 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev 12:00 < jonasschnelli> Is there a way to detect if IsInitialBlockDownload() via RPC? 12:01 < jonasschnelli> nm: getblockchaininfo 12:01 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Remote host closed the connection] 12:02 -!- eck [~eck@fsf/member/eck] has joined #bitcoin-core-dev 12:04 -!- jamesob [~james@199.230.10.198] has joined #bitcoin-core-dev 12:06 -!- bsm117532 [~mcelrath@104.129.204.130] has joined #bitcoin-core-dev 12:07 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Ping timeout: 264 seconds] 12:13 < BlueMatt> #11888 should get an 0.16 tag 12:13 < gribble> https://github.com/bitcoin/bitcoin/issues/11888 | Prevent Opening Wallets Simultaneously in Two Instances · Issue #11888 · bitcoin/bitcoin · GitHub 12:17 < jonasschnelli> Tagged 12:19 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 12:19 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 12:20 < bitcoin-git> [bitcoin] ryanofsky opened pull request #11889: Drop extra script variable in ProduceSignature (master...pr/dupvar) https://github.com/bitcoin/bitcoin/pull/11889 12:22 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has joined #bitcoin-core-dev 12:24 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has quit [] 12:27 < jonasschnelli> BlueMatt: re: https://github.com/bitcoin/bitcoin/pull/11281#pullrequestreview-82968766 12:27 < jonasschnelli> can you explain that a bit more for me? 12:28 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Quit: .] 12:28 < jonasschnelli> I think locking cs_main during the AddToWalletIfInvolvingMe() part would be removing most of the lock optimization done in this PR 12:28 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 12:28 < BlueMatt> jonasschnelli: the !chainActive.Contains(pindex) check *must* be in the same cs_main lock as AddToWalletIfInvolvingMe 12:29 < jonasschnelli> BlueMatt: But AddToWalletIfInvolvingMe is currently (in the PR) done without cs_main 12:30 < jonasschnelli> If we remove the general locks and add those back in ever block, it seems like a wast of effort. I don't see why AddToWalletIfInvolvingMe would need cs_main... 12:30 < jonasschnelli> *every 12:31 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has quit [Remote host closed the connection] 12:31 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has joined #bitcoin-core-dev 12:32 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has joined #bitcoin-core-dev 12:32 < jonasschnelli> I way expecting that we can do the two most significant time consumers (ReadBlockFromDisk, AddToWalletIfInvolvingMe) without cs_main 12:32 < BlueMatt> jonasschnelli: uhhhh well thats a second bug then 12:32 < BlueMatt> AddToWalletIfInvolvingMe requires cs_main 12:32 < BlueMatt> cause it can call AbandonTransaction 12:32 < BlueMatt> errrr, I meant MarkConflicted 12:33 < jonasschnelli> BlueMatt: ahh.. redudant deadlock 12:33 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has quit [Client Quit] 12:33 < jonasschnelli> seems my #11281 approach is a dead end 12:33 < gribble> https://github.com/bitcoin/bitcoin/issues/11281 | Avoid permanent cs_main/cs_wallet lock during RescanFromTime by jonasschnelli · Pull Request #11281 · bitcoin/bitcoin · GitHub 12:33 < BlueMatt> no? 12:33 < BlueMatt> its still helpful to *unlock* cs_main after every block 12:34 < jonasschnelli> if we add AddToWalletIfInvolvingMe under cs_main two, alomst every code part will aquire the lock 12:34 < BlueMatt> so? 12:34 < BlueMatt> another thing you could do (which I thought you were going to) is push down the cs_main in the ReadBlockFromDisk 12:34 < jonasschnelli> BlueMatt: yes. I wanted to do this after the PR 12:34 < BlueMatt> then you take cs_main to get the diskpos out of CBlockIndex and then lose cs_main during the actual reading 12:34 < jonasschnelli> BlueMatt: yes 12:36 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has quit [Ping timeout: 264 seconds] 12:37 -!- alreadylate [~textual@46.39.118.13] has joined #bitcoin-core-dev 12:38 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Read error: Connection reset by peer] 12:41 -!- alreadylate [~textual@46.39.118.13] has quit [Client Quit] 12:43 -!- BlueMatt [~BlueMatt@mail.bluematt.me] has joined #bitcoin-core-dev 12:43 -!- BlueMatt [~BlueMatt@mail.bluematt.me] has quit [Changing host] 12:43 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #bitcoin-core-dev 12:43 -!- tiagotrs [~tiago@unaffiliated/tiagotrs] has quit [Ping timeout: 240 seconds] 12:44 -!- lifeofguenter [~lifeofgue@bnc.pro.to.co.ls] has joined #bitcoin-core-dev 12:44 -!- asoltys [~adam@104.198.96.115] has joined #bitcoin-core-dev 12:44 -!- sdaftuar [~sdaftuar@100.38.11.146] has joined #bitcoin-core-dev 12:44 -!- sdaftuar [~sdaftuar@100.38.11.146] has quit [Changing host] 12:44 -!- sdaftuar [~sdaftuar@unaffiliated/sdaftuar] has joined #bitcoin-core-dev 12:44 -!- Netsplit over, joins: AndyS2, comboy, gijensen, zxzzt 12:45 -!- paracyst_ [paracyst@unaffiliated/paracyst] has quit [Ping timeout: 240 seconds] 12:46 < jonasschnelli> Would adding a function ReadBlockFromDiskLock() be a bad design (where the function would lock cs_main for pindex->GetBlockPos() but not for the actual reading ReadBlockFromDisk() 12:46 -!- paracyst [paracyst@unaffiliated/paracyst] has joined #bitcoin-core-dev 12:46 -!- Netsplit over, joins: dlb76 12:48 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 12:48 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 12:51 < gmaxwell> normally you'd want to push up the lock by passing in the offset so the lock acqusition can be merged into the caller grabbing cs_main for other reasons. 12:51 < gmaxwell> like to decide if it knows about the block at all. 12:52 -!- quantbot_ [~quantbot@cpe-74-73-145-69.nyc.res.rr.com] has joined #bitcoin-core-dev 12:53 -!- quantbot [~quantbot@38.101.106.141] has quit [Ping timeout: 248 seconds] 13:00 < BlueMatt> gmaxwell: I disagree 100%... 13:00 < BlueMatt> jonasschnelli: we already do, just push down the lock instead of taking it outside 13:01 -!- m8tion01 [~m8tion@81-65-53-254.rev.numericable.fr] has quit [Read error: Connection reset by peer] 13:01 < BlueMatt> gmaxwell: there are already two ReadBlockFromDisk's - one that does not require cs_main (and is often called without it), and one which does, but only for the non-disk-read part of the function 13:01 < BlueMatt> no reason to require the caller take cs_main for the whole time if they dont want to 13:01 < BlueMatt> cs_main is recursive for a reason.... 13:01 < gmaxwell> BlueMatt: you think you should take a lock to fetch a single integer, when the caller already needed the lock in the first place to get the pindex member? 13:01 -!- quantbot [~quantbot@38.101.106.141] has joined #bitcoin-core-dev 13:02 < BlueMatt> I mean that version of ReadBlockFromDisk already is barely called anywhere, iirc jonasschnelli's use-case here would be one of two places its used, and in his case you clearly *dont* want to be holding cs_main 13:02 < BlueMatt> his whole goal is to reduce its usage in this case 13:02 < gmaxwell> sure, so look up the offset when you check if the block is in the index to begin with. 13:03 < BlueMatt> well in jonasschnelli's use-case above you cant do that... 13:03 < BlueMatt> you *must* do the check after reading, when processing 13:03 < gmaxwell> okay I didn't see the usecase then 13:03 -!- gmaxwell [gmaxwell@wikimedia/KatWalsh/x-0001] has left #bitcoin-core-dev [] 13:03 -!- quantbot_ [~quantbot@cpe-74-73-145-69.nyc.res.rr.com] has quit [Ping timeout: 255 seconds] 13:03 < BlueMatt> the race in AddToWalletIfInvolvingMe in the rescan stuff is subtle af 13:04 < jonasschnelli> BlueMatt: so acquiring cs_main in ReadBlockFromDisk() just for reading CDiskBlockPos blockPos;,... right? 13:04 < jonasschnelli> Doesn't it hurt to acquire it twice for the existing use cases of ReadBlockFromDisk()? 13:04 < BlueMatt> i think thats fine 13:05 < BlueMatt> indeed 13:05 < BlueMatt> its recursive 13:05 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has joined #bitcoin-core-dev 13:07 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has joined #bitcoin-core-dev 13:09 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev 13:10 < jamesob> somewhat related question... was browsing getrawtransaction and noticed we acquire cs_main in a slightly more broad scope than necessary (though not by much) -- is it worth making a change to scope cs_main use as tightly as possible, or does it not matter so much (i.e. within the context of a single rpc call)? 13:10 -!- agileDeveloper [~Mohamed@178.162.197.145] has joined #bitcoin-core-dev 13:10 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has quit [Ping timeout: 264 seconds] 13:10 -!- agileDeveloper [~Mohamed@178.162.197.145] has quit [Client Quit] 13:11 < jonasschnelli> jamesob: I think it would be worth... though ask BlueMatt, he is actually working on optimising concurrency 13:13 < jamesob> also, is there somewhere we're having an ongoing discussion about splitting cs_main into separate read & write locks? 13:13 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has joined #bitcoin-core-dev 13:14 -!- Kozuch [~Kozuch@81.0.198.168] has joined #bitcoin-core-dev 13:14 < BlueMatt> jamesob: I mean looks like getrawtransaction only acquires it too broadly for like the parsing of two parameters, dunno if thats worth it...for something where you hit disk or are parsing a huge map and have a ton of logic it'd probably be worth it, but no need to create review burden to avoid holding cs_main for a ParseHashV... 13:14 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has quit [] 13:14 < jamesob> BlueMatt: yup, makes sense 13:15 < BlueMatt> jamesob: heh, I dont think cs_main has made much progress of late....I think most of the curren progress is on making things use cs_main less 13:16 < BlueMatt> I think the generally-accepted goal is for things to have their own "view" of the chain - eg wallet probably can/should start doing checks on a cached/validationinterface-updated chainActive.Tip() instead of ever locking cs_main to query for the current validation state 13:16 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 13:16 < BlueMatt> same goes for other subsystems 13:16 < BlueMatt> but its a long road ahead...I think we may be not too far off on wallet in my brief glancing a few weeks ago when sipa was saying we should do it sooner rather than later, but I dunno if anyone's tried to implement it 13:16 < BlueMatt> gonna be lots of corner cases either way, I'm sure 13:17 < BlueMatt> also working on (very slowly) migrating CNodeState out of cs_main, but I havent picked that work up in a while due to number of outstanding prs :/ 13:17 < jamesob> yeah, that sounds like the right way to go. definitely easier to make gradual changes that way instead of having to (delicately) modify cs_main itself. 13:18 < BlueMatt> exactly 13:18 < BlueMatt> I mean the other (obvious) thing is to make, as you suggested, cs_main a read/write/upgrade lock so that simple things like reading CBlockIndex->nStatus dont require a full cs_main global lock 13:18 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has quit [Ping timeout: 264 seconds] 13:19 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has joined #bitcoin-core-dev 13:19 < BlueMatt> just doing that for CBlockIndex fields feels like it'd be helpful (see, eg, the above discussion about needing cs_main for ReadBlockFromDisk....), but also not something I've tried to do in like 5 years, dunno if anyone else has 13:25 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has quit [Quit: DrFeelGood] 13:28 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 13:29 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has quit [Remote host closed the connection] 13:31 < ossifrage> Did changing the wallet passphrase stop dumping the keypool in 0.15.x? I just changed the passphrase but keypoololdest is still old? 13:34 < BlueMatt> did it ever dump the keypool? 13:35 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has joined #bitcoin-core-dev 13:35 -!- saint_ [~saint_@unaffiliated/saint-/x-0540772] has joined #bitcoin-core-dev 13:36 * BlueMatt sees no evidence that it did in 0.13.2 13:38 < ossifrage> BlueMatt, okay, I guess I had bad information, someone told me that it discarded the keypool when you changed the passphrase as a security feature. 13:39 < BlueMatt> it does when you *first encrypt* (I'm 90% sure) 13:39 < BlueMatt> changing, I do not believe so 13:40 < ossifrage> Ah yeah, my wallet was unencrypted before that 13:41 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 13:41 < ossifrage> So I'm stuck calling getnewaddress 980 times :-( 13:41 < instagibbs> It should only throw away your master privkey on first encryption, yes 13:42 < instagibbs> I have not tested that sequence myself however 13:42 -!- mrfrasha_ [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Ping timeout: 272 seconds] 13:42 < BlueMatt> ossifrage: heh, 980? thats not too bad...I had to do like 99k recently...that took a while 13:43 < ossifrage> I basically want to get an address that is not in my backups 13:43 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Quit: .] 13:47 < ossifrage> My poor 'receiving addresses list' is already painfully long as it is (mostly with discarded/unused addresses) 13:47 < BlueMatt> getrawchangeaddress intead, I think 13:48 < luke-jr> I thought it discarded keypool on change passphrase also 13:48 -!- eck [~eck@fsf/member/eck] has quit [Quit: we out here] 13:49 < ossifrage> luke-jr, I changed the passphrase and keypoololdest is 109 days old 13:49 < ossifrage> which is about when I initially set the passphrase 13:49 < sipa> changing your passphrase doesn't change your masterkey, though 13:50 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has joined #bitcoin-core-dev 13:50 -!- quantbot_ [~quantbot@38.101.106.141] has joined #bitcoin-core-dev 13:50 < luke-jr> sipa: no? 13:52 < luke-jr> hmm 13:53 < luke-jr> is there a reason not to? 13:54 -!- quantbot [~quantbot@38.101.106.141] has quit [Ping timeout: 256 seconds] 13:54 < BlueMatt> yea..not having to re-encrypt everything 13:55 -!- quantbot_ [~quantbot@38.101.106.141] has quit [Ping timeout: 272 seconds] 13:56 < Randolf> In comparison, TrueCrypt works this way -- re-encrypting the whole hard drive every time the user wanted to change their boot-password would be very time-consuming. 13:56 < luke-jr> why would you need to reencrypt everything, just to add a new master key? 13:56 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 13:57 < BlueMatt> luke-jr: how in the hell would you do it otherwise? 13:57 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 13:57 < ossifrage> My goal was to invalidate my backup for new transactions without loosing the history/metadata 13:57 < luke-jr> BlueMatt: SetHDMasterKey(GenerateNewHDMasterKey())? 13:58 < sipa> luke-jr: the encryption master key, not the hd master key 13:58 < luke-jr> oh 13:58 < BlueMatt> luke-jr: we're not talking about HD master key 13:58 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 13:58 < ossifrage> In my case it is *not* a HD wallet (I think it predates the HD stuff) 13:58 < luke-jr> I was XD 13:58 < sipa> rotating out the hd master key is something we should support, but it can be orthogonal to the encryption question 13:59 < BlueMatt> ossifrage: yes, I think over time we need to support that use-case by upgrading to hd then letting people rotate the hd seed and optioanlly flush keypool at that time 13:59 < BlueMatt> #11085 13:59 < gribble> https://github.com/bitcoin/bitcoin/issues/11085 | Add sethdseed RPC to initialize or replace HD seed. by dooglus · Pull Request #11085 · bitcoin/bitcoin · GitHub 13:59 < sipa> yah 14:00 < ossifrage> Is there a way to 'decrypt' the wallet so I can reencrypt it and dump the keypool? 14:00 < luke-jr> I don't think so 14:00 < BlueMatt> not atm 14:00 < BlueMatt> i mean you can also hack in your own rpc that empties keypool 14:00 < BlueMatt> in one db batch 14:00 < BlueMatt> which would make it faster 14:02 < ossifrage> The 'receiving address list' UI is already insanely long, adding another 960 entries will suck 14:04 < luke-jr> [21:48:00] getrawchangeaddress intead, I think 14:06 -!- JackH [~laptop@cbg156.neoplus.adsl.tpnet.pl] has joined #bitcoin-core-dev 14:06 < ossifrage> luke-jr, yeah, that might work until I forget to do it 14:06 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has quit [] 14:07 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Quit: conversation terminated!] 14:09 < ossifrage> getrawchangeaddress caused keypoolsize to go down by 1 14:09 -!- cryptapus [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev 14:09 -!- cryptapus [~cryptapus@jupiter.osmus.org] has quit [Changing host] 14:09 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 14:09 -!- Solrac [052a8246@gateway/web/freenode/ip.5.42.130.70] has joined #bitcoin-core-dev 14:10 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Quit: .] 14:12 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 14:12 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 14:13 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 276 seconds] 14:13 < ossifrage> and 'bitcoin-cli listreceivedbyaddress 0 true | jq .[].address | grep ' does not return the address 14:15 < sipa> by definition transaction outputs to a change address are not treated as incoming payments 14:16 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 14:16 < ossifrage> sipa, ok yeah... but the getrawchangeaddress comes from the keypool 14:16 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 14:17 < sipa> yes? 14:17 < sipa> i don't understand what you're expecting 14:17 -!- LeMiner [LeMiner@unaffiliated/leminer] has joined #bitcoin-core-dev 14:18 < ossifrage> Ah, I understand now, use getrawchangeaddress 980 times to discard the old keys... duh 14:18 < sipa> it will only discard change keys 14:19 -!- Solrac [052a8246@gateway/web/freenode/ip.5.42.130.70] has quit [Ping timeout: 260 seconds] 14:19 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 248 seconds] 14:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood] 14:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 14:20 -!- Kozuch [~Kozuch@81.0.198.168] has quit [Ping timeout: 272 seconds] 14:22 -!- saint_ [~saint_@unaffiliated/saint-/x-0540772] has quit [Ping timeout: 264 seconds] 14:24 -!- tiagotrs [~tiago@p5DC47F60.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 14:24 -!- tiagotrs [~tiago@p5DC47F60.dip0.t-ipconnect.de] has quit [Changing host] 14:24 -!- tiagotrs [~tiago@unaffiliated/tiagotrs] has joined #bitcoin-core-dev 14:33 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Read error: Connection reset by peer] 14:33 -!- eck [~eck@fsf/member/eck] has joined #bitcoin-core-dev 14:33 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 14:42 -!- eck [~eck@fsf/member/eck] has quit [Quit: we out here] 14:44 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 246 seconds] 14:44 -!- eck [~eck@fsf/member/eck] has joined #bitcoin-core-dev 14:45 -!- shesek [~shesek@bzq-84-110-232-125.cablep.bezeqint.net] has joined #bitcoin-core-dev 14:45 -!- shesek [~shesek@bzq-84-110-232-125.cablep.bezeqint.net] has quit [Changing host] 14:45 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 14:47 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has joined #bitcoin-core-dev 14:50 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 14:50 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 14:56 -!- herzmeister[m] [herzmeiste@gateway/shell/matrix.org/x-wxfqofyahkfjinau] has quit [Ping timeout: 240 seconds] 14:57 -!- herzmeister[m] [herzmeiste@gateway/shell/matrix.org/x-uhlzljdsmjtjtrbr] has joined #bitcoin-core-dev 14:58 < ossifrage> Okay calling getrawchangeaddress 980 times did what I wanted, it consumed all the keys in the (non HD) keypool without bloating the 'receiving address' list. 14:58 < ossifrage> Now both getrawchangeaddress and getnewaddress fail with "Error: Keypool ran out, please call keypoolrefill first" as expected 14:59 < luke-jr> that's convenient 15:00 < ossifrage> I wanted to invalidate my backups without loosing the history that goes back to 2011 15:01 < ossifrage> BlueMatt, thanks! 15:14 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-fvmxnsrfoelqekle] has joined #bitcoin-core-dev 15:15 -!- pkx2 [~pkx@unaffiliated/pkx] has quit [Remote host closed the connection] 15:15 < bitcoin-git> [bitcoin] jonasschnelli opened pull request #11892: [Qt] Warn if fallback fee has been used (master...2017/12/qt_warn_fallbackfee) https://github.com/bitcoin/bitcoin/pull/11892 15:18 -!- gmaxwell [gmaxwell@wikimedia/KatWalsh/x-0001] has joined #bitcoin-core-dev 15:19 < gmaxwell> We might actually be running low on sockets on the network, not critically so, but low none the less. 15:19 < gmaxwell> I am seeing multiple nodes with all or nearly all inbound sockets in use, and it doesn't appear at first analysis to be a connect flood attack. 15:20 -!- unholymachine [~quassel@c-69-248-123-139.hsd1.nj.comcast.net] has quit [Ping timeout: 264 seconds] 15:20 -!- unholymachine [~quassel@c-69-248-123-139.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 15:23 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 15:25 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 15:25 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 15:28 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 15:30 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 15:31 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 15:35 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 15:38 -!- bityogi [~textual@208-104-132-26.brvd.dsl.dyn.comporium.net] has quit [Read error: Connection reset by peer] 15:44 -!- alreadylate [~textual@customer-46-39-118-13.stosn.net] has quit [] 15:46 < jonasschnelli> gmaxwell: due to a lot of peers in IBD? Or plenty of SPV? 15:57 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Ping timeout: 268 seconds] 15:57 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 15:57 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host] 15:57 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 15:57 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Ping timeout: 264 seconds] 16:05 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 16:05 -!- PaulCapestany [~PaulCapes@68.100.207.91] has joined #bitcoin-core-dev 16:06 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 16:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 16:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 16:17 -!- grondon [uid267547@gateway/web/irccloud.com/x-hfmsjtmbwhncxnji] has quit [Quit: Connection closed for inactivity] 16:26 -!- tiagotrs [~tiago@unaffiliated/tiagotrs] has quit [Quit: leaving] 16:28 -!- Deacydal [~Deacyde@unaffiliated/deacyde] has quit [Ping timeout: 255 seconds] 16:28 -!- B_ [3ba7c24c@gateway/web/freenode/ip.59.167.194.76] has joined #bitcoin-core-dev 16:29 -!- B_ [3ba7c24c@gateway/web/freenode/ip.59.167.194.76] has quit [Client Quit] 16:34 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 16:36 -!- Randolf [~randolf@24.244.32.245] has joined #bitcoin-core-dev 16:38 -!- saint_ [~saint_@unaffiliated/saint-/x-0540772] has joined #bitcoin-core-dev 16:39 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 16:40 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Client Quit] 16:41 -!- Randolf [~randolf@24.244.32.245] has quit [Ping timeout: 256 seconds] 16:42 -!- Randolf [~randolf@S010624a43c939027.vf.shawcable.net] has joined #bitcoin-core-dev 16:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 256 seconds] 16:43 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 16:56 -!- PaulCapestany [~PaulCapes@68.100.207.91] has quit [Ping timeout: 256 seconds] 16:56 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 255 seconds] 17:00 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 17:01 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 17:02 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 17:06 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 17:06 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 17:06 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 17:19 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Quit: .] 17:19 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 17:20 -!- To7 [~theo@68.129.242.238] has joined #bitcoin-core-dev 17:24 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 17:24 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 17:25 -!- Nobody_ [8ee7070d@gateway/web/freenode/ip.142.231.7.13] has joined #bitcoin-core-dev 17:26 < Nobody_> Please update Satoshi Nakamoto & The Bitcoin Core Developers that the Blockchain is complete and Copyright Free for this Holiday Season 17:26 < Nobody_> I will not reveil my Identity but things work in wonderful ways 17:27 < promag> nice, ty 17:27 < Nobody_> Here is for those group(s) and anyone who made a Cryptocurrency, never having to worry about it not being protected 17:27 < Nobody_> Blockchain ECDSA Public Key (Bitcoin Compatible): 15oZ3FrhQJsVnpT6Ho1ZrQFQRnaaZF9gdS exists since Wed Oct 11 2017 19:09:57 GMT-0700 (Pacific Summer Time) Hash (In HEX) SHA3-384 23b81d863e9607f3416d14cb5913ee4e83cc7bf32ae3a6fab12c53e741ac7dda028c3dcc1d25950bb2f1122cacba10ba SHA3-512 cc7240e11c025e2411630ba97e2e7cf59aa684823a147d1a3972d7b4eaf3019af7d8c25dcb25a6c25cd7b5b9b7f72c944b0fd6e7bda4aa365f036cc4a188fc65 HMAC (In 17:27 < Nobody_> magnet:?xt=urn:btih:0539a6634c7f87f17788767b3a3c250ddaa4cde2&dn=Blockchain+updated.txt&tr=wss%3A%2F%2Ftracker.btorrent.xyz&tr=wss%3A%2F%2Ftracker.fastcast.nz&tr=wss%3A%2F%2Ftracker.openwebtorrent.com 17:27 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Quit: .] 17:27 < Nobody_> Hash: 0539a6634c7f87f17788767b3a3c250ddaa4cde2 17:28 < Nobody_> HMAC (In HEX) Encrypted SHA3-384 00bed720e4ecd0897297c5b3f583d9567a19b2e9952c0a40fdd0bf24ae99093cfe27a3b433ca2b964a1a607c0dfb8b91 Encrypted SHA3-512 97013026b80c0a190e3591c42b3a75cce484a420d7f2305c28d6a1a7a937229d49aab88cb4d5aa90548df98eda2b699007bb5fae24e2485ec9fb0c0a1e685b41 17:30 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 17:30 < sipa> Nobody_: i have the impression you're trying to be nice, so i don't want to yell at you, but i have no clue what you're trying to say 17:31 < Nobody_> I truely am Nobody in the system and as the Court of Japan ruled, Nobody own's the Cryptocurrency as Nobody own's the Blockchain so enjoy your holiday ok? make it the Perfect Greatest you ever could have! ;) 17:31 < Nobody_> With even a bit of love from God 17:31 < Nobody_> No Joke! 17:31 -!- Randolf [~randolf@S010624a43c939027.vf.shawcable.net] has quit [Ping timeout: 264 seconds] 17:31 < sipa> ok, thank you! 17:31 < Nobody_> Hahaha 17:31 < Nobody_> Time to leave, have a great one and that magnet link will download if you need it 17:32 < Nobody_> https://btorrent.xyz/#0539a6634c7f87f17788767b3a3c250ddaa4cde2 17:32 < gribble> https://github.com/bitcoin/bitcoin/issues/0539 | Qt GUI updates by laanwj · Pull Request #539 · bitcoin/bitcoin · GitHub 17:32 < Nobody_> blob:https://btorrent.xyz/427f6751-7950-476d-84a3-693924bb02bc 17:32 < sipa> please don't expect people to download things from random lins 17:33 < Nobody_> Time to leave, please as we already added the Faucet in the Bitcoin Core make sure it is finalized 17:33 < Nobody_> it is crutial for the Robot's to request from Nobody 17:33 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Client Quit] 17:33 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 17:33 < Nobody_> it is a Free Faucet that you can deposit, withdraw or transact to a Nobody account in the Core that allow's for a Savings like Wallet 17:33 < mryandao> quick question: does bitcoin 0.7.0rc3 also build a qt GUI interface? 17:33 < Nobody_> for Everyone to use 17:34 < sipa> mryandao: you certainly can 17:34 < sipa> mryandao: Qt GUI was added in 0.5.0 17:34 < Nobody_> Other than that, Ten Four, Over and Out! 17:34 -!- Nobody_ [8ee7070d@gateway/web/freenode/ip.142.231.7.13] has quit [] 17:34 < mryandao> can we also ban the spammer. 17:34 < mryandao> oh, he left. 17:36 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 17:37 < jimpo> Is there is a way to see debug logs generated during tests? And even better in tests running on Travis? 17:39 < sipa> you can call the functional tests .py file with an argument to not clean up the testdir 17:39 < sipa> --nocleanup 17:39 < jimpo> For unit tests 17:40 < jimpo> stdout seems to be suppressed 17:41 -!- jamesob [~james@199.230.10.198] has quit [Ping timeout: 256 seconds] 17:45 -!- xmsx [4e24bd68@gateway/web/freenode/ip.78.36.189.104] has joined #bitcoin-core-dev 17:46 < xmsx> Quick question -- can I import P2SH-P2WPKH address using importmulti? 17:46 < sipa> no 17:46 < xmsx> What RPC should I use for it? 17:47 < sipa> import the private key however you want, and then call addwitnessaddress 17:47 < sipa> the wallet just doesn't support segwit addresses natively yet 17:47 < xmsx> addwitnessaddress doesn't rescan the blockchain :'( 17:47 < sipa> you can call rescanblockchain manually 17:48 < sipa> not saying all of this is ideal; none of it should be necessary (and soon won't) 17:49 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev 17:49 < xmsx> So we'll be able to use importmulti for segwit soon? 17:49 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-vabvxrinxehuevvt] has quit [Quit: Connection closed for inactivity] 17:50 < xmsx> Atm it imports the address as watch only :( 17:50 < sipa> yes 17:50 < sipa> next release 17:50 < sipa> (with high probability; unexpected events can always change release plans) 17:50 < xmsx> Yay, any ETA by any chance? 17:51 < sipa> no 17:51 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 17:51 < xmsx> Nvm, thanks a lot for your hard work anyway :) 17:52 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 17:52 < sipa> thanks! 17:55 < xmsx> Another question from newb -- is there a way to find out the block height by timestamp?:) 17:59 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 18:02 -!- CubicEarth [~cubiceart@xdsl-31-164-85-6.adslplus.ch] has quit [] 18:05 -!- ederfdias [bd128d67@gateway/web/freenode/ip.189.18.141.103] has joined #bitcoin-core-dev 18:06 -!- gaf_ [~fag@12.smos-linux.org] has quit [Ping timeout: 246 seconds] 18:07 -!- ederfdias [bd128d67@gateway/web/freenode/ip.189.18.141.103] has quit [Client Quit] 18:10 -!- gaf_ [~fag@12.smos-linux.org] has joined #bitcoin-core-dev 18:13 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 18:18 < promag> xmsx: iirc no 18:20 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 18:20 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 18:29 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Quit: .] 18:31 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 18:36 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 18:36 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 18:36 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 18:36 -!- bsm117532 [~mcelrath@104.129.204.130] has joined #bitcoin-core-dev 18:36 -!- [b__b] [~b__b]@ec2-54-85-45-223.compute-1.amazonaws.com] has joined #bitcoin-core-dev 18:36 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 18:36 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 18:36 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has joined #bitcoin-core-dev 18:36 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 18:36 -!- edman80 [~edman80@pool-173-70-115-60.nwrknj.fios.verizon.net] has joined #bitcoin-core-dev 18:36 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev 18:36 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 18:36 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Max SendQ exceeded] 18:37 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 18:37 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 18:37 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 18:40 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Ping timeout: 240 seconds] 18:41 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 18:56 < promag> how long 'make -j5 check VERBOSE=1' usually takes on your machine? anyone? 18:59 < sipa> from scratch? with ccache? 18:59 -!- lnostdal [~lnostdal@62.90-149-73.nextgentel.com] has quit [Ping timeout: 260 seconds] 18:59 < promag> from scratch? without ccache.. 19:02 < xmsx> Do I have to use Bech32, or using P2SH-P2WPKH is ok for now? 19:03 -!- freeark1 [75e36443@gateway/web/freenode/ip.117.227.100.67] has joined #bitcoin-core-dev 19:03 < luke-jr> xmsx: you don't have to use anything. you can even use p2pk if you really want to. 19:04 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Ping timeout: 255 seconds] 19:04 -!- bule2 [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 19:05 < xmsx> I really want to stay on bleeding edge :D 19:05 < sipa> xmsx: at this point, the bitcoin core wallet does not fully support segwit - you can use the addwitnessaddress approach at your own risk 19:05 < luke-jr> xmsx: well then you should just use Lightning :p 19:05 < sipa> if you want bleeding edge, try running with https://github.com/bitcoin/bitcoin/pull/11403 19:06 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 19:06 < sipa> promag: benchmarking 19:06 < promag> sipa: ah thanks 19:07 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds] 19:07 < promag> sipa: but it turns out I had a deadlock 19:07 < sipa> what do you want? a 4-core i7 system, an 8-core AMD Ryzen, or a 14-core Xeon v3? 19:08 < luke-jr> 16-core POWER9 system? <.< 19:08 < xmsx> What's the best software for LN? should I use eclair? 19:08 < promag> heh i5 19:08 < luke-jr> xmsx: if you're not *writing* software, you should really be asking in #bitcoin 19:08 < promag> luke-jr: sup? 19:08 < luke-jr> promag: ? 19:08 < promag> luke-jr: multiwallet gui :D 19:09 < luke-jr> sorry, tied up with high priority RL stuff lately :/ 19:09 < xmsx> I'm a backend developer, so I am kinda writing stuff :) 19:09 < luke-jr> maybe I'll take a break and update multiwallet gui.. 19:09 < promag> np +1 19:09 < sipa> xmsx: right, but this channel is about bitcoin core's development 19:09 < sipa> you're welcome to ask here how things work, or discuss related things 19:09 < sipa> but questions about usage really don't belong here 19:10 < xmsx> Kk, got it, thanks :) 19:12 < sipa> promag: on 8-core AMD Ryzen: 19:12 < sipa> real 3m28.787s 19:12 < sipa> user 43m10.276s 19:12 < promag> thanks 19:14 -!- sanada [~bitktn@36-2-119-80.chiba.ap.gmo-isp.jp] has joined #bitcoin-core-dev 19:15 -!- freeark1 [75e36443@gateway/web/freenode/ip.117.227.100.67] has quit [Quit: Page closed] 19:16 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 19:22 -!- lnostdal [~lnostdal@62.90-149-73.nextgentel.com] has joined #bitcoin-core-dev 19:22 -!- archaeal [62ce095e@gateway/web/freenode/ip.98.206.9.94] has quit [Ping timeout: 260 seconds] 19:24 -!- bule2 [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 19:25 -!- bule2 [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 19:35 < luke-jr> k, #11383 rebased & comments addressed 19:35 < gribble> https://github.com/bitcoin/bitcoin/issues/11383 | Basic Multiwallet GUI support by luke-jr · Pull Request #11383 · bitcoin/bitcoin · GitHub 19:35 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Remote host closed the connection] 19:36 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 19:36 -!- archaeal [62ce095e@gateway/web/freenode/ip.98.206.9.94] has joined #bitcoin-core-dev 19:36 < promag> is fee estimation an activity? like it should show up in the activity window while it's not ready? 19:37 < promag> luke-jr: k 19:38 < sipa> promag: that's maybe a useful way to present it 19:38 < sipa> though it's not actually acitivity as in doing something - it just needs enough data 19:38 < sipa> so perhaps you can call it 'gather data for fee estimation' 19:38 < promag> waiting is an activity :D 19:39 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has joined #bitcoin-core-dev 19:39 < promag> or that 19:39 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Remote host closed the connection] 19:39 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 19:40 -!- quantbot_ [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 19:40 < promag> I like that 19:41 < fanquake> I'm going to delete the "help me hard fork bitcoin for $500" comments and lock the threads they've been posted on. Seem to be kind of alt-coin related anyway. 19:42 < sipa> fanquake: thanks 19:46 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-fvmxnsrfoelqekle] has quit [Quit: Connection closed for inactivity] 19:50 -!- furusato [ca55338d@gateway/web/freenode/ip.202.85.51.141] has joined #bitcoin-core-dev 19:54 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has quit [Ping timeout: 256 seconds] 19:55 -!- bule2 [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 19:55 -!- _parts_ is now known as _parts 19:55 -!- bule2 [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 19:56 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has joined #bitcoin-core-dev 19:57 -!- furusato [ca55338d@gateway/web/freenode/ip.202.85.51.141] has quit [Ping timeout: 260 seconds] 20:10 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 20:11 -!- quantbot_ [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Remote host closed the connection] 20:12 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 20:15 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 264 seconds] 20:16 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Ping timeout: 240 seconds] 20:21 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ejacnovcrxycfqcz] has joined #bitcoin-core-dev 20:26 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ejacnovcrxycfqcz] has quit [Ping timeout: 240 seconds] 20:36 -!- mrfrasha_ [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 20:40 -!- bule2 [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds] 20:40 -!- derrekito [~derrekito@cpe-65-29-218-61.cinci.res.rr.com] has joined #bitcoin-core-dev 20:42 -!- mrfrasha_ [~mrfrasha@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Read error: Connection reset by peer] 20:42 -!- mrfrasha_ [~mrfrasha@66.188.250.34] has joined #bitcoin-core-dev 20:43 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-oodyvsjjqfchmyec] has joined #bitcoin-core-dev 20:57 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 20:58 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 21:10 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 21:10 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 21:31 -!- Squidicuz [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has quit [Ping timeout: 240 seconds] 21:31 -!- Squidicc [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 21:36 -!- saint_ [~saint_@unaffiliated/saint-/x-0540772] has quit [Quit: UNIVERSE CORRUPTED. REBOOT (Y/N) ?] 21:59 -!- To7 [~theo@68.129.242.238] has quit [Quit: Whatever ... bye] 22:03 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has quit [Ping timeout: 240 seconds] 22:04 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds] 22:05 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has joined #bitcoin-core-dev 22:06 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has quit [Remote host closed the connection] 22:08 < jonasschnelli> [17:12:01] promag: on 8-core AMD Ryzen: 22:08 < jonasschnelli> sipa: you are working on a desktop? 22:10 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 22:10 < sipa> jonasschnelli: via ssh 22:11 < jonasschnelli> sipa: heh... yes. I also use a ssh remote build script when I'm on low battery but high bandwidth. 22:15 < sipa> jonasschnelli: no, i don't generally don't build remotely 22:15 < sipa> i just ssh'ed into my desktop 22:15 < sipa> and compiled there 22:15 < jonasschnelli> Yeah.. makes sense... 22:15 < sipa> usually i build just on my laptop 22:16 < jonasschnelli> compiling is just a battery drainer... 22:18 < sipa> i have a power socket nearby :) 22:21 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 248 seconds] 22:29 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has joined #bitcoin-core-dev 22:29 < jonasschnelli> I think it's a travelers work from non-home location problem. :) 22:40 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-oodyvsjjqfchmyec] has quit [Quit: Connection closed for inactivity] 22:44 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-lrygtttfzqivkntj] has joined #bitcoin-core-dev 22:44 -!- jadee_ [~Jadee@50-248-173-75-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 22:49 -!- _jadeeUnix [~Mutter@pool-173-63-207-238.nwrknj.fios.verizon.net] has joined #bitcoin-core-dev 22:49 < _jadeeUnix> . 22:50 -!- _jadeeUnix [~Mutter@pool-173-63-207-238.nwrknj.fios.verizon.net] has quit [Client Quit] 22:51 -!- _jadeeUnix [~Mutter@pool-173-63-207-238.nwrknj.fios.verizon.net] has joined #bitcoin-core-dev 22:51 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-lrygtttfzqivkntj] has quit [Ping timeout: 240 seconds] 22:59 -!- _jadeeWeb [32f8ad4b@gateway/web/freenode/ip.50.248.173.75] has joined #bitcoin-core-dev 22:59 -!- _jadeeWeb [32f8ad4b@gateway/web/freenode/ip.50.248.173.75] has left #bitcoin-core-dev [] 23:00 -!- _jadeeUnix [~Mutter@pool-173-63-207-238.nwrknj.fios.verizon.net] has quit [Quit: Mutter: www.mutterirc.com] 23:08 -!- Randolf [~randolf@96.53.47.42] has quit [Quit: https://www.randolfrichardson.com/] 23:17 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 23:22 -!- go1111111 [~go1111111@gateway/vpn/privateinternetaccess/go1111111] has joined #bitcoin-core-dev 23:31 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has quit [Ping timeout: 240 seconds] 23:32 -!- Cogito_Ergo_Sum [~Myself@80.107.151.135] has joined #bitcoin-core-dev 23:32 -!- Cogito_Ergo_Sum [~Myself@80.107.151.135] has quit [Changing host] 23:32 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 23:42 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has joined #bitcoin-core-dev 23:47 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 23:48 -!- SopaXorzTaker is now known as Xanukkah 23:50 < jonasschnelli> luke-jr: a complete UTXO scan with sweepprivkeys takes ~3mins on my machine (mainnet)... is there a nice way to show progress? 23:50 < jonasschnelli> (probably not with RPC) 23:56 -!- jadee_ [~Jadee@50-248-173-75-static.hfc.comcastbusiness.net] has quit [Quit: This computer has gone to sleep] 23:56 -!- jadee_ [~Jadee@50.248.173.75] has joined #bitcoin-core-dev 23:56 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-hepmstwikhajqboh] has joined #bitcoin-core-dev 23:56 -!- jadee_ [~Jadee@50.248.173.75] has quit [Client Quit] 23:57 -!- jadee_ [~Jadee@50-248-173-75-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 23:57 -!- jadee_ [~Jadee@50-248-173-75-static.hfc.comcastbusiness.net] has quit [Client Quit] 23:57 -!- jadee_ [~Jadee@50-248-173-75-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 23:58 -!- jadee_ [~Jadee@50-248-173-75-static.hfc.comcastbusiness.net] has quit [Client Quit]