1 2017-07-23 00:54:33	0|NicolasDorier|sipa: in my case it is p2wsh, will take a look when I get my pc back
  2 2017-07-23 00:55:07	0|NicolasDorier|Yes p2wsh without p2sh
  3 2017-07-23 04:15:07	0|btcdrak|4 blocks to go
  4 2017-07-23 04:18:20	0|arubi|https://pastebin.com/raw/t0qiBaEW invalid block relayed
  5 2017-07-23 04:20:23	0|arubi|error is ERROR: ConnectBlock(): inputs missing/spent
  6 2017-07-23 04:23:51	0|gmaxwell|So a bit ago 1hash produced in invalid block
  7 2017-07-23 04:24:03	0|gmaxwell|It has a transaction whos parent wasn't in the block.
  8 2017-07-23 04:24:22	0|gmaxwell|They did also did this two weeks ago.
  9 2017-07-23 04:24:42	0|gmaxwell|And when asked about it they reported that it was an error with automation.
 10 2017-07-23 04:24:59	0|praxeology|"an error with automation" :)
 11 2017-07-23 04:25:20	0|gmaxwell|This new block, like the prior invalid block, has exactly 256 transactions.
 12 2017-07-23 04:26:58	0|gmaxwell|I'll leave it to others to form their own suspicions; but it seems pretty clear that this isn't a direct result of today's network fun.
 13 2017-07-23 04:29:12	0|praxeology|256 could be made into a very evenly filled tree, maybe they were swapping transactions... and they swapped out the wrong one?
 14 2017-07-23 04:29:49	0|praxeology|swapping algorithm doesn't do a very good job checking for dependencies?
 15 2017-07-23 04:33:21	0|BlueMatt|praxeology: that is one conclusion
 16 2017-07-23 04:33:31	0|BlueMatt|and likely the most obvious
 17 2017-07-23 04:34:14	0|gmaxwell|offtopic for here for now
 18 2017-07-23 04:34:26	0|praxeology|I would guess that gmaxwell is suggesting that the purpose of the swapping might be to perform ASICB... oh offtopic
 19 2017-07-23 04:34:30	0|gmaxwell|in any case, I just wanted to make it clear that this has happened before with this miner and isn't some BIP-91 thing.
 20 2017-07-23 04:34:43	0|gmaxwell|{
 21 2017-07-23 04:34:43	0|gmaxwell|"height": 477115,
 22 2017-07-23 04:34:44	0|gmaxwell|"hash": "0000000000000000013ee4a86822d37a061732e04ee5f41fb77168f193363d1b",
 23 2017-07-23 04:34:46	0|gmaxwell|"branchlen": 1,
 24 2017-07-23 04:34:49	0|gmaxwell|"status": "invalid"
 25 2017-07-23 04:34:51	0|gmaxwell|},
 26 2017-07-23 04:46:57	0|gmaxwell|Active.
 27 2017-07-23 04:49:49	0|btcdrak|121 no forks detected yet
 28 2017-07-23 04:52:19	0|praxeology|Canoe was like the last significant hashpower miner hold out on signaling... so it might be a full day or more before someone makes a non-segwit signaling block
 29 2017-07-23 04:53:05	0|achow101|praxeology: their stratum had segwit this morning, but they were not mining segwit block for some reason.
 30 2017-07-23 04:53:17	0|achow101|we contacted them and it looks like they fixed it afterwards
 31 2017-07-23 04:53:24	0|praxeology|unless... someone does it on purpose to test it and potentially waste $39,000
 32 2017-07-23 04:54:48	0|btcdrak|I emailed Canoe and Connect this morning. Connect immediately updated their Stratum
 33 2017-07-23 04:55:07	0|gmaxwell|btcdrak: it's interesting that their public stratum was already okay.
 34 2017-07-23 04:55:35	0|btcdrak|gmaxwell: maybe they have a private mine, or VIP pool for special customers?
 35 2017-07-23 04:55:48	0|gmaxwell|ya, I'm sure it was something like that.
 36 2017-07-23 04:55:55	0|praxeology|maybe... their private server runs a different algorithm
 37 2017-07-23 04:56:06	0|praxeology|*private server farm
 38 2017-07-23 04:56:20	0|BlueMatt|praxeology: full day? prob closer to 2
 39 2017-07-23 04:56:37	0|BlueMatt|achow101: looks like they fixed it china-morning today
 40 2017-07-23 04:57:03	0|BlueMatt|gmaxwell: (almost all pools have "VIP" stratum endpoints they set up when asked if you have lots of hashrate, so thats not strange)
 41 2017-07-23 04:57:53	0|achow101|BlueMatt: I noticed
 42 2017-07-23 05:41:37	0|gmaxwell|btcdrak: I see miners still setting 4, this is going to cause segsignal and btc1 to throw warnings.
 43 2017-07-23 12:08:59	0|bitcoin-git|[13bitcoin] 15tiagmoraismorgado opened pull request #10913: fixing a couple of typos (06master...06patch-2) 02https://github.com/bitcoin/bitcoin/pull/10913
 44 2017-07-23 12:17:20	0|bitcoin-git|[13bitcoin] 15fanquake closed pull request #10913: fixing a couple of typos (06master...06patch-2) 02https://github.com/bitcoin/bitcoin/pull/10913
 45 2017-07-23 18:14:15	0|achow101|I just looked into the second 1hash invalid block and it looks like the transaction with missing inputs actually has its parent transaction farther down in the block
 46 2017-07-23 18:25:40	0|praxeology|achow101: oh really? as in maybe mid-tree nodes had been swapped?
 47 2017-07-23 18:28:17	0|arubi|what's the child's txid achow101 ?
 48 2017-07-23 18:39:47	0|arubi|uhh, I'm getting much more than one
 49 2017-07-23 18:40:37	0|arubi|I'm getting all of these (reversed bytes) grep-able in the hex block https://0bin.net/paste/X2984kGzXMzqfSVN#XdVdT8WRmJ0J733Y78ZxddH8ssahW212qTkVXaWytXr
 50 2017-07-23 18:43:32	0|arubi|hm, maybe wrong :\
 51 2017-07-23 18:43:50	0|arubi|ah no, that should be right, but some of the ordering might be correct.  I didn't check
 52 2017-07-23 18:44:52	0|arubi|the txids as core sees them are https://0bin.net/paste/CMTE11Ng6NI2J4Z1#k03F6Ns2u16Ode4aAUsjWZ2s7tfpi4ONQotxq3GapxQ
 53 2017-07-23 18:52:18	0|achow101|arubi: 7a122ef22468e4af16b010d7acf7aa81e5af3636423c613fd98246c179d79800 is the child, parent is 9639dd073e67efc879abb1075fafa4fa23d5fa427c129b2b1dd4f5a5520b408d
 54 2017-07-23 18:52:26	0|bitcoin-git|[13bitcoin] 15TheBlueMatt opened pull request #10914: Add missing lock in CScheduler::AreThreadsServicingQueue() (06master...062017-04-fix-missing-scheduler-lock) 02https://github.com/bitcoin/bitcoin/pull/10914
 55 2017-07-23 18:53:43	0|arubi|thanks, looks like it's one of the catches alright
 56 2017-07-23 18:53:52	0|arubi|(parent)
 57 2017-07-23 19:16:54	0|BlueMatt|whats the expected outcome if a node that is reindexing connects to you?
 58 2017-07-23 19:35:52	0|bitcoin-git|[13bitcoin] 15benma opened pull request #10915: get rid of the fRelayTxes global (06master...06fRelayTxes) 02https://github.com/bitcoin/bitcoin/pull/10915
 59 2017-07-23 19:59:06	0|BluePills|I have a wallet and it's saying locked amount. How to make it available?
 60 2017-07-23 20:04:10	0|sipa|do you use lockunspent and/or fundrawtransaction RapCs?
 61 2017-07-23 20:04:16	0|sipa|RPC?
 62 2017-07-23 20:40:32	0|phantomcircuit|the wallet backup functional test doesn't seem to ever work
 63 2017-07-23 20:41:47	0|phantomcircuit|BlueMatt, it *should* add any new blocks it sees to the headers list and then request those blocks once it's finished reindexing
 64 2017-07-23 20:41:52	0|phantomcircuit|not sure what actually happens
 65 2017-07-23 20:42:30	0|BlueMatt|phantomcircuit: dunno, got a guy I'm talking to claiming to run stock ppa 0.14.2 with a somewhat-reasonable bitcoin.conf and his node isnt sending any messages (not even veracks)
 66 2017-07-23 20:44:29	0|phantomcircuit|BlueMatt, that doesn't sound right
 67 2017-07-23 20:44:49	0|BlueMatt|phantomcircuit: it sends initial version message *if* its connecting outbound, though
 68 2017-07-23 20:44:56	0|BlueMatt|(ie his message handler thread is fucked)
 69 2017-07-23 20:45:06	0|BlueMatt|but i dont see a reasonable explination of how that could happen
 70 2017-07-23 20:46:42	0|phantomcircuit|BlueMatt, the reindex stuff could be holding locks for very very long times as a result of a failing hdd or something
 71 2017-07-23 20:46:56	0|BlueMatt|phantomcircuit: initial *outbound* version send takes cs_main, though
 72 2017-07-23 20:46:58	0|BlueMatt|so I dont get it
 73 2017-07-23 20:47:06	0|BlueMatt|like, what, its taking some node lock or smth? makes no sense
 74 2017-07-23 20:48:30	0|phantomcircuit|BlueMatt, sort of hard to say what's happening there without more information
 75 2017-07-23 20:48:38	0|phantomcircuit|kind of sounds like ShitsFucked(tm) though
 76 2017-07-23 20:49:14	0|BlueMatt|yea, thats my impression, I'm also not sure what else to ask the guy
 77 2017-07-23 20:49:22	0|BlueMatt|not much more information that woul be useful
 78 2017-07-23 20:49:38	0|phantomcircuit|can he attach gdb to it and get stack traces?
 79 2017-07-23 20:49:48	0|BlueMatt|his msghandler thread is using a small but non-0 cpu time implying its not proper-hung
 80 2017-07-23 20:49:59	0|gmaxwell|BlueMatt: its still reindexing however?
 81 2017-07-23 20:50:32	0|gmaxwell|if so, sounds like you should just attempt to reproduce.
 82 2017-07-23 20:51:23	0|BlueMatt|i believe so
 83 2017-07-23 20:56:45	0|phantomcircuit|i get the feeling reproducing is going to be hard
 84 2017-07-23 20:57:01	0|BlueMatt|yea, that
 85 2017-07-23 21:35:36	0|gmaxwell|how is it going to be hard. Reindex and see if the network is braindead.
 86 2017-07-23 21:41:55	0|bitcoin-git|[13bitcoin] 15benma opened pull request #10916: add missing lock to crypter GetKeys() (06master...06GetKeys) 02https://github.com/bitcoin/bitcoin/pull/10916
 87 2017-07-23 21:53:30	0|BlueMatt|gmaxwell: E_CANT_REPRODUCE
 88 2017-07-23 21:54:34	0|phantomcircuit|BlueMatt, i am le shocked
 89 2017-07-23 21:56:38	0|sipa|xkcd 583...
 90 2017-07-23 21:59:17	0|BlueMatt|gah, sipa you were correct
 91 2017-07-23 22:00:18	0|BlueMatt|but then became un-correct
 92 2017-07-23 22:18:34	0|sipa|BlueMatt: the weird thing i observed was that if you interrupt mid-reindex, and then restart it will first activate the reindexed-so-far part before continuing the reindex again
 93 2017-07-23 22:18:45	0|sipa|BlueMatt: however, the same turns out to be true in master
 94 2017-07-23 22:19:41	0|BlueMatt|wait, didnt you tell me that it was not the case later?
 95 2017-07-23 22:19:46	0|BlueMatt|ehh, whatever, its now fixed in the pr
 96 2017-07-23 22:22:13	0|sipa|i thought it was worth fixing, but wasn't a critical thing to have in 0.15, so i didn't want to burden you with fixing an extra pre-existing weirdness
 97 2017-07-23 22:22:23	0|sipa|if you've fixed it now, so much the better
 98 2017-07-23 22:22:26	0|sipa|i'll test it again
 99 2017-07-23 22:24:22	0|BlueMatt|sipa: it is a regression, I believe
100 2017-07-23 22:24:28	0|BlueMatt|is it not also broken in 14?
101 2017-07-23 22:26:40	0|sipa|BlueMatt: unsure
102 2017-07-23 22:27:06	0|BlueMatt|ah, i fixed cause i assumed regression
103 2017-07-23 22:27:13	0|BlueMatt|anyway, its clearly the intended behavior, so.....
104 2017-07-23 22:27:25	0|sipa|agree.
105 2017-07-23 23:58:09	0|bitcoin-git|[13bitcoin] 15jamesob closed pull request #10903: Add configuration files for a Docker-based development environment (06master...06docker) 02https://github.com/bitcoin/bitcoin/pull/10903