1 2017-12-28 01:25:41 0|achow101|are we having a meeting tomorrow?
2 2017-12-28 02:49:53 0|echeveria|2017-12-28 02:49:21.589437 Reindexing block file blk00854.dat...
3 2017-12-28 02:49:53 0|echeveria|2017-12-28 02:49:23.455371 LoadExternalBlockFile: Deserialize or I/O error - Read attempted past buffer limit: unspecified iostream_category error
4 2017-12-28 02:49:54 0|echeveria|eh?
5 2017-12-28 02:56:28 0|phantomcircuit|echeveria, disk failure i believe
6 2017-12-28 02:57:17 0|echeveria|looking at the block binaries there's a bunch which fell short of being full. maybe that happens during an unclean shutdown?
7 2017-12-28 02:57:37 0|phantomcircuit|shouldn't
8 2017-12-28 02:57:55 0|phantomcircuit|but i guess a very unclean shutdown could do that
9 2017-12-28 02:58:22 0|phantomcircuit|the blockindex won't point to those but the block file itself would have the partial write
10 2017-12-28 02:59:41 0|echeveria|I'll chalk that up to random corruption.
11 2017-12-28 10:15:57 0|karanlearns|hi
12 2017-12-28 10:16:30 0|karanlearns|when i run make - where is the so file bitcoin-qt generated . is it the one in /usr/bin or the one in src folder
13 2017-12-28 10:21:24 0|karanlearns|arubi: on running make where is the bitcoin-qt so file made ? is it in /usr/bin or the one in src folder ?
14 2017-12-28 10:28:30 0|luke-jr|karanlearns: user questions in #bitcoin
15 2017-12-28 10:38:45 0|karanlearns|luke-jr: i cannot join bitcoin channel, i get switched to bitcoin-unregistered although i have registered. this question is in continuation of my discussion from yesterday do - please accomodate.
16 2017-12-28 10:54:54 0|karanlearns|Hi
17 2017-12-28 10:55:47 0|karanlearns|I tried cd depends , make , cd root , configure prefix = depends build dir , make , I got this error - https://pastebin.com/H1h0z4wY
18 2017-12-28 10:56:02 0|luke-jr|karanlearns: you're not presently identified with NickServ
19 2017-12-28 10:56:33 0|luke-jr|karanlearns: and just because you might not have access to a better place to ask questions, does not justify asking them here
20 2017-12-28 10:59:59 0|karanlearns|rafalcpp: https://pastebin.com/H1h0z4wY
21 2017-12-28 11:00:26 0|karanlearns|luke-jr: sorry. please forgive.
22 2017-12-28 11:02:05 0|karanlearns|arubi: hey . i got this https://pastebin.com/H1h0z4wY
23 2017-12-28 11:09:39 0|sipa|karanlearns: not here, please
24 2017-12-28 11:55:19 0|zelest|morning
25 2017-12-28 14:51:35 0|bitcoin-git|[13bitcoin] 15lionello opened pull request #12040: fix: add support for CORS headers and pre-flight request (06master...06http-options-pre-flight) 02 https://github.com/bitcoin/bitcoin/pull/12040
26 2017-12-28 15:04:03 0|bitcoin-git|[13bitcoin] 15Zelest opened pull request #12041: doc: Rewrite the OpenBSD build instructions (06master...06openbsd-build-revamp) 02 https://github.com/bitcoin/bitcoin/pull/12041
27 2017-12-28 17:34:13 0|provoostenator|sipa: regarding #3220, rather than using a wallet, would it make sense to create a new persistent wallet-ish datastructure that is specifically designed to track a set of outputs?
28 2017-12-28 17:34:15 0|gribble|https://github.com/bitcoin/bitcoin/issues/3220 | Getrawtransaction working partially without -txindex is confusing ÷ Issue #3220 ÷ bitcoin/bitcoin ÷ GitHub
29 2017-12-28 17:37:08 0|sipa|provoostenator: perhaps!
30 2017-12-28 17:37:50 0|sipa|sorry if i'm sounding grumpy there, but all these use cases assuming access to the historical blockchain at all is available kind of annoy me
31 2017-12-28 17:38:09 0|sipa|it's using the easy totally unscalable approach out of laziness
32 2017-12-28 17:39:34 0|provoostenator|I don't mind grumpiness. Just trying to figure out what the right division of labor should be between the Core node and layer 2 stuff.
33 2017-12-28 17:39:53 0|provoostenator|Especially if there's still an opportunity to get a small but useful change into 0.16 while Lightning is also still in alpha.
34 2017-12-28 17:40:27 0|provoostenator|I'm also still trying to understand what exactly these lightning implementations need that an unindexed node can't provide.
35 2017-12-28 17:40:46 0|sipa|i don't mind helping out - but relying on everyone indexing everything and keeping it around just to being able to query 2 transactions from it later
36 2017-12-28 17:40:53 0|sipa|seems a bit silly
37 2017-12-28 17:41:12 0|provoostenator|Especially if you already know the outputs to keep track of.
38 2017-12-28 17:41:46 0|provoostenator|Which by definition you do if you know which tx ids you want to track.
39 2017-12-28 17:42:47 0|provoostenator|Maybe this new data structure can watch for either outputs or specific transactions (don't know if the latter makes things easier).
40 2017-12-28 17:53:22 0|provoostenator|I also wonder how c-lightning works and if it really doesn't need txindex=1 (there's no getrawtransaction in the codebase). I'll take it for a spin.
41 2017-12-28 17:59:45 0|jb55|provoostenator: you have to paste the raw tx via the cli
42 2017-12-28 18:00:22 0|jb55|as described here https://github.com/ElementsProject/lightning#opening-a-channel-on-the-bitcoin-testnet
43 2017-12-28 18:02:31 0|provoostenator|jb55: that's just for funding the wallet right, not for opening a channel and monitoring for unilateral close by the other side?
44 2017-12-28 18:03:45 0|provoostenator|jb55 let's head over to #c-lightning for those details...
45 2017-12-28 19:00:16 0|meshcollider|Is there a meeting today?
46 2017-12-28 19:00:20 0|jonasschnelli|no sure
47 2017-12-28 19:00:25 0|jonasschnelli|Wlad said he's gone this week
48 2017-12-28 19:00:35 0|jonasschnelli|We can start one if there are enough people around
49 2017-12-28 19:00:36 0|provoostenator|Such decentralized...
50 2017-12-28 19:00:42 0|jonasschnelli|:-)
51 2017-12-28 19:01:24 0|cfields|hi
52 2017-12-28 19:02:01 0|jonasschnelli|Meeting request: wumpus sipa gmaxwell jonasschnelli morcos luke-jr btcdrak sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag
53 2017-12-28 19:02:13 0|kanzure|hi.
54 2017-12-28 19:02:53 0|jonasschnelli|Should we cancel this weeks meeting? Seems not much people are around?
55 2017-12-28 19:03:00 0|meshcollider|Doesn't look promising, yeah
56 2017-12-28 19:03:03 0|achow101|Oh, there's a meeting?
57 2017-12-28 19:03:11 0|provoostenator|Or just keep it short if anyone has a topic? I don't.
58 2017-12-28 19:03:18 0|jonasschnelli|#startmeeting
59 2017-12-28 19:03:18 0|lightningbot|Meeting started Thu Dec 28 19:03:17 2017 UTC. The chair is jonasschnelli. Information about MeetBot at http://wiki.debian.org/MeetBot.
60 2017-12-28 19:03:18 0|lightningbot|Useful Commands: #action #agreed #help #info #idea #link #topic.
61 2017-12-28 19:03:25 0|cfields|maybe a quick 15min meeting? I have one short topic, at least
62 2017-12-28 19:03:27 0|achow101|Merge segwit wallet
63 2017-12-28 19:03:33 0|meshcollider|Ok :)
64 2017-12-28 19:03:47 0|jonasschnelli|cfields: you have the stage
65 2017-12-28 19:04:14 0|sipa|i'm at 34C3 with MarkoFalke and BlueMatt
66 2017-12-28 19:04:19 0|cfields|just an update on the codesigning. I've got the csr just about figured out, we should get going on the key creation in parallel
67 2017-12-28 19:04:29 0|jonasschnelli|#topic code signing
68 2017-12-28 19:04:47 0|jonasschnelli|cfields: can you write a short gist/docu how to proceed?
69 2017-12-28 19:04:48 0|cfields|^^ is mainly aimed at gmaxwell, i guess
70 2017-12-28 19:04:51 0|achow101|Who are going to hold the keys?
71 2017-12-28 19:05:13 0|jonasschnelli|achow101: It will be distributed amoung some devs
72 2017-12-28 19:05:34 0|jonasschnelli|though, at least for apple, who ever holds the login access, can revoke and re-do the cert
73 2017-12-28 19:05:46 0|sipa|one step at a time
74 2017-12-28 19:05:53 0|jonasschnelli|So partially a clown show in terms of user security,.. though we should still do it
75 2017-12-28 19:06:10 0|cfields|jonasschnelli: as far as i can tell, we'll just need to use *procedure* for the setup, grab the pubkey, shove it into the csr, and submit to apple
76 2017-12-28 19:06:51 0|jonasschnelli|cfields: okay. Someone needs to coordinate whos going to create (be a part) a key and who does create the csr
77 2017-12-28 19:07:10 0|jonasschnelli|I can submit the csr and get back with the provisioning file, etc.
78 2017-12-28 19:07:44 0|cfields|jonasschnelli: i'm working on a quick prog to generate the csr from the pubkey, just have to work out exactly which parts get hashed
79 2017-12-28 19:07:56 0|provoostenator|Is this a threshold thing or do you need _all_ particpants for everything you do in the future?
80 2017-12-28 19:08:01 0|cfields|fyi, our cert expires on Jan 11, so the apple key is the priority
81 2017-12-28 19:08:09 0|jonasschnelli|provoostenator: it's a one time thing
82 2017-12-28 19:08:19 0|cfields|provoostenator: threshold
83 2017-12-28 19:08:25 0|jonasschnelli|cfields: oh. Yes. The expiration!
84 2017-12-28 19:08:36 0|jonasschnelli|So thanks then for beeing behind it.
85 2017-12-28 19:08:40 0|provoostenator|Happy to help geneate the key regardless.
86 2017-12-28 19:08:53 0|jonasschnelli|I expect the already signed binaries do still validate after jan 11th?
87 2017-12-28 19:09:03 0|cfields|jonasschnelli: if it's possible to have more than one at a time, it might be wise to go ahead and request one in only your name
88 2017-12-28 19:09:16 0|jonasschnelli|cfields: I can do that...
89 2017-12-28 19:09:17 0|cfields|then we could revoke it assuming we got the other one going
90 2017-12-28 19:09:27 0|meshcollider|Just in case we don't get it done in time?
91 2017-12-28 19:09:35 0|cfields|but that would save us in case we get tripped up and don't have it ready in time
92 2017-12-28 19:09:36 0|cfields|yea
93 2017-12-28 19:09:39 0|jonasschnelli|I think already signed binaries are not affected,... it's just the new 0.16 release that needs the new cert
94 2017-12-28 19:09:50 0|cfields|jonasschnelli: yes, they're timestamped
95 2017-12-28 19:10:18 0|jonasschnelli|So we need a cert for the 0.16 release... making one where I hold the key is a 5min thing... that's always possible
96 2017-12-28 19:10:50 0|cfields|jonasschnelli: great, thanks
97 2017-12-28 19:11:00 0|cfields|ok, that's all from me
98 2017-12-28 19:11:07 0|meshcollider|We could just release 0.16 before the 11th :)
99 2017-12-28 19:11:14 0|jonasschnelli|Other topics?
100 2017-12-28 19:11:28 0|jonasschnelli|meshcollider: heh.. yeah... but I'm happy if "Bitcoin Foundation" is gone in 0.16.
101 2017-12-28 19:11:41 0|jonasschnelli|I mean gone from our OSX/Windows binaries
102 2017-12-28 19:11:47 0|bitcoin-git|[13bitcoin] 15jeromer opened pull request #12042: Add hdenabled flag in getwalletinfo (06master...06getwalletinfo/hdenabledflag) 02 https://github.com/bitcoin/bitcoin/pull/12042
103 2017-12-28 19:12:05 0|meshcollider|jonasschnelli: yep :) no other topics from me
104 2017-12-28 19:12:11 0|jonasschnelli|[09:03:27] <achow101> Merge segwit wallet?
105 2017-12-28 19:12:14 0|cfields|jonasschnelli: oh, remind me and I'll sign some message with the old key containing the new pubkey
106 2017-12-28 19:12:27 0|jonasschnelli|I think that needs to wait until we BlueMatt's points have been worked out?
107 2017-12-28 19:12:41 0|jonasschnelli|cfields: Good point!
108 2017-12-28 19:12:56 0|jonasschnelli|cfields: where would you pubish that?
109 2017-12-28 19:12:56 0|provoostenator|If there's still a lot of outstanding issues, are there parts of that PR than can get merged earlier?
110 2017-12-28 19:13:24 0|cfields|jonasschnelli: we can stick it in git next to the new pubkey
111 2017-12-28 19:13:35 0|meshcollider|provoostenator: I think sipa wanted to leave most of the points raised for a follow-up PR yeah
112 2017-12-28 19:13:40 0|jonasschnelli|provoostenator: I need to catch up there,... I think at some point, a merge can be done even when there are some minor points to fix later
113 2017-12-28 19:14:10 0|jonasschnelli|I guess the main trigger for a merge is when BlueMatt's points are done (maybe they are already) and sipa thinks it's ready
114 2017-12-28 19:14:18 0|jonasschnelli|But that will happen next year
115 2017-12-28 19:14:21 0|jonasschnelli|(IMO)
116 2017-12-28 19:15:20 0|provoostenator|It might be easier to review if all the stuff that BlueMatt is already happy with can get merged earlier?
117 2017-12-28 19:15:22 0|sipa|i'd like an avkby BlueMatt
118 2017-12-28 19:15:26 0|sipa|*ack by
119 2017-12-28 19:15:35 0|jonasschnelli|sipa: yes. Agree
120 2017-12-28 19:15:38 0|provoostenator|But maybe that's impractical to tease apart.
121 2017-12-28 19:16:03 0|sipa|it could be merged commit by commit
122 2017-12-28 19:16:06 0|jonasschnelli|provoostenator: Yes. Involves some risks,.. and may need aditional reviews...
123 2017-12-28 19:16:17 0|sipa|though the biggest part is really just one commit
124 2017-12-28 19:16:21 0|provoostenator|Alright, giant atomic change it is :-)
125 2017-12-28 19:16:33 0|sipa|it's not giant by any metric
126 2017-12-28 19:17:05 0|jonasschnelli|Yes. Let's try to get an ack from BlueMatt, merge it in a whole, and do fixups later...
127 2017-12-28 19:18:18 0|jonasschnelli|Other topics?
128 2017-12-28 19:19:16 0|jonasschnelli|#endmeeting
129 2017-12-28 19:19:16 0|lightningbot|Log: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-12-28-19.03.log.html
130 2017-12-28 19:19:16 0|lightningbot|Meeting ended Thu Dec 28 19:19:15 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
131 2017-12-28 19:19:16 0|lightningbot|Minutes: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-12-28-19.03.html
132 2017-12-28 19:19:16 0|lightningbot|Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-12-28-19.03.txt
133 2017-12-28 19:20:15 0|cfields|thanks for taking the lead, jonasschnelli :)
134 2017-12-28 19:20:27 0|jonasschnelli|np
135 2017-12-28 19:46:53 0|achow101|do we know how/have software that can do more than just 3 of 3?
136 2017-12-28 19:46:53 0|achow101|the think that gmaxwell pointed me to only works for 3 of 3.
137 2017-12-28 19:50:09 0|jo__|hi
138 2017-12-28 19:50:11 0|jo__|anyone here
139 2017-12-28 19:58:23 0|sipa|no
140 2017-12-28 20:00:44 0|Chris_Stewart_5|-brought to you by sipabot(TM)
141 2017-12-28 20:11:21 0|zelest|hehe
142 2017-12-28 20:12:07 0|zelest|might be insulting to ask, but i'll ask anyway.. when is 0.16 scheduled to be released? :)
143 2017-12-28 20:20:41 0|Randolf|zelest: It will be released when it's ready.
144 2017-12-28 20:20:56 0|zelest|ah, the perfect answer. thanks :)
145 2017-12-28 20:32:16 0|bob___|o_O
146 2017-12-28 20:35:36 0|sipa|O_o
147 2017-12-28 23:57:59 0|warren|To whom it may concern, somebody wrote this in a random channel: "ehm, dunno if im right here, i stumbled upon a severe translation error in bitcoincoreWallet..at the transaction window, " abandon transaction" has been translated with " transaktion einstellen" - well this means exactly the opposite in german, something like: enter transaction into database,ledger - the better translation imo would be: " transaktion senden einstellen"...