1 2017-02-27 00:23:55 <pirosb3> Hi, I'm having problems spending a OP_CHECKLOCKTIMEVERIFY transaction on testnet
 2 2017-02-27 00:25:26 <pirosb3> upon creating a redeem transaction for a7681326607bbb94026fca9f21563b2c1418c22b8e39638f7910e338915ead46 (testnet), adding a locktime, changing the sequence to 0, I get "64: non-final" from bitcoin CLI
 3 2017-02-27 00:26:35 <pirosb3> This is my TX: https://gist.github.com/PirosB3/004745633f31d19c608c94be57315c10
 4 2017-02-27 00:36:27 <achow101> pirosb3: for one thing, your transaction version number is 0. it needs to be at least 1, I think 2 for OP_CLTV to work
 5 2017-02-27 00:36:49 <pirosb3> oh interesting! I thought version was not used..
 6 2017-02-27 00:36:54 <achow101> also, this transaction won't be accepted by nodes until after the locktime has passed
 7 2017-02-27 00:37:03 <pirosb3> I'll change that immediately and give it a go
 8 2017-02-27 00:37:05 <pirosb3> Thanks!
 9 2017-02-27 00:37:08 <pirosb3> will update
10 2017-02-27 00:39:51 <pirosb3> achow101: I undated version to 2, but it's still erroring in the same way. Here is the decoded tx: https://gist.github.com/PirosB3/004745633f31d19c608c94be57315c10
11 2017-02-27 00:41:06 <achow101> the locktime has not passed yet. locktime now uses median time past, which is the median time of the last 11 blocks
12 2017-02-27 00:41:28 <achow101> if you do getblockchaininfo, you can see what the current median time is
13 2017-02-27 00:42:34 <pirosb3> median past time? O_O that's what it was!!
14 2017-02-27 00:42:37 <pirosb3> ok, let me add that value inside
15 2017-02-27 00:42:56 <pirosb3> thanks
16 2017-02-27 01:08:33 <pirosb3> cool, achow101 now I'm getting "64 non-manatory-script-verify-flag"
17 2017-02-27 01:08:56 <pirosb3> is this an error with my script? is there any detail I can extract on to where it failed?
18 2017-02-27 01:18:48 <achow101> it's nonstandard
19 2017-02-27 01:19:34 <achow101> IIRC op_cltv is still technically a non-standard script
20 2017-02-27 01:31:16 <danielpyrathon> achow101: when you say it's nonstandard, does that mean I cannot submit transactions with CLTV in them? doesn't the blockchain support them atm?
21 2017-02-27 01:32:28 <achow101> danielpyrathon: they are valid, just won't be relayed as well
22 2017-02-27 01:33:00 <achow101> most nodes don't accept nonstandard transactions
23 2017-02-27 01:33:44 <danielpyrathon> really?
24 2017-02-27 01:36:21 <danielpyrathon> achow101: could it be my signature not being valid?
25 2017-02-27 01:37:10 <danielpyrathon> if most nodes don't accept CLTV, then why was my first transaction (using OP_CHECKLOCKTIMEVERIFY) relayed?
26 2017-02-27 15:07:30 <XMG> Hey, i have trouble with bitcoind. I'm running bitcoind on my localhost and generated me a wallet with addresses. I paid to these addresses, but i didnt get a balance. I dumped privkey and imported to my "normal" wallet. There I have the ballance (also in the blockchain). Does anyone know this iussue and can help me?
27 2017-02-27 15:10:07 <kinlo> XMG: that's not a question for -dev, go to #bitcoin
28 2017-02-27 15:11:01 <XMG> Ok thanks!
29 2017-02-27 15:42:43 <gielbier> Am i correct in assuming that the current number of transactions displayed by bitcoin-cores debug window. Isn't counting replaced transaction with opt in rbf?
30 2017-02-27 15:42:51 <gielbier> mempool transaction
31 2017-02-27 15:42:52 <gielbier> s