Topic: [HYP] HyperStake | Generous Reward Staking | Advanced Staking Controls & Wallet - page 299. (Read 679335 times)
October 02, 2014, 09:58:59 AM
i don't know how many total coin of hyperstake..
October 02, 2014, 09:41:10 AM
A little tip for HYPsters. When you backup the wallet.dat file to a cloud storage and then stake for a long time not bothering about change addresses, you can lose part of your money after restoring from your backup. There are 100 pregenerated keys in client's keypool. Every new address used for change is taken from there. When all 100 addresses are used, new ones are generated, but your backup doesn't have them. To avoid it, backup your wallet.dat regularly and do not use excessive number of addresses. You can also start your wallet with this command /path/to/wallet-qt -keypool=1000, or add this line in the HyperStake.conf file: keypool=1000. If the wallet is encrypted, additional keys will not be created until the wallet is unlocked. To check your keypool size, use "getinfo" console command.
so the solutions is..generate new address and then back up again,is like that?
Yes, preferably, if you have money on this address or plan to use it in future. New addresses for change are used when you do not set your initial address as a custom change address. So every time you split your block, you can have new address used. Do it 100 times without custom change address, and your backup will be outdated. Just try to backup on a regular basis and enlarge your keypool size, and everything will be OK
Two ways to combat this. First is that we can change the code to store a keypool of 500 or so addresses, HBN has done this, and it has hardly any memory implications. This will allow the average user much more room. Second, the user should concentrate on consolidating any change addresses back to their main address, to minimize the risk of not having a properly backed up wallet. My own wallet has 2,000+ transactions and I only have a few blocks in change.
And concerning David's dismissal, the code change suggested was that S4C uses custom change address. This does not mean that a user has to use this, or that a user will use it for normal transactions. It is definitely something that should be kept track of. Thanks for reminding us all iantunc!
October 02, 2014, 09:31:19 AM
Expected time to earn reward 2589 days... I waited 9 Days for this. Kind of anti climax 
What is your block size and the wallet version?
v1.0.5.0HyperStake-1.0.5 and how to discover block size?
Please install Version 1.0.6 wallet. This issue was resolved.
After that enable coin control:
Tools -> Options -> Display -> Display coin control features
Then go to SEND and click Coin control. There will be a column with the block(s') size(s).
October 02, 2014, 09:22:49 AM
Expected time to earn reward 2589 days... I waited 9 Days for this. Kind of anti climax
What is your block size and the wallet version?
v1.0.5.0HyperStake-1.0.5 and how to discover block size?
October 02, 2014, 09:21:11 AM
Expected time to earn reward 2589 days... I waited 9 Days for this. Kind of anti climax
What is your block size and the wallet version?
October 02, 2014, 09:16:54 AM
Expected time to earn reward 2589 days... I waited 9 Days for this. Kind of anti climax
October 02, 2014, 08:59:29 AM
A little tip for HYPsters. When you backup the wallet.dat file to a cloud storage and then stake for a long time not bothering about change addresses, you can lose part of your money after restoring from your backup. There are 100 pregenerated keys in client's keypool. Every new address used for change is taken from there. When all 100 addresses are used, new ones are generated, but your backup doesn't have them. To avoid it, backup your wallet.dat regularly and do not use excessive number of addresses. You can also start your wallet with this command /path/to/wallet-qt -keypool=1000, or add this line in the HyperStake.conf file: keypool=1000. If the wallet is encrypted, additional keys will not be created until the wallet is unlocked. To check your keypool size, use "getinfo" console command.
so the solutions is..generate new address and then back up again,is like that?
Yes, preferably, if you have money on this address or plan to use it in future. New addresses for change are used when you do not set your initial address as a custom change address. So every time you split your block, you can have new address used. Do it 100 times without custom change address, and your backup will be outdated. Just try to backup on a regular basis and enlarge your keypool size, and everything will be OK
October 02, 2014, 08:45:30 AM
A little tip for HYPsters. When you backup the wallet.dat file to a cloud storage and then stake for a long time not bothering about change addresses, you can lose part of your money after restoring from your backup. There are 100 pregenerated keys in client's keypool. Every new address used for change is taken from there. When all 100 addresses are used, new ones are generated, but your backup doesn't have them. To avoid it, backup your wallet.dat regularly and do not use excessive number of addresses. You can also start your wallet with this command /path/to/wallet-qt -keypool=1000, or add this line in the HyperStake.conf file: keypool=1000. If the wallet is encrypted, additional keys will not be created until the wallet is unlocked. To check your keypool size, use "getinfo" console command.
so the solutions is..generate new address and then back up again,is like that?
October 02, 2014, 08:12:52 AM
if you ever heard ''Lets your money work for you
and then with Hyperstake: Lets your coin work for you
and then with Hyperstake: Lets your coin work for you
October 02, 2014, 04:48:32 AM
A little tip for HYPsters. When you backup the wallet.dat file to a cloud storage and then stake for a long time not bothering about change addresses, you can lose part of your money after restoring from your backup. There are 100 pregenerated keys in client's keypool. Every new address used for change is taken from there. When all 100 addresses are used, new ones are generated, but your backup doesn't have them. To avoid it, backup your wallet.dat regularly and do not use excessive number of addresses. You can also start your wallet with this command /path/to/wallet-qt -keypool=1000, or add this line in the HyperStake.conf file: keypool=1000. If the wallet is encrypted, additional keys will not be created until the wallet is unlocked. To check your keypool size, use "getinfo" console command.
With the new code that doesn't need change address, this issue should be alleviated.Presstab, is there a way to split up the stake for charity so that if you select 50%, 25% can go to one address and the other 25% to another?
Not at the moment, right now the code has the ability for this to be added and it is something that will be in a future release. The next release for the wallet will focus on adding custom change address to S4C so that you can keep all your coins under one address with S4C instead of them automatically being sent to new change addresses. Tranz from HBN has made huge progress on this.
Following up, my big block did stake finally. Not sure why it staked dead last over smaller, less mature blocks, but it did. As you said, the process is random 
It was way over max, so I hit the cap. Which I can now report works
Mine is still stuck. And I still get new block to mint several time per day It was way over max, so I hit the cap. Which I can now report works 
October 02, 2014, 03:58:15 AM
A little tip for HYPsters. When you backup the wallet.dat file to a cloud storage and then stake for a long time not bothering about change addresses, you can lose part of your money after restoring from your backup. There are 100 pregenerated keys in client's keypool. Every new address used for change is taken from there. When all 100 addresses are used, new ones are generated, but your backup doesn't have them. To avoid it, backup your wallet.dat regularly and do not use excessive number of addresses. You can also start your wallet with this command /path/to/wallet-qt -keypool=1000, or add this line in the HyperStake.conf file: keypool=1000. If the wallet is encrypted, additional keys will not be created until the wallet is unlocked. To check your keypool size, use "getinfo" console command.
October 02, 2014, 01:17:45 AM
keep hold guys,..i'm start promoting HYP in fb 
good idea,sir 
October 01, 2014, 08:24:23 PM
keep hold guys,..i'm start promoting HYP in fb
October 01, 2014, 07:00:49 PM
Presstab, is there a way to split up the stake for charity so that if you select 50%, 25% can go to one address and the other 25% to another?
Not at the moment, right now the code has the ability for this to be added and it is something that will be in a future release. The next release for the wallet will focus on adding custom change address to S4C so that you can keep all your coins under one address with S4C instead of them automatically being sent to new change addresses. Tranz from HBN has made huge progress on this.
That sounds great! Thanks
October 01, 2014, 06:44:24 PM
Following up, my big block did stake finally. Not sure why it staked dead last over smaller, less mature blocks, but it did. As you said, the process is random It was way over max, so I hit the cap. Which I can now report works
It was way over max, so I hit the cap. Which I can now report works October 01, 2014, 06:35:22 PM
Presstab, is there a way to split up the stake for charity so that if you select 50%, 25% can go to one address and the other 25% to another?
Not at the moment, right now the code has the ability for this to be added and it is something that will be in a future release. The next release for the wallet will focus on adding custom change address to S4C so that you can keep all your coins under one address with S4C instead of them automatically being sent to new change addresses. Tranz from HBN has made huge progress on this.
October 01, 2014, 06:17:56 PM
Presstab, is there a way to split up the stake for charity so that if you select 50%, 25% can go to one address and the other 25% to another?
October 01, 2014, 05:32:00 PM
HYP's performance compared to other PoS coins https://bitcointalksearch.org/topic/m.9047596
October 01, 2014, 02:18:46 PM
good update to stay safe minting
October 01, 2014, 02:05:00 PM
Here is a beta release of the wallet. It adds some new code to allow the client to sync past 21000 and 21500 without restarting. This also adds full Unlock For Mint functionality.
Please report any bugs with syncing or unlock for mint.
https://github.com/presstab/HyperStake/releases/tag/v1.0.6.5
Please report any bugs with syncing or unlock for mint.
https://github.com/presstab/HyperStake/releases/tag/v1.0.6.5
Jump to: