1 2017-02-05T00:20:43  *** bsm117532 has quit IRC
  2 2017-02-05T00:20:44  *** morcos has quit IRC
  3 2017-02-05T00:30:29  *** iv3c has quit IRC
  4 2017-02-05T00:31:01  *** iv3c has joined #bitcoin-dev
  5 2017-02-05T00:33:54  *** blueness has quit IRC
  6 2017-02-05T00:37:07  *** blueness has joined #bitcoin-dev
  7 2017-02-05T00:39:58  *** Guyver2 has quit IRC
  8 2017-02-05T00:49:16  *** mrkent has joined #bitcoin-dev
  9 2017-02-05T00:50:26  *** cyphase_eviltwin has joined #bitcoin-dev
 10 2017-02-05T01:00:53  *** echonaut4 has quit IRC
 11 2017-02-05T01:01:10  *** echonaut has joined #bitcoin-dev
 12 2017-02-05T01:04:05  *** janko33 has quit IRC
 13 2017-02-05T01:20:00  *** copumpkin has quit IRC
 14 2017-02-05T01:32:17  *** GNULinuxGuy has joined #bitcoin-dev
 15 2017-02-05T01:40:03  *** blueness has quit IRC
 16 2017-02-05T01:40:31  *** cyphase_eviltwin is now known as cyphase
 17 2017-02-05T01:40:40  *** blueness has joined #bitcoin-dev
 18 2017-02-05T01:55:38  *** luke-jr has quit IRC
 19 2017-02-05T01:57:56  *** luke-jr has joined #bitcoin-dev
 20 2017-02-05T02:01:50  *** OMDPrebel has joined #bitcoin-dev
 21 2017-02-05T02:02:08  *** HostFat_ has joined #bitcoin-dev
 22 2017-02-05T02:05:15  *** blueness has quit IRC
 23 2017-02-05T02:05:37  *** HostFat__ has quit IRC
 24 2017-02-05T02:07:12  *** blueness has joined #bitcoin-dev
 25 2017-02-05T02:11:43  *** Burrito has quit IRC
 26 2017-02-05T02:22:13  *** mnk has quit IRC
 27 2017-02-05T02:23:46  *** blueness has quit IRC
 28 2017-02-05T02:27:23  *** blueness has joined #bitcoin-dev
 29 2017-02-05T02:32:29  *** Soligor has quit IRC
 30 2017-02-05T02:41:11  *** blueness has quit IRC
 31 2017-02-05T02:42:08  *** mrkent has quit IRC
 32 2017-02-05T02:42:27  *** mrkent has joined #bitcoin-dev
 33 2017-02-05T02:42:47  *** mrkent has quit IRC
 34 2017-02-05T02:59:10  *** HostFat__ has joined #bitcoin-dev
 35 2017-02-05T03:02:02  *** harai_ has quit IRC
 36 2017-02-05T03:02:48  *** HostFat_ has quit IRC
 37 2017-02-05T03:18:40  *** airbreather has quit IRC
 38 2017-02-05T03:21:24  *** Delta_ has joined #bitcoin-dev
 39 2017-02-05T03:24:13  *** airbreather has joined #bitcoin-dev
 40 2017-02-05T03:25:06  *** Subo1977 has quit IRC
 41 2017-02-05T03:36:40  *** Jay- has joined #bitcoin-dev
 42 2017-02-05T04:00:21  *** harai_ has joined #bitcoin-dev
 43 2017-02-05T04:06:24  *** harai_ has quit IRC
 44 2017-02-05T04:09:16  *** harai_ has joined #bitcoin-dev
 45 2017-02-05T04:13:05  *** CheckDavid has quit IRC
 46 2017-02-05T04:13:57  *** dgenr8 has quit IRC
 47 2017-02-05T04:16:16  *** Giszmo has quit IRC
 48 2017-02-05T04:20:52  *** dgenr8 has joined #bitcoin-dev
 49 2017-02-05T04:23:10  *** harai_ has quit IRC
 50 2017-02-05T04:25:06  *** janko33 has joined #bitcoin-dev
 51 2017-02-05T04:30:27  *** iv3c has quit IRC
 52 2017-02-05T04:53:19  *** harai_ has joined #bitcoin-dev
 53 2017-02-05T05:00:15  *** dermoth has quit IRC
 54 2017-02-05T05:01:08  *** dermoth has joined #bitcoin-dev
 55 2017-02-05T05:08:16  *** TheSeven has quit IRC
 56 2017-02-05T05:08:31  *** [7] has joined #bitcoin-dev
 57 2017-02-05T05:11:08  *** Cory has quit IRC
 58 2017-02-05T05:11:59  *** Cory has joined #bitcoin-dev
 59 2017-02-05T05:34:36  *** ThomasV has joined #bitcoin-dev
 60 2017-02-05T05:44:32  *** harai_ has quit IRC
 61 2017-02-05T05:46:48  *** OMDPrebel has quit IRC
 62 2017-02-05T06:25:50  *** harai_ has joined #bitcoin-dev
 63 2017-02-05T06:38:22  *** harai_ has joined #bitcoin-dev
 64 2017-02-05T06:56:13  *** paveljanik has quit IRC
 65 2017-02-05T06:57:19  *** paveljanik has joined #bitcoin-dev
 66 2017-02-05T07:06:20  *** cannon-c has joined #bitcoin-dev
 67 2017-02-05T07:11:42  *** cannon-c has left #bitcoin-dev
 68 2017-02-05T07:13:21  *** reBrain has joined #bitcoin-dev
 69 2017-02-05T07:15:05  *** chjj has quit IRC
 70 2017-02-05T07:17:23  *** harai_ has quit IRC
 71 2017-02-05T07:32:25  *** Sosumi has quit IRC
 72 2017-02-05T07:45:44  *** btiefert has quit IRC
 73 2017-02-05T08:00:41  *** harai_ has joined #bitcoin-dev
 74 2017-02-05T08:03:13  *** ThomasV has quit IRC
 75 2017-02-05T08:05:04  *** justanotheruser has quit IRC
 76 2017-02-05T08:08:36  *** chjj has joined #bitcoin-dev
 77 2017-02-05T08:09:52  *** justanotheruser has joined #bitcoin-dev
 78 2017-02-05T08:16:29  *** blueness has joined #bitcoin-dev
 79 2017-02-05T08:22:38  *** harai_ has quit IRC
 80 2017-02-05T08:51:34  *** Soligor has joined #bitcoin-dev
 81 2017-02-05T08:54:07  *** |Clown| is now known as Guest70121
 82 2017-02-05T08:54:10  *** |Clown| has joined #bitcoin-dev
 83 2017-02-05T08:57:46  *** reBrain has quit IRC
 84 2017-02-05T09:04:49  *** ThomasV has joined #bitcoin-dev
 85 2017-02-05T09:07:23  *** mnk has joined #bitcoin-dev
 86 2017-02-05T09:13:42  *** petrkr has joined #bitcoin-dev
 87 2017-02-05T09:25:04  *** harai_ has joined #bitcoin-dev
 88 2017-02-05T10:09:31  *** wasi has quit IRC
 89 2017-02-05T10:41:55  *** McLovinMcLovin has joined #bitcoin-dev
 90 2017-02-05T10:44:58  <McLovinMcLovin> fork question: i have bought bitcoin some days ago, sent them through just a few wallets with bitWallet for ios. this goes from block 449795 (first tx) to block 451138 (last tx). all in all there are just 1-2 blocks in between i used for sending. are my coins already not existing in the BU/SW forks?
 91 2017-02-05T10:45:31  <McLovinMcLovin> bought them from kraken if that helps
 92 2017-02-05T10:46:05  <McLovinMcLovin> and the ios app bitwallet is some old schooler kind of thing wallet.
 93 2017-02-05T10:47:28  <McLovinMcLovin> here are list of all used blocks: 449795, 450739, 450259, 450243, 451138. hope this helps
 94 2017-02-05T10:57:24  *** reBrain has joined #bitcoin-dev
 95 2017-02-05T10:58:19  *** joeykrim has quit IRC
 96 2017-02-05T10:58:37  *** joeykrim has joined #bitcoin-dev
 97 2017-02-05T11:01:56  *** McLovinMcLovin has quit IRC
 98 2017-02-05T11:04:43  *** twistedline has quit IRC
 99 2017-02-05T11:20:11  *** blueness has quit IRC
100 2017-02-05T11:24:42  *** McLovinMcLovin has joined #bitcoin-dev
101 2017-02-05T11:28:23  *** harai_ has quit IRC
102 2017-02-05T11:29:26  *** Guyver2 has joined #bitcoin-dev
103 2017-02-05T11:38:41  *** twistedline has joined #bitcoin-dev
104 2017-02-05T11:46:19  *** JackH has quit IRC
105 2017-02-05T11:47:55  *** blueness has joined #bitcoin-dev
106 2017-02-05T11:54:53  *** ThomasV has quit IRC
107 2017-02-05T12:12:16  *** Belkaar has joined #bitcoin-dev
108 2017-02-05T12:12:42  *** Belkaar has quit IRC
109 2017-02-05T12:15:56  *** Belkaar has joined #bitcoin-dev
110 2017-02-05T12:16:37  *** Belkaar has joined #bitcoin-dev
111 2017-02-05T12:18:13  *** jtimon has quit IRC
112 2017-02-05T12:20:21  *** ThomasV has joined #bitcoin-dev
113 2017-02-05T12:33:38  *** CheckDavid has joined #bitcoin-dev
114 2017-02-05T12:43:19  *** O01eg has joined #bitcoin-dev
115 2017-02-05T13:09:14  *** reBrain has quit IRC
116 2017-02-05T13:58:20  *** Giszmo has joined #bitcoin-dev
117 2017-02-05T14:22:12  *** reBrain has joined #bitcoin-dev
118 2017-02-05T14:24:49  *** ThomasV has quit IRC
119 2017-02-05T14:30:16  *** iv3c has joined #bitcoin-dev
120 2017-02-05T15:11:54  *** agricocb has joined #bitcoin-dev
121 2017-02-05T15:12:33  *** ThomasV has joined #bitcoin-dev
122 2017-02-05T15:25:38  *** cyphase has quit IRC
123 2017-02-05T15:30:40  *** cyphase has joined #bitcoin-dev
124 2017-02-05T15:37:34  *** Giszmo has quit IRC
125 2017-02-05T15:38:36  *** Belkaar has quit IRC
126 2017-02-05T15:39:48  *** Belkaar has joined #bitcoin-dev
127 2017-02-05T16:11:07  *** blueness has quit IRC
128 2017-02-05T16:21:20  *** clopez has quit IRC
129 2017-02-05T16:23:49  *** clopez has joined #bitcoin-dev
130 2017-02-05T16:25:18  *** blueness has joined #bitcoin-dev
131 2017-02-05T16:30:28  *** iv3c has quit IRC
132 2017-02-05T16:31:13  *** iv3c has joined #bitcoin-dev
133 2017-02-05T16:31:44  *** Burrito has joined #bitcoin-dev
134 2017-02-05T16:57:24  *** frank1e has joined #bitcoin-dev
135 2017-02-05T17:09:08  *** ThomasV has quit IRC
136 2017-02-05T17:10:51  *** ThomasV has joined #bitcoin-dev
137 2017-02-05T17:12:33  *** btiefert has joined #bitcoin-dev
138 2017-02-05T17:19:13  *** Guyver2 has quit IRC
139 2017-02-05T17:19:50  *** Belkaar has quit IRC
140 2017-02-05T17:20:57  *** Belkaar has joined #bitcoin-dev
141 2017-02-05T17:21:25  *** aschildbach has joined #bitcoin-dev
142 2017-02-05T17:21:51  <aschildbach> Hi there, I've got a question:
143 2017-02-05T17:22:02  <Wayward> good luck with that
144 2017-02-05T17:23:05  <aschildbach> What is the expected behaviour for wallets if they receive a version-2 transaction that otherwise looks like a standard pay-to-address tx? Assuming it pays to the wallet, shall be displayed, the value be added to the balance and be spendable?
145 2017-02-05T17:23:46  <aschildbach> Clarification: Received in a block.
146 2017-02-05T17:24:19  <Wayward> That's a #bitcoin question.
147 2017-02-05T17:24:26  *** harai_ has joined #bitcoin-dev
148 2017-02-05T17:24:59  <aschildbach> Hu? I'm asking as a developer and it is a very technical question. Definately not for users.
149 2017-02-05T17:25:25  <Wayward> This channel has been inactive for years.  I just grepped, and the last 40 people who asked a question received no response.
150 2017-02-05T17:25:52  <aschildbach> ok good to know
151 2017-02-05T17:28:54  <achow101> aschildbach: IIRC the only difference between v2 and v1 txs is that v2 allows relative time locks
152 2017-02-05T17:30:33  <aschildbach> BIP68 I assume?
153 2017-02-05T17:30:38  <achow101> yes
154 2017-02-05T17:32:42  <aschildbach> Ok thanks that's a great hint
155 2017-02-05T17:33:04  <arubi> version 2 is for csv, bip 112
156 2017-02-05T17:33:28  <aschildbach> Having read the BIP68 spec, after being mined such a tx is not different to v1 tx.
157 2017-02-05T17:33:54  <arubi> op csv rules are only taken into account when the tx is v2, but currently core creates all tx's as version 2, at lease afaict
158 2017-02-05T17:34:00  *** ThomasV has quit IRC
159 2017-02-05T17:35:00  *** frank1e has quit IRC
160 2017-02-05T17:53:38  <TZander> if it does, thats a bug.
161 2017-02-05T17:55:43  <arubi> why is that a bug?  again, I'm usually using a very customized setup.  what I see might not be what's actually the standard
162 2017-02-05T17:57:49  <arubi> currently on (lightly) modified master and transactions created by -cli and -tx are version 2.  just normal pay to pubkey hash
163 2017-02-05T17:57:50  <aschildbach> Hmmm currently at least tx version 2 seems to be very rare. Otherwise I'd have more users complaining about their txns not appearing immediately.
164 2017-02-05T17:58:19  <aschildbach> What's the behaviour on the latest release?
165 2017-02-05T17:58:36  <arubi> aschildbach, I'm on testnet\regtest (and master), maybe things are a bit different.  I do remember it being a policy not to relay weird version tx's, but not sure what's the state now
166 2017-02-05T17:58:48  <arubi> what do you mean testnet release?
167 2017-02-05T17:59:29  <aschildbach> I meant release of Bitcoin Core.
168 2017-02-05T17:59:41  <aschildbach> You said master, but I'm interested what is being used by users.
169 2017-02-05T17:59:57  <arubi> eyeballing some testnet block explorer, only seeing v1's for now
170 2017-02-05T18:00:14  <TZander> check CURRENT_VERSION in transaction.h
171 2017-02-05T18:00:15  <arubi> aschildbach, weird version transactions are valid in a block
172 2017-02-05T18:00:38  <TZander> its set to 1
173 2017-02-05T18:00:53  <aschildbach> Well there is at least one mined v2 transaction on mainnet: 0321b1413ed9048199815bd6bc2650cab1a9e8d543f109a42c769b1f18df4174
174 2017-02-05T18:00:58  <aschildbach> But I guess there are many more
175 2017-02-05T18:03:11  <TZander> there is unfortunately no consensus rule that forbids version numbers for transactions not defined.  Its a policy rule.
176 2017-02-05T18:03:13  <arubi> hm.  I wonder if it's setting version 2 due to use of locktime (current block)
177 2017-02-05T18:03:37  <TZander> on testnet you'll find loads of interesting version numbers
178 2017-02-05T18:03:42  <arubi> current_version says 1, right
179 2017-02-05T18:04:13  <TZander> arubi: and thats used in cmutable_transaction
180 2017-02-05T18:04:28  <TZander> and as such the wallet
181 2017-02-05T18:04:52  <arubi> well I'm reporting what I see.  I don't see how my current setup can interfere
182 2017-02-05T18:05:41  <arubi> sorry, have to go back to crunching other numbers :)
183 2017-02-05T18:07:15  <aschildbach> Ok, my investigation yields: v0.13.2 uses 1, master uses 2. Is v0.14 already branched?
184 2017-02-05T18:07:26  <achow101> branching will probably happen tomorrow
185 2017-02-05T18:07:32  <achow101> or in a few days
186 2017-02-05T18:11:48  <TZander> aschildbach: my suggestion is to have a two layer approach.  If a tx.nversion == 2, check the sequence mask to see if anything is set. If that is the case, you either want to check the logic itself, or just make funds unspendable until they are known to be in a block.
187 2017-02-05T18:12:55  <arubi> no.  read bip112.  if you encounter op_csv in a redeeming script, do check for all the things mentioned (version == 2 being one of them) and validate or not according to the rules
188 2017-02-05T18:13:19  <TZander> thats what my "check the logic itself" means.
189 2017-02-05T18:13:46  <arubi> should happen first.  you shouldn't care at all about what version a tx is if it's in a block.  go ahead and don't relay whatever you don't want to though
190 2017-02-05T18:14:38  <arubi> also, csv rules only make sense when an input is redeemed, so of course it's already in a block
191 2017-02-05T18:16:25  <arubi> well I take that back
192 2017-02-05T18:16:32  <TZander> that makes no sense...   A wallet can recieve a transaction that redeems a transaction that has op-csv.
193 2017-02-05T18:17:04  <arubi> yea, and that tx paying to op_csv can even be version 1.  the redeeming one is version 2.  pebkac
194 2017-02-05T18:17:21  <TZander> I understand, it took me a bit to get my head around this too ;)
195 2017-02-05T18:19:03  <arubi> yep, I love when I suddenly realize some confusion I'm having about these things, and it's not like I never did csv\cltv transactions before, just gets a bit confusing for humans :)
196 2017-02-05T18:19:49  <achow101> ok, so as I understand this, v2 txs are considered standard because the csv softfork activated. this means that v2 txs are being mined and relayed
197 2017-02-05T18:20:18  <arubi> nice, good to know.
198 2017-02-05T18:20:39  <achow101> bitcoin core will default to making v2 txs in 0.14+. se https://github.com/bitcoin/bitcoin/pull/7562
199 2017-02-05T18:20:46  <achow101> *see
200 2017-02-05T18:20:52  <arubi> yay
201 2017-02-05T18:36:19  *** jtimon has joined #bitcoin-dev
202 2017-02-05T19:01:57  *** fatalhalt has joined #bitcoin-dev
203 2017-02-05T19:11:15  *** Burrito has quit IRC
204 2017-02-05T19:16:26  <aschildbach> arubi: For now, I will probably only check the "disabled" bit. However, I'm currently puzzled by how/if BIP68 interacts with opt-in RBF. Both use the sequence field if I'm not mistaken.
205 2017-02-05T19:17:02  *** d9b4bef9 has quit IRC
206 2017-02-05T19:18:08  *** d9b4bef9 has joined #bitcoin-dev
207 2017-02-05T19:20:04  <arubi> aschildbach, so consider the conditions for redeeming anything csv or cltv
208 2017-02-05T19:20:38  <arubi> if such an opcode exists in the script, you should check the tx as bip68 rules
209 2017-02-05T19:21:09  <arubi> if not, then you haven't even tried to check it and just raised the rbf flag way before that
210 2017-02-05T19:22:11  <arubi> as the signer of a tx, you're pretty much always free to change the sequence and send again.  it's an awesome feature, and combined with cltv, csv or rbf, it has different meanings
211 2017-02-05T19:22:57  *** reBrain has quit IRC
212 2017-02-05T19:23:19  <arubi> so really you shouldn't be considering any rule until you come to parse it.  of course a csv\cltv transaction is replaceable.  another sequence exists that satisfies the cltv\csv opcodes which might appear in the script
213 2017-02-05T19:23:44  <arubi> you just raise the rbf flag, and consider everything replaceable anyway
214 2017-02-05T19:24:10  <aschildbach> Somehow this is over my horizon... )-:  For now at least.
215 2017-02-05T19:24:25  <aschildbach> I'm currently only looking at transaction, not creating them.
216 2017-02-05T19:25:20  <arubi> right, but unless you're always expecting to parse transactions to addresses that you know how to parse, you'll have to actually implement every bip that exists
217 2017-02-05T19:25:21  <aschildbach> So if the RBF spec is valid for version 2 transactions too that means you can use BIP68 only if a tx is RBF at the same time.
218 2017-02-05T19:25:27  <aschildbach> Right?
219 2017-02-05T19:26:05  <arubi> a tx is marked rbf if the sequence is less than so and so.  a tx is marked non csv or clrv if the sequence is max_sequence
220 2017-02-05T19:26:12  <arubi> so you see, there's no overlap :)
221 2017-02-05T19:26:48  <arubi> s/clrv/cltv
222 2017-02-05T19:27:36  <aschildbach> Hu, BIP68 talks about a disable bit. It's not a sequence == MAX_SEQUENCE rule.
223 2017-02-05T19:27:59  <aschildbach> And besides, MAX_SEQUENCE = 0xffffffff?
224 2017-02-05T19:28:02  <arubi> you're right, it's a bunch of sequences.  even better
225 2017-02-05T19:28:42  <arubi> aschildbach, you may encounter op_csv or op_cltv where the sequence says that it's disabled
226 2017-02-05T19:29:18  <arubi> you have to treat these opcodes as op_nops.  you look for the sequence (and other rules) to validate
227 2017-02-05T19:29:49  <aschildbach> All I need to know is if the features are enabled.
228 2017-02-05T19:29:55  <arubi> well, specifically op_csv, maybe not cltv ?
229 2017-02-05T19:30:02  <aschildbach> I'm not doing any script evaluation.
230 2017-02-05T19:30:11  <aschildbach> (I == bitcoinj)
231 2017-02-05T19:30:31  <arubi> hm.  so just wait until they're in a block
232 2017-02-05T19:30:56  <arubi> act like a pre-softfork node.  just assume non-relay and ignored until it's mined
233 2017-02-05T19:31:03  <aschildbach> Yes if the tx in a block it's decided anyhow.
234 2017-02-05T19:31:17  <aschildbach> But I want to know beforehand.
235 2017-02-05T19:31:25  <arubi> that's the best you can do.  don't try to act on non confirmed
236 2017-02-05T19:32:01  <arubi> aschildbach, bitcoinj is used by wallets right?  don't assume anything until it's mined if you're not going to validate it
237 2017-02-05T19:32:36  <aschildbach> Well, unconfirmed txns are shown to the user (if low risk), so some acting is needed
238 2017-02-05T19:33:01  <aschildbach> Yes bitcoinj is mostly aimed at wallets, but some devs use it for different things too
239 2017-02-05T19:33:27  <arubi> but you do currently check for some things right?  if you can't check for soft forked rules, just ignore transactions that use them
240 2017-02-05T19:34:01  <arubi> you don't need to parse or validate anything, just implement the "how to check if this is enabled" part of the bips I guess
241 2017-02-05T19:34:34  <aschildbach> Yes, exactly that is my point.
242 2017-02-05T19:34:42  <aschildbach> I currently do check for RBF.
243 2017-02-05T19:35:11  <aschildbach> Now for version 2 txns I need to check for RBF AND BIP68 enable bit I guess
244 2017-02-05T19:35:25  <aschildbach> So I'm trying to understand how these two interacgt.
245 2017-02-05T19:35:37  <arubi> any tx with a sequence set that activates rbf is rbf.
246 2017-02-05T19:36:03  <aschildbach> Yes that rule is part of RBF.
247 2017-02-05T19:36:36  <arubi> now, if you see op cltv in the script, you check of disabled bit.  if you see op csv and it's version 2, you check for disabled bit
248 2017-02-05T19:36:53  *** ThomasV has joined #bitcoin-dev
249 2017-02-05T19:37:17  <aschildbach> I'm not going to see any script opcode, because I don't parse scripts.
250 2017-02-05T19:37:29  <aschildbach> So I just check the disabled bit, right?
251 2017-02-05T19:37:59  <arubi> yea, I guess, but.. you don't parse scripts at all?
252 2017-02-05T19:38:12  <arubi> not even normal ones?
253 2017-02-05T19:38:18  <aschildbach> The funny thing is for non-RBF inputs the disabled bit will always be set
254 2017-02-05T19:38:35  <arubi> right, because it's 0xfff...
255 2017-02-05T19:38:41  <aschildbach> Because non-RBF txns either use 0xffffffff or 0xfffffffe as a sequence
256 2017-02-05T19:38:46  <aschildbach> Maybe that's be design
257 2017-02-05T19:38:46  <arubi> really anything 0x07... is set
258 2017-02-05T19:38:58  <arubi> I'm pretty sure that's the right bit
259 2017-02-05T19:39:32  <arubi> well yea endian-ness
260 2017-02-05T19:40:07  <arubi> 0xffffff7f is set, I /think/
261 2017-02-05T19:40:45  <aschildbach> No RBF is "sequence < NO_SEQUENCE - 1" I'm pretty sure
262 2017-02-05T19:41:31  <arubi> yea rbf is anything lower than 0xfffffffe, core sets 2^32-3, pretty sure
263 2017-02-05T19:41:51  <arubi> I mean the disabled bit
264 2017-02-05T19:43:14  <aschildbach> I think in the current release it depends if you use the CLI or the UI.
265 2017-02-05T19:43:46  <arubi> you can set it with 'walletrbf=1' for cli, not sure if it sticks with gui
266 2017-02-05T19:43:56  <aschildbach> or the JSON interface
267 2017-02-05T19:52:21  <aschildbach> Ok but many thanks for the explanations. I think for now I know enough.
268 2017-02-05T19:59:31  <arubi> cheers
269 2017-02-05T20:04:14  *** aschildbach has quit IRC
270 2017-02-05T20:23:31  *** MoALTz has quit IRC
271 2017-02-05T20:30:29  *** iv3c has quit IRC
272 2017-02-05T20:31:14  *** iv3c has joined #bitcoin-dev
273 2017-02-05T20:47:25  *** bsm117532 has joined #bitcoin-dev
274 2017-02-05T20:59:05  *** blueness has quit IRC
275 2017-02-05T21:01:13  *** blueness has joined #bitcoin-dev
276 2017-02-05T21:43:20  *** ThomasV has quit IRC
277 2017-02-05T21:45:27  *** blueness has quit IRC
278 2017-02-05T21:45:44  *** copumpkin has joined #bitcoin-dev
279 2017-02-05T21:49:02  *** DiabloD3 has joined #bitcoin-dev
280 2017-02-05T21:49:34  *** Diablo-D3 has quit IRC
281 2017-02-05T21:49:35  *** DiabloD3 is now known as Diablo-D3
282 2017-02-05T21:51:19  *** blueness has joined #bitcoin-dev
283 2017-02-05T21:52:19  *** ThomasV has joined #bitcoin-dev
284 2017-02-05T21:58:13  *** e4xit_ has joined #bitcoin-dev
285 2017-02-05T21:58:58  *** Diablo-D3 has quit IRC
286 2017-02-05T21:59:38  *** Diablo-D3 has joined #bitcoin-dev
287 2017-02-05T22:04:29  *** janko33 has quit IRC
288 2017-02-05T22:09:13  *** Diablo-D3 has quit IRC
289 2017-02-05T22:09:58  *** Diablo-D3 has joined #bitcoin-dev
290 2017-02-05T22:10:55  *** JackH has joined #bitcoin-dev
291 2017-02-05T22:18:24  *** copumpkin has quit IRC
292 2017-02-05T22:19:05  *** blueness has quit IRC
293 2017-02-05T22:21:33  *** ThomasV has quit IRC
294 2017-02-05T22:33:20  *** ThomasV has joined #bitcoin-dev
295 2017-02-05T22:40:08  *** copumpkin has joined #bitcoin-dev
296 2017-02-05T22:41:11  *** Chris_Stewart_5 has quit IRC
297 2017-02-05T22:47:27  *** Chris_Stewart_5 has joined #bitcoin-dev
298 2017-02-05T22:51:14  *** blueness has joined #bitcoin-dev
299 2017-02-05T22:52:34  *** ThomasV has quit IRC
300 2017-02-05T23:03:07  *** wasi has joined #bitcoin-dev
301 2017-02-05T23:08:24  *** JackH has quit IRC
302 2017-02-05T23:14:09  *** Starduster has joined #bitcoin-dev
303 2017-02-05T23:23:29  *** copumpkin has quit IRC
304 2017-02-05T23:45:04  *** copumpkin has joined #bitcoin-dev