[HYP] HyperStake | Generous Reward Staking | Advanced Staking Controls & Wallet

[ryanb]

my new wallet keeps going out of sync

any ideas why is it doing that?

[presstab]

my new wallet keeps going out of sync

any ideas why is it doing that?

There are two competing forks at the moment. If you are running the new version, you should be on the correct fork.  Given enough time, the reorg settings will not look far enough back to find the other fork.

You can solve the problem temporarily by connecting to my server, and leaving it with only one connection for a few hours. I think this should get rid of the message. Personally, my QT wallet is not saying out of sync.

If you want to connect:
connect=104.131.135.232

[nioc]

I just staked a block while "out of sync" and am now synced.

[ryanb]

I just staked a block while "out of sync" and am now synced.

Mine also staked while out of sync

[mistercoin]

Is there seriously going to be a true hard-fork with a few hours notice? If so, you are looking at a major train wreck.

Have the services that use/support  Hyperstake been notified? I know I haven't, I only noticed it because it popped up in my reply post list.

Exchanges, explorers, gambling, etc etc?? All these services need time to get setup even after they are notified.

How many users are going to end up on a forked chain because they didn't happen to come to a forum where it has been announced in the last few hours?

Major exchanges have been notified, most of our services have been notified. You were on my list as well, just hadn't got there yet. Trying to do a lot of things at once here.

I was hoping that this was really going to be a soft fork until I saw this in the code currently in github:

Code:

 if (pfrom->nVersion < 72099)
{
printf("partner %s using an old client %d, disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->nVersion);
pfrom->fDisconnect = true;

I hope it is for testing purposes, and you are not intending to truly block out version 72000 from the new client (In  other words a true hard fork) in the next few hours or even days.

This has to be a misunderstanding on my part. When is the hard-fork actually going to be enforced?

This was for my own personal testing. This should be doable via softfork, but I am sure old clients will be likely to get off on their own forks if not updated. Its hard to say for sure. At first we were planning on going all out and getting our whole list of fork items crossed off the list. This is just too much now, and too quick in advanced. I will simply be changing the timedrift code to 60 seconds. No difficulty changes or other changes. Hope this answers your questions, I will get you the updated code as soon as I have it.

No matter how much work someone puts into something, time, effort, sweat and tears, there will always be some douchebag(s) that will try to undermine all of your work...

[ryanb]

my new wallet keeps going out of sync

any ideas why is it doing that?

There are two competing forks at the moment. If you are running the new version, you should be on the correct fork.  Given enough time, the reorg settings will not look far enough back to find the other fork.

You can solve the problem temporarily by connecting to my server, and leaving it with only one connection for a few hours. I think this should get rid of the message. Personally, my QT wallet is not saying out of sync.

If you want to connect:
connect=104.131.135.232

I am getting 0 connections, connecting to your server, i added the connect command to the conf file.

[presstab]

my new wallet keeps going out of sync

any ideas why is it doing that?

There are two competing forks at the moment. If you are running the new version, you should be on the correct fork.  Given enough time, the reorg settings will not look far enough back to find the other fork.

You can solve the problem temporarily by connecting to my server, and leaving it with only one connection for a few hours. I think this should get rid of the message. Personally, my QT wallet is not saying out of sync.

If you want to connect:
connect=104.131.135.232

I am getting 0 connections, connecting to your server, i added the connect command to the conf file.

Hmm it could be at full capacity now.

[ryanb]

my new wallet keeps going out of sync

any ideas why is it doing that?

There are two competing forks at the moment. If you are running the new version, you should be on the correct fork.  Given enough time, the reorg settings will not look far enough back to find the other fork.

You can solve the problem temporarily by connecting to my server, and leaving it with only one connection for a few hours. I think this should get rid of the message. Personally, my QT wallet is not saying out of sync.

If you want to connect:
connect=104.131.135.232

I am getting 0 connections, connecting to your server, i added the connect command to the conf file.

Hmm it could be at full capacity now.

I got 1 connection now and it is in sync

[dreamwatcher]

Is there seriously going to be a true hard-fork with a few hours notice? If so, you are looking at a major train wreck.

Have the services that use/support  Hyperstake been notified? I know I haven't, I only noticed it because it popped up in my reply post list.

Exchanges, explorers, gambling, etc etc?? All these services need time to get setup even after they are notified.

How many users are going to end up on a forked chain because they didn't happen to come to a forum where it has been announced in the last few hours?

Major exchanges have been notified, most of our services have been notified. You were on my list as well, just hadn't got there yet. Trying to do a lot of things at once here.

I was hoping that this was really going to be a soft fork until I saw this in the code currently in github:

Code:

 if (pfrom->nVersion < 72099)
{
printf("partner %s using an old client %d, disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->nVersion);
pfrom->fDisconnect = true;

I hope it is for testing purposes, and you are not intending to truly block out version 72000 from the new client (In  other words a true hard fork) in the next few hours or even days.

This has to be a misunderstanding on my part. When is the hard-fork actually going to be enforced?

This was for my own personal testing. This should be doable via softfork, but I am sure old clients will be likely to get off on their own forks if not updated. Its hard to say for sure. At first we were planning on going all out and getting our whole list of fork items crossed off the list. This is just too much now, and too quick in advanced. I will simply be changing the timedrift code to 60 seconds. No difficulty changes or other changes. Hope this answers your questions, I will get you the updated code as soon as I have it.

No matter how much work someone puts into something, time, effort, sweat and tears, there will always be some douchebag(s) that will try to undermine all of your work...

Excuse me??

It is obvious you do not know who I am, nor do you understand what is going on. The only "douchebag" I see here is yourself.

Next time try to comprehend what is going on and who it involves before you make incorrect statements and embarrass yourself.

[presstab]

Mac Binary has been built by billotronic and added to the release page

https://github.com/hyperstake/HyperStake/releases/tag/v1.1

[Hilux74]

Wish I looked at this thread before going to work...old wallet running away oblivious to whether it is on the fork or the spoon side of the equation.

[Biomech]

Is there seriously going to be a true hard-fork with a few hours notice? If so, you are looking at a major train wreck.

Have the services that use/support  Hyperstake been notified? I know I haven't, I only noticed it because it popped up in my reply post list.

Exchanges, explorers, gambling, etc etc?? All these services need time to get setup even after they are notified.

How many users are going to end up on a forked chain because they didn't happen to come to a forum where it has been announced in the last few hours?

Major exchanges have been notified, most of our services have been notified. You were on my list as well, just hadn't got there yet. Trying to do a lot of things at once here.

I was hoping that this was really going to be a soft fork until I saw this in the code currently in github:

Code:

 if (pfrom->nVersion < 72099)
{
printf("partner %s using an old client %d, disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->nVersion);
pfrom->fDisconnect = true;

I hope it is for testing purposes, and you are not intending to truly block out version 72000 from the new client (In  other words a true hard fork) in the next few hours or even days.

This has to be a misunderstanding on my part. When is the hard-fork actually going to be enforced?

This was for my own personal testing. This should be doable via softfork, but I am sure old clients will be likely to get off on their own forks if not updated. Its hard to say for sure. At first we were planning on going all out and getting our whole list of fork items crossed off the list. This is just too much now, and too quick in advanced. I will simply be changing the timedrift code to 60 seconds. No difficulty changes or other changes. Hope this answers your questions, I will get you the updated code as soon as I have it.

No matter how much work someone puts into something, time, effort, sweat and tears, there will always be some douchebag(s) that will try to undermine all of your work...

Excuse me??

It is obvious you do not know who I am, nor do you understand what is going on. The only "douchebag" I see here is yourself.

Next time try to comprehend what is going on and who it involves before you make incorrect statements and embarrass yourself.

I don't think it was aimed at you Just a general comment that if there is an exploit, some jackass will use it.

[ofeefee]

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.

[presstab]

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.

[chilly2k]

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. 

[presstab]

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]

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]

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.

[ShrykeZ]

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. 

[kePd8CT5]

BEWARE! Orphans Invasion!

Any ideas?

P.S. My local time - GMT +3