--- Day changed Wed Dec 06 2017 00:05 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 00:05 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 00:05 -!- michagogo [uid14316@wikia/Michagogo] has quit [Read error: Connection reset by peer] 00:06 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Ping timeout: 250 seconds] 00:06 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 00:06 -!- michagogo [uid14316@wikia/Michagogo] has joined #bitcoin-core-dev 00:11 -!- nejon [uid38993@gateway/web/irccloud.com/x-ktjyaqfajnicfjsi] has quit [Ping timeout: 240 seconds] 00:14 < kabaum> Why are the sequence of other inputs zeroed when signing an input with SIGHASH_NONE or SIGHASH_SINGLE? 00:14 -!- nejon [uid38993@gateway/web/irccloud.com/x-dnulivtkbpjlbzyu] has joined #bitcoin-core-dev 00:16 -!- eck [~eck@fsf/member/eck] has quit [Quit: we out here] 00:16 -!- roadcrap [~roadcrypt@unaffiliated/roadcrap] has joined #bitcoin-core-dev 00:16 -!- eck [~eck@fsf/member/eck] has joined #bitcoin-core-dev 00:18 -!- eck [~eck@fsf/member/eck] has quit [Client Quit] 00:18 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 00:19 -!- JackH [~laptop@212.78.169.180] has joined #bitcoin-core-dev 00:19 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 00:35 < GAit> jonasschnelli: isnt the jetson just some arm board with some reasonably powerful gpu for opencl/cuda? most use cases ive seen involved opencv 00:38 < jonasschnelli> GAit: it's just a SOC. You either need the dev kit or your custom ext. 00:38 < jonasschnelli> GAit: The GPU power would go pretty much unused for a full node. 00:39 < jonasschnelli> GAit: but the CPU, SATA feature and memory would make it a good choice for a full node in a bbox 00:40 < jonasschnelli> But a custom board with LAN, I2C for a little b/w screen, SATA/SSD, etc. would something that would have to been built 00:42 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 00:43 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 00:43 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 00:50 < GAit> jonasschnelli: maybe lemaker banana pro, has eth, has sata, doesn't have the powerful gpu but we don't need that. Otherwise x86 the apu2c4 isn't too bad (maybe a bit old nowdays) 00:52 < GAit> non that many boards out there with sata and decent amounts of ram unfortunately 00:53 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 00:55 -!- timothy [~tredaelli@redhat/timothy] has quit [Remote host closed the connection] 00:55 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 00:56 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:02 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 01:03 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 01:06 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 268 seconds] 01:07 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-lmffeyinuciozanc] has joined #bitcoin-core-dev 01:10 -!- DvdKhl [~Arokh@ip-37-201-210-118.hsi13.unitymediagroup.de] has quit [Ping timeout: 248 seconds] 01:12 -!- noglar_ [~cl0uding@62.43.144.42.dyn.user.ono.com] has quit [Ping timeout: 260 seconds] 01:13 -!- noglar_ [~cl0uding@62.43.144.42.dyn.user.ono.com] has joined #bitcoin-core-dev 01:14 -!- Deacydal [~Deacyde@unaffiliated/deacyde] has joined #bitcoin-core-dev 01:17 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has quit [Ping timeout: 255 seconds] 01:23 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 01:26 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Remote host closed the connection] 01:28 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 01:30 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 01:43 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 01:43 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 01:45 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 01:46 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 01:46 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 01:51 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Killed (thomas ())] 01:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:55 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:56 -!- gurjeet [29a01a02@gateway/web/freenode/ip.41.160.26.2] has quit [Quit: Page closed] 01:58 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds] 02:19 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 248 seconds] 02:20 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 02:28 -!- booyah is now known as GeekNerd_fapping 02:29 -!- GeekNerd_fapping is now known as booyah 02:30 -!- blackbaba [~blackbaba@gateway/vpn/privateinternetaccess/blackbaba] has joined #bitcoin-core-dev 02:37 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 02:38 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 02:48 -!- blackbaba [~blackbaba@gateway/vpn/privateinternetaccess/blackbaba] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 02:57 -!- wxss [~user@46.19.137.221] has joined #bitcoin-core-dev 03:00 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 03:00 -!- ExtraCrispy [~ExtraCris@185.22.175.244] has joined #bitcoin-core-dev 03:00 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 03:03 -!- Babozor [~babozor@195.154.25.201] has joined #bitcoin-core-dev 03:05 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/5bea05bc1d17...a13e44385147 03:05 < bitcoin-git> bitcoin/master 6d2f277 Henrik Jonsson: rpcuser.py: Use 'python' not 'python2' 03:05 < bitcoin-git> bitcoin/master a13e443 Wladimir J. van der Laan: Merge #11830: rpcuser.py: Use 'python' not 'python2'... 03:05 < bitcoin-git> [bitcoin] laanwj closed pull request #11830: rpcuser.py: Use 'python' not 'python2' (master...rpcuser-py) https://github.com/bitcoin/bitcoin/pull/11830 03:10 < wumpus> jonasschnelli: thanks, agreed 03:11 < bitcoin-git> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/a13e44385147...497d0e014cc7 03:11 < bitcoin-git> bitcoin/master a5f5a2c Karl-Johan Alm: [rpc] Fix fVerbose parsing (remove excess if cases). 03:11 < bitcoin-git> bitcoin/master b167951 Karl-Johan Alm: [rpc] Allow getrawtransaction to take optional blockhash to fetch transaction from a block directly. 03:11 < bitcoin-git> bitcoin/master 434526a Karl-Johan Alm: [test] Add tests for getrawtransaction with block hash. 03:15 -!- indistylo [~indistylo@119.82.105.106] has joined #bitcoin-core-dev 03:17 -!- wxss_ [~user@176.53.23.252] has joined #bitcoin-core-dev 03:20 < promag> wumpus: yes, there are a couple of early returns taht 03:20 < promag> that happen when there is an interrupt 03:20 < promag> or something fails 03:21 -!- wxss [~user@46.19.137.221] has quit [Ping timeout: 248 seconds] 03:21 < wumpus> promag: strange, maybe the !.. is inherited from the time when that was not the case, otherwise it makes kind of little sense. Though I'm surprised that it causes a crash. 03:22 < promag> actually fRequestShutdown is checked multiple times while the block index is loaded 03:22 < wumpus> ideally returning false, even at the end of the init process, should not cause a crash. But if this works around it, fine.\ 03:22 < wumpus> yes it should be 03:22 < meshcollider> self-reminder i think we should discuss the config file situation at the meeting tomorrow, re https://github.com/bitcoin/bitcoin/pull/11829#issuecomment-349610380 03:22 < promag> crash aside, i think at that point it should return true 03:23 < wumpus> it should check that flag at any time that the process is interruptible 03:23 < wumpus> meshcollider: yep 03:23 < promag> wumpus: right, at that point it's not interruptible 03:24 < wumpus> promag: agree 03:29 -!- akar [~user@182.253.1.146] has left #bitcoin-core-dev [] 03:33 < wumpus> GAit: jonasschnelli: indeed, it seems any reasonably modern ARM board, even with a USB stick or SD card for storage, can keep up with the chain once it's synchronized. Additional i/o and CPU speed will contribute to the initial sync, and when catching up after it's been off. 03:37 < wumpus> (as well as towards serving blocks to others if you want that) 03:40 < Sentineo> yeah I am running a full node on an odroid for 7 months now 03:41 < Sentineo> and mainly the assembler optimisation helps a lot 03:46 < wumpus> we should probably consider making the assembly optimization be the default on ARM 03:46 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:ccb:77c3:dd05:df16] has joined #bitcoin-core-dev 03:51 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 03:56 < CubicEarth> sat/byte seems to have become the default way people talk about fees. What about we changing the fee selector / estimator in core to display fees in those same terms? 03:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 04:02 -!- wxss_ is now known as wxss 04:04 < wumpus> that's just a factor 100, right? 04:05 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 04:07 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Ping timeout: 240 seconds] 04:08 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 04:10 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:12 < CubicEarth> from the 'recommended' selector, yes, factor of 100. 04:12 < CubicEarth> For the custom part, there is no 'satoshi' option, and there is no 'byte' option 04:13 < wumpus> were it to be redesigned from scratch I'd agree with you. I think changing it now is too dangerous. 04:14 < wumpus> for the RPC interface people already have software that uses the current convention, for the GUI people already have the habit of entering /kb numbers, it's kind of a fight upstream to change it 04:14 < CubicEarth> because of confusion from the change? 04:14 < wumpus> yes 04:16 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev 04:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 04:17 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 258 seconds] 04:17 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 04:21 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 04:22 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-eavqfqfnyiqrvbfk] has joined #bitcoin-core-dev 04:23 < wumpus> I do agree that for new users it would be less confusing 04:24 < CubicEarth> Well, perhaps just some addition information beside what is given. 1.24291 mBTC/kB (124.291 satoshis/byte) 04:25 < CubicEarth> It's the double conversion that makes it 'harder' 04:26 < wumpus> that's ok with me 04:28 < CubicEarth> giving the extra information? 04:28 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 04:29 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 04:30 < Sentineo> yeah a conversion info would be enough I think - better than no option 04:30 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 04:30 < Sentineo> and wumpus yeah, making the asm optimisation on arm the default would be cool. It realy make noticable difference. 04:30 < wumpus> CubicEarth: yes 04:31 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 04:33 < CubicEarth> Cool! I'll see if I can follow the proper protocol on github to make the idea legit 04:35 < wumpus> I don't personally think at least that adding the information in another unit and mentioning that unit will cause confusion. The danger is mostly when entering fees (e.g. the custom fee). 04:37 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev 04:42 < luke-jr> can anyone think of a reason that might cause block=00000000000000000961eb789c07cc05be9609821e9c3e5bcc4094c332a22d4f height=383488 log2_work=83.598077 date=2015-11-14 06:58:23 to be rejected for missing/spent inputs? :/ 04:45 -!- pAcmAn113 [5b5a4600@gateway/web/freenode/ip.91.90.70.0] has joined #bitcoin-core-dev 04:47 -!- pAcmAn113 [5b5a4600@gateway/web/freenode/ip.91.90.70.0] has quit [Client Quit] 04:49 -!- pAcmAn113 [5b5a4600@gateway/web/freenode/ip.91.90.70.0] has joined #bitcoin-core-dev 04:49 -!- pAcmAn113 [5b5a4600@gateway/web/freenode/ip.91.90.70.0] has left #bitcoin-core-dev [] 04:54 < wumpus> weird? corrupted database? has 114442 confirmations so it's safe to say it should be valid 04:55 < luke-jr> yeah. user says he's having problems syncing on two different machines (TBD if it's the same height) 04:56 < wumpus> the only thing I can think of is either a corruption that happens to have excised that record (maybe in the bloom filter portion of the leveldb file?), or that it somehow was missed while writing to disk 04:57 < CubicEarth> Did they sync directly from one machine to the other? 04:57 < wumpus> or miscellaneous problems caused by malfunctioning hardware, though I'd usually expect a CRC error first 04:57 < luke-jr> CubicEarth: not sure, but that shouldn't matter 04:58 < wumpus> what version of bitcoin core? 04:58 < luke-jr> v0.14.0.0-46952c8-dirty apparently; wtf, why? 05:00 < luke-jr> he said new install, so I assumed latest.. guess I should tell him to try that 05:00 < wumpus> the 'dirty' part worries me 05:01 < wumpus> also that commit is not part of our repo 05:01 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:ccb:77c3:dd05:df16] has quit [Remote host closed the connection] 05:01 < wumpus> maybe knots? 05:01 < luke-jr> yeah, looks like it's Knots 0.14.0 05:01 < luke-jr> still old either way 05:02 < Sentineo> are the leveldb keys documented somewhere? Having hard time to find it. 05:02 < wumpus> leveldb *keys*? 05:02 < Sentineo> for the chainstate 05:02 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:ccb:77c3:dd05:df16] has joined #bitcoin-core-dev 05:02 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:ccb:77c3:dd05:df16] has quit [Remote host closed the connection] 05:02 < wumpus> ohh that kind of keys 05:02 < luke-jr> Sentineo: txdb.cpp 05:03 < wumpus> right, that one has all the (de)serialization logic and prefixes 05:04 < Sentineo> ah cool! 05:04 < Sentineo> thanks 05:06 < wumpus> if you're trying to write external troubleshooting code in python this might be of help: https://github.com/laanwj/blockdb-troubleshoot Though currently there's nothing for chainstate in there, just block indexes. 05:07 < wumpus> but it builds a leveldb python module that can be used to inspect bitcoind's files without making it incompatible, as most system leveldbs would do 05:10 < Provoostenator> CubicEarth: #11564 (I'll link to the above chat there) 05:10 < gribble> https://github.com/bitcoin/bitcoin/issues/11564 | [Qt] display fees in Sat / vByte instead of (μ/m)BTC/kB · Issue #11564 · bitcoin/bitcoin · GitHub 05:11 < wumpus> oh we already had an issue open for that, thanks Provoostenator 05:12 < Sentineo> ah even better, I am trying to understand how the db is set up, I would like to extract the fees only somehow. Right now I have an app that shows fees in real time and it kills my odroid. So I will have to create a separate db just to get the fees, as it creates too much stress on the system to RPC all inputs and compute the fee. 05:12 < bitcoin-git> [bitcoin] hkjn opened pull request #11836: Rename rpcuser.py to rpcauth.py (master...rename-rpcuser) https://github.com/bitcoin/bitcoin/pull/11836 05:13 < wumpus> be aware that the databases are not an interface, the format might change at any time, so please don't parse them in a production app 05:13 < Sentineo> not a production app, just a learning tool 05:13 < Sentineo> but goot to know 05:13 < wumpus> then it's fine 05:13 < Sentineo> RPCing would take ages, but is much safer, agree 05:14 < wumpus> RPC batching helps if you need to do a lot of queries 05:15 < wumpus> if you really need the whole utxo set, well I tried adding functionality for that once in #7759, but streaming safely seems impossible with the current http server 05:15 < gribble> https://github.com/bitcoin/bitcoin/issues/7759 | [WIP] rest: Stream entire utxo set by laanwj · Pull Request #7759 · bitcoin/bitcoin · GitHub 05:18 < wumpus> it worked more or less but there were strange intermittent issues, such as timeout while streaming 05:22 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 05:22 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 05:23 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has joined #bitcoin-core-dev 05:23 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 05:28 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 05:33 < hkjn0> re: assembler optimization for ARM, where would I find info on enabling this? 05:33 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 05:33 < hkjn0> I have a full node on baremetal armv7l, it managed to catch up on IBD eventually, but might be useful for future reference.. 05:33 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 05:34 < Sentineo> hkjn0: I have it saved, just a sec ... let me find it 05:35 < Sentineo> hkjn0: build it with ./configure --with-asm=arm --enable-experimental 05:36 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 05:36 < wumpus> that should be it ^ 05:39 < Sentineo> I could not find a documentation of it, but if you check https://github.com/bitcoin-core/secp256k1/blob/master/configure.ac#L151 it is there 05:43 < hkjn0> thanks Sentineo, I'll give it a whirl 05:45 < wumpus> the only documentation of it is in ./configure. secp256's configure at that, not bitcoin's. 05:47 -!- pops [~pops@host86-146-151-188.range86-146.btcentralplus.com] has joined #bitcoin-core-dev 05:51 < hkjn0> hm, right. so I guess that L1289-1290 in bitcoin's configure.ac would be where to pass through the config flags to secp256k1: AC_CONFIG_SUBDIRS([src/secp256k1]) 05:51 < wumpus> yes 05:52 < wumpus> I also discovered that by accident, FWIW 05:52 < wumpus> would make sense to document it somewhere though I'm not sure where 05:57 < hkjn0> yeah, I am new to some of these tools myself, but the wiring of automake/autoconf with several different projects is definitely not trivial 06:01 -!- Guest60956 [~null@contents-vnder-pressvre.mit.edu] has quit [Ping timeout: 246 seconds] 06:05 -!- JackH [~laptop@212.78.169.180] has quit [Ping timeout: 260 seconds] 06:05 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:ccb:77c3:dd05:df16] has joined #bitcoin-core-dev 06:07 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wylpslaarchyzcao] has quit [Quit: Connection closed for inactivity] 06:08 < wumpus> aj: we might do completely away with the priority labels, I don't anyone is using them for anything in practice 06:09 < wumpus> priorities really only make sense if they're discussed weekly in the meeting, and we already have a 'high priority for review' project which is what someone should be looking for if they want to do something high priority 06:09 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:ccb:77c3:dd05:df16] has quit [Ping timeout: 264 seconds] 06:10 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 06:11 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 06:11 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 06:12 -!- kabaum [~kalle@h-13-35.A163.priv.bahnhof.se] has quit [Quit: Leaving] 06:13 -!- m8tion [~m8tion@81-65-53-254.rev.numericable.fr] has quit [Quit: Leaving] 06:15 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-lmffeyinuciozanc] has quit [Quit: Connection closed for inactivity] 06:15 < aj> wumpus: makes sense 06:15 < BlueMatt> jonasschnelli: there are two ReadBlockFromDisk's - one requires cs_main to read non-const CBlockIndex fields, one does not 06:16 < bitcoin-git> [bitcoin] laanwj closed pull request #11741: Add -logdir option to control where debug.log lives (master...logdir) https://github.com/bitcoin/bitcoin/pull/11741 06:17 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #bitcoin-core-dev 06:18 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:ccb:77c3:dd05:df16] has joined #bitcoin-core-dev 06:28 -!- instagibbs [~instagibb@pool-100-15-116-35.washdc.fios.verizon.net] has quit [Ping timeout: 240 seconds] 06:30 < BlueMatt> jonasschnelli: most obvious cs_main-needing-bit: GetBlockPos reads CBlockIndex.nChainState 06:33 -!- iPhone [c9a7d7a0@gateway/web/freenode/ip.201.167.215.160] has joined #bitcoin-core-dev 06:33 -!- iPhone is now known as Guest24637 06:36 -!- instagibbs [~instagibb@pool-100-15-116-35.washdc.fios.verizon.net] has joined #bitcoin-core-dev 06:38 -!- jack_ [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 06:38 -!- Guest24637 [c9a7d7a0@gateway/web/freenode/ip.201.167.215.160] has quit [Ping timeout: 260 seconds] 06:41 -!- indistylo [~indistylo@119.82.105.106] has quit [Ping timeout: 240 seconds] 06:52 -!- mathi [b69ce3e2@gateway/web/freenode/ip.182.156.227.226] has joined #bitcoin-core-dev 06:53 -!- mathi [b69ce3e2@gateway/web/freenode/ip.182.156.227.226] has left #bitcoin-core-dev [] 06:59 -!- CubicEar_ [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has joined #bitcoin-core-dev 07:03 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:ccb:77c3:dd05:df16] has quit [Ping timeout: 255 seconds] 07:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 07:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 07:12 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-eavqfqfnyiqrvbfk] has quit [Quit: Connection closed for inactivity] 07:13 -!- whphhg [~whphhg@unaffiliated/whphhg] has quit [Quit: Leaving] 07:14 -!- whphhg [~whphhg@unaffiliated/whphhg] has joined #bitcoin-core-dev 07:15 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 07:36 < Provoostenator> I'm trying to figure out why the segwit QT wallet in #11403 doesn't show a popup when it receives a transaction. 07:37 < gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub 07:37 < Provoostenator> It should happen somewhere around here, is a row is inserted in the transaction table model: https://github.com/sipa/bitcoin/blob/e2e9ead25fe0ddb364e35f8eabb5a7f937d3973b/src/qt/walletview.cpp#L140 07:38 < Provoostenator> The transaction does show up on the Transactions screen and Overview screen. I'm assuming they use the same table, but assuming stuff is generally a bad idea :-) 07:38 < Provoostenator> What's a good practice for adding debug log statements to this area of the code? 07:40 -!- noglar_ [~cl0uding@62.43.144.42.dyn.user.ono.com] has quit [Ping timeout: 260 seconds] 07:45 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 07:51 < Provoostenator> Receiving funds on a legacy (testnet) address doesn't trigger a notification either. 07:52 -!- noglar_ [~cl0uding@62.43.144.42.dyn.user.ono.com] has joined #bitcoin-core-dev 07:53 -!- ExtraCrispy [~ExtraCris@185.22.175.244] has quit [Ping timeout: 246 seconds] 07:55 < Provoostenator> Instagibs: I wonder if this is related to the pending balance issues 07:55 < instagibbs> might be 07:55 < instagibbs> I'm seeing issues too 07:55 < Provoostenator> Maybe a transaction not getting fully commited to a db? 07:55 < instagibbs> it's entering mempool but not being applied to balance, randomly 07:55 < Provoostenator> Or some flushing thing. 07:55 < instagibbs> I don't think so 07:55 < instagibbs> my guess is the p2sh stuff is tripping up ISMINE logic somewhere 07:56 < instagibbs> confirming it makes it stick, which means it's some mempool/unconfirmed interaction 07:56 < Provoostenator> IsMine is done at the wallet level right? So are you able to produce these issues with just RPC? 07:56 < instagibbs> yep 07:57 < Provoostenator> Ok, that narrows is down a lot 07:57 < instagibbs> ok, I just sent confirmed coins from p2sh to p2sh, stopped, restarted, it's gone 07:57 < instagibbs> easy to reproduce here 07:58 < instagibbs> 2017-12-06 15:57:30 Imported mempool transactions from disk: 1 succeeded, 0 failed, 0 expired, 0 already there 07:58 < instagibbs> so it hits mempool, yet wallet is barfing 07:58 < Provoostenator> "gone" means the bug is gone? 07:58 < instagibbs> no, funds are gone from unconfirmed or confirmed 07:58 < instagibbs> i believe they should be considered confirmed, since they're from yourself 08:00 < Provoostenator> I think so too. I'm recompiling master now, but when I tried that a few days ago on master, sending to self is not shown as pending. Total balance is just reduced by fees. Presumably because the wallet is allowed to spend unconfirmed change. 08:00 < Provoostenator> However even on master, restarting changes what's displayed. I can't remember how though, will try again in a bit. 08:01 < Provoostenator> I there any way to boost compilation speed by spinning up a few EC2 nodes? 08:01 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 08:03 < Provoostenator> Back in my iOs days, this type of buggy behavior usually was a result of using the database on the wrong thread. 08:03 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #11838: qa: Add getrawtransaction in_active_chain=False test (master...Mf1712-qaRpcRawTx) https://github.com/bitcoin/bitcoin/pull/11838 08:04 < Provoostenator> But obviously it could be something completely different here. 08:07 < instagibbs> ugh, getbalance api. what a trainwreck 08:08 < instagibbs> going to debug once it re-compiled with --enable-debug... 08:08 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 08:09 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 08:14 -!- yoctopede is now known as intcat 08:15 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 08:15 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 08:16 -!- noglar_ [~cl0uding@62.43.144.42.dyn.user.ono.com] has quit [Ping timeout: 258 seconds] 08:17 -!- noglar_ [~cl0uding@62.43.144.42.dyn.user.ono.com] has joined #bitcoin-core-dev 08:21 -!- CubicEar_ [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has quit [Remote host closed the connection] 08:22 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 08:22 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 08:25 -!- pops [~pops@host86-146-151-188.range86-146.btcentralplus.com] has quit [Quit: Leaving] 08:33 < instagibbs> conclusion: unconfirmed to-self payments will never enter balance on restart, fixing 08:41 < achow101> instagibbs: is that present in current master? 08:41 < achow101> or just 11403 08:42 < instagibbs> master 08:42 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 08:42 < instagibbs> remind me again where triggering rebroadcast is done during normal operation? 08:42 < instagibbs> wallet rebroadcast* 08:42 < instagibbs> IIRc it's a signal somewhere I cannot find, heh 08:43 < achow101> https://github.com/bitcoin/bitcoin/blob/master/src/wallet/wallet.cpp#L1990 08:44 -!- wxss [~user@176.53.23.252] has quit [Quit: leaving] 08:44 < achow101> grep for ResendWalletTransactions 08:44 < instagibbs> yeah found old PR where ryanofsky thought it was unused code and tried removing it 08:44 -!- wxss [~user@176-53-23-252.turkrdns.com] has joined #bitcoin-core-dev 08:44 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 276 seconds] 08:45 < achow101> hah, lol 08:45 < instagibbs> wondering why ReacceptWalletTransactions doesn't use RelayWalletTransaction 08:45 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 08:45 < ryanofsky> heh, that was a more embarrassing pr 08:45 < instagibbs> eh, i had a hard time finding it again on my own 08:46 < instagibbs> :P 08:46 < instagibbs> I have a minimal fix for it, but wondering if we can do better. Seems brittle. 08:52 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has joined #bitcoin-core-dev 08:56 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 08:56 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has quit [Ping timeout: 240 seconds] 09:05 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 09:07 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 09:08 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:08 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 248 seconds] 09:16 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev 09:19 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 09:23 -!- DvdKhl [~Arokh@ip-37-201-210-118.hsi13.unitymediagroup.de] has joined #bitcoin-core-dev 09:36 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:38 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 09:38 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:43 -!- jamesob [~james@199.230.10.198] has joined #bitcoin-core-dev 09:44 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt] 09:47 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 09:57 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 09:59 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has joined #bitcoin-core-dev 09:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 10:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 10:03 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 248 seconds] 10:04 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has quit [Ping timeout: 252 seconds] 10:13 -!- jannes [~jannes@095-097-246-234.static.chello.nl] has joined #bitcoin-core-dev 10:16 < Provoostenator> #11839 for anyone interested 10:16 < gribble> https://github.com/bitcoin/bitcoin/issues/11839 | dont attempt mempool entry for wallet transactions on startup if alr… by instagibbs · Pull Request #11839 · bitcoin/bitcoin · GitHub 10:17 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 10:22 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 10:25 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 10:26 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 10:34 -!- ekrok [~ekrok@85.200.34.95.customer.cdi.no] has joined #bitcoin-core-dev 10:43 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 10:43 -!- ekrok [~ekrok@85.200.34.95.customer.cdi.no] has quit [Quit: Leaving] 10:44 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 10:47 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Quit: .] 10:48 < cluelessperson> is bitcoin core planning on implementing lightning built in? 10:53 < sipa> i don't know, are you? :) 10:53 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 10:59 < BlueMatt> jamesob: wait, are you seeing this on reindex 10:59 < BlueMatt> or during normal operation? 10:59 < sipa> BlueMatt: looks like reindex to me 10:59 < sipa> (it's processing blocks from 2015 in his dump) 11:00 < jamesob> yep, reindex 11:01 < BlueMatt> sipa: hmm, my rss is reliably 500MB+ more than dbcache listed in debug.log 11:01 < BlueMatt> and thats true of 0.15.1 too, afaict 11:02 < sipa> sure, but not 5GB 11:02 < BlueMatt> yea 11:02 < sipa> during early reindex it's around 300MB on top of dbcache for me on 0.15.1 11:02 < sipa> near the end of the chain it's probably a bit more 11:04 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 11:04 < hkjn0> just curious, do we currently have graphs somewhere of memory consumption / other resource usage over time for nodes built at different commits on master? 11:04 < hkjn0> even if it took many hours to gather the data and only could be done rarely (say once per day) it might limit the range of commits where a leak could sneak in.. 11:04 < BlueMatt> not afaik :/ 11:05 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 11:06 < sipa> that would be nice to have 11:06 < sipa> heap usage during reindex graphs 11:07 < sipa> as well as performance graphs 11:09 < hkjn0> cool, I'll start taking notes / hacking something up on that.. 11:09 < BlueMatt> zcash has some stuff to do that 11:09 < BlueMatt> may want to look into copying their stuff, dunno 11:10 < sipa> hkjn0: cool! 11:12 -!- saint_ [~saint_@unaffiliated/saint-/x-0540772] has quit [Quit: UNIVERSE CORRUPTED. REBOOT (Y/N) ?] 11:14 < hkjn0> right BlueMatt.. seems to be available at https://speed.z.cash/ 11:14 -!- gauravgoyal [~gauravgoy@103.227.53.68] has joined #bitcoin-core-dev 11:17 < hkjn0> hmm, maybe this is going on a tangent, but would such regular measurements that also showed IBD time be useful? or is that measured automatically somewhere? (i know people have done one-off measurements of different releases..) 11:17 < sipa> hkjn0: no, that would be awesome to have, and we currently don't have it 11:17 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 11:23 -!- gauravgoyal [~gauravgoy@103.227.53.68] has quit [Remote host closed the connection] 11:24 < jamesob> hkjn0: +1 11:25 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 11:26 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 11:28 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 11:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 11:30 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 11:31 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 11:36 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 11:36 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 11:37 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 11:37 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [] 11:38 -!- BGL [twenty@75-149-171-58-Washington.hfc.comcastbusiness.net] has quit [Read error: Connection reset by peer] 11:39 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has quit [Remote host closed the connection] 11:39 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev 11:43 -!- mesh_ [meshcollid@gateway/shell/elitebnc/x-qfmjfirebdnaqply] has quit [Ping timeout: 260 seconds] 11:43 -!- kbgg_ [Elite20763@gateway/shell/elitebnc/x-zmhlxmhgoqkkvafu] has quit [Ping timeout: 240 seconds] 11:49 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 11:50 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 11:55 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 11:55 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 255 seconds] 11:56 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Read error: Connection reset by peer] 12:07 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 12:08 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:08 -!- roadcrap [~roadcrypt@unaffiliated/roadcrap] has quit [Remote host closed the connection] 12:08 -!- Babozor [~babozor@195.154.25.201] has quit [] 12:08 < jonasschnelli> hkjn0: that would be nice. sdaftuar once mentioned that he has something like a network bypasser... 12:09 < jonasschnelli> Because you want to measure IBD without measuring the network stack 12:09 < jonasschnelli> (that would be another thing though) 12:09 < sipa> you can benchmark reindex-chainstate instead 12:11 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [] 12:13 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:16 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 12:19 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 12:26 < jonasschnelli> sipa: https://github.com/bitcoin/bitcoin/pull/11281/files#r154675029, does ReadBlockFromDisk requires cs_main? I don't think so. 12:27 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-lmhoazmpbqsocmdk] has joined #bitcoin-core-dev 12:27 < sipa> jonasschnelli: ReadBlockFromDisk itself doesn't, but reading the disk pos information from CBlockIndex does 12:28 < sipa> (as it's mutable data in case you're pruning) 12:30 -!- jannes [~jannes@095-097-246-234.static.chello.nl] has quit [Quit: Leaving] 12:31 < jonasschnelli> sipa: that means that pindex->GetBlockPos() (accessing nFile, nPos) needs cs_main? 12:31 < sipa> yes 12:32 < jonasschnelli> Oh.. then ReadBlockFromDisk should be refactored to allow the actual disk access without cs_main 12:32 -!- bordeaux_facile [~a@128.199.208.178] has quit [Ping timeout: 252 seconds] 12:33 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:33 -!- spinza [~spin@196.212.164.26] has quit [Ping timeout: 240 seconds] 12:34 -!- ajtowns[m] [ajtownsmat@gateway/shell/matrix.org/x-yvjwcjswtbfywzug] has quit [Ping timeout: 248 seconds] 12:35 -!- herzmeister[m] [herzmeiste@gateway/shell/matrix.org/x-dpxtxwltptjicagt] has quit [Ping timeout: 276 seconds] 12:35 -!- bordeaux_facile [~a@128.199.208.178] has joined #bitcoin-core-dev 12:36 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 12:38 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 12:40 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 12:40 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:42 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 12:43 -!- BGL [sixty@75-149-171-58-Washington.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 12:45 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:47 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 12:47 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 12:47 -!- noglar_ [~cl0uding@62.43.144.42.dyn.user.ono.com] has joined #bitcoin-core-dev 12:47 -!- windsok [~windsok@unaffiliated/windsok] has joined #bitcoin-core-dev 12:47 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev 12:47 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 12:47 -!- instagibbs [~instagibb@pool-100-15-116-35.washdc.fios.verizon.net] has joined #bitcoin-core-dev 12:47 -!- _flow_ [flow@2a03:4000:2:2de::1] has joined #bitcoin-core-dev 12:47 -!- helo [~helo@unaffiliated/helo] has joined #bitcoin-core-dev 12:47 -!- hsmiths [uid95325@gateway/web/irccloud.com/x-ieceermpktuwxjbq] has joined #bitcoin-core-dev 12:47 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has joined #bitcoin-core-dev 12:47 -!- PatBoy [xyz@192.99.249.194] has joined #bitcoin-core-dev 12:47 -!- harding_ [~harding@mail.dtrt.org] has joined #bitcoin-core-dev 12:47 -!- pigeons [~pigeons@androzani.sysevolve.com] has joined #bitcoin-core-dev 12:48 -!- dqx [~dqx@unaffiliated/dqx] has quit [Max SendQ exceeded] 12:49 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 12:49 < BlueMatt> jonasschnelli: there are two ReadBlockFromDisk's - one requires cs_main to read non-const CBlockIndex fields, one does not 12:49 < BlueMatt> jonasschnelli: most obvious cs_main-needing-bit: GetBlockPos reads CBlockIndex.nChainState 12:50 -!- lio17 [~bumi@ns350827.ip-37-187-174.eu] has quit [Ping timeout: 260 seconds] 12:52 -!- lio17 [~bumi@ns350827.ip-37-187-174.eu] has joined #bitcoin-core-dev 12:55 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:57 < jnewbery> aj: delayed pong 12:59 < aj> jnewbery: nice 13:00 -!- WowSuchEarlz is now known as earlz 13:00 < aj> jnewbery: i guess you've seen pr 4 on your repo now? 13:01 < jnewbery> aj: I hadn't, I'm a little behind. I'll take a look now 13:01 < aj> jnewbery: okay, well that's the content of the ping :) 13:04 < jonasschnelli> BlueMatt: thanks. Got it. will update the PR soon 13:09 -!- spinza [~spin@196.212.164.26] has joined #bitcoin-core-dev 13:09 -!- gaf_ [~fag@12.smos-linux.org] has quit [Ping timeout: 268 seconds] 13:12 -!- gaf_ [~fag@12.smos-linux.org] has joined #bitcoin-core-dev 13:17 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Read error: Connection reset by peer] 13:19 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 13:20 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 13:22 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 13:26 < jnewbery> aj: thanks - I've commented on your PR. Looks good to me 13:27 -!- meshcollider [meshcollid@gateway/shell/elitebnc/x-gaqodbwqduovxbiv] has joined #bitcoin-core-dev 13:27 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Read error: Connection reset by peer] 13:28 -!- kbgg [Elite20763@gateway/shell/elitebnc/session] has joined #bitcoin-core-dev 13:29 < cfields> jonasschnelli: still around by any chance? 13:29 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev 13:30 < aj> jnewbery: i guess the right approach for dropping LEEWAY is for me to go through all the outstanding PRs and comment on the ones that add tests to fix the name, and drop LEEWAY once the second PR goes in and there aren't any pending PRs that haven't adopted the newnaming scheme. should be easy to semi-automate 13:30 < cfields> jonasschnelli: please ping me when you have a few min to look at the signing cert stuff 13:30 < jonasschnelli> cfields: currently on the go.. will be back at my desk in about 9hs 13:31 < cfields> jonasschnelli: np. Not sure if I'll still be around, though. I'll try to hop on before bed. 13:35 < jonasschnelli> okay.. I'll ping you and we will see 13:35 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 250 seconds] 13:36 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has joined #bitcoin-core-dev 13:36 < cfields> jonasschnelli: thanks! 13:38 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 13:40 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has quit [Ping timeout: 252 seconds] 13:42 < BlueMatt> sipa: typo? 13:42 < BlueMatt> #11825 is definitely not fixed by "final TODOs for release notes for 0.15" 13:42 < gribble> https://github.com/bitcoin/bitcoin/issues/11825 | When running bitcoind I keep getting - boost::filesystem::space: Operation not permitted · Issue #11825 · bitcoin/bitcoin · GitHub 13:42 -!- Netsplit over, joins: Guyver2 13:43 < sipa> BlueMatt: yes 13:43 < sipa> it's #11829 13:43 < gribble> https://github.com/bitcoin/bitcoin/issues/11829 | Test datadir specified in conf file exists by MeshCollider · Pull Request #11829 · bitcoin/bitcoin · GitHub 13:44 < BlueMatt> ahah, heh, ok, i missed the error that non-existent datadir would give 13:46 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 13:54 -!- earlz [~earlz@earlz.net] has joined #bitcoin-core-dev 13:55 < BlueMatt> sipa: I'd say #3465 is sufficiently out of date it could just be closed 13:55 < gribble> https://github.com/bitcoin/bitcoin/issues/3465 | [RFC] Post-0.9 network/protocol/main refactor · Issue #3465 · bitcoin/bitcoin · GitHub 13:56 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 252 seconds] 13:58 < sipa> hahaha 14:00 -!- rhavar_ [uid237883@gateway/web/irccloud.com/session] has joined #bitcoin-core-dev 14:01 -!- BGL [sixty@75-149-171-58-Washington.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 14:01 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 14:01 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 14:01 -!- booyah [~bb@193.25.1.157] has joined #bitcoin-core-dev 14:01 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev 14:01 -!- murchandamus [~murchghos@ghostdub.de] has joined #bitcoin-core-dev 14:01 -!- merehap [~sean@c-73-239-115-62.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 14:01 -!- Provoostenator [~Provooste@ec2-18-194-164-183.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev 14:01 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #bitcoin-core-dev 14:01 -!- Deadhand [~deadhand@CPE6038e0be3871-CMf0f249a14e40.cpe.net.cable.rogers.com] has joined #bitcoin-core-dev 14:01 -!- echonaut [~echonaut@46.101.192.134] has joined #bitcoin-core-dev 14:02 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/session] has joined #bitcoin-core-dev 14:02 -!- echonaut2 [~echonaut@46.101.192.134] has joined #bitcoin-core-dev 14:03 -!- echonaut [~echonaut@46.101.192.134] has quit [Remote host closed the connection] 14:03 -!- kbgg [Elite20763@gateway/shell/elitebnc/session] has quit [Changing host] 14:03 -!- kbgg [Elite20763@gateway/shell/elitebnc/x-ddcrriwlavunczga] has joined #bitcoin-core-dev 14:03 -!- rhavar_ [uid237883@gateway/web/irccloud.com/session] has quit [Changing host] 14:03 -!- rhavar_ [uid237883@gateway/web/irccloud.com/x-vxshqsbsyevuqzxd] has joined #bitcoin-core-dev 14:04 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/session] has quit [Changing host] 14:04 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-lnghmimkpwlqblsn] has joined #bitcoin-core-dev 14:05 -!- Provoostenator [~Provooste@ec2-18-194-164-183.eu-central-1.compute.amazonaws.com] has quit [Ping timeout: 260 seconds] 14:06 -!- noglar_ [~cl0uding@62.43.144.42.dyn.user.ono.com] has quit [Ping timeout: 250 seconds] 14:07 -!- Provoostenator [~Provooste@ec2-18-194-164-183.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev 14:07 -!- noglar_ [~cl0uding@62.43.144.42.dyn.user.ono.com] has joined #bitcoin-core-dev 14:15 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has joined #bitcoin-core-dev 14:20 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has quit [Ping timeout: 264 seconds] 14:20 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 14:25 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:26 -!- guneyozsan [c236398c@gateway/web/freenode/ip.194.54.57.140] has joined #bitcoin-core-dev 14:26 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 14:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 14:30 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has joined #bitcoin-core-dev 14:34 -!- pkx2__ [~pkx2@24.13.105.201] has joined #bitcoin-core-dev 14:36 -!- pkx2__ [~pkx2@24.13.105.201] has quit [Remote host closed the connection] 14:38 -!- pkx2 [~pkx2@24.13.105.201] has joined #bitcoin-core-dev 14:40 -!- so [~so@unaffiliated/so] has joined #bitcoin-core-dev 14:43 -!- TheMadSc_ [~TheMadSci@65.112.10.39] has joined #bitcoin-core-dev 14:44 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:45 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 14:50 -!- TheMadSc_ [~TheMadSci@65.112.10.39] has left #bitcoin-core-dev ["Leaving..."] 14:51 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 14:51 -!- TheMadSc_ [~TheMadSci@65.112.10.39] has joined #bitcoin-core-dev 14:51 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-wqbodauetmpudfby] has joined #bitcoin-core-dev 14:51 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 14:51 -!- pkx2 [~pkx2@24.13.105.201] has quit [Remote host closed the connection] 14:52 -!- pkx2 [~pkx2@24.13.105.201] has joined #bitcoin-core-dev 14:52 -!- jack_ [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Ping timeout: 248 seconds] 14:53 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 14:53 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 14:57 -!- TheMadSc_ [~TheMadSci@65.112.10.39] has left #bitcoin-core-dev ["Leaving..."] 14:57 -!- pkx2 [~pkx2@24.13.105.201] has quit [Remote host closed the connection] 14:58 -!- pkx2 [~pkx2@24.13.105.201] has joined #bitcoin-core-dev 14:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 15:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 15:04 -!- photonclock_ [~photonclo@47.37.153.193] has quit [Remote host closed the connection] 15:05 -!- photonclock_ [~photonclo@47.37.153.193] has joined #bitcoin-core-dev 15:07 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 250 seconds] 15:10 -!- Usman_Mutawakil [~Usman_Mut@65.112.10.39] has joined #bitcoin-core-dev 15:12 -!- Usman_Mutawakil [~Usman_Mut@65.112.10.39] has left #bitcoin-core-dev [] 15:18 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 15:20 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 15:21 -!- pkx2 [~pkx2@24.13.105.201] has quit [Remote host closed the connection] 15:22 -!- pkx2 [~pkx2@24.13.105.201] has joined #bitcoin-core-dev 15:23 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 15:25 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 15:26 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 15:29 -!- jack_ [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 15:32 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 250 seconds] 15:35 -!- guneyozsan [c236398c@gateway/web/freenode/ip.194.54.57.140] has quit [Quit: Page closed] 15:36 -!- DvdKhl [~Arokh@ip-37-201-210-118.hsi13.unitymediagroup.de] has quit [Ping timeout: 248 seconds] 15:43 -!- pkx2 [~pkx2@24.13.105.201] has quit [Remote host closed the connection] 15:44 -!- pkx2 [~pkx2@24.13.105.201] has joined #bitcoin-core-dev 15:46 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 246 seconds] 15:47 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 15:47 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host] 15:47 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 15:49 -!- booyah_ [~bb@193.25.1.157] has joined #bitcoin-core-dev 15:50 -!- wxss [~user@176-53-23-252.turkrdns.com] has quit [Read error: Connection reset by peer] 15:51 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 260 seconds] 15:51 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 268 seconds] 15:53 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 15:55 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 16:02 -!- griswaalt[m] [griswaaltm@gateway/shell/matrix.org/x-yozyocldaimjhgcx] has joined #bitcoin-core-dev 16:04 -!- str4d [~str4d@183.191.6.51.dyn.plus.net] has joined #bitcoin-core-dev 16:08 -!- rhavar_ [uid237883@gateway/web/irccloud.com/x-vxshqsbsyevuqzxd] has quit [Quit: Connection closed for inactivity] 16:10 -!- herzmeister[m] [herzmeiste@gateway/shell/matrix.org/x-zwwnlmzlbfmgecmw] has joined #bitcoin-core-dev 16:10 -!- kewde[m] [kewdematri@gateway/shell/matrix.org/x-byyhxcgwehcgukqm] has joined #bitcoin-core-dev 16:10 -!- Masaomi[m] [masaomimat@gateway/shell/matrix.org/x-jdupzxuykuizwaob] has joined #bitcoin-core-dev 16:10 -!- ajtowns[m] [ajtownsmat@gateway/shell/matrix.org/x-yvlsixijjapqulbr] has joined #bitcoin-core-dev 16:10 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 255 seconds] 16:14 -!- vh [bcaa5082@gateway/web/freenode/ip.188.170.80.130] has joined #bitcoin-core-dev 16:21 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 252 seconds] 16:22 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 16:23 -!- Sentineo [~Undefined@unaffiliated/sentineo] has quit [Ping timeout: 260 seconds] 16:27 -!- Soligor [~Soligor@unaffiliated/soligor] has quit [Read error: Connection reset by peer] 16:29 -!- Soligor [~Soligor@unaffiliated/soligor] has joined #bitcoin-core-dev 16:34 -!- jack_ is now known as j_ 16:34 -!- microapple [~textual@2601:240:8101:9698:7dd5:a2ff:a76c:480a] has joined #bitcoin-core-dev 16:43 -!- microapple [~textual@2601:240:8101:9698:7dd5:a2ff:a76c:480a] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 16:46 -!- vh [bcaa5082@gateway/web/freenode/ip.188.170.80.130] has quit [Quit: Page closed] 16:49 -!- pkx2 [~pkx2@24.13.105.201] has quit [Remote host closed the connection] 16:53 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:34b0:dd09:91e2:e473] has quit [Remote host closed the connection] 16:54 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:54 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:117d:848:50c0:3946] has joined #bitcoin-core-dev 16:55 -!- CubicEarth [~cubiceart@2a02:aa16:5781:8500:117d:848:50c0:3946] has quit [Remote host closed the connection] 16:55 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 16:58 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 17:00 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 17:00 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 17:06 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 17:10 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 240 seconds] 17:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 17:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 17:17 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 17:20 -!- trippysalmon [~trippysal@cyberdynesys.org] has quit [Ping timeout: 268 seconds] 17:21 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-wqbodauetmpudfby] has quit [Quit: Connection closed for inactivity] 17:29 -!- trippysalmon [~trippysal@cyberdynesys.org] has joined #bitcoin-core-dev 17:34 -!- DrFeelGood [~DrFeelGoo@unaffiliated/olufunmilayo] has quit [Ping timeout: 276 seconds] 17:48 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-lnghmimkpwlqblsn] has quit [] 17:48 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-tdpkihraknyfzitt] has joined #bitcoin-core-dev 17:49 -!- meshcollider is now known as mesh_ 17:57 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-lmhoazmpbqsocmdk] has quit [Quit: Connection closed for inactivity] 17:58 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-tdpkihraknyfzitt] has quit [] 17:58 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-ozgzxpxdpmrojxkf] has joined #bitcoin-core-dev 18:05 -!- microapple [~textual@c-98-212-150-206.hsd1.il.comcast.net] has joined #bitcoin-core-dev 18:16 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 18:20 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 18:21 -!- fengling [~fengling@117.136.0.114] has joined #bitcoin-core-dev 18:22 -!- fengling is now known as qinfengling 18:23 -!- qinfengling [~fengling@117.136.0.114] has quit [Client Quit] 18:24 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 18:24 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 250 seconds] 18:24 -!- fengling [~fengling@117.136.0.114] has joined #bitcoin-core-dev 18:24 -!- fengling [~fengling@117.136.0.114] has left #bitcoin-core-dev [] 18:25 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 268 seconds] 18:26 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 18:28 -!- j_ [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Quit: j_] 18:31 -!- qinfengling [~qinfengli@117.136.0.114] has joined #bitcoin-core-dev 18:32 -!- qinfengling [~qinfengli@117.136.0.114] has quit [Client Quit] 18:43 -!- qinfengling [~qinfengli@117.136.0.114] has joined #bitcoin-core-dev 18:43 -!- Usman_Mutawakil [~usman_mut@2601:184:4080:c7b:e4dd:43a5:1440:515a] has joined #bitcoin-core-dev 18:45 < Usman_Mutawakil> Is their any documentation that expands on the details of the source code? I'm having difficulty finding the entry points. 18:45 < Usman_Mutawakil> there* 18:46 -!- jack [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 18:46 -!- jack is now known as __J 18:46 -!- jamesob [~james@199.230.10.198] has quit [Ping timeout: 248 seconds] 18:55 -!- qinfengling [~qinfengli@117.136.0.114] has quit [Ping timeout: 240 seconds] 18:57 -!- Randolf [~randolf@24.244.32.158] has joined #bitcoin-core-dev 18:58 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 248 seconds] 18:58 -!- qinfengling [~qinfengli@117.136.0.114] has joined #bitcoin-core-dev 18:59 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 18:59 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host] 18:59 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 19:00 < meshcollider> Usman_Mutawakil: The entry points of the programs, or the entry point to understanding it? 19:01 < Usman_Mutawakil> Both, initially the former 19:03 -!- __J is now known as j_ 19:10 -!- Randolf [~randolf@24.244.32.158] has quit [Ping timeout: 240 seconds] 19:13 -!- Usman_Mutawakil [~usman_mut@2601:184:4080:c7b:e4dd:43a5:1440:515a] has quit [] 19:31 < meshcollider> Usman_Mutawakil: the main() function for bitcoind is in bitcoind.cpp, for bitcoin-qt it is in qt/bitcoin.cpp and there is one in bitcoin-tx.cpp and bitcoin-cli.cpp for their respective binaries too 19:40 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has quit [Ping timeout: 276 seconds] 19:40 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has joined #bitcoin-core-dev 19:43 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Read error: Connection reset by peer] 19:43 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Read error: Connection reset by peer] 19:43 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Read error: Connection reset by peer] 19:43 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 19:44 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 19:44 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 19:46 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 19:54 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 19:59 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Quit: Page closed] 20:03 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 20:04 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 20:05 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 20:06 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 20:07 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 20:22 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 20:22 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has quit [Ping timeout: 268 seconds] 20:23 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 20:24 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has joined #bitcoin-core-dev 20:30 -!- qinfengling [~qinfengli@117.136.0.114] has quit [Read error: Connection reset by peer] 20:42 -!- microapple [~textual@c-98-212-150-206.hsd1.il.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 20:46 -!- shesek [~shesek@bzq-84-110-55-92.red.bezeqint.net] has joined #bitcoin-core-dev 20:46 -!- shesek [~shesek@bzq-84-110-55-92.red.bezeqint.net] has quit [Changing host] 20:46 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 21:10 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 21:11 -!- jimJackson [adefe678@gateway/web/freenode/ip.173.239.230.120] has joined #bitcoin-core-dev 21:11 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 21:13 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 240 seconds] 21:14 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 21:14 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host] 21:14 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 21:14 < BGL> can anyone help me with instructions on storing the blockchain &/or the wallet seperately on windows, via symbolic link, drive/mount or anything that works? 21:21 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 21:22 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 21:39 -!- j_ [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Quit: j_] 21:45 -!- j_ [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev 21:49 < meshcollider> BGL: are you using 0.15.1 or build of master? 21:49 < BGL> yeah newest copy 21:49 -!- Randolf [~randolf@96.53.47.38] has joined #bitcoin-core-dev 21:50 < BGL> 0.15.1 21:52 -!- Randolf [~randolf@96.53.47.38] has quit [Client Quit] 21:52 -!- Randolf [~randolf@96.53.47.38] has joined #bitcoin-core-dev 21:58 < jonasschnelli> cfields: ping (in case you are still awake) 22:00 -!- indistylo [~indistylo@119.82.105.106] has joined #bitcoin-core-dev 22:03 -!- Randolf [~randolf@96.53.47.38] has quit [Quit: https://www.randolfrichardson.com/] 22:03 < cfields> jonasschnelli: pong, hi 22:04 < jonasschnelli> hi 22:05 < cfields> jonasschnelli: any chance you can get ahold of a dummy certificate signing request? 22:05 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 22:05 < jonasschnelli> cfields: I have one here... one sec 22:05 < cfields> oh, that was easy :) 22:07 < jonasschnelli> cfields: there is now also the option to request ECC (up to 521 bits... though not sure if they will be accepted 22:07 < cfields> ah, nice 22:07 < cfields> we'd need to check back-compat too, though 22:07 < cfields> oh, i guess that's what you meant :) 22:07 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 22:08 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 22:09 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #bitcoin-core-dev 22:09 < jonasschnelli> cfields: Yes. Not sure if its accepted and backward compat... so better to go for RSA 22:10 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 248 seconds] 22:10 < cfields> got the dummies, thanks a bunch. It's late now, but I'll have a look in the morning. 22:11 < jonasschnelli> cfields: Sure. Just tell me if you want access to the apple developer programm interface 22:12 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev 22:13 < cfields> jonasschnelli: hmm, we probably need to keep that locked down. assuming that access would allow me to revoke the current or request a new cert. 22:13 -!- j_ [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Remote host closed the connection] 22:13 -!- Cory [~Cory@unaffiliated/cory] has quit [Read error: Connection reset by peer] 22:13 < jonasschnelli> cfields: I don't know how to best deal with that... 22:15 -!- QuangNA [71ad1074@gateway/web/freenode/ip.113.173.16.116] has joined #bitcoin-core-dev 22:19 < cfields> jonasschnelli: i wonder if it's possible to cancel your account without revoking the certs. a quick search turned up an email address to use for revoking without an account, so maybe that's possible? 22:20 < cfields> then a new account could be created for each renewal. Or would that require re-certification? 22:21 < jonasschnelli> cfields: the account setup is somehow cumbersome. I had to verify the account (by phone) because it's an organisation. You need a DUNS number, and need to pay 99USD. 22:22 < cfields> ah damn, ok. I was thinking the dev account and corp id might not be 100% tied together. 22:22 < jonasschnelli> cfields: and finally, it's social hackable. If we lock ourselfs out,.. apple probably has a solution to lock in again if the right person from the organisation authorizes himself 22:22 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 22:22 < jonasschnelli> cfields: I can setup an new "team member". Maybe I can even revoke my own admin user (after have setup a new one)... but not sure how this would allow to improve things 22:23 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 22:23 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev 22:24 < cfields> yea, maybe not 22:25 < cfields> well, i guess the same threshold scheme would work for revocation as well. if ever necessary. 22:25 < cfields> ah nm, it'd be a different key 22:26 < cfields> (assuming someone got control of the account and created a new key) 22:27 < cfields> blah, I'll dive in tomorrow. thanks again :) 22:33 -!- Apocalyptic [~Apocalypt@unaffiliated/apocalyptic] has quit [Ping timeout: 240 seconds] 22:35 -!- musalbas [~musalbas@2001:bc8:30c2:ff00::] has quit [Ping timeout: 276 seconds] 22:47 -!- booyah_ is now known as booyah 22:58 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-mssqmlrrmazaprfp] has joined #bitcoin-core-dev 23:09 -!- musalbas [~musalbas@algebra.musalbas.com] has joined #bitcoin-core-dev 23:09 -!- DvdKhl [~Arokh@ip-37-201-210-118.hsi13.unitymediagroup.de] has joined #bitcoin-core-dev 23:10 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 23:10 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 23:11 < jonasschnelli> cfields: Yeah. Have some rest. I think it's not solvable in a secure way. On top, apple has control over everything. It's just code signing and does not ensure the binary has built properly. It's far less valuable then the gitian signatures... 23:14 -!- Apocalyptic [~Apocalypt@unaffiliated/apocalyptic] has joined #bitcoin-core-dev 23:18 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 23:20 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 23:27 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 23:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 23:29 -!- Cogito_Ergo_Sum [~Myself@ppp-94-64-159-66.home.otenet.gr] has joined #bitcoin-core-dev 23:29 -!- Cogito_Ergo_Sum [~Myself@ppp-94-64-159-66.home.otenet.gr] has quit [Changing host] 23:29 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 23:39 -!- QuangNA [71ad1074@gateway/web/freenode/ip.113.173.16.116] has quit [Ping timeout: 260 seconds] 23:40 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 23:45 < warren> A while ago checkpoints were there in part to allow IBD to go a lot faster. The checkpoints are still in there now. After headersfirst, are those checkpoints in there still serving any IBD performance purpose? 23:47 < sipa> warren: no, we have assumevalid for that now 23:47 < sipa> the checkpoints are just there to prevent a low-work headers spam attack 23:49 < warren> thx. 23:50 < sipa> assumevalid was introduced in 0.13 or 0.14 iirc 23:50 < sipa> https://bitcoin.org/en/release/v0.14.0#introduction-of-assumed-valid-blocks 23:56 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 23:56 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 255 seconds]