Blockchain.info Rejects v0.12 Core TX'es.

[cakir]

Hi everyone. I've been using v0.12 for a few days and so far all transactions are rejected by blockchain.info's explorer with this warning:
"Transaction rejected by our node. Reason: The transaction is not final"
Other block explorers shows my transactions as usual.

Is there a problem on bc.info's explorer?



Upfront edit: yes my transactions are showed on bc.info's explorer after they get in a block. If you're saying something like that you're a sig spammer & your message is deleted.

[Quickseller]

Do you happen to have RBF enabled when sending a transaction with 0.12? If so then it would be trivial to double spend such transaction as long as it has not yet been confirmed and bc.i may not want to relay/display such transactions.

[cakir]

Do you happen to have RBF enabled when sending a transaction with 0.12? If so then it would be trivial to double spend such transaction as long as it has not yet been confirmed and bc.i may not want to relay/display such transactions.

No RBF is not enabled.
These tx'es are not double spends BTW.

[dooglus]

Is there a problem on bc.info's explorer?

Yes, blockchain.info won't display unconfirmed transactions from the current Bitcoin Core release. It's a known issue, caused by the new fee-sniping protection.

See Peter Todd's comment where he says:

My testing turned up only blockchain.info and Bitcoin Core itself as having issues with nLockTime at the limit transactions; hopefully by the time v0.12 is released these wallets will all be fixed

I reported the same issue back in February when testing the 0.12 release candidate:

I just sent a transaction from my Bitcoin Core wallet and tried to use a blockchain.info link to the transaction to show the recipient that I had sent it, but blockchain.info shows an error message:

  

I checked on other block explorers, and they all show it just fine:

but I got no response.

I would recommend using a different blockchain explorer. I mentioned 5 working alternatives in the post I partially quoted above.

Edit: see this reddit thread where I asked for and received an explanation of the new anti-fee sniping code.

[cakir]

Thanks a lot @dooglus for the info.
I'm using btc.blockr.io mainly now.