Quote from: esotericizm on February 02, 2016, 10:55:44 AM

Quote from: bitspill on January 31, 2016, 09:00:21 AM

Yep, it got stuck.

This transaction is failing to pass verification so the block gets rejected and the peer banned for being malicious.

http://florincoin.info/explorer/tx/?txid=6cba295dbd61a81c35ab994a94b6e758782661b976ee015043ea2314f84535bf

Can someone with a synced node run this command in either debug console or florincoind?

Code:

gettransaction 6cba295dbd61a81c35ab994a94b6e758782661b976ee015043ea2314f84535bf

While I was debugging that I also deleted my chainstate index so now it's redoing the entire blockchain, yay waiting. Cheesy

I believe im running into a similar issue trying to port over a block explorer. Some Peers appear to be issuing txes with invalid inputs (invalid txids). If you have any thoughts please send me a PM. T

As of right now I'm wondering if the issue comes back to openSSL vs libsecp256k1 and the handling of signatures. https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009697.html & https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki

As a dirty hack I set all transactions to pass verification which then allowed it to fully sync. I then deleted the blockchain and am now syncing again with validation checks back in but also some debug log statements.