[HYP] HyperStake | Generous Reward Staking | Advanced Staking Controls & Wallet - page 176.

candlesticks

sr. member

Activity: 345

Merit: 250

Quote from: ikfrujdey on February 13, 2015, 10:50:04 PM

Something buggy version 1.1, after the launch of the purse and the first sync, then stops synchronizing, and so hanging the whole day. hyperstake.konf there.

After I updated, my wallet synced, then fell behind. I restarted it and it did the same thing. I checked what block I was on, and it was the same as the block explorer http://hyp.cryptocoinexplorer.com/ My wallet was still showing out of sync, I sent a small amount of coins to Poloniex, just to see what would happen. Coins arrived safely. A few hours later, I checked and my wallet no longer says out of sync.

Everything seems fine with my wallet, just took a few hours to connect to mostly good nodes I think.

ikfrujdey

full member

Activity: 168

Merit: 100

Something buggy version 1.1, after the launch of the purse and the first sync, then stops synchronizing, and so hanging the whole day. hyperstake.konf there.

infovortice2013

legendary

Activity: 1176

Merit: 1000

wow

, GOgogOGo

what must do i just see qt v1.1 fork, must update normal? or what to do?

i try this after update client

04:14:50

getblock hash 235999

04:14:50

Error: value is type int, expected bool

how to know if is running ok?
any tip?

ok i find integrated block explorer
at 235999 giveme this hash e165587140a5965f94cda6869abed770981207a946b4f2de17c8a053747a352e

what to do? with this repair??
Block Chain Bootstrap
Through block 235,000 - https://www.dropbox.com/s/d1zva60jizzoe3y/bootstrap.zip
Usage: extract bootstrap.dat into data directory (for Windows go to "run" and type in %appdata% and find HyperStake folder), remove blkindex.dat and blk0001.dat if they exist already and use the following from command line to start the bootstrap: HyperStake-qt.exe -loadblock=bootstrap.dat
Bootstrapping may take an hour or two depending on the machine, please be patient, the bootstrap happens from the splashscreen, and clicking on it while bootstrapping may cause it to quit.

mafort1469

sr. member

Activity: 364

Merit: 250

Quote from: Tranz on February 13, 2015, 09:54:15 PM

Quote from: mafort1469 on February 13, 2015, 09:48:16 PM

Quote from: Tranz on February 13, 2015, 08:46:01 PM

Presstab. I know you are crazy right now. Have you issued an alert to the clients? If not you should immediately issue a high priority alert.

Hey Tranz, I do believe he has contacted everyone.

Right I am sure he did, to the best he could. But there could be hundreds of nodes running HYP, and many are people who will remain anonymous.

Issuing an alert will reach every client that is running. And if someone comes back from holiday and starts up the client, the alert will pop up and let them know there is an issue.

Ah, sorry misread your post. Yes, this is true as diff is around 4 now. Lowest it has been in a very long time.

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: mafort1469 on February 13, 2015, 09:48:16 PM

Quote from: Tranz on February 13, 2015, 08:46:01 PM

Presstab. I know you are crazy right now. Have you issued an alert to the clients? If not you should immediately issue a high priority alert.

Hey Tranz, I do believe he has contacted everyone.

Right I am sure he did, to the best he could. But there could be hundreds of nodes running HYP, and many are people who will remain anonymous.

Issuing an alert will reach every client that is running. And if someone comes back from holiday and starts up the client, the alert will pop up and let them know there is an issue.

mafort1469

sr. member

Activity: 364

Merit: 250

Quote from: Tranz on February 13, 2015, 08:46:01 PM

Presstab. I know you are crazy right now. Have you issued an alert to the clients? If not you should immediately issue a high priority alert.

Hey Tranz, I do believe he has contacted everyone.

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Presstab. I know you are crazy right now. Have you issued an alert to the clients? If not you should immediately issue a high priority alert.

kePd8CT5

member

Activity: 88

Merit: 10

Quote from: Biomech on February 13, 2015, 06:46:51 PM

Never be sorry for that! Up the Irons!

Iron Maiden? West Ham United? Or both?

I think Maiden and WHU FC, of course!
~~Sorry~~, i am football fan too. He-he...

Biomech

legendary

Activity: 1372

Merit: 1022

Anarchy is not chaos.

Quote from: kePd8CT5 on February 13, 2015, 06:26:36 PM

Quote from: presstab on February 13, 2015, 06:16:28 PM

Perfect! Keep trying to stake. I am getting some orphans right now too. Remember that you don't lose anything if you have an orphan. Click on tools->repairwallet to clear your orphans.

Thanks. Keep thrashing and good luck! (Sorry, i am old school metalhead).

Never be sorry for that! Up the Irons!

kePd8CT5

member

Activity: 88

Merit: 10

Quote from: presstab on February 13, 2015, 06:16:28 PM

Perfect! Keep trying to stake. I am getting some orphans right now too. Remember that you don't lose anything if you have an orphan. Click on tools->repairwallet to clear your orphans.

Thanks. Keep thrashing and good luck! (Sorry, i am old school metalhead).

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: kePd8CT5 on February 13, 2015, 06:10:01 PM

What next?

Perfect! Keep trying to stake. I am getting some orphans right now too. Remember that you don't lose anything if you have an orphan. Click on tools->repairwallet to clear your orphans.

kePd8CT5

member

Activity: 88

Merit: 10

Quote from: presstab on February 13, 2015, 05:43:25 PM

...
Make sure you are on the correct fork. Can type in debug console "getblock hash 235999" it should match this: afe60dd0ab56ef529db21ea648ea4fd8de758a11b6a8ac1fa5cd2d4959162106
If it doesn't match you will need to restore to a backup of your chain or resync your client. I will update the bootstrap file on the OP right now.
...

What next?

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: kePd8CT5 on February 13, 2015, 05:24:42 PM

BEWARE! Orphans Invasion!

Any ideas?

P.S. My local time - GMT +3

Make sure you are on the correct fork. Can type in debug console "getblock hash 235999" it should match this: afe60dd0ab56ef529db21ea648ea4fd8de758a11b6a8ac1fa5cd2d4959162106

If it doesn't match you will need to restore to a backup of your chain or resync your client. I will update the bootstrap file on the OP right now.

kePd8CT5

member

Activity: 88

Merit: 10

+1

kePd8CT5

member

Activity: 88

Merit: 10

BEWARE! Orphans Invasion!

Any ideas?

P.S. My local time - GMT +3

ShrykeZ

hero member

Activity: 630

Merit: 500

Just want to say good work on figuring out the exploit / testing it and implementing a fix at a commendable speed. Good work Presstab + others. Grin

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: chilly2k on February 13, 2015, 03:47:47 PM

Quote from: presstab on February 13, 2015, 03:36:41 PM

Quote from: chilly2k on February 13, 2015, 03:25:48 PM

Quote from: presstab on February 13, 2015, 03:17:48 PM

Quote from: ofeefee on February 13, 2015, 02:00:29 PM

just checked mine, 13 blocks out of sync, setting connect, see what happens. I cannot tell looking at the peers which ones may be correct protocol or subver?

so connect synced it back up, so i changed connect to addnode, and turned my listen off. Expected this to connect to your peer and then pickup good clients, but it's showing 84 blocks remaining now, so must be connected to some other clients that are on wrong fork.

Will let it run for a bit, then try something else.

Protocol and sebver are the same right now. Just check to see if your height matches up to the block explorer hyp and you should be good. Eventually these other nodes on their alt fork will slow down and get behind the main chain.

What do you suggest if the height is not correct. The fork I'm on is almost 100 blocks ahead of the explorer.

I would make sure to have the correct client (v1.1). And restore to a backup of the chain if you have one. If not you might need to bootstrap from scratch.

I have the new client (V1.1). I got this after I thought I was on the wrong fork. No back up of the chain. (Is there an easy way to do this?) and last do you have a new bootstrap.dat?

I'd love to know how to make my own backup. I have problem with a few different clients, and making my own would be sweet. It isn't as simple as making a copy and renaming it?

Yeah you would just rename blk0001.dat to bootstrap.dat, but you would have to make sure you don't get up to the fork height.

chilly2k

legendary

Activity: 1007

Merit: 1000

Quote from: presstab on February 13, 2015, 03:36:41 PM

Quote from: chilly2k on February 13, 2015, 03:25:48 PM

Quote from: presstab on February 13, 2015, 03:17:48 PM

Quote from: ofeefee on February 13, 2015, 02:00:29 PM

just checked mine, 13 blocks out of sync, setting connect, see what happens. I cannot tell looking at the peers which ones may be correct protocol or subver?

so connect synced it back up, so i changed connect to addnode, and turned my listen off. Expected this to connect to your peer and then pickup good clients, but it's showing 84 blocks remaining now, so must be connected to some other clients that are on wrong fork.

Will let it run for a bit, then try something else.

Protocol and sebver are the same right now. Just check to see if your height matches up to the block explorer hyp and you should be good. Eventually these other nodes on their alt fork will slow down and get behind the main chain.

What do you suggest if the height is not correct. The fork I'm on is almost 100 blocks ahead of the explorer.

I would make sure to have the correct client (v1.1). And restore to a backup of the chain if you have one. If not you might need to bootstrap from scratch.

I have the new client (V1.1). I got this after I thought I was on the wrong fork. No back up of the chain. (Is there an easy way to do this?) and last do you have a new bootstrap.dat?

I'd love to know how to make my own backup. I have problem with a few different clients, and making my own would be sweet. It isn't as simple as making a copy and renaming it?

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: chilly2k on February 13, 2015, 03:25:48 PM

Quote from: presstab on February 13, 2015, 03:17:48 PM

Quote from: ofeefee on February 13, 2015, 02:00:29 PM

just checked mine, 13 blocks out of sync, setting connect, see what happens. I cannot tell looking at the peers which ones may be correct protocol or subver?

so connect synced it back up, so i changed connect to addnode, and turned my listen off. Expected this to connect to your peer and then pickup good clients, but it's showing 84 blocks remaining now, so must be connected to some other clients that are on wrong fork.

Will let it run for a bit, then try something else.

Protocol and sebver are the same right now. Just check to see if your height matches up to the block explorer hyp and you should be good. Eventually these other nodes on their alt fork will slow down and get behind the main chain.

What do you suggest if the height is not correct. The fork I'm on is almost 100 blocks ahead of the explorer.

I would make sure to have the correct client (v1.1). And restore to a backup of the chain if you have one. If not you might need to bootstrap from scratch.

chilly2k

legendary

Activity: 1007

Merit: 1000

Quote from: presstab on February 13, 2015, 03:17:48 PM

Quote from: ofeefee on February 13, 2015, 02:00:29 PM

just checked mine, 13 blocks out of sync, setting connect, see what happens. I cannot tell looking at the peers which ones may be correct protocol or subver?

so connect synced it back up, so i changed connect to addnode, and turned my listen off. Expected this to connect to your peer and then pickup good clients, but it's showing 84 blocks remaining now, so must be connected to some other clients that are on wrong fork.

Will let it run for a bit, then try something else.

Protocol and sebver are the same right now. Just check to see if your height matches up to the block explorer hyp and you should be good. Eventually these other nodes on their alt fork will slow down and get behind the main chain.

What do you suggest if the height is not correct. The fork I'm on is almost 100 blocks ahead of the explorer.

Topic: [HYP] HyperStake | Generous Reward Staking | Advanced Staking Controls & Wallet - page 176. (Read 679332 times)