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

Yeah, I need plenty to test code with myself, and plenty to distribute out to others. No point in having a PoW war to get testnet coins that are meant for development purposes.

All fixed! The repair process caused the program to crash several times. Each time the program restarted, there was more restored to my balance. No more orphans! Thanks for your help!

daFaq??? Really?? Wow.

Got testnet up and running for HYP. As you can see in the code, it came complete with a premine scam

PM me if you want some coins to mess around with, don't post your testnet address here please.

Here is a windows binary - https://github.com/hyperstake/HyperStake/releases/download/v1.1/HyperStake-qt-v1.1.0.2-withtestnet-windows.zip

To connect use: HyperStake-qt.exe -testnet -addnode=192.241.233.70
PoW is active for testnet, so go ahead and use "setgenerate true" in the debug console.

no problemo. IF that does not sort you out, jump on to irc so we can help you better.

Will be sending a tweet out soon too

Will do! Thanks!

backup your wallet.dat then Tools -> Repair wallet

Thanks for your hard work dreamwatcher. I am not entirely sure what would be causing this from the HYP side of the code, but will continue to investigate.

BTW the explorer has run very well since the fork, many of our peers checking it frequently. Thanks for providing us this great utility.

In regards to hyp.cryptocoinexplorer.com :

Lately on a few occasions the explorer would get "stuck".

Occasionally the HyperStake daemon will not respond to a database loader RPC call. The daemon does not return an error, just completely ignores the request.

In the past this has not been an issue as the loader was using the Python library "requests" to handle RPC calls. This library has an auto-timeout feature that would resend the RPC call if not answered in a certain period of time.

The latest version of requests somehow entirely breaks the RPC request code in CCE 3.5. I needed to revert the RPC request code to an much earlier version which uses the Urllib python libraries instead. These libraries do not have the same error and timeout handling that requests has. When the HyperStake daemon ignores an RPC request, the loader will sit there and wait for an answer hence getting stuck.

I was hoping I would not have to patch 3.5 and instead address the requests issue in 4.0, but as 4.0 is still in development,  I have patched 3.5.

Due to some of the changes over the last few versions of requests   , I need to limit the patched 3.5 and the future 4.0 to a certain version of Linux server.

This morning, I switched the HyperStake explorer to its new server with the patched 3.5 code.

This should solve the hung explorer issue.

Thank you for your patience

Thanks for your good work mtwelve!! Adding to the OP.

Well, my balance is about 50% of what it was late last week.
I must have gotten off on the wrong fork. Easy come, easy go.

@Presstab, that was a very nice explanation you put forth in that article.

It was fun presstab

http://bitcoinist.net/interview-presstab-pos-vulnerabilities/

all this , thanks to the ass that stake 2 hours ahead , get in line, wait like the rest of us

You could have definitely staked a lot of coins while on the wrong fork. Anything you would have minted after 2/13/15 would not have carried over. You can double check the block explorer to make sure that your address contains the correct amount.

I have the same issue with the download, ended up with less then half of what I accumulated prior to it. This is not good. Were we on the wrong chain to begin with? 

Today I downloaded bootstrap and before that I had around 300,000 Hyp. After I downloaded and I resync bootstrap wallet, I just 246,567 Hyp. So I had to do this operation staking thousands daily. On 16 February I received about 20,000 Hyp, but now after resync. last day of minting in wallet appears to be on 13. Can you explain me why this happens? Sorry for my poor english.

My first clue that something was amiss this morning was when the network weight was less than 50,000 and a bunch of stuff wanted to stake rapidly.

I´m glad that I dug through the forums and learned about the hard-fork. 

I started doing this when I realized that I had copied my backup wallet.dat into the wrong folder so I really had never repaired my wallet. It is all fixed now, and I was able to send.

Thanks for the help.

Hmm well this is getting more complicated real fast isn't it? You could try in the debug window "rescanfromblock 230000" that might help, but I am guessing not. The fail safe way to sync your wallet exactly with the blockchain is to reimport your privkey to a new wallet. Make sure your wallet is backed up, go to debug window and type "dumpprivkey yourHYPaddresshere" and copy your private key. Make sure never to share this with anyone else, or else your coins could be stolen.

Shut down your wallet. Go back to the appdata folder and name wallet.dat to walletold.dat.

Restart your client. You should have a fresh wallet with no balance. Go to debug, "importprivkey yourprivkeyhere". This will scan the entire chain for your key, and this could take a few minutes. After that, restart your wallet one more time and everything should be good to go.

repairwallet is supposed to prevent this procedure from being done, but looks like it couldn't fix it in your case.