HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive

[Tranz]

Yes, yes, YES, you're a hero!
Can I send you some Bismuth? PM me your adress, we now even have a web wallet https://biswallet.acc-pool.pw/index.php

Thank you.  Let's wait until a week or two after the fork takes effect, before we celebrate.

I am still seeing lots of orphan blocks, so side chains may still getting created.   Such as these:

2017-09-10 21:25:10 ProcessBlock: ORPHAN BLOCK, prev=f2f0e3d7722e00a65705
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=e607d22ea5c1f601b3c0
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=1fb5c078b1a6b7a30d50
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=35ce6730686a04b690a7
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=3cbc17db53cfac395246
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=4ab6bb39632a867f3dfb
2017-09-10 21:25:14 ProcessBlock: ORPHAN BLOCK, prev=fdd9df756e73c7a65b02
2017-09-10 21:25:14 ProcessBlock: ORPHAN BLOCK, prev=7a9c13ab610f14d7f177

Do these belong to anybody?


Now granted I am still allowing the older clients on the chain until Sept 15.  After then I expect to see less and less of this type of thing.

BTW the Block Explorer is now on the right chain.  

But for the next 2 weeks we need to be vigilant.  If you do NOT match the BE then either you or it is wrong.  If that is the case then double check your block vs the checkpoint block. If you are wrong, best to remove turn off your wallet and get right..

[PeterTheGrape]

You have done a lot of work over the years tranz.

[vancefox]

Apparently I'm on the right chain comparing the txids to the blocks from Tranz... and I've updated to 2.0.

[CoinEraser]

HoboNickels Version 2.0 is now live.  https://github.com/Tranz5/HoboNickels/releases/latest

Very good Tranz!
I have updated to the latest version and everything is running very well and am still on the right chain.
Waiting for the fork now 

[versprichnix]

I am still seeing lots of orphan blocks, so side chains may still getting created.   Such as these:

2017-09-10 21:25:10 ProcessBlock: ORPHAN BLOCK, prev=f2f0e3d7722e00a65705
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=e607d22ea5c1f601b3c0
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=1fb5c078b1a6b7a30d50
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=35ce6730686a04b690a7
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=3cbc17db53cfac395246
2017-09-10 21:25:12 ProcessBlock: ORPHAN BLOCK, prev=4ab6bb39632a867f3dfb
2017-09-10 21:25:14 ProcessBlock: ORPHAN BLOCK, prev=fdd9df756e73c7a65b02
2017-09-10 21:25:14 ProcessBlock: ORPHAN BLOCK, prev=7a9c13ab610f14d7f177

Do these belong to anybody?

These are mine. They occured after the upgrade to version 2.0. I'm running a self compiled version on ubuntu linux 14.04.5 LTO.

I'm on block 5655511 at this time, and it seems to be the right chain.

I'm running my stake over a VPN, perhaps the time lag could cause issues?

[mayfun]

Nice to see licensed blockchain will open it's doors for investors gambling industry is growing rapidly. I always like to invest in gambling casino because being on the house side give us more opportunities to make huge profit so that I will keep eye on this thread.

[versprichnix]

Nice to see licensed blockchain will open it's doors for investors gambling industry is growing rapidly. I always like to invest in gambling casino because being on the house side give us more opportunities to make huge profit so that I will keep eye on this thread.

No, I will make profit, so you will not!

Ignore.

[Tranz]

Blocks coming in fast and furious!  We are only 8,500 blocks away from the first part of the fork.


So far the network seems to be hold together just fine.. Does anyone see anything different?

[dnp]

Blocks coming in fast and furious!  We are only 8,500 blocks away from the first part of the fork.


So far the network seems to be hold together just fine.. Does anyone see anything different?

i suspect my wallet at coins.dognose.com is on a shorter fork
too busy with other stuff to look deeper.
current block 5656212 at timestamp 1505178634 (Sep 11 21:10:34 EDT)

[Tranz]

Blocks coming in fast and furious!  We are only 8,500 blocks away from the first part of the fork.


So far the network seems to be hold together just fine.. Does anyone see anything different?

i suspect my wallet at coins.dognose.com is on a shorter fork
too busy with other stuff to look deeper.
current block 5656212 at timestamp 1505178634 (Sep 11 21:10:34 EDT)

Looks like maybe?
https://chainz.cryptoid.info/hbn/block.dws?36874e4b721cb0b91f2263c9f4f0f103cea59aba91f59f6739fa0dbd873aea7c.htm

Let me know when you have time.
Version 2.0? How many peers?   Were you on right chain before 2.0? or after?

Might be best to shut down wallet until you can look.

Edit: Are these you?

017-09-12 02:40:53 ProcessBlock: ORPHAN BLOCK, prev=0571ceb5802db3dbf75e
017-09-12 02:40:55 ProcessBlock: ORPHAN BLOCK, prev=c826bf51db66ad6c4094
017-09-12 02:40:55 ProcessBlock: ORPHAN BLOCK, prev=1e3ee6d83f24cde352f4
017-09-12 02:40:55 ProcessBlock: ORPHAN BLOCK, prev=cfbe97191df55ed0abb5
017-09-12 02:40:55 ProcessBlock: ORPHAN BLOCK, prev=cc822675d70c858fb7fc
017-09-12 02:40:55 ProcessBlock: ORPHAN BLOCK, prev=b4ce09697e2e51b3d6b9
017-09-12 02:40:55 ProcessBlock: ORPHAN BLOCK, prev=a9db8c8dd4d7d691ba27
017-09-12 02:40:55 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:40:55 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:40:55 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:40:55 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:40:55 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:40:55 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:40:55 ProcessBlock: ORPHAN BLOCK, prev=b9f44a2817f2dc930788
017-09-12 02:40:57 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:40:57 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:40:57 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:40:57 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:40:57 ProcessBlock: ORPHAN BLOCK, prev=60969a4f6449fcd58539
017-09-12 02:40:58 ProcessBlock: ORPHAN BLOCK, prev=fe7d6e53cead28229c84
017-09-12 02:40:58 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:40:58 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:40:58 ProcessBlock: ORPHAN BLOCK, prev=da5e56531975180cef38
017-09-12 02:41:00 ProcessBlock: ORPHAN BLOCK, prev=fc55d038a118c217b582
017-09-12 02:41:00 ProcessBlock: ORPHAN BLOCK, prev=c6cf9223fb04b3cd0db5
017-09-12 02:41:00 ProcessBlock: ORPHAN BLOCK, prev=c4c789e6937b94c04fa5
017-09-12 02:41:00 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:41:00 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:41:00 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:41:00 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:41:00 ProcessBlock: ORPHAN BLOCK, prev=ca72209bc3c99b29464a
017-09-12 02:41:01 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:41:01 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:41:01 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:41:01 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:41:01 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:41:01 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:41:01 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:41:01 ERROR: ProcessBlock() : AcceptBlock FAILED
017-09-12 02:41:01 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:41:01 ERROR: ProcessBlock() : AcceptBlock FAILED

[dnp]

Blocks coming in fast and furious!  We are only 8,500 blocks away from the first part of the fork.


So far the network seems to be hold together just fine.. Does anyone see anything different?

i suspect my wallet at coins.dognose.com is on a shorter fork
too busy with other stuff to look deeper.
current block 5656212 at timestamp 1505178634 (Sep 11 21:10:34 EDT)

Looks like maybe?
https://chainz.cryptoid.info/hbn/block.dws?36874e4b721cb0b91f2263c9f4f0f103cea59aba91f59f6739fa0dbd873aea7c.htm

Let me know when you have time.
Version 2.0? How many peers?   Were you on right chain before 2.0? or after?

Might be best to shut down wallet until you can look.

Edit: Are these you?

017-09-12 02:40:53 ProcessBlock: ORPHAN BLOCK, prev=0571ceb5802db3dbf75e
017-09-12 02:40:55 ProcessBlock: ORPHAN BLOCK, prev=c826bf51db66ad6c4094
017-09-12 02:40:55 ProcessBlock: ORPHAN BLOCK, prev=1e3ee6d83f24cde352f4

 <brevity>

017-09-12 02:41:01 ERROR: AcceptBlock() : rejected by synchronized checkpoint
017-09-12 02:41:01 ERROR: ProcessBlock() : AcceptBlock FAILED

v2.0, was on correct chain when my 2.0 started running yesterday around 7pm EDT
been running 24/7.
4 peers, but one of them was my win7 qt 2.0 wallet

time... is there a vending machine for that?
i shut them both down.
i have a backup of blocks from sep.5 11pm, i'll restore those and restart tomorrow. (although i dont stricly recall that backup being of a good chain)

[Turrican]

On http://coinserver.ddns.net/hobonickelsd-status/ is the Node Version: v1.5.3.1-gf46fa0c-V1.5 ... pls update 

[lightspeedy]

Hello, I was interested in this coin, but apparently everything is in maintenance, because I went to buy in Cryptopia and the negotiations are paused, what is the current difficulty of getting HoboNickels in mining?

This coin is changing currently from PoW/PoS to PoS.
After cryptopia has updated their client to version 2.0.0 the trading can continue.

Just download the new 2.0.0 wallet on GitHub
https://github.com/Tranz5/HoboNickels/releases/tag/2.0 and sync.

There is currently a bug to resolve but the future for this coin in bright and shiny.
Stay tuned!

[papasmurph]

Flawless. Thx.

[str4w]

I've updated 2 wallets to 2.0. Everything went fine but on block 5659047 I forked, I cant sync since then now I'm 20h behind and nothing happens. How to proceed without resyncing the whole chain for 4 days?`


01:20:50
getblockhash 5659047
01:20:50
def614b5c9920cff69150c4d65c67d83591b42d9a02a2e171c8468bd3306ae2e


here what its supposed to be on the explorer

Details for Block #5659047
Hash    0000000956b04c02d0dadc51fc139aae70f879e49948d28c0170145e2c5a98f9
Date/Time   2017-09-12 03:06:45

[pazor_true]

start a new client v2.0 and try to sync from scratch on two different machines.

receive on debug.log
date connect() failed after select(): Connection refused  or No route to host

any idea ?

starting with addnode command included
addnode=80.56.92.208
addnode=103.86.99.7

[Tranz]

I've updated 2 wallets to 2.0. Everything went fine but on block 5659047 I forked, I cant sync since then now I'm 20h behind and nothing happens. How to proceed without resyncing the whole chain for 4 days?`


01:20:50
getblockhash 5659047
01:20:50
def614b5c9920cff69150c4d65c67d83591b42d9a02a2e171c8468bd3306ae2e


here what its supposed to be on the explorer

Details for Block #5659047
Hash    0000000956b04c02d0dadc51fc139aae70f879e49948d28c0170145e2c5a98f9
Date/Time   2017-09-12 03:06:45

Do you have the full debug.log file? Can you upload it somewhere for me? Encrypt it if you want..

How many connection did you have? Were they older clients?  Did you compile yourself or use my download?
 
For now turn off your wallets and hang tight. I will get a fresh copy of the blockchain as soon as the fork takes place.  You can use that to get back up to speed quickly.

hmmm, 7 leading zeros again, i hate zeroes

This is just a PoW block. The difficulty is low.

start a new client v2.0 and try to sync from scratch on two different machines.

receive on debug.log
date connect() failed after select(): Connection refused  or No route to host

any idea ?

starting with addnode command included
addnode=80.56.92.208
addnode=103.86.99.7

Just no connection to those nodes.
You can try a few others.
109.227.254.135
71.126.179.61
87.98.159.143


The fork is about 4k away. So I think we are looking about this time if not a little later tomorrow night. Stay vigilant. If you are not on the right chain, just shut off and wait. I will help you get right once the fork takes place.  I have 4 clients running and watching the block explore. All have been doing very well so far. I think after the fork, these side chains should be a thing of the past... Well I hope at least..

[str4w]

Thanks Tranz but I think I fixed it. Got wallets mixed up and started from a older chain which forked. Then I copied it and screwed up both wallets.
I opened up an older copy and it seems to be syncing now. 13h behind und closing in.

Code:

2017-09-13 02:40:11 SetBestChain: new best=0000001f43047bd46354 height=5660712 trust=87829329949953 blocktrust=94 date=09/12/17 13:33:45
2017-09-13 02:40:11 ProcessBlock: ACCEPTED
2017-09-13 02:40:11 SetBestChain: new best=478ef65309a47237ebfb height=5660713 trust=87829348893658 blocktrust=18943705 date=09/12/17 13:34:19
2017-09-13 02:40:11 ProcessBlock: ACCEPTED
2017-09-13 02:40:12 SetBestChain: new best=b064439e12816352d065 height=5660714 trust=87829367845853 blocktrust=18952195 date=09/12/17 13:34:23
2017-09-13 02:40:12 ProcessBlock: ACCEPTED
2017-09-13 02:40:13 SetBestChain: new best=233321847b0b8af276ad height=5660715 trust=87829386869862 blocktrust=19024009 date=09/12/17 13:34:59
2017-09-13 02:40:13 ProcessBlock: ACCEPTED
2017-09-13 02:40:13 SetBestChain: new best=050e8b6181a6b1321a33 height=5660716 trust=87829405877427 blocktrust=19007565 date=09/12/17 13:35:17
2017-09-13 02:40:13 ProcessBlock: ACCEPTED
2017-09-13 02:40:17 connection from 71.126.179.61:27237 dropped (banned)
2017-09-13 02:41:44 connection from 103.86.99.7:12699 dropped (banned)

[dnp]

Thanks Tranz but I think I fixed it. Got wallets mixed up and started from a older chain which forked. Then I copied it and screwed up both wallets.
I opened up an older copy and it seems to be syncing now. 13h behind und closing in.

i too seem to have things on track after restoring blocks from sept.5

[Turrican]

Code:

IP 	                Time Connected 	                        Protocol Version 	         Last Send 	                         Last Receive 	                          
NL 80.56.92.208 	07:50:43 CEST, 13 September 2017 	70009 HoboNickels 1.5.5.4 	09:39:48 CEST, 13 September 2017 	09:36:51 CEST, 13 September 2017
CA 158.69.48.52 	07:58:36 CEST, 13 September 2017 	70008 HoboNickels 1.5.3.1 	09:40:24 CEST, 13 September 2017 	09:40:30 CEST, 13 September 2017
DE 144.76.138.145 	08:01:53 CEST, 13 September 2017 	70008 HoboNickels 1.5.3.1 	09:40:24 CEST, 13 September 2017 	09:40:24 CEST, 13 September 2017
SE 83.255.67.196 	08:47:56 CEST, 13 September 2017 	70009 HoboNickels 1.5.5.5 	09:38:16 CEST, 13 September 2017 	09:33:42 CEST, 13 September 2017

Pls Update to new Version