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

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.

Thank you Presstab.

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

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!   

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".

249189 now

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.   

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

242455 is my newest high.

119732

highest ever ~145k

almost all stake @<100k and<20 days

smallest 49302

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





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

Option 2

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

Example if you send to an incorrect address

Hopefully Matylda will soon follow.

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.

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.

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:


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

On the latest wallet is there a S4C?

I do not see the option.

press or jay: fluffy is willing to help in porting OA.

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

i really like the wallet on this one , so bright and awesome!

I stake several times per day and I managed to have only one block at more than 30 days (a 1666 block) with my new average size of 10K. But with 10% interest, I am considering going back to 9000 (already done) and even 8000 (today I combined my first at 8000).

I'm glad to see so coding getting consistent, where a lot of coins stop coding after the pump (or even before)

Regarding the address deletion issue: I just compiled from source and... no difference. It is possible this is related to my interface bug (no main menu wth file etc.) although it seems unlikely.

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.
Presstab, you asked me earlier if there was already a Bitcoin port of OpenAlias and I erronously told you there is not: there is indeed a PR for electrum, you (or jaybeeuk) could use it as a starting point: https://github.com/spesmilo/electrum/pull/986

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

OK, thank you!