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

lightspeedy

jr. member

Activity: 109

Merit: 6

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!

Turrican

member

Activity: 227

Merit: 26

“BitCloud [BTDX]”

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

dnp

full member

Activity: 401

Merit: 110

Quote from: Tranz on September 11, 2017, 09:39:02 PM

Quote from: dnp on September 11, 2017, 08:21:35 PM

Quote from: Tranz on September 11, 2017, 07:14:55 PM

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 Sad

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?

Quote

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: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)

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: dnp on September 11, 2017, 08:21:35 PM

Quote from: Tranz on September 11, 2017, 07:14:55 PM

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 Sad

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?

Quote

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

full member

Activity: 401

Merit: 110

Quote from: Tranz on September 11, 2017, 07:14:55 PM

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 Sad

too busy with other stuff to look deeper.
current block 5656212 at timestamp 1505178634 (Sep 11 21:10:34 EDT)

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

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?

versprichnix

sr. member

Activity: 876

Merit: 291

Quote from: mayfun on September 11, 2017, 01:21:33 AM

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.

mayfun

jr. member

Activity: 57

Merit: 10

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

sr. member

Activity: 876

Merit: 291

Quote from: Tranz on September 10, 2017, 05:42:32 PM

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

Quote

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?

CoinEraser

legendary

Activity: 1988

Merit: 1768

Quote from: Tranz on September 10, 2017, 12:15:41 AM

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 Wink

vancefox

legendary

Activity: 1033

Merit: 1005

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

PeterTheGrape

sr. member

Activity: 462

Merit: 250

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

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: HCLivess on September 10, 2017, 03:25:51 PM

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:

Quote

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..

johnnarmst

newbie

Activity: 90

Merit: 0

Perfect site for trading online for both newbies and well experienced traders.

HCLivess

legendary

Activity: 2114

Merit: 1090

=== NODE IS OK! ==

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

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: lightspeedy on September 10, 2017, 08:32:12 AM

Quote from: Tranz on September 10, 2017, 07:35:09 AM

Quote from: Zels on September 10, 2017, 05:53:40 AM

Update from 1.5.3 to 2.0: Error loading blockchain even if I was on the good one, but after redowloading your, it's fine now

About the stake age set to 1 day, it's for new coin generated after update only ?

No all coins, but doesn't effect until after the block 5667000 .

Best hash right now:
SetBestChain: new best=ef68f741ec495654d34e height=5652466 trust=87692314699589 blocktrust=19509069 date=09/10/17 12:34:29

Thanks for all your hard work, Tranz! Cool

Updated the Client from v1.5.5.5 > v2.0.0 an everything went smooth.
At the time writing my client is connected to 5 v2.0.0 clients already. Total connected peers are 23 with < v2.00

Current PoS Difficulty: 0.00468566
Current PoS Netweight: 936376

I had recently lot of orphans, but i guess this had to do with the chain issues.

I am sending out alerts this morning, so that should get more people on the right version.

Orphans should be much lower after the changes take effect.

In the mean time you can try to stop client, remove or rename peers.dat and add 1 or 2 peers you know are good.. Don't have to do it, but it may help.

lightspeedy

jr. member

Activity: 109

Merit: 6

Quote from: Tranz on September 10, 2017, 07:35:09 AM

Quote from: Zels on September 10, 2017, 05:53:40 AM

Update from 1.5.3 to 2.0: Error loading blockchain even if I was on the good one, but after redowloading your, it's fine now

About the stake age set to 1 day, it's for new coin generated after update only ?

No all coins, but doesn't effect until after the block 5667000 .

Best hash right now:
SetBestChain: new best=ef68f741ec495654d34e height=5652466 trust=87692314699589 blocktrust=19509069 date=09/10/17 12:34:29

Thanks for all your hard work, Tranz! Cool

Updated the Client from v1.5.5.5 > v2.0.0 an everything went smooth.
At the time writing my client is connected to 5 v2.0.0 clients already. Total connected peers are 23 with < v2.00

Current PoS Difficulty: 0.00468566
Current PoS Netweight: 936376

I had recently lot of orphans, but i guess this had to do with the chain issues.

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: Zels on September 10, 2017, 05:53:40 AM

Update from 1.5.3 to 2.0: Error loading blockchain even if I was on the good one, but after redowloading your, it's fine now

About the stake age set to 1 day, it's for new coin generated after update only ?

No all coins, but doesn't effect until after the block 5667000 .

Best hash right now:
SetBestChain: new best=ef68f741ec495654d34e height=5652466 trust=87692314699589 blocktrust=19509069 date=09/10/17 12:34:29

Zels

full member

Activity: 203

Merit: 100

Update from 1.5.3 to 2.0: Error loading blockchain even if I was on the good one, but after redowloading your, it's fine now

About the stake age set to 1 day, it's for new coin generated after update only ?

2xjO9M3P

full member

Activity: 147

Merit: 100

Code:

master@miranda:~$ hobonickelsd getinfo
{
"version" : "v2.0.0.0-g-V2.0",
"protocolversion" : 70010,
"blocks" : 5651145,

So far so good.

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