--- Day changed Mon Nov 02 2015 00:06 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev 01:01 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 01:22 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 01:57 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 02:48 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Ping timeout: 246 seconds] 02:48 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev 02:55 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Ping timeout: 260 seconds] 02:56 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Ping timeout: 260 seconds] 03:05 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev 05:02 -!- ParadoxSpiral [~ParadoxSp@p508B9E91.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 05:04 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 05:04 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Excess Flood] 05:04 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 05:04 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Excess Flood] 05:04 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 05:04 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Excess Flood] 05:05 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 05:05 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Excess Flood] 05:05 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 05:05 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Excess Flood] 05:20 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.] 05:22 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer] 05:23 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev 05:41 < morcos> sipa: i have a few questions for you when you have a couple mins 05:43 < morcos> 1) secp256k1, i've been doing my benchmarking on ConnectBlock and CreateNewBlock improvements assuming that might be released and merged for 0.12. It's fine either way, but do you have a sense of status? 05:44 < morcos> 2) I'd like to create a modification to UpdateCoins so that when you are explicitly creating the outputs for a new tx you don't touch the database. Should this be a flag to ModifyCoins or a new function NewCoins. 05:45 < morcos> the reaosn I believe this is safe is you blow away the old coins immediately afterwards anyway with FromTx, so if there were some reason those old coins existed (which they shouldn't because then you would no longer have the inputs available anyway) it would already be broken. 05:45 < wumpus> I'm also interested in status of secp256k1 verification :) 05:46 < morcos> but in the depths of brokenness, one difference is whether the new coins i'm creating are marked FRESH or not. since i'm just assuming they don't exist i'd like to mark my new coins as FRESH, but in the circumstance where these were then spent, then the conflicting coins would never be written over the underlying databases coins, unlike what would happen now. 05:47 < morcos> Since this is a slight change in behavior (that should never happen) I wanted hour thoughts on that. 05:48 < morcos> Also this question is for everyone. Thanks to Luke-Jr and gmaxwell I realized you can actually do the priority portion of the block relatively quickly in CreateNewBlock as well. But to do this I need to be able to get priority without accessing inputs. I can think of 3 options: 05:49 < morcos> a) use current CTxMemPoolEntry::GetPriority() which is an upper bound on the possible actual priority (seems bad as it's gameable) 05:50 < morcos> b) take the part of 6357 which calculates inchainInputValue when a mempool entry is created and use that to have a lower bound on actual priority (don't update when further inputs are confirmed) (the downside of this approach is it could be slightly broken during a reorg) 05:51 < morcos> c) use 6357 to dynamically calculate priority. I rebased this and will push. I think its reasonably efficient, but its adding more machinary to support priority, thats also a bit complicated. Is priority here for the forseaeable future? 05:52 < morcos> Oh and one more question sipa. Is 6914 something that you are about to change, should I also benchmark with that included, or hold off? 06:08 -!- treehug8_ [~textual@static-108-30-103-59.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 06:42 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev 06:46 -!- Thireus1 [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev 06:48 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Ping timeout: 264 seconds] 06:51 -!- Thireus1 [~Thireus@icy.thireus.fr] has quit [Ping timeout: 264 seconds] 06:51 -!- sipa [~pw@2a02:348:86:3011::1] has joined #bitcoin-core-dev 06:57 < GitHub153> [bitcoin] laanwj reopened pull request #6248: Fix Qt build on arch by setting -fPIC (master...archbuild) https://github.com/bitcoin/bitcoin/pull/6248 06:59 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev 07:13 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.] 07:14 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev 07:26 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Disconnected by services] 07:27 -!- Arnavion3 [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 07:27 -!- Arnavion3 is now known as Arnavion 07:30 -!- wump [~quassel@pdpc/supporter/professional/wumpus] has joined #bitcoin-core-dev 07:33 -!- CodeShark [CodeShark@cpe-76-167-237-202.san.res.rr.com] has quit [Ping timeout: 252 seconds] 07:35 -!- Netsplit *.net <-> *.split quits: wumpus, BlueMatt, sipa, guruvan 07:37 -!- Netsplit over, joins: BlueMatt 07:37 -!- Netsplit over, joins: guruvan 07:44 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has joined #bitcoin-core-dev 08:07 -!- sipa [~pw@2a02:348:86:3011::1] has joined #bitcoin-core-dev 08:09 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.] 08:24 < morcos> gmaxwell and sipa: re point 2 above. So correct me if I'm wrong. the existing 2 cases of duplicate coin bases are just that only duplicate coin bases. the first coinbase is now overwritten and lost, and as of yet, the second has not been spent. 08:25 < morcos> so in order to preserve correct behavior with that, i do need to make sure I overwrite the existing coins in those 2 cases when we're processing the chain from the beginning. 08:26 < morcos> it seems the best way to do this is to special case coinbase outputs being created (UpdateCoins already special cases coinbases). And in the case of coinbase outputs being created either still do the txdb lookup, or don't mark the new coins as FRESH to force them to be written 08:27 < morcos> i realize this is getting a tad hacky, but it seems its well worth it to avoid all these database lookups 08:28 < morcos> any other thoughts on how to properly accomplish this? 08:33 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has quit [Remote host closed the connection] 08:34 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has joined #bitcoin-core-dev 09:17 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 09:26 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has quit [Ping timeout: 240 seconds] 09:34 -!- deepcore [~deepcore@2a01:79d:469e:ed94:8e70:5aff:fe5c:ae78] has joined #bitcoin-core-dev 09:34 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has joined #bitcoin-core-dev 09:46 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Quit: .] 09:48 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev 10:01 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 10:34 -!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has joined #bitcoin-core-dev 10:34 -!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has quit [Changing host] 10:34 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev 11:31 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has quit [Ping timeout: 268 seconds] 11:48 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 11:50 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 12:30 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev 12:45 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving] 13:16 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev 13:49 -!- ParadoxSpiral [~ParadoxSp@p508B9E91.dip0.t-ipconnect.de] has quit [Quit: cya] 13:54 -!- treehug8_ [~textual@static-108-30-103-59.nycmny.fios.verizon.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 14:09 -!- zooko [~user@c-73-217-96-13.hsd1.co.comcast.net] has joined #bitcoin-core-dev 14:13 -!- zooko` [~user@c-73-217-16-2.hsd1.co.comcast.net] has joined #bitcoin-core-dev 14:15 -!- zooko [~user@c-73-217-96-13.hsd1.co.comcast.net] has quit [Ping timeout: 255 seconds] 14:36 -!- CodeShark [~CodeShark@cpe-76-167-237-202.san.res.rr.com] has joined #bitcoin-core-dev 14:38 -!- zooko` is now known as zooko 14:46 -!- mcelrath [~bsm117532@38.121.165.30] has quit [Ping timeout: 244 seconds] 15:08 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has quit [Ping timeout: 246 seconds] 15:11 < helo> second time today, sync.cpp:112: void potential_deadlock_detected(const std::pair&, const LockStack&, const LockStack&): Assertion `onlyMaybeDeadlock' failed. 15:12 -!- crescendo [~mozart@unaffiliated/crescendo] has joined #bitcoin-core-dev 15:12 < helo> at 725539e, and 8fe30fb4 (~current head) 15:14 < helo> built/running on ubuntu 15.10 with boost 1.58 fwiw 15:41 -!- deepcore [~deepcore@2a01:79d:469e:ed94:8e70:5aff:fe5c:ae78] has quit [Ping timeout: 240 seconds] 15:57 -!- [b__b] [~b__b]@ec2-54-85-45-223.compute-1.amazonaws.com] has quit [Ping timeout: 240 seconds] 16:14 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has quit [Ping timeout: 246 seconds] 16:21 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has quit [Quit: Leaving.] 17:14 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-awjjctyqdtzjmrxb] has quit [Quit: Connection closed for inactivity] 17:43 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: Leaving] 18:01 -!- PRab [~chatzilla@2601:40a:8000:8f9b:d59b:22a1:99bf:deb1] has quit [Quit: ChatZilla 0.9.92 [Firefox 41.0.2/20151014143721]] 18:02 -!- PRab [~chatzilla@2601:40a:8000:8f9b:d59b:22a1:99bf:deb1] has joined #bitcoin-core-dev 18:06 -!- challisto [~challisto@c-76-16-149-33.hsd1.il.comcast.net] has joined #bitcoin-core-dev 18:06 -!- challisto [~challisto@c-76-16-149-33.hsd1.il.comcast.net] has quit [Changing host] 18:06 -!- challisto [~challisto@unaffiliated/challisto] has joined #bitcoin-core-dev 18:13 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 18:20 < GitHub30> [bitcoin] morcos opened pull request #6931: Skip BIP 30 verification where not necessary (master...skipBIP30) https://github.com/bitcoin/bitcoin/pull/6931 18:33 < GitHub1> [bitcoin] morcos opened pull request #6932: ModifyNewCoins saves database lookups (master...newCoinsThinAir) https://github.com/bitcoin/bitcoin/pull/6932 19:01 -!- molly [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 19:03 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 19:07 < midnightmagic> Is there a patch which ignores tx its already seen or is already in the mempool (preferrably pre-BlueMatt's mutation mech?) 19:11 < midnightmagic> or maybe lets me ban that host+src port peer for sending dupes even though it looks as though I have so far never seen a dupe sent? 19:29 -!- CodeShark [~CodeShark@cpe-76-167-237-202.san.res.rr.com] has quit [Ping timeout: 250 seconds] 19:30 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving] 20:08 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has quit [Ping timeout: 255 seconds] 20:24 < btcdrak> bfxda 20:27 -!- challisto [~challisto@unaffiliated/challisto] has quit [Quit: Leaving] 20:56 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev 20:57 < dcousens> hmph, not sure why, but since I re-compiled this node from master and started a re-download, its still ~4 months behind, slowly getting there, but taking forever 20:57 < dcousens> usually a full-resync/download only takes 2-3 days 20:57 < dcousens> This is over a week now 20:57 < dcousens> Any speculation as to why that might have changed since 0.11? 20:58 < sipa> is this a reindex or a redownload? 20:58 < dcousens> redownload 20:59 < dcousens> Would have been a re-index, but cancelled midway causing it to corrupt 21:00 < dcousens> not like its running at 100% either 21:00 < dcousens> plenty of resources all round 21:01 -!- CodeShark [~CodeShark@cpe-75-85-165-151.san.res.rr.com] has joined #bitcoin-core-dev 21:04 < dcousens> hmmm, wait, might have a theory, nvm :) 21:33 < Luke-Jr> dcousens: huh? nothing you can do should ever corrupt to the point reindex fails. 21:38 < dcousens> Luke-Jr: I must be doing something wrong then, restarted bitcoind, hashPrevBlock == view.GetBestBlock() 21:38 < dcousens> assert threw 21:38 < dcousens> sigh, any ideas for reconciliation? 21:38 < Luke-Jr> reindex is the usual solution for that.. 21:39 -!- harding [~harding@mail.dtrt.org] has quit [Ping timeout: 250 seconds] 21:40 -!- harding [~harding@mail.dtrt.org] has joined #bitcoin-core-dev 21:43 < dcousens> Luke-Jr: we'll see how we go 21:43 < dcousens> interesting 21:43 < dcousens> Luke-Jr: since I started the re-index, my node is now showing up correctly on the network in a few places 21:43 < dcousens> I wonder if something was just borked that meant I only connected to 1 or 2 nodes? 21:47 -!- zooko [~user@2601:281:8001:26aa:dd9b:1012:6c2e:3d84] has joined #bitcoin-core-dev 22:25 -!- ParadoxSpiral [~ParadoxSp@p508B857D.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 22:46 -!- deepcore [~deepcore@2a01:79d:469e:ed94:8e70:5aff:fe5c:ae78] has joined #bitcoin-core-dev 22:47 -!- ParadoxSpiral [~ParadoxSp@p508B857D.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 22:59 -!- deepcore [~deepcore@2a01:79d:469e:ed94:8e70:5aff:fe5c:ae78] has quit [Ping timeout: 240 seconds] 23:00 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-kjopeqdjpdvdhwwd] has joined #bitcoin-core-dev 23:02 -!- zooko [~user@2601:281:8001:26aa:dd9b:1012:6c2e:3d84] has quit [Ping timeout: 240 seconds] 23:22 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.] 23:35 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev 23:35 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Client Quit] 23:58 -!- [b__b] [~b__b]@ec2-54-85-45-223.compute-1.amazonaws.com] has joined #bitcoin-core-dev