HyperDigest #5

A lot at happened since last entry in the HyperStake Development journal. A bit too much, I do not know where to start.

== The price of stability ==
Price is stable which is good - of course those who bought much higher would prefer a higher price to recoup their losses, but the general interest is for stable price: less pain and you can still benefit but selling your stake, which encourage keepin in your wallet, thus strentghtening the network.

== Enter the multisend ==
Multisend is finally here and it rocks.

Multisend http://hyperstake.wikia.com/wiki.RPC is the next step in HyperSend and the natural evolution of Stake4Charity. You can now send your stake to more than one address. Also, you are not limited to 50% or your stake anymore - all of it can be sent.
Remember to frequently sell to ensure liquidity (as well as profit) https://bitcointalk.org/index.php?topic=678849.msg8905328#msg8905328

Multisend for the moment is only accessible though RPC calls. For more information, read hyperstake.wikia.com/wiki/Multisend

If you experience heavy CPU or bandwith usage, you now have two RPC calls (accessible from the debug console): strictprotocol and strictincoming. Information on how to use them on the wiki: http://hyperstake.wikia.com/wiki.RPC


== HYP is government-immune ==
Speaking of that, I realised that HYP is protected against a menace that threatens most PoS, particularly non high-PoS: a government could subpoena exchanges and get the hold on the network. Subpoena can have "gag orders" which prohibits the said exchange to even say they received a subpoena, which would make the action completely unnoticed. In the end, the government would control the coin, because in most case, exchanges as a whole have more than 50% of the coins.

This is not the case with HYP. A very large majority of HYP is held in wallet. So HYP is effectively immune from governement-seizing thanks to the economical incentive to keep the coin in the wallet - which by the way means that cold staking could be a bad idea, security-wise.

== OpenAlias comes to HYP ==
HyperStake is the very first Bitcoin-based coin that implements OpenAlias (only with a bot for the moment). OpenAlias is a neat feature that make sending coin easier. This is a originally a Monero development and it is a big deal. Yesterday, Bitcoin become the second coin to accept it, since the PR for Electrum had been accepted (Electrum is a Bitcoin wallet which doesn't require to download the blockchain - it also has mnemonic seed, another neat feature I expect to see on HyperStake one day) More information about OpenAlias here: https://monero.cc/talks/monerotalks-whatisopenalias.html

You can already donate to the development fund by going on IRC and either joinin #hyppero or contacting hyppero and use the following address: donate.hyperstake.com (no www, no http, just this)

== HYP saves they day ==
Presstab discovered an exploit that affect most PoS coins. Despite the tremendous security of HYP, it was still possible to use a "timedrift" (different from timewarp) to generate more coins than allowed. It was solved in a matter of day but unfortunately required a hard fork, so we are still recovering since not everyone is on the right chain at the moment. Still, it had been solve very fast. As someone wrote:
https://bitcointalk.org/index.php?topic=678849.msg10492461#msg10492461

A potential bad salad situation was handled well.

A article was published on bitcoinist.net: http://bitcoinist.net/interview-presstab-pos-vulnerabilities/

== Going testnet ==
We learnt from this lesson. We decided to create a testnet and now HYP has its own testnet to evaluate new features or anticipate exploit. This is a big step, because most coin do not have a testnet. To move to testnet, you should open a second wallet with the following instructions:

== Reduce your load ==
If you experience heavy CPU or bandwith usage, you now have two RPC calls (accessible from the debug console): strictprotocol and strictincoming. Information on how to use them on the wiki: http://hyperstake.wikia.com/wiki.RPC

We also have, in beta, a feature called liteStake:
"liteStake beta: Previously the staking process would continuosly rehash the same hashes over and over, needlessly taking up valuable CPU power. HYP 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 means that there will be 1-5 seconds of CPU hashing once every minute, compared to continuous CPU hashing."

In the same spirit, we are considering changing some algo for lighter ones. This was supposed to be done for the hard fork, but due to the emergency nature of the hard fork, we postponed everything else.

== Hardfork wishlist ==
This is purely informational, it may never be completed (much like the feature galore https://bitcointalk.org/index.php?topic=784363.msg9768803#msg9768803 list) but here it is:


There is too much to summarize here. That's the price of not updating the HDJ often enough. So browser the ANN https://bitcointalk.org/index.php?topic=678849 and scan ##hyperstake and ##hyperstake-dev for latest info!