presstab (OP)
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
February 15, 2015, 07:25:40 PM |
|
I am getting lot of orphans i am on the new wallet
I think it is more common for orphans at current settings. We have time drift set at 60 seconds, and we also have hashing set to 60 seconds. This means that there is really no wiggle room at all. I might need to bump our hashing down to 30-50 seconds and see where the sweet spot is.
|
|
|
|
presstab (OP)
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
February 15, 2015, 07:30:46 PM |
|
Hello I sent HYP 1200 to the address of Poloniex offered me Hyperstake and has not reached me, the transaction is confirmed 1 hour, knows what is the problem? thx
Best to ask Poloniex in the troll box. Transactions are working there but when asked they said, "I am noticing the blocks are coming through a little slower now on HYP. Not much but, a little." thanks for the quick answer let the problem is poloniex, thought it could be HyperStack, I stay calmer, greetings The problem is not of Poliniex at the end, the problem is of Hyperstake at now. I still my money.I was sent the address where my transfer occurs , but my wallet is still empty. I contribute capture that link past 24 hours I still have the 1206 HYP in my wallet. http://hyp.cryptocoinexplorer.com/transaction?transaction=bdb82735e269cf51d12d22c849e3620a226b231253e72c49eca849256b3f5210aplication in windows --> http://www.casimages.es/i/150215063255290285.png.htmlthanks a lot 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.
|
|
|
|
almightyruler
Legendary
Offline
Activity: 2268
Merit: 1092
|
|
February 15, 2015, 07:41:39 PM |
|
For the config file, is the file name 'HyperStake.conf' (case sensitive, I assume)?
Thanks!
My config works fine with all lowercase. Should be fine on Windows, but for other OSs which are case sensitive, the source does specify "HyperStake.conf"
|
|
|
|
ulfie
Newbie
Offline
Activity: 31
Merit: 0
|
|
February 15, 2015, 07:42:39 PM |
|
For the config file, is the file name 'HyperStake.conf' (case sensitive, I assume)?
Thanks!
Unlike Windows, Linux is case sensitive. That is the correct filename on Linux, Nelldog.
|
|
|
|
presstab (OP)
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
February 15, 2015, 07:46:24 PM |
|
For the config file, is the file name 'HyperStake.conf' (case sensitive, I assume)?
Thanks!
Unlike Windows, Linux is case sensitive. That is the correct filename on Linux, Nelldog. Just confirmed this on linux. Thanks for the reminder guys.
|
|
|
|
David Latapie
|
|
February 16, 2015, 01:04:56 AM |
|
For the config file, is the file name 'HyperStake.conf' (case sensitive, I assume)?
Thanks!
My config works fine with all lowercase. Because you are on Windows. Unix (Mac and Linux) are case-sensitive I don't have conf file myself but the folder containing my wallet is .HyperStake, not .hyperstake
|
|
|
|
CiZ
Member
Offline
Activity: 81
Merit: 10
HyperStake Member
|
|
February 16, 2015, 04:09:26 AM |
|
|
.I'm CiZ my HyperStake Member.
|
|
|
mtwelve
Legendary
Offline
Activity: 1330
Merit: 1009
|
|
February 16, 2015, 04:37:02 AM |
|
when did the difficulty get so low?
|
|
|
|
presstab (OP)
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
February 16, 2015, 04:45:38 AM |
|
when did the difficulty get so low?
Good eye. CiZ I think you are on the wrong fork.
|
|
|
|
jk9694
|
|
February 16, 2015, 04:55:42 AM |
|
When did and how did the fork happen?
|
|
|
|
CiZ
Member
Offline
Activity: 81
Merit: 10
HyperStake Member
|
|
February 16, 2015, 04:56:04 AM |
|
when did the difficulty get so low?
Good eye. CiZ I think you are on the wrong fork. I'm stuck.. presstab, wrong fork ? tell me more please. How to do right fork ?
|
.I'm CiZ my HyperStake Member.
|
|
|
zodiac3011
|
|
February 16, 2015, 04:59:13 AM |
|
um....multipool closed ? aw man still got renting contract for 3days
|
|
|
|
CiZ
Member
Offline
Activity: 81
Merit: 10
HyperStake Member
|
|
February 16, 2015, 05:02:59 AM |
|
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 ?
|
.I'm CiZ my HyperStake Member.
|
|
|
mtwelve
Legendary
Offline
Activity: 1330
Merit: 1009
|
|
February 16, 2015, 05:41:22 AM |
|
when did the difficulty get so low?
Good eye. CiZ I think you are on the wrong fork. Been out of loop with HYP, what's the security fork all about?
|
|
|
|
presstab (OP)
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
February 16, 2015, 06:29:56 AM |
|
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 ? Download this version of the wallet https://github.com/hyperstake/HyperStake/releases/tag/v1.1and follow this: 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.
|
|
|
|
presstab (OP)
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
February 16, 2015, 06:33:30 AM |
|
Been out of loop with HYP, what's the security fork all about?
Discovered that timedrift parameter for PoS coins is much more exploitable than a traditional time warp attack. 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.
|
|
|
|
presstab (OP)
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
|
February 16, 2015, 06:43:02 AM |
|
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 strictincomingIf 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
|
|
|
|
CiZ
Member
Offline
Activity: 81
Merit: 10
HyperStake Member
|
|
February 16, 2015, 09:04:23 AM |
|
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 ? Download this version of the wallet https://github.com/hyperstake/HyperStake/releases/tag/v1.1and follow this: 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.
Thanks so much presstab ,I will to do from your instruction
|
.I'm CiZ my HyperStake Member.
|
|
|
CiZ
Member
Offline
Activity: 81
Merit: 10
HyperStake Member
|
|
February 16, 2015, 01:19:40 PM |
|
done!! but wallet it use very a lot of upload bandwidth.
|
.I'm CiZ my HyperStake Member.
|
|
|
chilly2k
Legendary
Offline
Activity: 1007
Merit: 1000
|
|
February 16, 2015, 01:26:59 PM |
|
done!! but wallet it use very a lot of upload bandwidth. Read back a page or 2. You can add connect statements to you HyperStake.conf file to force the client to only connect to known good clients. Also did you have to use the -loadblock=bootstrap.dat option when you reloaded the blockchain? I forgot to add that when I recovered and I think I ended up pulling everything from the network.
|
|
|
|
|