--- Day changed Tue Jun 14 2016
00:02 < jonasschnelli> wumpus: windows gitian builds still broken? https://bitcoin.jonasschnelli.ch/nightlybuilds/2016-06-14/build-win.log (check bottom)
00:02 < jonasschnelli> checking whether the C++ compiler works... no
00:08 < GitHub28> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/36b74002f840...8c1d5ebd1706
00:08 < GitHub28> bitcoin/master 01a9904 fanquake: [trivial] Ignore split-debug.sh
00:08 < GitHub28> bitcoin/master 8c1d5eb Wladimir J. van der Laan: Merge #8197: [trivial] Ignore split-debug.sh...
00:08 < GitHub102> [bitcoin] laanwj closed pull request #8197: [trivial] Ignore split-debug.sh (master...ignore-split-debug) https://github.com/bitcoin/bitcoin/pull/8197
00:14 < GitHub69> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/8c1d5ebd1706...cca1c8cff011
00:14 < GitHub69> bitcoin/master fa61756 MarcoFalke: [gitian] set correct PATH for wrappers
00:14 < GitHub69> bitcoin/master cca1c8c Wladimir J. van der Laan: Merge #8194: [gitian] set correct PATH for wrappers...
00:14 < GitHub108> [bitcoin] laanwj closed pull request #8194: [gitian] set correct PATH for wrappers (master...Mf1606-gitianPath) https://github.com/bitcoin/bitcoin/pull/8194
00:40 -!- shangzhou [uid156782@gateway/web/irccloud.com/x-uwbkdfbzlldxjhtm] has joined #bitcoin-core-dev
01:26 -!- Netsplit *.net <-> *.split quits: cjcj
01:40 -!- murch [~murch@p4FE38CDB.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
01:54 -!- MarcoFalke [~marco@host10-2.natpool.mwn.de] has joined #bitcoin-core-dev
01:57 < MarcoFalke> jonasschnelli: The windows build should be working now
01:57 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
01:57 < MarcoFalke> Try the new descriptors from master
02:06 -!- MarcoFalke [~marco@host10-2.natpool.mwn.de] has left #bitcoin-core-dev []
02:11 -!- jannes [~jannes@178.132.211.90] has joined #bitcoin-core-dev
02:13 -!- proslogion [~proslogio@90.210.173.173] has joined #bitcoin-core-dev
02:29 -!- Amnez777 [~Amnez777@37.157.216.176] has joined #bitcoin-core-dev
02:31 < jonasschnelli> Okay. Testing now with the new windows descriptor: https://bitcoin.jonasschnelli.ch/pulls/7636/
02:40 < GitHub13> [bitcoin] laanwj closed pull request #7186: [WIP] Backports for 0.10.5 (updated to 93ca5a3) (0.10...backports-for-0.10.5) https://github.com/bitcoin/bitcoin/pull/7186
02:45 < GitHub46> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/cca1c8cff011...b67a4726dfc3
02:45 < GitHub46> bitcoin/master f190251 Jonas Schnelli: [Wallet] Add simplest BIP32/deterministic key generation implementation
02:45 < GitHub46> bitcoin/master c022e5b Jonas Schnelli: [Wallet] use constant for bip32 hardened key limit
02:45 < GitHub46> bitcoin/master 17c0131 Jonas Schnelli: [Docs] Add release notes and bip update for Bip32/HD wallets
02:45 < GitHub22> [bitcoin] laanwj closed pull request #8035: [Wallet] Add simplest BIP32/deterministic key generation implementation (master...2016/05/simplest_hd) https://github.com/bitcoin/bitcoin/pull/8035
02:45 < jonasschnelli> Yes!
02:48 -!- shangzhou [uid156782@gateway/web/irccloud.com/x-uwbkdfbzlldxjhtm] has quit [Quit: Connection closed for inactivity]
02:50 < GitHub55> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/b67a4726dfc3...520161480eb1
02:50 < GitHub55> bitcoin/master 0e209f9 fanquake: [trivial] Sync ax_pthread with upstream draft
02:50 < GitHub55> bitcoin/master 5201614 Wladimir J. van der Laan: Merge #8198: [trivial] Sync ax_pthread with upstream draft4...
02:50 < GitHub4> [bitcoin] laanwj closed pull request #8198: [trivial] Sync ax_pthread with upstream draft4 (master...sync-pthread) https://github.com/bitcoin/bitcoin/pull/8198
02:55 < wumpus> jonasschnelli: bah, if this continues we'll have no 0.13 release for windows :p
02:56 < wumpus> getting all OS builds to work should probably be focus #1 after the feature freeze
02:56 -!- proslogion [~proslogio@90.210.173.173] has left #bitcoin-core-dev ["离开"]
02:57 < wumpus> as well as getting qt 5.6.1 to work
02:58 -!- proslogion [~proslogio@90.210.173.173] has joined #bitcoin-core-dev
03:00 < wumpus> I really like the new parallel rpc test launcher
03:01 -!- rubensayshi [~ruben@c89225.upc-c.chello.nl] has joined #bitcoin-core-dev
03:07 -!- cjcj [2e3b026a@gateway/web/freenode/ip.46.59.2.106] has joined #bitcoin-core-dev
03:08 < wumpus> anyone recognize this issue with gitian? http://www.hastebin.com/xununifuxa.txt
03:09 < wumpus> interesting, just repeating the gbuild seems to get past it
03:10 < wumpus> lxc is weird
03:17 < btcdrak> wumpus: it happens randomly and you just have to run the command again. It's been like that for as long as i remember
03:17 < wumpus> it's building the dependencies, this couuld take awhile
03:17 < wumpus> btcdrak: yes I also remember seeing it before
03:20 < wumpus> it's half-panic every time, debugging issues with gitian is tiring as everything goes so slow, I use this VM for nothing else to make sure (hopefully) nothing breaks it
03:21 < wumpus> I wonder why we have no "upgrade gitian base image" step? doing a system upgrade before every build seems... overkill
03:21 < wumpus> I know apt-cacher is caching the packages so there is no bandwidth overhead but it is still slow
03:27 < GitHub83> [bitcoin] laanwj closed pull request #7230: BIP-draft:  2mb blocksize step (master...2015_2mb_blocksize_step) https://github.com/bitcoin/bitcoin/pull/7230
03:33 < wumpus> jonasschnelli: I'm trying to get a bucket of random testnet hosts by looking up testnet-seed.bitcoin.jonasschnelli.ch manually, but none of the node IP returned seem to have port 18333 open, am I doing something wrong?
03:34 < wumpus> or just incredibly unlucky, one time I even got only ipv6 addresses :)
03:36 < wumpus> oh it must be the address obfuscation, of course
03:38 < sipa> address obfuscation? i thought we never adopted that
03:39 < wumpus> I don't think so either
03:40 < wumpus> I don't know then - using another seed gave me valid addresses, btw
03:41 < sipa> maybe all testnet seeds are short lived?
03:42 -!- mkarrer [~mkarrer@80.red-79-151-141.dynamicip.rima-tde.net] has quit []
03:43 < wumpus> well I checked about 30 addresses returned from jonasschnelli's seed, none could connect, the first one I tried from petertodd's seed was a hit
03:43 < sipa> hmm
03:45 -!- mkarrer [~mkarrer@80.red-79-151-141.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
03:46 < wumpus> *yawn* now my testnet node hangs at 40% verification
03:46 < wumpus> I should go back to bed, everything goes wrong today
03:46 < sipa> awww
03:48 < sipa> i see a stream of questions on stackexchange about unconfirmed transactions (mostly created by old software)... i really hope we can get some "fee increase" mechanism in
03:49 < wumpus> well https://github.com/bitcoin/bitcoin/pull/7865 is tagged for 0.13, but I doubt it is ready yet
03:49 < wumpus> ugh, why would a node with checklevel=0 hang while doing the initial verification, I don't get it
03:51 < wumpus> oh of course, let attach gdb, great idea, thanks ubuntu for making it so difficult I first have to become root or enable a flag...
03:51 < sipa> ha, yes, after doing that a dozen times, i changed the default in sysctl.conf
03:52 < sipa> my guess is that leveldb is compacting
03:52 < jonasschnelli> wumpus: I think the windows build works again: https://bitcoin.jonasschnelli.ch/pulls/7636/
03:52 < wumpus> I forget that every time, normally I just start bitcoind in gdb, but thought I was donig something so trivial now that it would be unnecessary - wrong :p
03:52 < jonasschnelli> wumpus: re seeder, I started the testnet seeder with a new database this morning. Not sure if the seeder already results enough data.
03:53 < sipa> jonasschnelli: perhaps you should delete the db and start over?
03:53 < jonasschnelli> yes. I did this this morning ~9oclock
03:53 < sipa> ah
03:53 < jonasschnelli> ah.. wait... I guess it's scanning mainnet. :(
03:53 < sipa> ha
03:53 < btcdrak> lmao
03:54 < wumpus> oh, nm, I was looking at the wrong log
03:54 < jonasschnelli> fooled by the subdomain. :)
03:55 < jonasschnelli> Okay. removed the database and started in testnet mode
03:55 < wumpus> yes, windows build seems to work
03:55 < jonasschnelli> sipa: [...] i really hope we can get some "fee increase" mechanism in
03:55 < wumpus> current master: 291be202508e518646116677cc99cb1333739d52e2c4ae7259359b3bd3729e0c  bitcoin-0.12.99-win-unsigned.tar.gz
03:56 < jonasschnelli> sipa: you could review the bumpfee command.
03:56 < jonasschnelli> I'm not entirely sure if taking a txid and autobump it is the way to go though.
03:57 < sipa> if CPFP gets in, there is an easier solution
03:58 < sipa> jonasschnelli: i don't know how to make this easy to use
03:58 < wumpus> how is addnode supposed to work? I added a few (seemingly functional) testnet nodes, but they all stay at "connected": false in getaddednodeinfo (testing #8113)
03:58 < jonasschnelli> I'm planing on extending the HD feature. Importing/starting a wallet with a xpriv key. How should we do that. I guess having a -xpriv= startup argument is very bad.
03:58 < sipa> wumpus: it cycles every 2 minutes
03:58 < wumpus> let's first worry about having some mechanism in, and then about making it easy to use
03:59 < sipa> wumpus: and then tries to connect to one of the unconnected addnodes
03:59 < wumpus> there's only two days left before the feature freeze so we need to make some choices
03:59 < wumpus> sipa: okay, thanks
04:02 < jonasschnelli> would ./bitcoin-wallet be a tool where users could create a wallet(.dat) with a xpriv?
04:02 < jonasschnelli> Everything that goes over RPC is somehow not ideal
04:02 < wumpus> that's the eternal question - command line isn't the ideal interface either though, especially if you're not writing shell script
04:04 < wumpus> I think having wallet creation commands on RPC makes some sense, at least once there is multi-wallet support
04:04 < jonasschnelli> wumpus: Yes. But right now, we create the wallet before the RPC is ready.
04:05 < wumpus> yes, right now, I'm sure that needs to be changed
04:05 < wumpus> is there a hurry?
04:05 < jonasschnelli> No hurry.
04:05 < jonasschnelli> Certenly not something for 0.13
04:05 < jonasschnelli> But need some brainfood for afk time. :)
04:05 < wumpus> decoupling the wallet further would mean that node RPC could be ready, before the wallet even starts loading/creating
04:06 < wumpus> especially if the wallet has its own entry point
04:06 < jonasschnelli> yes. I'm working on removine the splash screen and add this state
04:06 < wumpus> removing the splash screen? I'd think we still need it during initial verification
04:07 < jonasschnelli> wumpus: Yes. But you can access the wallet during this time. Get addresses, list transactions, etc.
04:07 < wumpus> there's something to be said for having a wallet as an external tool/library, but the scope for doing that within bitcoin core is very small
04:07 < wumpus> jonasschnelli: I don't think that's a very good idea, even being able to access the wallet during *synchronization* caused a ton of confused users
04:08 < jonasschnelli> wumpus: but decoupling the wallet would result in such states. I guess all SPV wallets allow address/tx access in out-of-sync state.
04:08 < wumpus> e.g. 'I downloaded bitcoin core and sent from *web wallet provider* to a new address, now my transaction doesn't show!'
04:08 < jonasschnelli> Sure, we might want to add a SPV mode first.
04:09 < wumpus> possibly, but I don't think - right now - there is any benefit to removing the splash screen and showing a (mostly dysfunctional) GUI instead
04:09 < jonasschnelli> But its annoying that you need to go through verification/checkblocks if you want to get a new address
04:09 < wumpus> possibly... checkblocks takes too long by default, that's aother issue
04:10 < jonasschnelli> IMO the (wallet)GUI is fully functional during init-verification
04:10 < wumpus> I think validating the last blocks is a good thing, but the default depth setting is overkill
04:10 < jonasschnelli> Yes. But the node (validation) is not tied to the wallet/GUI.
04:10 < wumpus> that's true...
04:11 < jonasschnelli> But right. We need more prominent warnings if the wallet is not in sync
04:11 < wumpus> but it won't start syncing blocks until that part is done, so people will still complain 'why isn't it synching!!!'
04:11 < wumpus> WHHY IS THERE NO BLOCK SOURCE AVAILABLE
04:11 < jonasschnelli> Heh... yes. probably.
04:12 < jonasschnelli> Step by step... 
04:12 < jonasschnelli> For 0.14 i'd like to focus more on the UI
04:12 < wumpus> you're right that creating an address can be done without any node functionality, but then, people can't see transactions to the address without it, or being in sync
04:12 < sipa> i think we should disable that feature by default
04:13 < wumpus> which is arguably the part people care about, actually receiving coins
04:13 < sipa> not show a receive address until sync is done
04:13 < wumpus> well for a start it should show a big red warning in the transaction pane when not up to date
04:13 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
04:13 < wumpus> I don't think you need to actually disable it
04:13 < wumpus> but just warn better
04:13 < sipa> perhaps make it greyed out with a button, and if you click it it first asks you "are you aware that you'll only receive once you're synced?"
04:14 < wumpus> there is no indication right now excapt for the extremely toned-down out-of-sync triangles
04:14 < jonasschnelli> Wouldn't this be to much handholding for expert users?
04:14 < jonasschnelli> (not the warning)
04:14 < jonasschnelli> (just the fact that you can't get addresses when you are not in sync)
04:14 < wumpus> yes, i think that's too much babysitting
04:15 < jonasschnelli> IMO even the fact that you need to wait for the init/checks before you can list transactions or get new addresses.
04:15 < wumpus> lots of people do know that, it's just new users that don't, maybe we should add a tutorial mode on first use
04:15 < sipa> right
04:16 < sipa> yes, just thinking through how a first time user sees all this
04:16 < jonasschnelli> This is the difficulty: make it useable for basic/new bitcoin users but also make the experts happy.
04:17 < wumpus> yes
04:17 < wumpus> in any case, adding a warning wouldn't hurt and is easy to do
04:18 < GitHub179> [bitcoin] jonasschnelli pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/520161480eb1...fb0ac482eee7
04:18 < GitHub179> bitcoin/master 1c2a1ba Francesco 'makevoid' Canessa: Add address label to request payment QR Code (QT)...
04:18 < GitHub179> bitcoin/master fb0ac48 Jonas Schnelli: Merge #7636: Add bitcoin address label to request payment QR code...
04:18 < GitHub124> [bitcoin] jonasschnelli closed pull request #7636: Add bitcoin address label to request payment QR code (master...request_payment_qrcode_address_label) https://github.com/bitcoin/bitcoin/pull/7636
04:19 -!- Inaltoasinistra [~jonathan@88-149-242-82.v4.ngi.it] has quit [Read error: Connection reset by peer]
04:20 < wumpus> how exactly is up to the person implementing it, I guess
04:21 < wumpus> there's enough place on the "receive" tab to add a warning, and in the transaction pane I suppose it could show an overlay if there are no transactions yet and it is syncing
04:21 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]
04:26 -!- MarcoFalke [~marco@host10-2.natpool.mwn.de] has joined #bitcoin-core-dev
04:26 < MarcoFalke> Anyone seeing OOM for gitian builds?
04:26 < MarcoFalke> in main.cpp
04:27 < wumpus> no, though adding of debug symbols in #8167 did increase the memory requirements for gitian a bit
04:28 < MarcoFalke> How does gbuild set up the ram of the vm?
04:28 < MarcoFalke> I could try to increase it, I guess.
04:29 < wumpus> -j5 -m5000  where -j is the parallelism and -m is the memory size in mb
04:31 < wumpus> what is the expected behavior when addnoding a seed?
04:32 < sipa> very fuzzy
04:32 < sipa> i think it won't make any connection if you already have 8 outgoing ones
04:32 < wumpus> for me it works with IPs but not with hostnames
04:33 < sipa> it should work with hostnames
04:33 < sipa> wumpus: is this in #8113?
04:33 < wumpus> the expectation is that it looks up the address for the seed then connect to the first address, I suppose?
04:33 < wumpus> yes
04:34 < sipa> it randonly tries one of the returned ip addtesses every 2 minutes
04:34 < sipa> if one fails, there is another attempt 2 minutes later
04:34 < wumpus> it stays at 'connected': false all the time
04:34 < sipa> do you have 8 outgoing connections already?
04:35 < wumpus> yes
04:35 < wumpus> should I kick some other connections?
04:35 < wumpus> ok disconnected all nodes, let's see what happens
04:36 < sipa> the addnode logic should be integrated into the normal outgoing connection logic, and be protected from eviction
04:37 < wumpus> yes, I suppose so, how badly this works I wonder if anyone was actually using this functionality and whether it makes sense to spend time on it
04:38 < sipa> i think after we have p2p encryption and authentication, we may want to encourage it
04:40 < MarcoFalke> looks like it is using 2000MiB as default. In case the default is no longer enough, it may be worth to adjust https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#build-and-sign-bitcoin-core-for-linux-windows-and-os-x
04:40 < wumpus> I set up a hostname for a known-working testnet node, lets see if it wants to connect to that...
04:42 < wumpus> evicting all other nodes again
04:42 < wumpus> MarcoFalke: yes, I guess so
04:43 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
04:44 < wumpus> it didn't work automatically, though I could force it to connect with "addnode hostname onetry"
04:44 < wumpus> now it shows up in getaddednodeinfo
04:45 < sipa> over long periods of time, it will end up connecring to the addnode nodes when other outgoing connections die
04:45 < wumpus> but I disconnected all other nodes; I don't see why I would have to wait longer than 2 minutes in that case
04:45 < wumpus> in any case I managed to force it to connect and it shows up in getaddednodeinfo correcty
04:47 < wumpus> I still hope Matt can give #8113 a try
04:47 < wumpus> and check it still does whatever he expects from it
04:47 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
04:48 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
04:51 -!- cryptapus_ is now known as cryptapus
05:10 -!- Inaltoasinistra [~jonathan@5-157-127-0.v4.ngi.it] has joined #bitcoin-core-dev
05:18 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
05:28 < murch> sipa: Perhaps you remember that we talked about the Coin Selection algorithm a little bit about a month ago. I'm now indeed writing my Master's thesis about that problem. :) I was wondering if someone could confirm or deny my understanding of the current algorithm's behavior.
05:28 < murch> https://github.com/bitcoin/bitcoin/blob/fb0ac482eee761ec17ed2c11df11e054347a026d/src/wallet/wallet.cpp#L1863
05:29 < murch> Do I understand correctly, that this actually uses the sorted list (decreasing) of available UTXO and selects each UTXO with a 50%? That would easily explain the growth of the UTXO set, if I'm not mistaken.
05:29 -!- cryptapus_ [~cyptapus@66.119.84.15] has joined #bitcoin-core-dev
05:29 -!- cryptapus_ [~cyptapus@66.119.84.15] has quit [Changing host]
05:29 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
05:30 < sipa> murch: i can't say that i've ever looked at the algorithm in detail
05:32 < sipa> murch: it looks like it does 1000 iterations over all UTXOs twice, stopping when it goes over the maximum
05:33 < murch> sipa: But vValue is sorted in decreasing order by size, and it starts at the front selecting UTXO with a random binary chance. That would significantly increase the chance for large UTXO to be selected as inputs, especially since the maximum should be reached quickly when big inputs are added first.
05:33 -!- cryptapus [~cyptapus@unaffiliated/cryptapus] has quit [Ping timeout: 240 seconds]
05:34 < murch> I used to think that it randomly selected from all UTXO with equal chance (that's what I simulated two years ago), but I just realized yesterday, that it doesn't seem to do that (anymore?).
05:35 < murch> Unless I'm jut confused about what's happening there, because that seems like a really easy explanation for the UTXO growth.
05:35 < sipa> murch: it's in increasing value, i think?
05:36 < sipa> CompareValueOnly does a < for the value
05:36 < murch> sipa: sort() puts it in ascending order, and it is reversed afterwards: https://github.com/bitcoin/bitcoin/blob/fb0ac482eee761ec17ed2c11df11e054347a026d/src/wallet/wallet.cpp#L1962
05:37 < sipa> oh, right
05:37 < instagibbs> it used to be a much more ocnfusing rsort....
05:38 < murch> instagibbs: Yeah, I proposed to at least split it in two lines for better readability. :)
05:39 < murch> sipa: Now don't fix it today though, I still want to write my thesis on it! ^^
05:39 < sipa> murch: i'm not going to fix anything; i hope you do :)
05:41 < murch> sipa: But, it would be very helpful to me if you could tell me whether I understood correctly what it does there, and I'm not overlooking something glaringly obvious. Because my next step would be to simulate how much of a difference it would make to pick randomly instead of from the front.
05:41 < murch> Seems like a good idea to check the facts before I spend a bunch of hours on something useless. :)
05:41 < sipa> i think you've looked at it better than i have
05:42 < murch> Yeah, but my overall familiarity with the Bitcoin Core is slightly behind yours. ;) But I guess, I'd count that as an "I haven't seen anything that contradicts Murch". :)
05:43 < murch> Then… coming up next, simulation results, I hope.
05:45 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
05:46 < murch> sipa: Thanks
05:47 < MarcoFalke> murch: Correct
05:47 < murch> MarcoFalke: Thank you
05:47 < MarcoFalke> The first pass is selecting a coin with prob .5 as long as the target is not reached
05:47 < sipa> perhaps you should talk to MarcoFalke instead :)
05:48 < murch> Yeah, I believe we've collaborated on this last time around as well. :)
05:48 < MarcoFalke> The second pass will select anything that is not included as long as the target is not reached
05:48 < NicolasDorier> might be useful to see the votes http://api.qbit.ninja/versionstats
05:48 < MarcoFalke> But in any case it will always "unselect" coins when the target was reached to try to "hit the target better" by trying with smaller coins
05:49 < murch> MarcoFalke: I didn't realize this before, but that approach significantly biases towards selecting large UTXO. Do you remember whether the algorithm used to work differently? That would explain the accelerated growth of the UTXO set, no?
05:49 < murch> Aaah, right. I had forgotten about that.
05:49 < MarcoFalke> I think this is still the way satoshi wrote it
05:50 -!- _anthony_ [~anthony@ec2-54-164-183-56.compute-1.amazonaws.com] has joined #bitcoin-core-dev
05:50 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
05:50 < MarcoFalke> (you could check git log -S or something)
05:50 < instagibbs> murch, you have to remember that excessive amounts of inputs take longer to verify
05:50 < instagibbs> might be taken into account
05:51 < _anthony_> morning all
05:51 < MarcoFalke> The problem is that zero-fee (free) transaction were more common back then
05:51 < MarcoFalke> Right now transaction with no fee (trying to "pay" with priority) are impossible to get through
05:51 < sipa> if you're not trying to hit the target exactly, i think you can limit yourself to only choosing a certain number of utxos from within a range around the target value (say [0.1*target...3*target]
05:51 < MarcoFalke> but coin selection was not adjusted accordingly
05:52 < murch> instagibbs: I solved that by outsourcing the selection to a binary array that flags selected inputs, instead of directly creating sets. That made it much faster. (or do you mean for confirmation on the network?)
05:52 < instagibbs> murch, signing the txn requires hashing the txn over and over for each input.
05:52 < instagibbs> (pre-segwit)
05:53 < murch> instagibbs: Ah, now I get what you mean. Yes, I'm aware. There are also a bunch of other incentives why you don't want to use too many inputs such as fees, and privacy. I'm working on properly writing up all those constraints and requirements for my thesis. :)
05:53 < _anthony_> I have a question: as far as I can tell, script versioning lets you put arbitrary data in the blockchain (just use an unused version number). Is this right?
05:54 < instagibbs> I'm almost sure it wasn't the original idea though, just saying. As sipa said you can simply make sure it doesn't do that by bounding input size
05:55 < instagibbs> _anthony_, the block cost is still static
05:55 < MarcoFalke> murch, you are welcome to do a presentation on your results during a irc meeting 
05:56 < MarcoFalke> they are every thursday
05:56 < _anthony_> hmm, yeah, I guess it isn't really much of an advantage
05:57 < murch> MarcoFalke: Thank you, I'd be happy to. I'll get in touch when I have something to present. Perhaps not this week, but next week.
05:57 < instagibbs> _anthony_, otherwise someone today could send a v16 segwit transaction, and stuff 8GB in it
05:57 < MarcoFalke> no pressure :)
05:58 < murch> MarcoFalke: Well, this time I'm fairly certain that I'll have something to present, as in October, I'll have to present some fifty odd pages of work. :)
05:58 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has quit [Remote host closed the connection]
05:58 < instagibbs> murch, will it include a PR? ;)
05:58 < MarcoFalke> We should look at the new model first
05:59 < murch> instagibbs: That's the plan, although my advisor scolded me last time that it's not part of my thesis, just an added bonus for myself. :)
05:59 < MarcoFalke> Otherwise the pr will receive no review and bitrot instantly
06:00 < _anthony_> yeah I caught that part....I was thinking of how you could make an altcoin using script versioning, but really it wouldn't provide any advantage over regular anyone-can-spend txes
06:00 < murch> instagibbs: Main goals of the work are a comprehensive overview of the problem, the different parameters and approaches how it could be solved, and an evaluation of said approaches. Whether or not it gets adopted by Bitcoin Core is not part of my thesis, but a personal goal. :)
06:00 < _anthony_> you'd have to have support of >50% of miners or else anyone could spend your altcoins out from under you
06:03 < murch> MarcoFalke: Noted. :)
06:10 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has quit [Quit: Conversation terminated!]
06:11 -!- cryptapus_ [~cyptapus@87.254.202.237] has joined #bitcoin-core-dev
06:11 -!- cryptapus_ [~cyptapus@87.254.202.237] has quit [Changing host]
06:11 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
06:31 -!- Amnez777 [~Amnez777@37.157.216.176] has quit [Ping timeout: 272 seconds]
06:37 -!- Amnez777 [~Amnez777@37.157.216.176] has joined #bitcoin-core-dev
06:43 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds]
06:44 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
06:46 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
06:51 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
06:57 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has quit [Ping timeout: 244 seconds]
07:01 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
07:10 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Quit: WeeChat 0.4.2]
07:12 -!- xiangfu [~xiangfu@123.125.212.64] has joined #bitcoin-core-dev
07:13 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #bitcoin-core-dev
07:13 -!- Chris_St1 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
07:21 -!- xiangfu [~xiangfu@123.125.212.64] has quit [Ping timeout: 240 seconds]
07:24 < Chris_St1> Is there a reason the user agent inside of a version message would change when connecting to nodes within a 5 second period? On testnet..
07:24 < sipa> the agent you sent send, or receive?
07:25 < wumpus> at least bitcoin core doesn't change the 'user agent' on such conditions, no
07:26 < Chris_St1> I'm sending a version message to a tesnet dns seed, and receiving their version message back. If I do this within a 5 second period I'm getting different versions on that same node
07:26 < wumpus> although you should avoid connecting to nodes too intensively
07:26 < Chris_St1> i.e /Satoshi:0.12.0/ then 5 seconds later /Satoshi:0.11.2/ 
07:26 < wumpus> 'change your user agent' isn't a very useful defense against that
07:27 < wumpus> you're connecting to the seed, as in the DNS name? that resolves to a different host every time
07:27 < Chris_St1> mmm yes that could be it
07:27 < sipa> pretty sure that's it :)
07:28 < Chris_St1> Yep. Doh! 
07:28 < Chris_St1> Thansk
07:31 < sipa> no results from x9.testnet-seed.bitcoin.jonasschnelli.ch :(
07:31 < jonasschnelli> sipa: this means no NODE_WITNESS nodes...
07:32 < sipa> indeed.
07:32 < sipa> that's pretty bad
07:32 < sdaftuar> i have one if you want to connect to it
07:32 < instagibbs> sipa, where should ACKs be going for segwit pr
07:32 < jonasschnelli> sipa: I guess in master the dnsseed.dump does not list the service flags?
07:33 < sipa> jonasschnelli: it does
07:33 < jonasschnelli> ah .. yes. second last col
07:33 < sipa> under svcs
07:34 < wumpus> instagibbs: https://github.com/bitcoin/bitcoin/pull/7910
07:34 -!- Chris_St1 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Quit: WeeChat 0.4.2]
07:35 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
07:35 < instagibbs> wumpus, roger
07:36 < sipa> wumpus, instagibbs: yeah, let's keep everhthing on 7910... thoughit's 8149 that would be merged, i guess
07:37 < instagibbs> that's fine
07:38 < btcdrak> maybe you can put an ACK transfer list in #8149 like was done in #7524
07:40 < jonasschnelli> sipa: Yes. There are no nodes with 00000009
07:41 < jonasschnelli> Could it be because I scan though tor? I guess should result in ~the same when scanning not through tor
07:41 < sipa> i guess there just are very few
07:47 < sdaftuar> i believe there are very few
07:47 < sdaftuar> i hacked my code recently to only connect to witness peers, and let it run for a long time (~hours) without finding anyone
07:48 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
07:50 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds]
07:53 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
07:56 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev
08:05 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
08:16 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has quit [Ping timeout: 250 seconds]
08:20 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev
08:26 -!- cryptapus_ [~cyptapus@87.254.202.199] has joined #bitcoin-core-dev
08:26 -!- cryptapus_ [~cyptapus@87.254.202.199] has quit [Changing host]
08:26 -!- cryptapus_ [~cyptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
08:31 -!- cryptapus_ is now known as cryptapus
08:46 -!- xiangfu [~xiangfu@123.125.212.64] has joined #bitcoin-core-dev
08:49 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
08:53 -!- xiangfu [~xiangfu@123.125.212.64] has quit [Remote host closed the connection]
08:54 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
08:59 -!- xiangfu [~xiangfu@123.125.212.64] has joined #bitcoin-core-dev
09:02 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds]
09:02 -!- Amnez777 [~Amnez777@37.157.216.176] has quit [Ping timeout: 244 seconds]
09:05 -!- murch [~murch@p4FE38CDB.dip0.t-ipconnect.de] has quit [Quit: Leaving.]
09:06 -!- Amnez777 [~Amnez777@37.157.216.176] has joined #bitcoin-core-dev
09:06 -!- cryptapus_afk [~cryptapus@unaffiliated/cryptapus] has quit [Remote host closed the connection]
09:06 -!- cryptapus_afk [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev
09:06 -!- cryptapus_afk [~cryptapus@jupiter.osmus.org] has quit [Changing host]
09:06 -!- cryptapus_afk [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
09:09 -!- aureianimus_ [~quassel@s55963df3.adsl.online.nl] has joined #bitcoin-core-dev
09:20 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has quit [Ping timeout: 276 seconds]
09:21 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev
09:22 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
09:26 -!- jtimon [~quassel@4.28.134.37.dynamic.jazztel.es] has quit [Remote host closed the connection]
09:29 -!- xiangfu [~xiangfu@123.125.212.64] has quit [Remote host closed the connection]
09:34 -!- mkarrer [~mkarrer@80.red-79-151-141.dynamicip.rima-tde.net] has quit []
09:37 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds]
09:40 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
09:51 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
09:56 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
10:00 -!- mkarrer [~mkarrer@96.red-79-151-27.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
10:21 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has joined #bitcoin-core-dev
10:25 -!- spudowiar1 [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev
10:26 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has quit [Quit: laurentmt]
10:41 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-kapjdlsuceqxxncx] has quit [Quit: Connection closed for inactivity]
10:41 -!- MarcoFalke [~marco@host10-2.natpool.mwn.de] has left #bitcoin-core-dev []
10:43 -!- mkarrer [~mkarrer@96.red-79-151-27.dynamicip.rima-tde.net] has quit []
10:46 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 250 seconds]
10:49 -!- mkarrer [~mkarrer@54.red-79-151-27.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
10:51 -!- kadoban [~mud@unaffiliated/kadoban] has joined #bitcoin-core-dev
10:52 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
10:53 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection]
10:54 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
10:55 -!- mkarrer_ [~mkarrer@54.red-79-151-27.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
10:55 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev
10:56 -!- mkarrer_ [~mkarrer@54.red-79-151-27.dynamicip.rima-tde.net] has quit [Client Quit]
10:57 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
10:59 -!- mkarrer [~mkarrer@54.red-79-151-27.dynamicip.rima-tde.net] has quit [Ping timeout: 276 seconds]
11:00 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Ping timeout: 244 seconds]
11:13 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
11:17 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Ping timeout: 250 seconds]
11:54 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
11:59 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
12:28 -!- murch [~murch@p4FE38CDB.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
12:37 -!- bsm1175321 [~mcelrath@38.121.165.30] has joined #bitcoin-core-dev
12:55 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
12:56 -!- cryptapus [~cyptapus@unaffiliated/cryptapus] has quit [Ping timeout: 246 seconds]
12:58 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has quit [Quit: bai]
13:00 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
13:20 -!- spudowiar1 is now known as spudowiar
13:26 -!- ennui [~user@unaffiliated/ennui] has joined #bitcoin-core-dev
13:43 -!- murch [~murch@p4FE38CDB.dip0.t-ipconnect.de] has quit [Quit: Leaving.]
13:48 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
13:57 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
14:01 -!- Frederic94500 [4d808e1f@gateway/web/freenode/ip.77.128.142.31] has joined #bitcoin-core-dev
14:02 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
14:05 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
14:05 -!- neuroses1412 [~neuroses@149.42.155.104.bc.googleusercontent.com] has joined #bitcoin-core-dev
14:05 -!- neuroses1412 [~neuroses@149.42.155.104.bc.googleusercontent.com] has quit [Changing host]
14:05 -!- neuroses1412 [~neuroses@unaffiliated/neuroses1412] has joined #bitcoin-core-dev
14:06 -!- Frederic94500 [4d808e1f@gateway/web/freenode/ip.77.128.142.31] has quit [Ping timeout: 250 seconds]
14:08 -!- neuroses1412 [~neuroses@unaffiliated/neuroses1412] has quit [Client Quit]
14:08 -!- neuroses1412 [~neuroses@unaffiliated/neuroses1412] has joined #bitcoin-core-dev
14:09 -!- neuroses1412 [~neuroses@unaffiliated/neuroses1412] has quit [Client Quit]
14:10 -!- instagibbs [~instagibb@pool-100-15-114-5.washdc.fios.verizon.net] has quit [Ping timeout: 260 seconds]
14:11 -!- neuroses1412 [~neuroses@unaffiliated/neuroses1412] has joined #bitcoin-core-dev
14:13 -!- cheese_ [~x@unaffiliated/cheeseo] has quit [Read error: Connection reset by peer]
14:15 -!- instagibbs [~instagibb@pool-100-15-114-5.washdc.fios.verizon.net] has joined #bitcoin-core-dev
14:19 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds]
14:35 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
14:47 -!- Cheeseo [~x@unaffiliated/cheeseo] has joined #bitcoin-core-dev
14:55 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Ping timeout: 244 seconds]
14:58 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
15:01 -!- afk11 [~afk11@109.255.154.81] has joined #bitcoin-core-dev
15:01 -!- afk11 [~afk11@109.255.154.81] has quit [Changing host]
15:01 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev
15:03 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
15:15 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has joined #bitcoin-core-dev
15:16 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
15:17 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has quit [Remote host closed the connection]
15:18 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
15:19 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has joined #bitcoin-core-dev
15:21 -!- gevs [~greg@unaffiliated/gevs] has quit [Ping timeout: 240 seconds]
15:26 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wppwsvyjcphotzzc] has joined #bitcoin-core-dev
15:32 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
15:35 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev
15:42 -!- _anthony_ [~anthony@ec2-54-164-183-56.compute-1.amazonaws.com] has quit [Quit: WeeChat 1.3]
15:51 -!- hsmiths2 [~hsmiths@cpe-76-174-26-91.socal.res.rr.com] has joined #bitcoin-core-dev
15:51 -!- hsmiths [~hsmiths@cpe-76-174-26-91.socal.res.rr.com] has quit [Read error: Connection reset by peer]
15:53 < GitHub116> [bitcoin] nathaniel-mahieu opened pull request #8203: Clarify documentation for running a tor node (master...master) https://github.com/bitcoin/bitcoin/pull/8203
15:56 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
15:56 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev
15:59 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
16:04 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
16:19 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]
16:28 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Remote host closed the connection]
16:29 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has quit [Remote host closed the connection]
16:30 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev
16:30 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has quit [Remote host closed the connection]
16:31 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev
16:32 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has quit [Remote host closed the connection]
16:32 -!- murch [~murch@p4FE38CDB.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
16:32 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev
16:33 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has quit [Remote host closed the connection]
16:33 -!- teward [teward@ubuntu/member/teward] has quit [Quit: Disconnected]
16:34 -!- teward [teward@ubuntu/member/teward] has joined #bitcoin-core-dev
16:35 -!- ennui [~user@unaffiliated/ennui] has quit [Ping timeout: 240 seconds]
16:35 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has joined #bitcoin-core-dev
16:35 -!- farghaly [c4ddd999@gateway/web/freenode/ip.196.221.217.153] has joined #bitcoin-core-dev
16:36 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has quit [Ping timeout: 250 seconds]
16:53 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
16:56 -!- murch [~murch@p4FE38CDB.dip0.t-ipconnect.de] has quit [Quit: Leaving.]
16:58 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Ping timeout: 252 seconds]
16:59 -!- ennui [~user@unaffiliated/ennui] has joined #bitcoin-core-dev
16:59 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has quit [Remote host closed the connection]
17:00 -!- farghaly [c4ddd999@gateway/web/freenode/ip.196.221.217.153] has quit [Ping timeout: 250 seconds]
17:01 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
17:06 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
17:09 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
17:10 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
17:12 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 272 seconds]
17:14 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
17:19 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has joined #bitcoin-core-dev
17:20 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 244 seconds]
17:20 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
17:25 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev
17:26 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has quit [Remote host closed the connection]
17:27 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds]
17:33 -!- proslogion [~proslogio@90.210.173.173] has quit [Ping timeout: 240 seconds]
17:37 -!- ennui [~user@unaffiliated/ennui] has quit [Ping timeout: 244 seconds]
17:42 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
17:56 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
18:01 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wppwsvyjcphotzzc] has quit [Quit: Connection closed for inactivity]
18:02 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
18:07 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
18:13 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has quit []
18:34 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
18:40 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
18:41 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
18:50 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
18:53 -!- xiangfu [~xiangfu@58.135.95.134] has joined #bitcoin-core-dev
19:01 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds]
19:16 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
19:20 -!- hsmiths2 [~hsmiths@cpe-76-174-26-91.socal.res.rr.com] has quit [Quit: END OF LINE]
19:23 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds]
19:27 -!- hsmiths [~hsmiths@cpe-76-174-26-91.socal.res.rr.com] has joined #bitcoin-core-dev
19:32 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
20:03 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev
20:33 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
20:35 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
20:41 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev
20:41 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Read error: Connection reset by peer]
20:47 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has quit [Quit: Leaving.]
21:14 < GitHub114> [bitcoin] petertodd opened pull request #8204: Update petertodd's testnet seed (master...2016-06-15-update-tbtc-seed) https://github.com/bitcoin/bitcoin/pull/8204
21:19 -!- frankenmint [~frankenmi@67-5-211-132.ptld.qwest.net] has joined #bitcoin-core-dev
21:27 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
21:41 -!- go1111111 [~go1111111@104.200.154.22] has quit [Ping timeout: 276 seconds]
21:48 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has quit [Remote host closed the connection]
21:51 -!- fengling [~fengling@58.135.95.133] has quit [Ping timeout: 240 seconds]
21:54 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev
21:55 -!- jiggalator [~jiggalato@unaffiliated/jiggalator] has quit [Client Quit]
22:14 -!- dingus [~grubles@unaffiliated/grubles] has quit [Ping timeout: 240 seconds]
22:18 -!- fengling [~fengling@58.135.95.133] has joined #bitcoin-core-dev
22:27 -!- dingus [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev
22:27 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
22:32 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [Ping timeout: 246 seconds]
22:42 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
23:04 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit []
23:38 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
23:40 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 244 seconds]