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

[billotronic]

On the latest wallet is there a S4C?

I do not see the option.

s4c has been replaced by the super duper sexy multisend. At the moment, this can only be used via command line or through the debug console in the Qt.

here is the output of the help for multisend:

Code:

multisend <command>
****************************************************************
WHAT IS MULTISEND?
MultiSend is a rebuild of what used to be called Stake For Charity (s4c)
MultiSend allows a user to automatically send a percent of their stake reward to as many addresses as you would like
The MultiSend transaction is sent when the staked coins mature (30 confirmations)
The only current restriction is that you cannot choose to send more than 100% of your stake using MultiSend
****************************************************************
MULTISEND COMMANDS (usage: multisend <command>)
print - displays the current MultiSend vector 
clear - deletes the current MultiSend vector 
enable/activate - activates the current MultiSend vector 
disable/deactivate - disables the current MultiSend vector 
delete <Address #> - deletes an address from the MultiSend vector 
disable <address> - prevents a specific address from sending MultiSend transactions
enableall - enables all addresses to be eligible to send MultiSend transactions
****************************************************************
TO CREATE OR ADD TO THE MULTISEND VECTOR:
multisend <HyperStake Address> <percent>
This will add a new address to the MultiSend vector
Percent is a whole number 1 to 100.
****************************************************************

Any questions hit someone up on irc or here bud. It's pretty bad ass.

[David Latapie]

here is the output of the help for multisend:

multisend print to see what is being sent
multisend enable to activate multisend
multisend disable to deactivet it. This does not reset the addresses and percentage, which is good
multisend (address) X, to send an percentage X to a certain address. You can several addresses at the same moment.

There are more option, but there are the most useful.

[MoneroMooo]

I'd like to mention that Myriadcoin is interested in porting OpenAlias (What is OpenAlias). HyperStake would miss the "first Bitcoin fork with OpenAlias" prize but it would then be easy to port it too.

As an encouragement, the IRC bot in ##hyp-games already allows you to withdraw your HYP using OpenAlias - should you have setup a oa1:hyp line on a domain's TXT record.

[David Latapie]

I'd like to mention that Myriadcoin is interested in porting OpenAlias (What is OpenAlias). HyperStake would miss the "first Bitcoin fork with OpenAlias" prize but it would then be easy to port it too.

As an encouragement, the IRC bot in ##hyp-games already allows you to withdraw your HYP using OpenAlias - should you have setup a oa1:hyp line on a domain's TXT record.

Excellent thing. I created two specific addresses so that we can keep track of donation in OpenAlias. One is david.latapie.name, which points to my own address and the second and most important one is donate.hyperstake.com.
Use the code below on your own server

Code:

Name: donate.hyperstake.com.
TTL: 14400
Type: TXT
TXT Data: oa1:hyp recipient_address=pAvP3gYfuyDVbUt98ToMbwU9rwEdBV1dHW; recipient_name=HyperStake community wallet\; tx_description=Donations to make HyperStake a better coin and secure the network with more trusted staking\;

Now if you want to test the thing, choose one of these two options (make sure to have at least 21 HYP there first - if you don't ask your address with !deposit then send)

Option 1

Code:

/join ##hyp-games
!withdraw donate.hyperstake.com 20

Option 2

Code:

/query #hyppero
!withdraw donate.hyperstake.com 20

Notice that, when you configure the DNS, you end with a period, but when you send, you omit the period.

Since this is the same address as the community wallet, there is no way to discriminate if money was sent directly (raw address) or through the openalias (except DNS logs, but most DNS servers do not track logs and I am not even sure I would know how to access the said logs for hyperstake.com).

Remember also, that with like anything DNS, it requires up to 48 hours to take effect, due to DNS propagation (in effect, though, 3 hours seems good enough). Which means you should not try this address before severa hours (like tomorrow, after a good night of sleep, should be good).

hyppero checks before sending so your money shall not be lost if the address does not exist (or is not propagated yet). If you want to force a check without sending HYP, use the !resolve command with hyppero or ##hyp-games

Code:

!resolve donate.hyperstake.com

Example if you send to an incorrect address

Code:

<davidlatapie> !resolve donate.hyperstake.com
<hyppero> Error: not found
<davidlatapie> !withdraw donate.hyperstake.com 20
<hyppero> Error: not found

Hopefully Matylda will soon follow.

[nioc]

Out of curiosity: what is your highest block height atm? My highest is at 237231.

My wallet shows the latest block sitting at 230944 right now! 
I double-checked with Matylda, and she agrees with my wallet.

119732

highest ever ~145k

almost all stake @<100k and<20 days

smallest 49302

[David Latapie]

Out of curiosity: what is your highest block height atm? My highest is at 237231.

242455 is my newest high.

[mafort1469]

Out of curiosity: what is your highest block height atm? My highest is at 237231.

242455 is my newest high.

Ha we are close david. My high is 246,586.

[myagui]

Out of curiosity: what is your highest block height atm? My highest is at 237231.

242455 is my newest high.

Ha we are close david. My high is 246,586.

Oh, the question was about weight! 
I've had a few at 145K (got only one such input right now), but not much really.
I think the majority of my blocks has been staking at about 80K weight on average, or slightly less in recent times.   

[David Latapie]

Out of curiosity: what is your highest block height atm? My highest is at 237231.

242455 is my newest high.

Ha we are close david. My high is 246,586.

249189 now

[presstab]

Alright another release for you folks! The last one should be looked at as the stable release the has few bugs and works well. This new release should be seen as a relatively stable beta version that you will need to make sure that you are in fact pulling in stakes with. Also for anyone that understand the code, feel free to give me some feedback.

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

I redesigned the hashing iteration in a few ways.

Code Reorginization - Instead of iterating the hashing in wallet.cpp, it
is iterated in kernel.cpp inside of checkstakekernelhash, this allows
the iteration to not need to initialize the variables for every
iteration. This is also true for the stake modifier, which was
previously
calculated for each iteration.

liteStake - Previously the staking process would continuosly rehash the
same hashes over and over, needlessly taking up valuable CPU power.
I have added a std::map that tracks the block height and the last time
the wallet hashed on this height. Depending on your staking settings,
the wallet will not begin a new round of hashing until after a certain
amount of time has passed, or a new block is accepted. This time delay
can be found in main.cpp bitcoinminer(). This means that there will be
1-5 seconds of heavier CPU use once every few minutes, compared to
continued heavy CPU use.

Staking Modes - This allows the user to decide how much time they want
to hash into the future and past. HYP has a max time drift of 15
minutes. The aggressive mode allows the user to hash 10 minutes into the future
and 10 into the past. This will affect the chains timing a bit, and also
might make difficulty more volatile in the short run. In my opinion it
is more dangerous to allow a creative coder to do these same accepted
practices without letting general users do the same. Use RCP "stakemode".

[myagui]

Awesome stuff presstab! Will run this beta version from now on, and I'll be checking out the code over the coming days. I will likely have lots of noob questions as customary, and I appreciate your patience in advance!   

[mafort1469]

Alright another release for you folks! The last one should be looked at as the stable release the has few bugs and works well. This new release should be seen as a relatively stable beta version that you will need to make sure that you are in fact pulling in stakes with. Also for anyone that understand the code, feel free to give me some feedback.

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

I redesigned the hashing iteration in a few ways.

Code Reorginization - Instead of iterating the hashing in wallet.cpp, it
is iterated in kernel.cpp inside of checkstakekernelhash, this allows
the iteration to not need to initialize the variables for every
iteration. This is also true for the stake modifier, which was
previously
calculated for each iteration.

liteStake - Previously the staking process would continuosly rehash the
same hashes over and over, needlessly taking up valuable CPU power.
I have added a std::map that tracks the block height and the last time
the wallet hashed on this height. Depending on your staking settings,
the wallet will not begin a new round of hashing until after a certain
amount of time has passed, or a new block is accepted. This time delay
can be found in main.cpp bitcoinminer(). This means that there will be
1-5 seconds of heavier CPU use once every few minutes, compared to
continued heavy CPU use.

Staking Modes - This allows the user to decide how much time they want
to hash into the future and past. HYP has a max time drift of 15
minutes. The aggressive mode allows the user to hash 10 minutes into the future
and 10 into the past. This will affect the chains timing a bit, and also
might make difficulty more volatile in the short run. In my opinion it
is more dangerous to allow a creative coder to do these same accepted
practices without letting general users do the same. Use RCP "stakemode".

Damn Press,  you NEVER cease to amaze me. THANK YOU!

[foroplus]

Thank you Presstab.

[presstab]

I am keeping my eye on the downward difficulty spiral that unleashing the full timedrift power to everyone is causing. This might be a reason for a fork in order to make time drift rules much more strict. My suggestion would be 60 seconds future as well as 60 seconds past.

[David Latapie]

Press is the man!

Here some more improvements, I wrote before even reading of your new code.

Improving multisend
Goal: be more intuitive and simpler. If all these suggestions are implemented, address number and the delete command are not necessary anymore (the address number may still be present in the code, but it is hidden to the user).
Subjective, based on what appears simpler and more intuitive to me - feedbacks welcomed.

Request 1
Change

Code:

multisend delete <Address #> - deletes an address from the MultiSend vector

For

Code:

multisend delete <address> - deletes an address from the MultiSend vector

Why
The only occurence where you have to use the number. Get rid of one variable, from the user's perspective. When using the GUI, you may as well copy the address. I understand this can be tricker when using the CLI, though, where one digit is much simpler than a long address.

Request 2
Changing the percentage of stake to one address just by typing a new percentage for the said address

Presently

Code:

1. multisend delete <Address #> - deletes an address from the MultiSend vector 
2. multisend <address> %

Proposed

Code:

1. multisend <address> %

Why
Only one step instead of two. Same remarks regarding CLI and GUI.

Request 3
Expands on request 2. Delete by just moving to 0%.

Presently

Code:

multisend delete <Address #>

Proposed

Code:

multisend <address> 0%

Why
Elimintate the need for the delete command. Same remarks regarding CLI and GUI.

[sparksi]

Nice! Looking forward to liteStake with my Raspberry Pi.

[presstab]

David awesome suggestions, those should be fairly easy to change in the code, I'll get on it asap

[presstab]

Nice! Looking forward to liteStake with my Raspberry Pi.

Sparksi you should be able to recompile with the latest github commits.

[myagui]

I am keeping my eye on the downward difficulty spiral that unleashing the full timedrift power to everyone is causing. This might be a reason for a fork in order to make time drift rules much more strict. My suggestion would be 60 seconds future as well as 60 seconds past.

I think this would be a great improvement to both network stability & security. There is no reasonable use case to support the original time drift allowance of 15 minutes. Keep up the great work Presstab!  

[Beoga]

Are any HyperStake assets and divident distribution system?