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

I don't get this error. Anyone else?

I get "segmentation fault"  when I clicked repair wallet.

Press! In new wallet (1.1.0.1)  "-datadir=" switch not working. Please fix it.

Thanks.

Makes sense, thanks for explaining!

You could definitely just copy someone elses files (so long as they are the same bdb version, os, etc), but the problem is that you don't know if they are valid. You are trusting someone else.

A bootstrap gives you the entire blockchain, and then your client scans through the rules for the entire chain and indexes it. This is safe. The other way can work I have done it with a copy and paste of blkindex.dat blk0001.dat and database folder), but its not as safe.

Why does bootstrap.dat always have to be imported?
Can't someone just upload the blk*.dat  files and the client would just instantly use them and start finishing syncing online?

Just sick of always having to wait for this importing.   What is the reason for it?

Download the bootstrap.dat file from the first post. Place the extracted bootstrap.dat into the folder you just deleted everything from. Start your hyperstake.exe (the new version) and patiently wait for the bootstrap process and for your wallet to sync. If your wallet jumps out of bootstrap mode before it finishes (it should be taken through block 235k) then go back into the folder, name bootstrap.dat.old back to bootstrap.dat and then restart your wallet.

Good luck.

guys im i on the correct chain? how to check?

can you also teach me how to set the s4c?

{
"version" : "v1.1.0.0HyperStake-1.1-BETA",
"protocolversion" : 72000,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 238577,
"moneysupply" : 116822219.73411700,
"connections" : 13,
"proxy" : "",
"ip" : "183.171.163.15",
"difficulty" : 5.83926647,
"testnet" : false,
"keypoololdest" : 1423803388,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}

done!! but wallet it use very a lot of upload bandwidth. 

I have updated the github release page with a new build of the wallet. It contains new checkpoints and ups the protocol version to 72001 from 72000.

I added two rpc commands:
strictprotocol
strictincoming

If you are having trouble with high CPU and other peers trying to give you wrong chain data, or requesting data continuously the use "strictincoming true"

If you still have more problems, you can try strictprotocol. Please do not use this unless you absolutely have to. It will drop your peer count low, and doesn't connect you to the main pool of peers.

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

done!! but wallet it use very a lot of upload bandwidth. 

Download this version of the wallet https://github.com/hyperstake/HyperStake/releases/tag/v1.1

and follow this:

Been out of loop with HYP, what's the security fork all about?

Every coin has a setting "timedrift". It is meant to allow nodes that are for one reason or another a bit out of sync with the median time, to be able to submit blocks and still be fine.

For example peercoin allows a time drift of 2 hours, and same with NovaCoin. HoboNickels, BottleCaps, HyperStake are all 15 minute timedrift allowance.

So when you are attempting to stake and meet the staking target, you create 60 hashes at once per UTXO if you are using standard peercoin hashing code. The only thing that changes from hash to hash is the input for time. It hashes 60 seconds into the future at once. This system works pretty good, and doesn't really have much problem.

The problem is that when you get someone that tweaks the code, and says "why not hash 2 hours into the future" I will have 7,200 hashes to attempt to stake instead of 60 hashes".  So this code tweakers chance of staking is actually 11,900% more likely to hit a hash (did I do the math correctly? I think I did).

My original thinking, and the reason I released the beta release, was that if some code tweaker has that advantage, let us even the playing field and give it to everyone. And so I released that code.

What I failed to realize is that this would really screw up difficulty. Let's say the code tweaker above hashed two hours into the future, submitted the stake, and the network accepted it with no problems.  The next block would calculate difficulty by taking that 2 hour future stake and subtracting the last time before that, calculating the time to stake as 2 hours between the two blocks. The difficulty code thinks that this means that people are having trouble staking, and the diff drops.

With the new HYP code, we got diff as low as 3 i think it was (from the 10+ that it had been before), made 1,975 blocks today (compared to the target of 960), and minted 1.8 million HYP compared to our targeted 960k max.

Hope that makes some sense.  Running the new code on a test network and should have it out soon.

or need to do this ? ,aside from changing wallet software, it's need to delete all file in C:\Users\xxxxx\AppData\Roaming\HyperStake except "wallet.dat"
and run wallet again ? 

You are on the wrong fork I think. What you are going to want to do is to download the new version of the wallet. Go into your appdata folder (type %appdata% into windows run and go to hyperstake folder). Make a backup of wallet.dat and hyperstake.conf (if you have that) and put them in a safe place.

Now delete blk0001.dat blkindex.dat peers.dat and the database folder. Download the bootstrap.dat file from the first post. Place the extracted bootstrap.dat into the folder you just deleted everything from. Start your hyperstake.exe (the new version) and patiently wait for the bootstrap process and for your wallet to sync. If your wallet jumps out of bootstrap mode before it finishes (it should be taken through block 235k) then go back into the folder, name bootstrap.dat.old back to bootstrap.dat and then restart your wallet.

Good luck.