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

[David Latapie]

Request: a way to know the build number. Compare illustations 1 (previous wallet) and 2 (new wallet, compiled today). No easy way to see the difference. Oh, there is one: the build date. And, surprise, surprise, the build date for the newer wallet is older than the build date of the newer wallet! Plus, none of these build date correspond to today, but I assume this is normal, because this is build date and not compilation|/i] date.







I also note that I once again have this issue of the menu bar (with the theme menu) disappearing with new code, so I have to stick with old code (illustration 3 is previous wallet, with menu bar and illustration 4 is new compilation without menu bar)








It is worth nothing that we I tried to upgrade old wallet (with a pull request and a compilation), I had this message:
Hi presstab,

Code:

david@david-laptop:~$ cd ~/cryptos/HyperStake && git pull && qmake HyperStake-qt.pro && make
Already up-to-date.
Project MESSAGE: Building with UPNP support
Project MESSAGE: Building with IPv6 support
Project MESSAGE: SSE2 detected, adding -msse2 flag
Warning: ignoring <defaultcodec> element
Warning: ignoring <defaultcodec> element
cd /home/david/cryptos/HyperStake; /bin/sh share/genbuild.sh /home/david/cryptos/HyperStake/build/build.h
g++ -c -m64 -pipe -fstack-protector-all --param ssp-buffer-size=1 -msse2 -O2 -fdiagnostics-show-option -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -D_REENTRANT -fPIE -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DBOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN -D__NO_SYSTEM_INCLUDES -DUSE_UPNP=1 -DSTATICLIB -DUSE_IPV6=1 -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -Isrc -Isrc/json -Isrc/qt -I/usr/include/qt5 -I/usr/include/qt5/QtWidgets -I/usr/include/qt5/QtXml -I/usr/include/qt5/QtGui -I/usr/include/qt5/QtCore -Ibuild -Ibuild -o build/sendcoinsdialog.o src/qt/sendcoinsdialog.cpp
In file included from src/qt/sendcoinsdialog.cpp:2:0:
build/ui_sendcoinsdialog.h:13:25: fatal error: QtGui/QAction: Aucun fichier ou dossier de ce type
 #include <QtGui/QAction>
                         ^
compilation terminated.
make: *** [build/sendcoinsdialog.o] Erreur 1

So in order to get the new code, I had to reinstall from scratch.


Does the new code handles S4C correctly Or do I lose of lot of my stake with this new code too?

[1714618323]

1714618323

[1714618323]

1714618323

[nioc]

Wasn't the name "multisend" picked due to proposed feature  to perform multiple s4c ? (More than 2).
David, correct me if I am wrong on this.

Also, I think "reaccuring" is only the nature of the function and should be undertood and expected by user, as it would continue  to preform a set function untill changed by user again.

multisend was just a temporary name. Of course, we all know what happens to code name... they stick multisend is an improvement of the current S4C but from the beginning, I named the whole thing HyperSend, S4C being just a subset.
That being said, both multisend and recurringsend are correct: You can can to several persons at once and you can send in an automated way.

HyperSend
HyperSend is a generalization of the idea that first came up with Stake for Charity. [...]  This can be used for a variety of purposes:

The above-mentioned well-known Stake for Charity.
[other examples]

So, just sticking to the original name HyperSend would make the most sense. multisending is just the latest improvement. Granted, we lose the "immediate understanding" of "recurring send" but we stay on the marque thing with "Hyper-*". as iantunc said, a "Feature name™".

RecurringSend
Multisend
HyperSend - I vote for this one

As the features we are trying to describe cannot be accurately done with a single word, HyperSend with a mouse over explanation seems good.  If this function evolves only the mouse over description needs to be changed.


One very small request.  Commas for the displayed wallet balance

[David Latapie]

One very small request.  Commas for the displayed wallet balance

I agree. Thousand separators are more and more necessary!

[presstab]

Done and testing before commit 



Also this is based on locale, so you folks that like "." instead of "," won't get too confused 

[presstab]

Don't forget to look at these charts that jaybeeuk has put online for us 

http://212.67.195.38/hyp-charts/

[crypto4jan]

Don't forget to look at these charts that jaybeeuk has put online for us 

http://212.67.195.38/hyp-charts/

Nice thx for charing.

[Startide]

550.886 coins now aging over 75 days without staking. 

[4x13]

Your block is too small

[Startide]

Really? Because I have other wallets, one with 3,666 potential stake over 2k and weight over 68k sitting at 27 days. For the past five days its said it has 15 hours to stake. Perhaps there's a time/language barrier, the developers used 360 minutes in an hour instead of 60. 750% PoS is not even remotely possible at this rate. It's looking more like 300 or less at this rate.

Startide

[myagui]

@Startide: Even if you stake with poor performance, the effective stake percentage over one year, is much higher than 750%, because of compounding (staking the blocks, then also staking the stakes, later staking the staked stakes, and so on).

What you are observing is simply a reflection of high difficulty. These days, it takes much larger blocks in order to stake relatively fast, and really small blocks (say, up to 1K for example) might not ever stake from here onwards, due to limited weight potential. That, and that a couple of blocks is not a large enough sample to draw conclusions, given the implicit variance in the staking process.

[presstab]

Make sure you are running the latest version of the wallet for the most accurate weight display and time estimates. Also revisit the first page of the thread and see if you find any red text saying something important.

[Startide]

As I stated previously, I have several wallets. In another wallet I've got blocks over 2000k staking over 30 days. I certainly understand compounded interest, however, the PoS % should not factor compounding. 750% was always lofty and we all new this was a grand experiment. With that said, perhaps some effort should be made to share the decrease in PoS as difficulty increases. By doing so all participating Stakers will have a more reasonable set of expectations going forward. I suspect if it were grafted we would see two lines moving in somewhat opposite directions.

Startide

[presstab]

The stake rate is 750% annual in the code, with a ceiling of 1,000 HYP.  This 750% does not count compounding, it is a raw percentage that is used to calculate how much reward to give you each time your stake, and this is the rate that we must report because it would be dishonest for a PPC based coin to not state the rate used in the code.

Inflation control (the 1,000 HYP max reward) can make it so you will get less than 750%, because part of your reward gets cut off. 2 out of my last 10 stakes have hit the 1,000 HYP max reward, resulting in a cap of a total of around 350 HYP.  This is the way HYP was designed, and it is intentional. Over time, 10/10 blocks will hit the max reward, and HYP will become more comparable to a fixed stake reward.

Part of this inflation control scheme is that this is a high difficulty coin.  As such mining (staking) is not easy. Small blocks will have a hard time staking and may quite possibly never stake. I have plenty over 80 days old and might need to take the hit and combine them into larger outputs.

I can try to add some more clarity to the OP to help newcomers understand this system of high reward with max subsidy.

[cycoinminer]

Don't forget to look at these charts that jaybeeuk has put online for us 

http://212.67.195.38/hyp-charts/

Nice thx for charing.

Great figures there from jaybeeuk!

Is there any way to add another feature showing the average weight of the blocks that stake?

It's interesting to see that we're getting closer and closer to maxing out the rewards. Roughly 50% of all my staking coins now are hitting the 1k limit.

[David Latapie]

For infromation: withdrawals on luckyalt.com/hyperstake/ are manually-approved so they may take hours to be accepted, which is completely normal.

[Biomech]

550.886 coins now aging over 75 days without staking. 

Hmm. Never had one go that long even with low numbers like that. It'll break eventually.

Actually, I need to amend that. the ten single coin blocks are way older than that

[Startide]

I decided to merge these 550 coins into a larger block in order to kick start them.

Startide

[presstab]

I decided to merge these 550 coins into a larger block in order to kick start them.

Startide

Your a brave man... I need to do this, but I just can't get myself to go through with it

[nioc]

I decided to merge these 550 coins into a larger block in order to kick start them.

Startide

Your a brave man... I need to do this, but I just can't get myself to go through with it

May I suggest you combine a small percentage of the blocks in that situation and see what happens

[HunterS]

im running 10 to 15 k block size now