Ive checked - this trans showns in pool wallet, but not on chain for now:
   "txid" : "4523c30dca685cca82f9ad0db3445e07e8dce50cd5d2e94e6aa4b8bcd6a449e1",
    "version" : 1,
    "time" : 1382301925,
    "locktime" : 0,
    "vin" : [
        {
            "txid" : "68f9ca67d26cc96b2b5a5506880ceb0d33843ea96d6cc15e4ce0af6283b2aab8",
            "vout" : 0,
            "scriptSig" : {
                "asm" : "3046022100e2f9adbc10df004c04760f8481ff0d0ec91fee708e5679d0fb86c5237531125f02210 0f94bcc9cd02db46a96f7a3d970aace09ba8c4a6ab11491622942d291afa2f7$
                "hex" : "493046022100e2f9adbc10df004c04760f8481ff0d0ec91fee708e5679d0fb86c5237531125f022 100f94bcc9cd02db46a96f7a3d970aace09ba8c4a6ab11491622942d291afa2$
            },
            "sequence" : 4294967295
        },
........
   ],
    "vout" : [
        {
            "value" : 2.04833100,
            "n" : 0,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 3ca5c2bd96bed544186d691f8b269dfc56726cf5 OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a9143ca5c2bd96bed544186d691f8b269dfc56726cf588ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "En2BbTY6aabfEyPJbCJ6xFq7dGpgvB9jjN"
                ]
            }
        },
        {
            "value" : 1002.92766900,
            "n" : 1,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 2996476c9f9ff8abf3ed8b822930ca107ac630a5 OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a9142996476c9f9ff8abf3ed8b822930ca107ac630a588ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw"
                ]
            }
        }
    ],
    "amount" : -1002.92766900,
    "fee" : -0.02400000,
    "confirmations" : 0,
    "txid" : "4523c30dca685cca82f9ad0db3445e07e8dce50cd5d2e94e6aa4b8bcd6a449e1",
    "time" : 1382301927,

Also, there are some bug in network i think.
debug.log on pool wallet spammed with this messages:

getblocks 133263 to 00000000000000000000 limit 500
  getblocks stopping at limit 133762 000000005baeb4f22781
getblocks 138763 to 00000000000000000000 limit 500
  getblocks stopping at limit 139262 000000020c092152544f
ERROR: mempool transaction missing input
getblocks 136263 to 00000000000000000000 limit 500
  getblocks stopping at limit 136762 00000000157c4e7cdd98
getblocks 139263 to 00000000000000000000 limit 500
  getblocks stopping at limit 139762 000000017127b2ca603a
ERROR: mempool transaction missing input
getblocks 136763 to 00000000000000000000 limit 500
  getblocks stopping at limit 137262 00000001180089e6dd22
getblocks 139763 to 00000000000000000000 limit 500
  getblocks stopping at limit 140262 000000002f37c5abec8e
ERROR: mempool transaction missing input
getblocks 136263 to 00000000000000000000 limit 500
  getblocks stopping at limit 136762 00000000157c4e7cdd98


Its constantly repeated many times (5-10) every second for all last days!
What can be wrong?
Especially with  this error "ERROR: mempool transaction missing input"
How to get this error out?

The getblocks message is normal an prints in everyone's debug. To be honest it should be under debug not general. I've made note of it.

The ERROR mempool message can be solved by shutting the daemon down and restarting.  If that doesn't work, try it with a -rescan option. Let me know if neither of those helped.

There  appears to be a bad client on the network. It is either on purpose or an old client. getblocks doesn't punish peers if they keep requesting the same blocks.  I am pretty sure it is 70.98.114.237. I banned him via firewall and it stopped.

Same here on hbn.zabmail.ru:

getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
ERROR: mempool transaction missing input
getblocks -1 to 00000000000000000000 limit 500
ERROR: mempool transaction missing input
Flushing wallet.dat
Flushed wallet.dat 93ms
getblocks -1 to 00000000000000000000 limit 500
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
connection timeout
ERROR: mempool transaction missing input
trying connection 83.79.123.234:7372 lastseen=37.1hrs
connect() failed after select(): Connection refused
ERROR: mempool transaction missing input
trying connection 46.98.62.63:7372 lastseen=66.6hrs
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ThreadRPCServer method=getinfo
ERROR: mempool transaction missing input
ThreadRPCServer method=getmininginfo
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input

At some point I will add in tighter checking against the client and discconect them if they are on wrong version or misbehave like we saw.

I know this is a pain, but could you try shutting down, removing the block chain files( blk0001.dat, blkindex.dat and database directory). Then start back up and re-download the block chain?

If that doesn't work I will look closer soon.

Should not use 1.1, as of Halloween you will be forked off the main chain.  As far as the Warning Checkpoint. That is ok, basically just a notice that the CP needs updated. With each release I update the CP.  In some future release I will make it automatic. But that won't be for a while.

Yes it will be. I have talked with them. Many other coins have gone through roll backs and been suspended, later to be brought back, once the issue was addressed. I believe I have it corrected.

I am testing 1.2.1 right now.

we changed our pools to stratum with vardiff.

please change your settings, we will close getwork soon.

https://coinex.pw/mining/pools/HBN

This is most likely caused by many micro stakes trying to stake at the same time. It eats up the CPU. The best option is to combine your coins into a few larger sets. Just send them to yourself.

This will be addressed in future releases. Although the best I can do is create additional threads for the staking processes. And perhaps further optimized the staking process. But at the core it is just mining so at some point it will be too much and combining will be necessary.


Other crypto clients don't stake at 10 days!