Author

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

legendary
Activity: 1330
Merit: 1000
Blockchain Developer
Is HyperStake Version 1.0.7.2  a mandatory update? 

I'm still on 1.0.6  is that ok yet?
Not mandatory but you should upgrade. 1.0.6 is good, though (contrary to 1.0.6.5 or 1.0.7.1). If you don't upgrade, you just don't get some new features.

Yep, 1.0.6 is a really solid build. If you are happy with it and don't want all the new bells and whistles, then keep it  Smiley
hero member
Activity: 658
Merit: 503
Monero Core Team
Is HyperStake Version 1.0.7.2  a mandatory update? 

I'm still on 1.0.6  is that ok yet?
Not mandatory but you should upgrade. 1.0.6 is good, though (contrary to 1.0.6.5 or 1.0.7.1). If you don't upgrade, you just don't get some new features.
legendary
Activity: 938
Merit: 1000
Is Version 1.0.7.2  a mandatory update?  

I'm still on 1.0.6  is that ok yet?

hero member
Activity: 658
Merit: 503
Monero Core Team
Right now, the entry price for HYP is extremely well priced for new people looking to enter the market. For those of you looking at HYP for the first time, consider taking up a small stake now, it will be worthwhile I'm sure.
Amusing: this is exactly what BaconPumpSlicer wrote on trollbox:
Quote
BaconPumpSlicer: davidlatapie, I find out about HYP, I find the price ridiculously perfect for embark on the adventure
sr. member
Activity: 420
Merit: 250
Hi David

Thanks for introducing Project Giveaway.

First of all, I want people to know my main objective for the Giveaways will be to spread the word about HyperStake and gain a wider audience.
As such, like David says, there'll be giveaways on Polo, IRC, like we've been used to - but I'm also going to start focusing on other exchange trollboxes, social media, etc. This will make others sit up and notice HyperStake who are currently outside of our current circle.

I also have plans to incentivise action. But more about that later.

Right now, the entry price for HYP is extremely well priced for new people looking to enter the market. For those of you looking at HYP for the first time, consider taking up a small stake now, it will be worthwhile I'm sure.



Two days ago on IRC, I started Project Giveaway. Objective: to create a self-sufficient giveaway address to increase the visibility and interest for HYP. Once, the idea came from cycoinminer, who is also the originator of the HyperLoan idea. Hat tip to yoy, cycoinminer!

This is how Project Giveaway will work:
If we reach 50,000 HYP, cycoinminer will give away 25 bunches of 25 HYP every Tuesday, Thursday or Saturday. On Poloniex trollbox, Cryptsy trollbox on anywhere else.
If we reach 100,000 HYP, either the number of giveaways or the amount of them will double. At 200,000 HYP, it wil double again. Beyond this, donations shall better be spent elsewhere, like HyperSanta.

Calculations are as follow:
25 HYP per giveaway, 25 giveaway a day, three days in the week, two weeks (period for staking) = 25*25*3*2 = 3,750
To achieve self-sufficiency (endowment approach), we assume principal must be ten times bigger so 37,500
Finally, the first two weeks, there won't be any stake, so we'll have to provide an extra 7,500
Total is 37,500+7,500 = 45,000 HYP
50K HYP is a round enough number and gives some extra for security.

At the time of writing and after only two days, we already got 47466.179688 HYP (and growing)!
cycoinminer, I believe tomorrow you'll be able to start giveaways Smiley
Polo trollbox, Cryptsy trollbox, reddit, elsewhere... Let the HYP begin... again!
legendary
Activity: 2114
Merit: 1023
Oikos.cash | Decentralized Finance on Tron
Two days ago on IRC, I started Project Giveaway. Objective: to create a self-sufficient giveaway address to increase the visibility and interest for HYP. Once, the idea came from cycoinminer, who is also the originator of the HyperLoan idea. Hat tip to yoy, cycoinminer!

This is how Project Giveaway will work:
If we reach 50,000 HYP, cycoinminer will give away 25 bunches of 25 HYP every Tuesday, Thursday or Saturday. On Poloniex trollbox, Cryptsy trollbox on anywhere else.
If we reach 100,000 HYP, either the number of giveaways or the amount of them will double. At 200,000 HYP, it wil double again. Beyond this, donations shall better be spent elsewhere, like HyperSanta.

Calculations are as follow:
25 HYP per giveaway, 25 giveaway a day, three days in the week, two weeks (period for staking) = 25*25*3*2 = 3,750
To achieve self-sufficiency (endowment approach), we assume principal must be ten times bigger so 37,500
Finally, the first two weeks, there won't be any stake, so we'll have to provide an extra 7,500
Total is 37,500+7,500 = 45,000 HYP
50K HYP is a round enough number and gives some extra for security.

At the time of writing and after only two days, we already got 47466.179688 HYP (and growing)!
cycoinminer, I believe tomorrow you'll be able to start giveaways Smiley
Polo trollbox, Cryptsy trollbox, reddit, elsewhere... Let the HYP begin... again!

WOW this is excellent news..  I am holding all my HYP..
legendary
Activity: 1372
Merit: 1022
Anarchy is not chaos.
Two days ago on IRC, I started Project Giveaway. Objective: to create a self-sufficient giveaway address to increase the visibility and interest for HYP. Once, the idea came from cycoinminer, who is also the originator of the HyperLoan idea. Hat tip to yoy, cycoinminer!

This is how Project Giveaway will work:
If we reach 50,000 HYP, cycoinminer will give away 25 bunches of 25 HYP every Tuesday, Thursday or Saturday. On Poloniex trollbox, Cryptsy trollbox on anywhere else.
If we reach 100,000 HYP, either the number of giveaways or the amount of them will double. At 200,000 HYP, it wil double again. Beyond this, donations shall better be spent elsewhere, like HyperSanta.

Calculations are as follow:
25 HYP per giveaway, 25 giveaway a day, three days in the week, two weeks (period for staking) = 25*25*3*2 = 3,750
To achieve self-sufficiency (endowment approach), we assume principal must be ten times bigger so 37,500
Finally, the first two weeks, there won't be any stake, so we'll have to provide an extra 7,500
Total is 37,500+7,500 = 45,000 HYP
50K HYP is a round enough number and gives some extra for security.

At the time of writing and after only two days, we already got 47466.179688 HYP (and growing)!
cycoinminer, I believe tomorrow you'll be able to start giveaways Smiley
Polo trollbox, Cryptsy trollbox, reddit, elsewhere... Let the HYP begin... again!

Very nice!

This also is a good program to illustrate the benefits of staking coins vs. proof of work. Both have their merits, but Staking coins are ideal for this sort of thing.
hero member
Activity: 658
Merit: 503
Monero Core Team
Two days ago on IRC, I started Project Giveaway. Objective: to create a self-sufficient giveaway address to increase the visibility and interest for HYP. Once, the idea came from cycoinminer, who is also the originator of the HyperLoan idea. Hat tip to yoy, cycoinminer!

This is how Project Giveaway will work:
If we reach 50,000 HYP, cycoinminer will give away 25 bunches of 25 HYP every Tuesday, Thursday or Saturday. On Poloniex trollbox, Cryptsy trollbox on anywhere else.
If we reach 100,000 HYP, either the number of giveaways or the amount of them will double. At 200,000 HYP, it wil double again. Beyond this, donations shall better be spent elsewhere, like HyperSanta.

Calculations are as follow:
25 HYP per giveaway, 25 giveaway a day, three days in the week, two weeks (period for staking) = 25*25*3*2 = 3,750
To achieve self-sufficiency (endowment approach), we assume principal must be ten times bigger so 37,500
Finally, the first two weeks, there won't be any stake, so we'll have to provide an extra 7,500
Total is 37,500+7,500 = 45,000 HYP
50K HYP is a round enough number and gives some extra for security.

At the time of writing and after only two days, we already got 47466.179688 HYP (and growing)!
cycoinminer, I believe tomorrow you'll be able to start giveaways Smiley
Polo trollbox, Cryptsy trollbox, reddit, elsewhere... Let the HYP begin... again!
hero member
Activity: 595
Merit: 500
Ok I am throwing out the updated release today. I was hoping to fix some of the painful syncing problems that lead to syncing requiring the wallet to be restarted a few times, but still don't have the bugs worked out all the way.

HyperStake Version 1.0.7.2

- Adjust the stake predictions to be more accurate
- Fix DNS seeding, this means that you should be able to fire up a brand new client and not have to add any nodes
- setstakesplitthreshold RPC call - this is an important change. By default your wallet will only split your stake if it results in each block being larger than 1,000 HYP, so you would need a total value of larger than 2k for them to split by default. You can adjust this 1k HYP threshold to be whatever you want using this RPC call.  It will need to be set everytime you open your wallet, or else it will go back to default. Consider this feature in beta stage. I confirm it works on my wallet.
- reduced nLimit to 1,000 blocks at a time so that limited RAM systems don't get memory errors as easy
- adjust max connections to 25 peers
- fix some bugs with the block splitter

https://github.com/presstab/HyperStake/releases/tag/v1.0.7.2

Please bootstrap for the fastest sync (if you are syncing from scratch). Bootstrap details can be found here: https://bitcointalksearch.org/topic/m.7695751

Enjoy! And as always, don't be hesitant to report errors, I can't fix them if I don't know about them! HyperStake is not perfect, but each release gets us one step closer  Wink
Nothing but good news at this end.
I did set a custom stakesplit threshold, so I will need to wait till the next stakes to see if it does what I expect. I just had 4 blocks stake in the past day, including a large block that was maxed out to 1000 rewards since a couple days, due to the high diff. I am happy to see the diff down from above 2 to 1 now, probably also the reason that I saw so much staking activity.
I also tested the splitblock function and not only did it work exactly as promised (split a large input into two almost equal size outputs as I had set the nr to 2) but I also noticed that the output lo longer was 0.00026 HYP lower, but only the specified 0.00001 HYP.
Earlier version wallets were "stealing dust" of 0.00025 HYP with every transaction ;-)
For me that added up to 0.014 HYP difference between my wallet balance and the explorer's view of my address.
legendary
Activity: 1078
Merit: 1011
Yes, Thank You!! Much Appreciated!! Smiley
legendary
Activity: 1330
Merit: 1000
Blockchain Developer

Mac OS X Version Please:)


Its cookin right now bud, hopefully be ready within the hour (assuming I can get a break and not have to work at work)

Thanks billotronic! The mac build is now added to the github release page.
legendary
Activity: 1330
Merit: 1000
Blockchain Developer

Perfect....   setstakesplitthreshold was what I was looking for.  I think I know the answer to this question but just to be clear. 

This will only split the staked block in 2.  It won't divide it into multiple blocks.   Correct? 

And lastly, what it the current felling for optimal block size?  In the past I've heard 4K, but with the difficulty rising I'm sure that size is getting scaled down.   

Yes, your option is to receive your stake in one or two blocks, no more than that.  I would aim for 1-3k at the moment, but up to you.
legendary
Activity: 1078
Merit: 1011
Awesome, I really need to learn how to do this..
legendary
Activity: 1610
Merit: 1000
Crackpot Idealist
Ok I am throwing out the updated release today. I was hoping to fix some of the painful syncing problems that lead to syncing requiring the wallet to be restarted a few times, but still don't have the bugs worked out all the way.

HyperStake Version 1.0.7.2

- Adjust the stake predictions to be more accurate
- Fix DNS seeding, this means that you should be able to fire up a brand new client and not have to add any nodes
- setstakesplitthreshold RPC call - this is an important change. By default your wallet will only split your stake if it results in each block being larger than 1,000 HYP, so you would need a total value of larger than 2k for them to split by default. You can adjust this 1k HYP threshold to be whatever you want using this RPC call.  It will need to be set everytime you open your wallet, or else it will go back to default. Consider this feature in beta stage. I confirm it works on my wallet.
- reduced nLimit to 1,000 blocks at a time so that limited RAM systems don't get memory errors as easy
- adjust max connections to 25 peers
- fix some bugs with the block splitter

https://github.com/presstab/HyperStake/releases/tag/v1.0.7.2

Please bootstrap for the fastest sync (if you are syncing from scratch). Bootstrap details can be found here: https://bitcointalksearch.org/topic/m.7695751

Enjoy! And as always, don't be hesitant to report errors, I can't fix them if I don't know about them! HyperStake is not perfect, but each release gets us one step closer  Wink


Can you explain the setstakesplitthreshold RPC call a little more.  I don't think I have anything that would make that call, maybe I'm wrong.  With just the windows wallet in default mode, will I automagically split?  Can I control the split size from the windows wallet?  Are the RPC calls done through commands on the debug console?  If these are commands, and they're not already explained in the help, can you explain them? 

   Sorry for what might be stupid questions.   Smiley
 

Not stupid at all. If you have a block of 5,000 HYP that stakes with a reward of 1,000 HYP after 10 days, the network will take your original 5k block and destroy it, and give you two blocks of 3k HYP, thus splitting your stake. 

In version 1.0.7.1 I attempting to switch the logic up, but coded it wrong, and this resulted in blocks not splitting at all when they stake, so you would have received a new block of 6k instead of two blocks of 3k.

In version 1.0.7.2 I added the ability for the user to define when they want their wallet to split their stakes. By default it is set to not split the stake if each new block is less than 1k HYP. So in the case of this 6k stake, it will still split them into two blocks of 3k HYP.

If you were to enter into your debug window "setstakesplitthreshold 4000", then that would mean your wallet won't split the blocks if it results in each block being less than 4k HYP. So in the example above, it would have produce one block of 6k and not split them. If you set the threshold to 2000, then it would have split them.

This is more advanced staking theory, and might be difficult to understand for those that aren't veteran stakers. If you don't understand why or how this works, simply don't use it until you do. I set the default to be a number that will optimize staking fairly well for those that don't want to mess around with this technical aspect of staking. But I do believe that allowing advanced users to craft their staking portfolio exactly how they want is essential.

Great explanation! Added that to the FAQ on the wiki for reference



Mac OS X Version Please:)


Its cookin right now bud, hopefully be ready within the hour (assuming I can get a break and not have to work at work)
legendary
Activity: 1078
Merit: 1011
Mac OS X Version Please:)
legendary
Activity: 1007
Merit: 1000
Ok I am throwing out the updated release today. I was hoping to fix some of the painful syncing problems that lead to syncing requiring the wallet to be restarted a few times, but still don't have the bugs worked out all the way.

HyperStake Version 1.0.7.2

- Adjust the stake predictions to be more accurate
- Fix DNS seeding, this means that you should be able to fire up a brand new client and not have to add any nodes
- setstakesplitthreshold RPC call - this is an important change. By default your wallet will only split your stake if it results in each block being larger than 1,000 HYP, so you would need a total value of larger than 2k for them to split by default. You can adjust this 1k HYP threshold to be whatever you want using this RPC call.  It will need to be set everytime you open your wallet, or else it will go back to default. Consider this feature in beta stage. I confirm it works on my wallet.
- reduced nLimit to 1,000 blocks at a time so that limited RAM systems don't get memory errors as easy
- adjust max connections to 25 peers
- fix some bugs with the block splitter

https://github.com/presstab/HyperStake/releases/tag/v1.0.7.2

Please bootstrap for the fastest sync (if you are syncing from scratch). Bootstrap details can be found here: https://bitcointalksearch.org/topic/m.7695751

Enjoy! And as always, don't be hesitant to report errors, I can't fix them if I don't know about them! HyperStake is not perfect, but each release gets us one step closer  Wink


Can you explain the setstakesplitthreshold RPC call a little more.  I don't think I have anything that would make that call, maybe I'm wrong.  With just the windows wallet in default mode, will I automagically split?  Can I control the split size from the windows wallet?  Are the RPC calls done through commands on the debug console?  If these are commands, and they're not already explained in the help, can you explain them? 

   Sorry for what might be stupid questions.   Smiley
 

Not stupid at all. If you have a block of 5,000 HYP that stakes with a reward of 1,000 HYP after 10 days, the network will take your original 5k block and destroy it, and give you two blocks of 3k HYP, thus splitting your stake. 

In version 1.0.7.1 I attempting to switch the logic up, but coded it wrong, and this resulted in blocks not splitting at all when they stake, so you would have received a new block of 6k instead of two blocks of 3k.

In version 1.0.7.2 I added the ability for the user to define when they want their wallet to split their stakes. By default it is set to not split the stake if each new block is less than 1k HYP. So in the case of this 6k stake, it will still split them into two blocks of 3k HYP.

If you were to enter into your debug window "setstakesplitthreshold 4000", then that would mean your wallet won't split the blocks if it results in each block being less than 4k HYP. So in the example above, it would have produce one block of 6k and not split them. If you set the threshold to 2000, then it would have split them.

This is more advanced staking theory, and might be difficult to understand for those that aren't veteran stakers. If you don't understand why or how this works, simply don't use it until you do. I set the default to be a number that will optimize staking fairly well for those that don't want to mess around with this technical aspect of staking. But I do believe that allowing advanced users to craft their staking portfolio exactly how they want is essential.

Perfect....   setstakesplitthreshold was what I was looking for.  I think I know the answer to this question but just to be clear. 

This will only split the staked block in 2.  It won't divide it into multiple blocks.   Correct? 

And lastly, what it the current felling for optimal block size?  In the past I've heard 4K, but with the difficulty rising I'm sure that size is getting scaled down.   
legendary
Activity: 1330
Merit: 1000
Blockchain Developer
Ok I am throwing out the updated release today. I was hoping to fix some of the painful syncing problems that lead to syncing requiring the wallet to be restarted a few times, but still don't have the bugs worked out all the way.

HyperStake Version 1.0.7.2

- Adjust the stake predictions to be more accurate
- Fix DNS seeding, this means that you should be able to fire up a brand new client and not have to add any nodes
- setstakesplitthreshold RPC call - this is an important change. By default your wallet will only split your stake if it results in each block being larger than 1,000 HYP, so you would need a total value of larger than 2k for them to split by default. You can adjust this 1k HYP threshold to be whatever you want using this RPC call.  It will need to be set everytime you open your wallet, or else it will go back to default. Consider this feature in beta stage. I confirm it works on my wallet.
- reduced nLimit to 1,000 blocks at a time so that limited RAM systems don't get memory errors as easy
- adjust max connections to 25 peers
- fix some bugs with the block splitter

https://github.com/presstab/HyperStake/releases/tag/v1.0.7.2

Please bootstrap for the fastest sync (if you are syncing from scratch). Bootstrap details can be found here: https://bitcointalksearch.org/topic/m.7695751

Enjoy! And as always, don't be hesitant to report errors, I can't fix them if I don't know about them! HyperStake is not perfect, but each release gets us one step closer  Wink


Can you explain the setstakesplitthreshold RPC call a little more.  I don't think I have anything that would make that call, maybe I'm wrong.  With just the windows wallet in default mode, will I automagically split?  Can I control the split size from the windows wallet?  Are the RPC calls done through commands on the debug console?  If these are commands, and they're not already explained in the help, can you explain them? 

   Sorry for what might be stupid questions.   Smiley
 

Not stupid at all. If you have a block of 5,000 HYP that stakes with a reward of 1,000 HYP after 10 days, the network will take your original 5k block and destroy it, and give you two blocks of 3k HYP, thus splitting your stake. 

In version 1.0.7.1 I attempting to switch the logic up, but coded it wrong, and this resulted in blocks not splitting at all when they stake, so you would have received a new block of 6k instead of two blocks of 3k.

In version 1.0.7.2 I added the ability for the user to define when they want their wallet to split their stakes. By default it is set to not split the stake if each new block is less than 1k HYP. So in the case of this 6k stake, it will still split them into two blocks of 3k HYP.

If you were to enter into your debug window "setstakesplitthreshold 4000", then that would mean your wallet won't split the blocks if it results in each block being less than 4k HYP. So in the example above, it would have produce one block of 6k and not split them. If you set the threshold to 2000, then it would have split them.

This is more advanced staking theory, and might be difficult to understand for those that aren't veteran stakers. If you don't understand why or how this works, simply don't use it until you do. I set the default to be a number that will optimize staking fairly well for those that don't want to mess around with this technical aspect of staking. But I do believe that allowing advanced users to craft their staking portfolio exactly how they want is essential.
sr. member
Activity: 475
Merit: 250
legendary
Activity: 1610
Merit: 1000
Crackpot Idealist
Ok I am throwing out the updated release today. I was hoping to fix some of the painful syncing problems that lead to syncing requiring the wallet to be restarted a few times, but still don't have the bugs worked out all the way.

HyperStake Version 1.0.7.2

- Adjust the stake predictions to be more accurate
- Fix DNS seeding, this means that you should be able to fire up a brand new client and not have to add any nodes
- setstakesplitthreshold RPC call - this is an important change. By default your wallet will only split your stake if it results in each block being larger than 1,000 HYP, so you would need a total value of larger than 2k for them to split by default. You can adjust this 1k HYP threshold to be whatever you want using this RPC call.  It will need to be set everytime you open your wallet, or else it will go back to default. Consider this feature in beta stage. I confirm it works on my wallet.
- reduced nLimit to 1,000 blocks at a time so that limited RAM systems don't get memory errors as easy
- adjust max connections to 25 peers
- fix some bugs with the block splitter

https://github.com/presstab/HyperStake/releases/tag/v1.0.7.2

Please bootstrap for the fastest sync (if you are syncing from scratch). Bootstrap details can be found here: https://bitcointalksearch.org/topic/m.7695751

Enjoy! And as always, don't be hesitant to report errors, I can't fix them if I don't know about them! HyperStake is not perfect, but each release gets us one step closer  Wink


Can you explain the setstakesplitthreshold RPC call a little more.  I don't think I have anything that would make that call, maybe I'm wrong.  With just the windows wallet in default mode, will I automagically split?  Can I control the split size from the windows wallet?  Are the RPC calls done through commands on the debug console?  If these are commands, and they're not already explained in the help, can you explain them? 

   Sorry for what might be stupid questions.   Smiley
 

There is no such thing as stupid questions, only stupid people too afraid to ask!

legendary
Activity: 1007
Merit: 1000
Ok I am throwing out the updated release today. I was hoping to fix some of the painful syncing problems that lead to syncing requiring the wallet to be restarted a few times, but still don't have the bugs worked out all the way.

HyperStake Version 1.0.7.2

- Adjust the stake predictions to be more accurate
- Fix DNS seeding, this means that you should be able to fire up a brand new client and not have to add any nodes
- setstakesplitthreshold RPC call - this is an important change. By default your wallet will only split your stake if it results in each block being larger than 1,000 HYP, so you would need a total value of larger than 2k for them to split by default. You can adjust this 1k HYP threshold to be whatever you want using this RPC call.  It will need to be set everytime you open your wallet, or else it will go back to default. Consider this feature in beta stage. I confirm it works on my wallet.
- reduced nLimit to 1,000 blocks at a time so that limited RAM systems don't get memory errors as easy
- adjust max connections to 25 peers
- fix some bugs with the block splitter

https://github.com/presstab/HyperStake/releases/tag/v1.0.7.2

Please bootstrap for the fastest sync (if you are syncing from scratch). Bootstrap details can be found here: https://bitcointalksearch.org/topic/m.7695751

Enjoy! And as always, don't be hesitant to report errors, I can't fix them if I don't know about them! HyperStake is not perfect, but each release gets us one step closer  Wink


Can you explain the setstakesplitthreshold RPC call a little more.  I don't think I have anything that would make that call, maybe I'm wrong.  With just the windows wallet in default mode, will I automagically split?  Can I control the split size from the windows wallet?  Are the RPC calls done through commands on the debug console?  If these are commands, and they're not already explained in the help, can you explain them? 

   Sorry for what might be stupid questions.   Smiley
 
Jump to: