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

[nioc]

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

I had the same problem, I was using 2>4 Mbps

presstab posted the following after responding to you.  I downloaded it and set "strictincoming true"
that was almost an hour ago and I'm up to 15 peers and bandwith is negligible, CPU usage is also very small

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

[m33]

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" : ""
}

[presstab]

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" : ""
}

Yep that is correct chain. S4C was replaced by multisend. Here is a link with quick overview http://hyperstake.wikia.com/wiki/Multisend

[presstab]

At the advice of Sr. Otronic, I purchase this little beauty last week Cost my about $80 after getting all the parts I wanted, heat sync, case, cables, etc.  I didn't fork up the extra cash for the eMMc *yet*, and am running a normal sdcard.

http://www.hardkernel.com/main/products/prdt_info.php?g_code=G141578608433


I just got it fully synced and got my first stake with it

I am running the daemon. It takes about 5% of my CPU and 17% of memory. The CPU bumps up near 100% for about one second once every 30 seconds or so when it produces a new round of PoS hashes (without the liteStake code it would have been near 100% all the time I would guess).

I was able to compile fairly easily. I used:

Code:

./autogen.sh
./configure --with-gui=no --with-incompatible-bdb
make

Takes about 30 minutes to compile. The bootstrap takes a few hours to complete as well.

Here is a pic with coffee cup for scale. Notice that the odroid is smaller than my WDTV.

[rocoro]

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.

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?

[presstab]

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.

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?

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.

[rocoro]

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.

Makes sense, thanks for explaining!

[presstab]

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.

Makes sense, thanks for explaining!

Also you could always just rename your own blk0001.dat to bootstrap.dat, and just make sure you pop out of bootstrap mode before the fork.

[kePd8CT5]

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

Thanks.

[presstab]

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

Thanks.

Working on it now.

[rocoro]

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

[presstab]

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

I don't get this error. Anyone else?

[rocoro]

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

I don't get this error. Anyone else?

Additional note:
client crashed with the seg fault,  but upon restarting,  the wallet was repaired..

[soulistyce]

whats going on dificulty is sky high double then yesterday 14.13

[presstab]

whats going on dificulty is sky high double then yesterday 14.13

I haven't had my wallet running consistently post-fork. Lots of rebuilds, and not leaving it on overnight. Its now 24/7. That definitely adds some. Also more peers making their way over to the correct chain. Being on the wrong chain lowers our diff because less competition. Once they get to the correct chain, they have even more weight than they would have had since they have been essentially offline for a few days.

This is my guess at least. Before the fork we were in the 10-17 range depending on the moment.

[presstab]

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

Thanks.

Allejupa worked hard to get the code working today. I have updated the release page with a new build.

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

[kePd8CT5]

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

Thanks.

Allejupa worked hard to get the code working today. I have updated the release page with a new build.
https://github.com/hyperstake/HyperStake/releases/tag/v1.1

Tested. Working well.

Thanks, Press & Co!

[m33]

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

Thanks.

Allejupa worked hard to get the code working today. I have updated the release page with a new build.

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

whats this resync again?

[presstab]

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

Thanks.

Allejupa worked hard to get the code working today. I have updated the release page with a new build.

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

whats this resync again?

Try this

https://bitcointalk.org/index.php?topic=678849.msg10475602#msg10475602

[ZACHM]

Yesterday I sent 73k+ HYP to Poloniex and it still has not shown up there. I asked on Poloniex and they told me make sure I was using the newest wallet (I am v1.1.0.1) and check the blockchain and transaction. At the time my wallet was telling me the transaction was in block 239010 and the most recent block on hyp.cryptocoinexplorer.com was about 23880, so I decided to wait to see if when it got to 239010 then maybe Poloniex's wallets would sync and the transaction would show up, but nope.

Also if I search for my TXID on hyp.cryptocoinexplorer.com it says it is not found.

What do I need to do? Is my HYP gone?



And now my wallet won't sync, it says there is 5 connections to network but is sitting at 112 blocks behind.

I have made backups and downloaded the bootstrap and have started resyncing, hopefully that helps something.