1 2016-11-26T00:20:53  *** windsok has quit IRC
  2 2016-11-26T00:21:14  *** CubicEarth has quit IRC
  3 2016-11-26T00:32:16  *** CubicEarth has joined #bitcoin-core-dev
  4 2016-11-26T01:04:01  *** windsok has joined #bitcoin-core-dev
  5 2016-11-26T01:15:47  *** fanquake has joined #bitcoin-core-dev
  6 2016-11-26T01:35:54  *** AaronvanW has quit IRC
  7 2016-11-26T01:40:04  *** AaronvanW has joined #bitcoin-core-dev
  8 2016-11-26T01:55:56  *** Madars has quit IRC
  9 2016-11-26T02:23:24  *** Madars has joined #bitcoin-core-dev
 10 2016-11-26T02:42:39  *** Ylbam has quit IRC
 11 2016-11-26T03:27:09  *** kadoban has quit IRC
 12 2016-11-26T03:43:21  *** crudel has joined #bitcoin-core-dev
 13 2016-11-26T03:56:56  *** justanotheruser has quit IRC
 14 2016-11-26T03:57:51  <morcos> sipa: what did you think about my last comment on 8610.  i think that alleviates both issues and doesn't cause the concern suhas was worried about
 15 2016-11-26T03:59:25  *** justanotheruser has joined #bitcoin-core-dev
 16 2016-11-26T04:20:53  *** Chris_Stewart_5 has quit IRC
 17 2016-11-26T04:21:07  *** justanotheruser has quit IRC
 18 2016-11-26T04:21:14  *** justan0theruser has joined #bitcoin-core-dev
 19 2016-11-26T04:58:09  *** chris200_ has quit IRC
 20 2016-11-26T05:09:40  *** BlueMatt has quit IRC
 21 2016-11-26T05:11:26  *** Alopex has quit IRC
 22 2016-11-26T05:11:47  *** BlueMatt has joined #bitcoin-core-dev
 23 2016-11-26T05:12:31  *** Alopex has joined #bitcoin-core-dev
 24 2016-11-26T05:38:33  *** Giszmo has quit IRC
 25 2016-11-26T05:39:38  *** Madars has quit IRC
 26 2016-11-26T05:45:52  *** Madars has joined #bitcoin-core-dev
 27 2016-11-26T06:20:53  *** CubicEarth has joined #bitcoin-core-dev
 28 2016-11-26T06:48:58  *** laurentmt has joined #bitcoin-core-dev
 29 2016-11-26T06:49:35  *** laurentmt has quit IRC
 30 2016-11-26T06:56:41  *** fanquake has quit IRC
 31 2016-11-26T07:05:00  *** CubicEar_ has joined #bitcoin-core-dev
 32 2016-11-26T07:08:37  *** CubicEarth has quit IRC
 33 2016-11-26T07:17:15  *** CubicEarth has joined #bitcoin-core-dev
 34 2016-11-26T07:20:03  *** CubicEar_ has quit IRC
 35 2016-11-26T07:24:09  <gmaxwell> oh god, does zapwallet not backup the wallet before zapping like salvage does?
 36 2016-11-26T07:38:48  *** justan0theruser has quit IRC
 37 2016-11-26T07:54:25  *** justan0theruser has joined #bitcoin-core-dev
 38 2016-11-26T08:16:40  *** Ylbam has joined #bitcoin-core-dev
 39 2016-11-26T08:47:40  *** Taek has quit IRC
 40 2016-11-26T08:48:33  *** JackH has joined #bitcoin-core-dev
 41 2016-11-26T09:13:06  *** Alopex has quit IRC
 42 2016-11-26T09:14:11  *** Alopex has joined #bitcoin-core-dev
 43 2016-11-26T09:19:12  <jonasschnelli> gmaxwell: heh. Yes. It copies all relevant wtxs into a vector vWtx (memory), EraseTx everything, does plenty of stuff (upgrade/rescan) and then try to write those vWtx txes back.
 44 2016-11-26T09:20:00  <jonasschnelli> There is a reasonable high risk that you will end up with a wallet without any wtxs.
 45 2016-11-26T09:20:20  <jonasschnelli> (risk of loosing comments)
 46 2016-11-26T09:34:06  *** Alopex has quit IRC
 47 2016-11-26T09:35:11  *** Alopex has joined #bitcoin-core-dev
 48 2016-11-26T10:18:12  *** Guyver2 has joined #bitcoin-core-dev
 49 2016-11-26T10:24:46  <luke-jr> gmaxwell: 9188: how to get results from testing, before I stop it to test other stuff?
 50 2016-11-26T10:26:11  <luke-jr> something to grep for?
 51 2016-11-26T10:40:19  *** Squidicuz has quit IRC
 52 2016-11-26T10:58:22  *** AaronvanW has quit IRC
 53 2016-11-26T11:00:33  <luke-jr> jonasschnelli: got a patch for you .. :x
 54 2016-11-26T11:37:06  *** Alopex has quit IRC
 55 2016-11-26T11:38:12  *** Alopex has joined #bitcoin-core-dev
 56 2016-11-26T11:47:31  <luke-jr> anyone can flood testnet? :x
 57 2016-11-26T12:16:06  *** Alopex has quit IRC
 58 2016-11-26T12:17:11  *** Alopex has joined #bitcoin-core-dev
 59 2016-11-26T12:18:57  * luke-jr grumbles at whoever found blocks and cleared his flood
 60 2016-11-26T12:22:15  *** BashCo has quit IRC
 61 2016-11-26T12:22:20  *** BashCo_ has joined #bitcoin-core-dev
 62 2016-11-26T12:40:33  *** bitcoinrbb has joined #bitcoin-core-dev
 63 2016-11-26T12:54:42  *** Squidicc has joined #bitcoin-core-dev
 64 2016-11-26T13:06:02  *** Squidicc is now known as squidicuz
 65 2016-11-26T13:34:16  *** bitcoinrbb has quit IRC
 66 2016-11-26T13:42:45  *** Victorsueca has quit IRC
 67 2016-11-26T13:43:11  *** Victorsueca has joined #bitcoin-core-dev
 68 2016-11-26T13:57:42  <bitcoin-git> [bitcoin] s-matthew-english opened pull request #9223: unification of Bloom filter representation (master...patch-10) https://github.com/bitcoin/bitcoin/pull/9223
 69 2016-11-26T14:38:41  <kanzure> https://elliot.land/sql-transaction-isolation-levels-explained
 70 2016-11-26T14:43:41  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 71 2016-11-26T15:52:08  *** tester1 has joined #bitcoin-core-dev
 72 2016-11-26T16:02:37  *** tester1 has quit IRC
 73 2016-11-26T16:32:49  *** abpa has joined #bitcoin-core-dev
 74 2016-11-26T16:53:34  <jonasschnelli> luke-jr: Thanks. Will have a look ai
 75 2016-11-26T16:53:36  <jonasschnelli> at it
 76 2016-11-26T16:53:53  <jonasschnelli> From what I saw when i cross read the code, you moved it to a Layout?
 77 2016-11-26T16:58:51  <bitcoin-git> [bitcoin] ivdsangen opened pull request #9224: Define FD_SETSIZE for all architectures (master...unix-compilation) https://github.com/bitcoin/bitcoin/pull/9224
 78 2016-11-26T17:00:30  *** To7 has joined #bitcoin-core-dev
 79 2016-11-26T17:09:08  *** molz has quit IRC
 80 2016-11-26T18:05:17  *** Guest52676 has joined #bitcoin-core-dev
 81 2016-11-26T18:06:57  *** Guest52676 is now known as roidster
 82 2016-11-26T18:17:03  *** GalvaNation has joined #bitcoin-core-dev
 83 2016-11-26T18:36:54  *** moli has joined #bitcoin-core-dev
 84 2016-11-26T18:45:17  *** abpa has quit IRC
 85 2016-11-26T19:10:53  *** droark has quit IRC
 86 2016-11-26T19:11:30  *** droark has joined #bitcoin-core-dev
 87 2016-11-26T19:16:06  *** droark has quit IRC
 88 2016-11-26T19:19:39  *** moli has quit IRC
 89 2016-11-26T19:21:48  *** moli has joined #bitcoin-core-dev
 90 2016-11-26T19:24:42  *** molz has joined #bitcoin-core-dev
 91 2016-11-26T19:27:57  *** moli has quit IRC
 92 2016-11-26T19:49:11  *** jtimon has joined #bitcoin-core-dev
 93 2016-11-26T19:50:25  *** typedef has joined #bitcoin-core-dev
 94 2016-11-26T19:50:41  * jtimon notes that the supposedly distuptive https://github.com/bitcoin/bitcoin/pull/8493 hasn't needed rebase for a long time...
 95 2016-11-26T20:02:00  *** harrymm has quit IRC
 96 2016-11-26T20:05:19  *** typedef has quit IRC
 97 2016-11-26T20:16:00  <luke-jr> jonasschnelli: yes, I reconstructed the widgets using standard interfaces so it should adapt to any environment reasonably
 98 2016-11-26T20:22:23  *** Guyver2 has quit IRC
 99 2016-11-26T20:24:46  *** harrymm has joined #bitcoin-core-dev
100 2016-11-26T20:29:12  <luke-jr> jonasschnelli: I wonder if the feerate line should figure out its scale independently from the rest
101 2016-11-26T20:29:29  <luke-jr> it doesn't really have a metric to compare with the other two
102 2016-11-26T21:24:04  *** mol has joined #bitcoin-core-dev
103 2016-11-26T21:28:20  *** molz has quit IRC
104 2016-11-26T21:37:18  *** AaronvanW has joined #bitcoin-core-dev
105 2016-11-26T21:37:44  *** AaronvanW has quit IRC
106 2016-11-26T21:37:44  *** AaronvanW has joined #bitcoin-core-dev
107 2016-11-26T21:44:41  *** mrkent has joined #bitcoin-core-dev
108 2016-11-26T21:56:13  *** layman01 has joined #bitcoin-core-dev
109 2016-11-26T21:58:04  <layman01> ok simple question [txid][in][out][sig][locktime] if i put extra data [txid][in][out][sig][locktime][something] does it auto invalidate a tx or just ignores 'something' and pushes it through
110 2016-11-26T21:59:43  <layman01> what i mean is. older clients that never understood nlocktime. do they store nlocktime as arbitrary data even though they dont know what the extra bytes after the tx actually do
111 2016-11-26T22:01:28  <sipa> every client understands nlocktime
112 2016-11-26T22:01:39  <sipa> and no, you can't just append more data to transactions
113 2016-11-26T22:01:50  <sipa> that would be a dos attack if that data is unverifiable
114 2016-11-26T22:02:02  <sipa> segwit adds extra data to transactions
115 2016-11-26T22:02:25  <sipa> but it uses a new format with optional fields, and it gets stripped out when relaying to old clients
116 2016-11-26T22:05:09  <layman01> "that would be a dos attack if that data is unverifiable" - so no possible way to just add random data. or just morally avoided but possible
117 2016-11-26T22:07:36  <luke-jr> wouldn't current nodes just ignore it (and relay the tx without it)?
118 2016-11-26T22:08:49  <layman01> EG [txid][in][out][sig][locktime][receipt number:123]&[thank you for shopping at walmart]
119 2016-11-26T22:09:19  <layman01> not physically possible in any way to have it locked in the blockchain
120 2016-11-26T22:10:02  <layman01> WITHOUT using the "output as message" trick (within the tx)
121 2016-11-26T22:11:26  <gmaxwell> layman01: the blockchain is NOT free file storage, it's carefully designed to avoid allowing people to dump their porn collections in it, if it were possible to do what you describe (it isn't as far as we know)-- we'd consider it a serious bug and would work diligently to fix it.
122 2016-11-26T22:12:36  <layman01> gmaxwell, so where will you store your confidential payment commitments
123 2016-11-26T22:15:47  <layman01> where is the bip/document information that stops extra data after signatures/locktime. eg what mechanism prevents extra data being added
124 2016-11-26T22:16:22  <gmaxwell> the structure of the protocol. There is just no 'extra' place to put it.
125 2016-11-26T22:17:10  <gmaxwell> layman01: if something is _confidential_ it should not be in the public blockchain.  If something is a commitment it can be commited to using the existing signatures or existing outputs without adding any data at all to the blockchain.
126 2016-11-26T22:19:32  <layman01> gmaxwell sound familiar: "CT is possible due to the cryptographic technique of additively homomorphic commitments. As a side-effect of its design, CT also enables the additional exchange of private "memo" data""
127 2016-11-26T22:20:05  <BlueMatt> layman01: do note that CT only exists in implemented form in non-public blockchains
128 2016-11-26T22:20:42  <gmaxwell> layman01: the private memo data is maigical and takes no size at all.
129 2016-11-26T22:20:57  <BlueMatt> also, that ^
130 2016-11-26T22:21:01  <layman01> but im asking how can extra data be added. how can gmaxwell also make output values private onchain.. if data cant be added..
131 2016-11-26T22:21:13  <gmaxwell> Otherwise it wouldn't have been interesting.
132 2016-11-26T22:21:56  <gmaxwell> layman01: CT's memo data doesn't add any other data at all. (also, even if it did: CT isn't part of Bitcoin-- though the memo data wouldn't have made sense if it added data, so I wouldn't have done it if it did)
133 2016-11-26T22:22:01  <BlueMatt> layman01: think of it kinda like pay-to-contract-hash: there is data there, but it takes no extra room compared to not having it (well, pay-to-contract-hash is just a commitment, whereas CT is more, but whatever)
134 2016-11-26T22:22:45  * luke-jr wonders if sipa is still working on sign-to-contract :x
135 2016-11-26T22:23:14  *** gribble has quit IRC
136 2016-11-26T22:23:23  <luke-jr> layman01: the payment protocol has an out-of-band mechanism for memos btw
137 2016-11-26T22:23:54  <layman01> out-of-band.. i need to research that :D
138 2016-11-26T22:24:27  <BlueMatt> * gribble :No such server
139 2016-11-26T22:24:30  <BlueMatt> nanotube: :'(
140 2016-11-26T22:25:29  *** gribble has joined #bitcoin-core-dev
141 2016-11-26T22:25:52  <BlueMatt> lol, helgrind is so slow that it makes my node think its nTimeOffset needs to be adjusted by 3 minutes
142 2016-11-26T22:26:21  <layman01> any link to 'out-of-band' documentation, instead of asking google and spending ages trying to find info
143 2016-11-26T22:26:25  <gmaxwell> I think some of the recent changes to smartptr may have slowed down valgrind.
144 2016-11-26T22:26:41  <luke-jr> layman01: BIP 70
145 2016-11-26T22:33:10  <layman01> ok so bip70 is still using the [output] part of a tx as the messaging tool (from my quick brief read of it) not adding data after [sig][nlocktime]
146 2016-11-26T22:35:26  <layman01> anyone with a current testnet open and about to do a tx, able to just add some random bytes after the raw tx to see what happens?
147 2016-11-26T22:36:33  <gmaxwell> layman01: you've misunderstood BIP70.
148 2016-11-26T22:36:46  <gmaxwell> It doesn't put message data in the transaction at all.
149 2016-11-26T22:37:15  *** mrkent has quit IRC
150 2016-11-26T22:37:27  *** mrkent has joined #bitcoin-core-dev
151 2016-11-26T22:38:18  *** mrkent has joined #bitcoin-core-dev
152 2016-11-26T22:38:49  *** mrkent has quit IRC
153 2016-11-26T22:39:09  *** mrkent has joined #bitcoin-core-dev
154 2016-11-26T22:39:37  <layman01> well my question is about putting messages into a transaction. that gets locked into a block. that gets distributed over a network. so i dont know why anyone is guiding me to stuff thats not about messages added to a transaction
155 2016-11-26T22:39:37  *** mrkent has quit IRC
156 2016-11-26T22:39:51  *** mrkent has joined #bitcoin-core-dev
157 2016-11-26T22:40:25  *** mrkent has quit IRC
158 2016-11-26T22:40:40  <layman01> plus i only took a few seconds to see the word output mentioned a few times. i know that outputs can be used to write messages but again my question was about messages not using the output area
159 2016-11-26T22:40:45  *** mrkent has joined #bitcoin-core-dev
160 2016-11-26T22:40:53  <gmaxwell> 14:11 < gmaxwell> layman01: the blockchain is NOT free file storage, it's carefully designed to avoid allowing people to dump their porn  collections in it, if it were possible to do what you describe (it isn't as far as we know)-- we'd consider it a serious  bug and would work diligently to fix it.
161 2016-11-26T22:41:14  *** mrkent has quit IRC
162 2016-11-26T22:41:57  <layman01> i know the morals. i know bitcoins ethos i know what its meant for. im asking about the possibility of adding data.
163 2016-11-26T22:43:04  <gmaxwell> As far as we know it's not possible to do what you're asking. If, due to some phenominial bug, it were possible it would be a _serious_ bug and patches to block it would be issued as fast as possible.
164 2016-11-26T22:44:09  <BlueMatt> layman01: have you seen pay-to-contract-hash?
165 2016-11-26T22:44:40  <layman01> so is the only way to use another unused opcode (like segwit did).. but safeguarded against happening due to mining pools not having consensus to allow funky tx's into block
166 2016-11-26T22:45:50  <layman01> bluematt, im looking while on here. but got interupted due to bip70 that didnt answer my question
167 2016-11-26T22:48:05  <BlueMatt> layman01: there are lots of answers depending on what your actual use-case is....problem is youre asking for a solution to a specific question to which there is no answer.....maybe go to #bitcoin and try again except start by stating waht, exactly youre trying to do
168 2016-11-26T22:48:37  *** moli has joined #bitcoin-core-dev
169 2016-11-26T22:50:22  <layman01> trying to see if there a way someone can fill the 'weight' area with bloat but not using 'outputs' to do it. theres a debate elsewhere, some say it can be done some say it cant. im just trying to figure who is right
170 2016-11-26T22:50:56  *** mol has quit IRC
171 2016-11-26T22:51:10  <gmaxwell> You seem to be unable to take no for an answer, so I'm going to bet that you're going to remain unenlightened.
172 2016-11-26T22:52:05  <layman01> its not a 'accept' no... its a why 'no' i need answering
173 2016-11-26T22:52:45  <sipa> transactions consist of inputs and outputs. if you want to increase their size, you'd need to put it in either of those
174 2016-11-26T22:52:53  <layman01> 'because bitcoin not designed that way' is an empty answer too
175 2016-11-26T22:52:57  <gmaxwell> Because extra data just isn't permitted, it's ignored. Nodes understand the data that they're parsing and they'll ignore any extra data that isn't actually part of the transaction, stripping it out.
176 2016-11-26T22:53:30  <gmaxwell> (or treating the whole transaction as corrupted, depending on what you did.)
177 2016-11-26T22:54:28  <BlueMatt> layman01: ahh! see now, thats a question: the answer is "no, treating the witness space as 'free' isnt true - witnesses are counted just like the rest of the transaction and, really, should be seen as a part of the inputs, not extra data"
178 2016-11-26T22:56:01  <gmaxwell> ^ by segwit nodes, by non-segwit nodes, segwit transactions aren't handled at all unless stripped of witness data-- they would be seen as corrupted if not witness stripped.
179 2016-11-26T22:56:11  <luke-jr> if it's part of a block, it's actually impossible to add the extra data at all because after the locktime, it will begin parsing the subsequent transaction implicitly
180 2016-11-26T22:56:12  <BlueMatt> that, too
181 2016-11-26T22:56:27  <layman01> so the mechanism that prevents it is the parsing data into classes with known lengths of bytes for each element/namespace/variable and then ignoring/dropping the remainder it does not recognise
182 2016-11-26T22:57:20  <sipa> right, nodes decode all messages they receive, and send them on in a form that the receiver understands
183 2016-11-26T22:57:28  <gmaxwell> Yes, or, in some contexts treating it as corrupted and dropping the whole thing.  Segwit blocks are handed to non-segwit nodes by first stripping out the witness data so they'll accept it.
184 2016-11-26T22:57:33  <sipa> they're not just relaying the transactions or blocks as just bytes
185 2016-11-26T22:57:40  <luke-jr> layman01: you can put anything inside the scripts within the transaction, but that doesn't change with segwit
186 2016-11-26T22:57:46  <luke-jr> or rather, miners can*
187 2016-11-26T22:58:53  <gmaxwell> The whole idea of a transaction as "bytes" is a too limited mental model. It would be like understanding numbers as a series of strokes on paper. :)   Bytes are one way of representing a transaction, but when a transaction comes in the bytes are decoded and turned into a different in memory form.  Then when they go out again they're converted back into bytes in a form sutiable for the reciever.
188 2016-11-26T23:02:22  <nanotube> BlueMatt: ? >_>
189 2016-11-26T23:02:39  <BlueMatt> nanotube: better now :)
190 2016-11-26T23:03:26  <layman01> so baseblock/base class (not using official terms) only has [txid][incount][in][val][outcount][out][value]   and witness class has [wtxid][witcount][witness][nlocktime] and nothing can appear after nlocktime on the blockchain because of it.. right?
191 2016-11-26T23:03:33  <layman01> just double checking
192 2016-11-26T23:03:42  <sipa> layman01: transactions don't contain a txid
193 2016-11-26T23:03:55  <sipa> the txid is just the hash of the (non-witness) serialization of the transaction
194 2016-11-26T23:03:59  <BlueMatt> also witnesses dont have witcount
195 2016-11-26T23:04:01  <BlueMatt> its implicit
196 2016-11-26T23:04:14  <BlueMatt> or wtxid...
197 2016-11-26T23:06:18  <layman01> ok i know in the [output] different op codes can be set at different lengths. is there any opcode or any other class variable that has adjustable/non restricted lengths
198 2016-11-26T23:06:41  <sipa> layman01: you should just study the documentation on this
199 2016-11-26T23:06:41  <nanotube> BlueMatt: ah ok :)
200 2016-11-26T23:07:02  <BlueMatt> nanotube: literally 2 seconds after that gribble re-connected
201 2016-11-26T23:07:09  <sipa> layman01: https://bitcoin.org/en/developer-guide
202 2016-11-26T23:07:18  <nanotube> heh good timing :)
203 2016-11-26T23:07:22  <layman01> sipa i would but the documentation is very loose and all over the place,
204 2016-11-26T23:08:36  <sipa> layman01: you're free to help improve things, but this is not the place to ask for a basic explanation
205 2016-11-26T23:08:45  <sipa> this channel is for discussing development
206 2016-11-26T23:09:19  <luke-jr> layman01: there aren't different classes
207 2016-11-26T23:11:26  <layman01> i heard it wasnt. i was told this place is where the close minded devs live who only think about themselves, just like the mailing list. just like every other place that the devs hang out in. like its a cabin fever experience where devs only want to speak to other devs and only agree with other devs and never talk to the community...
208 2016-11-26T23:11:44  <sipa> layman01: please
209 2016-11-26T23:11:47  <layman01> but goodnight anyway
210 2016-11-26T23:11:52  <sipa> layman01: http://bitcoin.stackexchange.com/
211 2016-11-26T23:11:53  <luke-jr> layman01: many of us are also in #bitcoin
212 2016-11-26T23:11:59  <sipa> i answer questions there on a daily basis
213 2016-11-26T23:12:07  *** layman01 has quit IRC
214 2016-11-26T23:37:47  *** dervisher has joined #bitcoin-core-dev
215 2016-11-26T23:45:16  <bitcoin-git> [bitcoin] TheBlueMatt opened pull request #9225: Fix some benign races (master...2016-11-lockfixes) https://github.com/bitcoin/bitcoin/pull/9225
216 2016-11-26T23:58:26  *** parsimony_ has joined #bitcoin-core-dev