Author

Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 290. (Read 478581 times)

legendary
Activity: 1540
Merit: 1052
May the force bit with you.
is there any chance for HBN to be listed again on cryptsy?

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.
newbie
Activity: 49
Merit: 0
is there any chance for HBN to be listed again on cryptsy?
legendary
Activity: 1540
Merit: 1052
May the force bit with you.
I'm not sure if this helps.  I don't run a mining pool.  Just a hobonickeler.

When I used 1.1 client I got the error message "WARNING: Checkpoint is too old. Redownload Blockchain. If warning persist contact the Development Team".  I deleted the blockchain info, upgraded to 1.2 client, and I still get the same error message.

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.
newbie
Activity: 15
Merit: 0
I'm not sure if this helps.  I don't run a mining pool.  Just a hobonickeler.

When I used 1.1 client I got the error message "WARNING: Checkpoint is too old. Redownload Blockchain. If warning persist contact the Development Team".  I deleted the blockchain info, upgraded to 1.2 client, and I still get the same error message.
legendary
Activity: 1540
Merit: 1052
May the force bit with you.

Blocking the IP did away with repeating getblocks messages for now.
The mempool messages are still rolling in after a wallet restart and a rescan.

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.
full member
Activity: 139
Merit: 100
Unfortunately, but 20.10.2013 at evening my coins have withdrawn from hbn.zabmail.ru to my wallet EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw.
And still they are unconfirmed:

Status: 0/unconfirmed
Date: 20.10.2013 23:45
From: unknown
To: EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw (own address)
Credit: 1002.927669 HOBO
Net amount: +1002.927669 HOBO
Transaction ID: 4523c30dca685cca82f9ad0db3445e07e8dce50cd5d2e94e6aa4b8bcd6a449e1


As long as vasp can very this, I will send these to you.

Ive checked - this trans showns in pool wallet, but not on chain for now:
 

Thanks. These are sent.

Thanks!
newbie
Activity: 49
Merit: 0

Blocking the IP did away with repeating getblocks messages for now.
The mempool messages are still rolling in after a wallet restart and a rescan.

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

newbie
Activity: 19
Merit: 0

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.

Yes, sometimes its normal, but not in this case, see - there are same blocks requested by same clients, its repeated constantly, with very high speed.
And start blocks are 136263 and 136762 - they are in far past already.
In normal life i've never seen same requests with any other altcoins.

Yesterday already tryed restart pool wallet, doesnt helped with mempool error. Will try with rescan later.

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.

Blocking the IP did away with repeating getblocks messages for now.
The mempool messages are still rolling in after a wallet restart and a rescan.
legendary
Activity: 1540
Merit: 1052
May the force bit with you.

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.

Yes, sometimes its normal, but not in this case, see - there are same blocks requested by same clients, its repeated constantly, with very high speed.
And start blocks are 136263 and 136762 - they are in far past already.
In normal life i've never seen same requests with any other altcoins.

Yesterday already tryed restart pool wallet, doesnt helped with mempool error. Will try with rescan later.

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.
newbie
Activity: 49
Merit: 0

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.

Yes, sometimes its normal, but not in this case, see - there are same blocks requested by same clients, its repeated constantly, with very high speed.
And start blocks are 136263 and 136762 - they are in far past already.
In normal life i've never seen same requests with any other altcoins.

Yesterday already tryed restart pool wallet, doesnt helped with mempool error. Will try with rescan later.
legendary
Activity: 1540
Merit: 1052
May the force bit with you.
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?



I can confirm this mine is filling up with these errors as well but at a far faster rate than 5-10 seconds.
My debug.log I just noticed entered the gigabyte size range.

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.
newbie
Activity: 19
Merit: 0
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?



I can confirm this mine is filling up with these errors as well but at a far faster rate than 5-10 seconds.
My debug.log I just noticed entered the gigabyte size range.
newbie
Activity: 49
Merit: 0
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?

legendary
Activity: 1540
Merit: 1052
May the force bit with you.
Unfortunately, but 20.10.2013 at evening my coins have withdrawn from hbn.zabmail.ru to my wallet EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw.
And still they are unconfirmed:

Status: 0/unconfirmed
Date: 20.10.2013 23:45
From: unknown
To: EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw (own address)
Credit: 1002.927669 HOBO
Net amount: +1002.927669 HOBO
Transaction ID: 4523c30dca685cca82f9ad0db3445e07e8dce50cd5d2e94e6aa4b8bcd6a449e1


As long as vasp can very this, I will send these to you.

Ive checked - this trans showns in pool wallet, but not on chain for now:
 

Thanks. These are sent.
newbie
Activity: 49
Merit: 0
Unfortunately, but 20.10.2013 at evening my coins have withdrawn from hbn.zabmail.ru to my wallet EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw.
And still they are unconfirmed:

Status: 0/unconfirmed
Date: 20.10.2013 23:45
From: unknown
To: EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw (own address)
Credit: 1002.927669 HOBO
Net amount: +1002.927669 HOBO
Transaction ID: 4523c30dca685cca82f9ad0db3445e07e8dce50cd5d2e94e6aa4b8bcd6a449e1


As long as vasp can very this, I will send these to you.

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,
legendary
Activity: 1540
Merit: 1052
May the force bit with you.
http://hbn.theblocksfactory.com/ , we lost about 400 HBN but it's not a problem for us

Ok well if you change your mind, you know where I'll be.
legendary
Activity: 1540
Merit: 1052
May the force bit with you.
Unfortunately, but 20.10.2013 at evening my coins have withdrawn from hbn.zabmail.ru to my wallet EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw.
And still they are unconfirmed:

Status: 0/unconfirmed
Date: 20.10.2013 23:45
From: unknown
To: EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw (own address)
Credit: 1002.927669 HOBO
Net amount: +1002.927669 HOBO
Transaction ID: 4523c30dca685cca82f9ad0db3445e07e8dce50cd5d2e94e6aa4b8bcd6a449e1


As long as vasp can very this, I will send these to you.
legendary
Activity: 1540
Merit: 1052
May the force bit with you.


We have lost 285.7046697 HBN on this

I will do my best to reimburse all losses if I can. I am still looking into what caused it.  

Please post an address.

Thank you Sir!

EqbmnfAGVTMuPxzQzv3XjB5tdAXuyycqZf

500 sent Thanks for your support.
full member
Activity: 139
Merit: 100
Unfortunately, but 20.10.2013 at evening my coins have withdrawn from hbn.zabmail.ru to my wallet EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw.
And still they are unconfirmed:

Status: 0/unconfirmed
Date: 20.10.2013 23:45
From: unknown
To: EkHQD8Fm2baHWp4s4X5YB5bWTJM13nhNPw (own address)
Credit: 1002.927669 HOBO
Net amount: +1002.927669 HOBO
Transaction ID: 4523c30dca685cca82f9ad0db3445e07e8dce50cd5d2e94e6aa4b8bcd6a449e1
sr. member
Activity: 294
Merit: 250


We have lost 285.7046697 HBN on this

I will do my best to reimburse all losses if I can. I am still looking into what caused it.  

Please post an address.

Thank you Sir!

EqbmnfAGVTMuPxzQzv3XjB5tdAXuyycqZf
Jump to: