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

I did try a few sync of the win-qt without issues. I will see about the git.

{   
    "version" : "v1.2.2.0-g38a5c87-hobo",
    "protocolversion" : 70002,
    "blocks" : 426573,
    "moneysupply" : 2149270.94403000,
    "connections" : 8,
    "wallets" : 1,
    "proxy" : "",
    "ip" : "128.73.93.200",
    "difficulty" : 0.41032721,
    "testnet" : false,
    "paytxfee" : 0.00100000,
    "errors" : ""
}

Successfully synchronize with this dump, thank you. Any other methods, through Tor and raw didn't work. Could you test synchronization of git's source client from zero? It looks like something with this source.

Ok glad to hear. You can also jump start the process by download the block chain as of 12-2 here.

http://www.hobonickels.info/downloads/HBN%20Block%20Chain%2012-2.rar

Looks like it was my provider, or something. Now i launch synchronization through Tor, i'm on block #86547. It is still 100 days ago, but in progress. I'm waiting, will report you about result.

Full debug.log:


http://pastebin.com/aWRjQRwQ



ProcessSyncCheckpoint: pending for sync-checkpoint 0000000155f54276051e57d8bce16ff41ca46c20b06a478686de82e7cf318e33
ProcessSyncCheckpoint: pending for sync-checkpoint 0000000155f54276051e57d8bce16ff41ca46c20b06a478686de82e7cf318e33
ProcessSyncCheckpoint: pending for sync-checkpoint 0000000155f54276051e57d8bce16ff41ca46c20b06a478686de82e7cf318e33
ProcessSyncCheckpoint: pending for sync-checkpoint 0000000155f54276051e57d8bce16ff41ca46c20b06a478686de82e7cf318e33
received block 38f21486264142a054f5
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 38f21486264142a054f50b977dbe2803b6e7a7558e6096f80b8dd1537bbba126
ThreadRPCServer method=getinfo
ERROR: FetchInputs() : 721c28d835 mempool Tx prev not found 92d3fb50dd
stored orphan tx 721c28d835 (mapsz 3)
received block 0000000127bea336c2bd
ProcessBlock: ORPHAN BLOCK, prev=0000000155f54276051e
ProcessSyncCheckpoint: pending for sync-checkpoint 0000000127bea336c2bdd012e0c3fd94ae7904e94f13ddf245ae2243364e8b13
ProcessSyncCheckpoint: pending for sync-checkpoint 0000000127bea336c2bdd012e0c3fd94ae7904e94f13ddf245ae2243364e8b13
ProcessSyncCheckpoint: pending for sync-checkpoint


I'll enable debug right now, this debug.log show with configuration `debug=0`. Here http://slexy.org/view/s20WgmlQ0W

1.2.2.0 is fine.  What does your debug log say? There is no reason you should not be able to get synced up..

{
    "version" : "v1.2.2.0-g38a5c87-hobo",
    "protocolversion" : 70002,
    "blocks" : 53985,
    "moneysupply" : 266685.49382100,
    "connections" : 7,
    "wallets" : 1,
    "proxy" : "",
    "ip" : "128.73.93.243",
    "difficulty" : 0.50919559,
    "testnet" : false,
    "paytxfee" : 0.00100000,
    "errors" : ""
}


https://github.com/ahmedbodi/HoboNickels.git

$ git pull
Already up-to-date.


Where can I get latest version ?

Are you on the correct software version? The newest release is 1.2.2.3 you need to be a least on 1.2.1.5, but I suggest grabbing the highest.

If you are on the correct version, please paste the last 20 lines from your debug file.

Tranz, I remove everything from .HoboNickels/


my .HoboNickels/HoboNickels.conf looks like:


daemon=1
debug=0
maxconnections=100
noirc=0
port=7372
rpcallowip=127.0.0.1
rpcconnect=127.0.0.1
rpcport=7373
rpctimeout=180
server=0
addnode=[2001:0:9d38:6ab8:412:3f55:43e8:a41f]:52421
addnode=[2001:0:9d38:6abd:34f7:314b:9e8f:a4a0]:59029
addnode=[2001:0:9d38:90d7:183e:2f92:e078:9a83]:54628
addnode=94.142.242.51:7372
addnode=68.96.120.248:7372
addnode=162.243.252.178:7372
addnode=91.121.16.64:7372
addnode=5.39.90.17:7372
addnode=5.249.152.30:7372
addnode=108.212.104.77
addnode=109.163.247.64
addnode=118.127.61.65
addnode=118.209.0.241
addnode=121.44.83.145
addnode=128.70.109.167
addnode=159.224.220.21
addnode=162.243.109.244
addnode=162.243.69.147
addnode=162.243.78.234
addnode=178.49.118.233
addnode=178.75.180.121
addnode=188.113.222.104
addnode=188.82.120.113
addnode=195.62.15.20
addnode=198.211.116.19
addnode=198.27.80.205
addnode=[2001:0:5ef5:79fb:1049:2e09:bdf7:127d]
addnode=[2001:0:9d38:6abd:86c:6ea0:aae5:1795]
addnode=202.60.64.105
addnode=206.72.202.20
addnode=24.93.183.133
addnode=46.10.123.227
addnode=50.125.160.28
addnode=5.249.152.30
addnode=5.35.249.3
addnode=5.39.90.17
addnode=67.165.141.206
addnode=68.186.147.243
addnode=68.96.120.248
addnode=69.17.228.195
addnode=69.85.86.195
addnode=69.85.86.195
addnode=71.232.52.37
addnode=71.79.101.70
addnode=72.191.117.227
addnode=74.196.48.62
addnode=75.155.136.206
addnode=84.22.139.7
addnode=85.210.3.169
addnode=85.218.40.108
addnode=86.161.0.24
addnode=89.28.206.126
addnode=91.124.31.249
addnode=91.69.177.224
addnode=92.5.104.102
addnode=98.232.23.64
addnode=99.189.84.118


Nevertheless, I'm stuck on block #53984. What a magic it might be?

These are orphans. They happen more often with coins that have quick block times. There is nothing you can do about them. The best strategy to prevent them is to leave the wallet running with a good number of peers connected.

To remove them from your wallet, start the HoboNickels-qt.exe with -salvagewallet . This will also remove your address book, so be sure to export it if it you need it.

Those seem like good peers. You may need to  delete peers.dat and try some of these.

"addr" : "[2001:0:9d38:6ab8:412:3f55:43e8:a41f]:52421",
"addr" : "[2001:0:9d38:6abd:34f7:314b:9e8f:a4a0]:59029",
addr" : "[2001:0:9d38:90d7:183e:2f92:e078:9a83]:54628",
addr" : "94.142.242.51:7372",
addr" : "68.96.120.248:7372",
"addr" : "162.243.252.178:7372",
"addr" : "91.121.16.64:7372",
"addr" : "5.39.90.17:7372",
"addr" : "5.249.152.30:7372",

If you are still stuck. try removing all peers from your config. Deleting peers.dat as well as database directory ,blk0001.dat,blkindex.dat. Then let it sync by using IRC.

Also be sure you are on the correct version.

Feel free to +1 my post for coin marketcap

https://bitcointalksearch.org/topic/m.4002229

hellow，Here are some errors  in my HoboNickel wallet

Status: 0/unconfirmed
Date: 2013/11/27 15:20
Debit: 0.00 HOBO
Net amount: -259.609 HOBO
Transaction ID: c0b5c072020513e2ddfd1549cfa77fccc7f593c2a7ff095498c7c59afe977f47

Generated coins must mature 25 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

Status: 0/unconfirmed
Date: 2013/10/3 09:49
Debit: 0.00 HOBO
Net amount: -153.99 HOBO
Transaction ID: d7666b3dfd50e90e966996a054c2820cd582bb38ad17e53272086a3e8ba7bc8b

Generated coins must mature 25 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

Status: 0/unconfirmed
Date: 2013/11/27 15:34
Debit: 0.00 HOBO
Net amount: -77.309 HOBO
Transaction ID: ba1c1541ecf10480e54ccfa364cd7309fe03a06e78e23d98b7e3b8b349667faf

Generated coins must mature 25 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

Status: 0/unconfirmed
Date: 2013/11/27 15:49
Debit: 0.00 HOBO
Net amount: -77.30 HOBO
Transaction ID: 43a3eab4aa2d582bb4d8fe5396b35c45feefa96bd93c12b77bdb2eaedb977576

Generated coins must mature 25 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

Status: 0/unconfirmed
Date: 2013/11/27 20:56
Debit: 0.00 HOBO
Net amount: -36.993 HOBO
Transaction ID: 462a66e3e623b183ea1457977a670b60970670d22f61e3173d3262d9d5a50d71

Generated coins must mature 25 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

Hello fellow HoboNickelers!

I am beginning an advertising campaign on Reddit on 12/19.  Nothing big, just a bit of advertising on /r/litecoin and /r/cryptocurrency.

Here is what the ad looks like so far: http://i.imgur.com/NagXQoz.jpg  

I am totally open for suggestions for the text, but I think this leaves it pretty simple.

I would like to have the ability to continue advertising, so we are going to open up a donation wallet address for the HBN Foundation that will go towards advertising, and hopefully if we get enough donations we will be able to hire a freelance web designer to make hobonickels.info looks slick!

Donations can be made through the following wallets:

Bitcoin: 1Paw5R56URCLPyDu87mdPuKLLavYXWFzgC

Litecoin: LXWR3Ph6rw3RW5a7rM787peyVwBUf6zmA9

HoboNickel: Ex3Z1roGMsaHbPRdvLZdeaMKn5ys5ZsEAn

 

I'm stuck with sync on block #53984, my .HoboNickels/HoboNickels.conf:

daemon=1
debug=0
# gen=1
# http://hobo.gets-it.net/peers.php
maxconnections=100
noirc=0
port=7372
rpcallowip=127.0.0.1
rpcconnect=127.0.0.1
rpcpassword=password
rpcport=7373
rpctimeout=180
rpcuser=user
server=0
#4way=1
addnode=108.212.104.77
addnode=109.163.247.64
addnode=118.127.61.65
addnode=118.209.0.241
addnode=121.44.83.145
addnode=128.70.109.167
addnode=159.224.220.21
addnode=162.243.109.244
addnode=162.243.69.147
addnode=162.243.78.234
addnode=178.49.118.233
addnode=178.75.180.121
addnode=188.113.222.104
addnode=188.82.120.113
addnode=195.62.15.20
addnode=198.211.116.19
addnode=198.27.80.205
addnode=[2001:0:5ef5:79fb:1049:2e09:bdf7:127d]
addnode=[2001:0:9d38:6abd:86c:6ea0:aae5:1795]
addnode=202.60.64.105
addnode=206.72.202.20
addnode=24.93.183.133
addnode=46.10.123.227
addnode=50.125.160.28
addnode=5.249.152.30
addnode=5.35.249.3
addnode=5.39.90.17
addnode=67.165.141.206
addnode=68.186.147.243
addnode=68.96.120.248
addnode=69.17.228.195
addnode=69.85.86.195
addnode=69.85.86.195
addnode=71.232.52.37
addnode=71.79.101.70
addnode=72.191.117.227
addnode=74.196.48.62
addnode=75.155.136.206
addnode=84.22.139.7
addnode=85.210.3.169
addnode=85.218.40.108
addnode=86.161.0.24
addnode=89.28.206.126
addnode=91.124.31.249
addnode=91.69.177.224
addnode=92.5.104.102
addnode=98.232.23.64
addnode=99.189.84.118


Could somebody share with me valid peers.dat?

Hey guys there is a mis behaving peer on the network.  2001:0:9d38:6ab8:2057:269:3c0f:bb73  is requesting the same blocks over and over again rapidly. Currently the client does not ban this type of behavior. I will see what can be done to not allow this, but in the mean time I suggest you ban him via firewall.

Wow Thanks, good stuff!

P2Pool.org now has HoboNickels!

To view the pool stats go here:
http://p2pool.org:38888/static/

To mine HoboNickels point your miner URL to:
http://p2pool.org:38888

Use your HoboNickels public key as the username and any password.

To get your public key open the console window in the HoboNickels client and enter "getnewpubkey p2pool" with out the quotes.

Check out our HoboNickels Block Crawler here:
http://p2pool.org/HBN/BlockCrawler/

Happy Mining!

You are welcome!

ABE block explorer is up explorer.hobonickels.info  Also 1 pool has been claimed a bounty.

I am leaving the bounty up for both for 1 more of each. Redundancy is a good thing.