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

[foroplus]

I haven't seen any HyperStake paperwallet generator.
So feel free to try this one:
http://comm.hopto.org/hypaddress/

I've generated and tried the "single wallet" tab and the "brain wallet" tab, importing the private keys into the wallet, working fine.

As all paper wallets is coded in javascript, so everyone can peruse the code...

[1714648426]

1714648426

[1714648426]

1714648426

[gribgo]

I think that the value of high POS coins is more clear now//as more people realize how much safer it is to invest in to high POS coins like TEKcoin or HYP i.e. Hashpower for proof-of-stake Virtual Mining! 
When people invest in such things like PBMining and other "cloud hashing" stuff
they better would consider investing into something they can hold and sell any time, then in "haspower that most likely does not even exist!"
ok.. after ponzies collapse - people go to something 100% legit like CEX.io, and buy haspower there..but you have to pay fees for every Ghs that you buy there.. so TEKcoin and HYPerstake are kicking ass.. because all you stake is yours! no f.. fees 
P.S> GAWminers basically started POS coin and have product called "Hashstaker"(which is just centralized way of what we have here with TEKcoin)
peace people

[ruddsd01]

Get me the crash info and we can take a lookie lou.

also, I can damn near always be reached on ##hyperstake on freenode as well... which ever is easiest for you.

I will put up some crash dump information later tonight when I get home. (Yes, maybe the answer is to upgrade my MacBook to the latest. I hesitate to do this quite yet.)

Thanks!

[Hilux74]

Get me the crash info and we can take a lookie lou.

also, I can damn near always be reached on ##hyperstake on freenode as well... which ever is easiest for you.

I will put up some crash dump information later tonight when I get home. (Yes, maybe the answer is to upgrade my MacBook to the latest. I hesitate to do this quite yet.)

Thanks!

Instead of upgrading your Mac Book I can just sell you some iHYP...they are just like HYP but come in a minimalist white box and are 10x as expensive.   

[Biomech]

Get me the crash info and we can take a lookie lou.

also, I can damn near always be reached on ##hyperstake on freenode as well... which ever is easiest for you.

I will put up some crash dump information later tonight when I get home. (Yes, maybe the answer is to upgrade my MacBook to the latest. I hesitate to do this quite yet.)

Thanks!

Instead of upgrading your Mac Book I can just sell you some iHYP...they are just like HYP but come in a minimalist white box and are 10x as expensive.   

Hey, now, be nice. Or he just might make you use Windows 8...

[ruddsd01]

V1.0.7.3 Crash Information for Billotronic

I only posted the information for the actual thread that crashed. No sense spamming this forum with a lot of unnecessary stuff.

Is this some type of dynamic linking issue? (I´m not very experienced in OS X development, so just a guess here.)

-------------------
Process:         hyperstake-qt [2395]
Path:            /Applications/hyperstake-qt.app/Contents/MacOS/hyperstake-qt
Identifier:      com.yourcompany.hyperstake-qt
Version:         0
Code Type:       X86-64 (Native)
Parent Process:  launchd [121]
User ID:         501

Date/Time:       2014-12-15 22:44:04.784 -0500
OS Version:      Mac OS X 10.8.5 (12F45)
Report Version:  10

Interval Since Last Report:          3419730 sec
Crashes Since Last Report:           32
Per-App Crashes Since Last Report:   19
Anonymous UUID:                      8851018E-F546-CCCA-D9E7-C8F2505206C6

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Dyld Error Message:
  Symbol not found: ___sincos_stret
  Referenced from: /Applications/hyperstake-qt.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui
  Expected in: /usr/lib/libSystem.B.dylib

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   dyld                             0x00007fff6765d09d dyld_fatal_error + 1
1   dyld                             0x00007fff67660048 dyld::fastBindLazySymbol(ImageLoader**, unsigned long) + 139
2   libdyld.dylib                    0x00007fff8ac0a8ee dyld_stub_binder_ + 13
3                                 0x0000000109eac008 0 + 4461346824
4   QtGui                            0x000000010982c9f3 0x109633000 + 2071027
5   QtGui                            0x00000001097ec4be QPainterPath::arcTo(QRectF const&, double, double) + 446
6   QtGui                            0x00000001097dcdec QPainter::drawArc(QRectF const&, int, int) + 124
7   QtGui                            0x00000001097b5917 0x109633000 + 1583383
8   QtGui                            0x00000001097b7c03 0x109633000 + 1592323
9   QtGui                            0x00000001099a072d 0x109633000 + 3594029
10  QtGui                            0x00000001099a0f62 0x109633000 + 3596130
11  QtGui                            0x00000001099a101d 0x109633000 + 3596317
12  QtGui                            0x00000001099a7aa4 0x109633000 + 3623588
13  QtGui                            0x0000000109a3e495 QComboBox::paintEvent(QPaintEvent*) + 165
14  QtGui                            0x00000001097101af QWidget::event(QEvent*) + 1199
15  QtGui                            0x0000000109a3e696 QComboBox::event(QEvent*) + 246
16  QtGui                            0x00000001096c179c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 252
17  QtGui                            0x00000001096c4743 QApplication::notify(QObject*, QEvent*) + 7107
18  QtCore                           0x000000010948ff96 QCoreApplication::notifyInternal(QObject*, QEvent*) + 118
19  QtGui                            0x000000010970b389 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 1961
20  QtGui                            0x000000010970bb50 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 1232
21  QtGui                            0x000000010970b9c8 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 840
22  QtGui                            0x000000010970b9c8 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 840
23  QtGui                            0x000000010970b9c8 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 840
24  QtGui                            0x000000010970b9c8 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 840
25  QtGui                            0x000000010970b9c8 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 840
26  QtGui                            0x000000010970b575 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 2453
27  QtGui                            0x000000010970bb50 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 1232
28  QtGui                            0x000000010970b575 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 2453
29  QtGui                            0x000000010970bb50 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 1232
30  QtGui                            0x000000010970b575 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 2453
31  QtGui                            0x000000010970bb50 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 1232
32  QtGui                            0x000000010970b575 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 2453
33  QtGui                            0x0000000109662eea 0x109633000 + 196330
34  com.apple.AppKit                 0x00007fff850d8140 -[NSView _drawRect:clip:] + 4437
35  com.apple.AppKit                 0x00007fff850d4fb3 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 3058
36  com.apple.AppKit                 0x00007fff850d5a44 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 5763
37  com.apple.AppKit                 0x00007fff850d4143 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 314
38  com.apple.AppKit                 0x00007fff850cfd6d -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 4675
39  com.apple.AppKit                 0x00007fff85099c93 -[NSView displayIfNeeded] + 1830
40  com.apple.AppKit                 0x00007fff850991cc _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 738
41  com.apple.AppKit                 0x00007fff85664901 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_invoke_01208 + 46
42  com.apple.CoreFoundation         0x00007fff89d51417 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
43  com.apple.CoreFoundation         0x00007fff89d51381 __CFRunLoopDoObservers + 369
44  com.apple.CoreFoundation         0x00007fff89d2c7b8 __CFRunLoopRun + 728
45  com.apple.CoreFoundation         0x00007fff89d2c0e2 CFRunLoopRunSpecific + 290
46  com.apple.HIToolbox              0x00007fff82cbbeb4 RunCurrentEventLoopInMode + 209
47  com.apple.HIToolbox              0x00007fff82cbbb94 ReceiveNextEventCommon + 166
48  com.apple.HIToolbox              0x00007fff82cbbae3 BlockUntilNextEventMatchingListInMode + 62
49  com.apple.AppKit                 0x00007fff85096533 _DPSNextEvent + 685
50  com.apple.AppKit                 0x00007fff85095df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
51  com.apple.AppKit                 0x00007fff8508d1a3 -[NSApplication run] + 517
52  QtGui                            0x00000001096757d0 0x109633000 + 272336
53  QtCore                           0x000000010948d32d QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 477
54  QtCore                           0x0000000109490547 QCoreApplication::exec() + 199
55  com.yourcompany.hyperstake-qt    0x0000000107a64678 main + 7416
56  libdyld.dylib                    0x00007fff8ac0c7e1 start + 1

[crypto4jan]

Well, its official.. 2400 blocks are gonna max out... Time to move to 2k..

I did it 9 days ago. Since I already have 36 block maxed out (and more by the day), I wil start moving my new blocks to 1800.

The lower the blocks, the more numerous the block, the faster the diff rise - without even accounting for more HYP being available for more blocks. Expect exponential rise.

I also moved the chart to open access, so you will not have to request access anymore, sorry about that.

One of these days, you guys will be finding out that making the blocks too tiny, will eventually cause them to not stake for over 30 days, at which point they stop gaining weight. With everyone moving to smaller blocks, and with difficulty continuing its rise, it will not be too long before 2K blocks become "to small to stake".

We'll all probably get away with it (staking small'ish blocks) for another month or so, but I'm guesstimating that soon enough, we'll stop worrying about hitting the cap, and start worrying about having enough size/weight to stake before reaching 30 days maturity.
Personally, my block sizes are anything between 2K ~ 4K at the moment, but by the end of the month I'll be aiming at 3K+ blocks.

Interesting times ahead!  
Happy Staking,

I see also estimated days to stake rising very much.
I thing I go to blocks of 10K HUP.
It is I presume the anti-inflation mega-ism in Hyperstake working.

[billotronic]

V1.0.7.3 Crash Information for Billotronic

I only posted the information for the actual thread that crashed. No sense spamming this forum with a lot of unnecessary stuff.

Is this some type of dynamic linking issue? (I´m not very experienced in OS X development, so just a guess here.)

It appears as such though not 100% sure yet... good ol stack overflow has some good suggestions for where I can start to troubleshoot.

Have you tried any other wallet other than 1.3?

[David Latapie]

Well, its official.. 2400 blocks are gonna max out... Time to move to 2k..

I did it 9 days ago. Since I already have 36 block maxed out (and more by the day), I wil start moving my new blocks to 1800.

The lower the blocks, the more numerous the block, the faster the diff rise - without even accounting for more HYP being available for more blocks. Expect exponential rise.

I also moved the chart to open access, so you will not have to request access anymore, sorry about that.

One of these days, you guys will be finding out that making the blocks too tiny, will eventually cause them to not stake for over 30 days, at which point they stop gaining weight. With everyone moving to smaller blocks, and with difficulty continuing its rise, it will not be too long before 2K blocks become "to small to stake".

We'll all probably get away with it (staking small'ish blocks) for another month or so, but I'm guesstimating that soon enough, we'll stop worrying about hitting the cap, and start worrying about having enough size/weight to stake before reaching 30 days maturity.
Personally, my block sizes are anything between 2K ~ 4K at the moment, but by the end of the month I'll be aiming at 3K+ blocks.

Interesting times ahead!  
Happy Staking,

You're right, I did not notice that two of my 2400 block already are more than 30 days old. I will start some 3000 blocks, then. The "lesser blocks means more block even if they take longer to stake" consideration is heavily affected by the 30 days limit.

Update:
The stake calculator is planned to be updated with "wasted coins" (how much I would have gotten if there was no 1000 HYP limit). I propose the stake calculator is further improved by outputting not only the stake, but also the weight - this value being particularly important at 30 days, when reaching max age (and not gaining more weight). Hence a "stake and weight calculator".

Also, could the block browser show the block weight? "Block network stake weight" is something different than weight in coin control.

FYI, at 2400 HYP per block, 30 days is 71200 of weight. A rule of three gives me this:
Size   Weight @30days
 2400   71200
 1000   29667
 3000   89000
 3033   90000
10000  296667
Since I have already two blocks at 30+ days, I believe that 71200 of weight (and so, 2400 of size) does not give enough chance to stake. Granted, I only have two of them stuck here, but I have a total of 44 blocks at 1000 (all with 2400 of blocksize). I will head to 89000 of weight (a nice round number of 3000).

[ruddsd01]

V1.0.7.3 Crash Information for Billotronic

I only posted the information for the actual thread that crashed. No sense spamming this forum with a lot of unnecessary stuff.

Is this some type of dynamic linking issue? (I´m not very experienced in OS X development, so just a guess here.)

It appears as such though not 100% sure yet... good ol stack overflow has some good suggestions for where I can start to troubleshoot.

Have you tried any other wallet other than 1.3?

Yes. I tried 1.0.6.0 and 1.0.7.0.
Both of these versions crash. 

[billotronic]

V1.0.7.3 Crash Information for Billotronic

I only posted the information for the actual thread that crashed. No sense spamming this forum with a lot of unnecessary stuff.

Is this some type of dynamic linking issue? (I´m not very experienced in OS X development, so just a guess here.)

It appears as such though not 100% sure yet... good ol stack overflow has some good suggestions for where I can start to troubleshoot.

Have you tried any other wallet other than 1.3?

Yes. I tried 1.0.6.0 and 1.0.7.0.
Both of these versions crash. 

Damn.

ok. Is bct the easiest way to get a hold of you?

[ruddsd01]

V1.0.7.3 Crash Information for Billotronic

I only posted the information for the actual thread that crashed. No sense spamming this forum with a lot of unnecessary stuff.

Is this some type of dynamic linking issue? (I´m not very experienced in OS X development, so just a guess here.)

It appears as such though not 100% sure yet... good ol stack overflow has some good suggestions for where I can start to troubleshoot.

Have you tried any other wallet other than 1.3?

Yes. I tried 1.0.6.0 and 1.0.7.0.
Both of these versions crash. 

Damn.

ok. Is bct the easiest way to get a hold of you?

Yes, BCT is easiest for now. I could get myself set up on Freenode. Would that work better?

[David Latapie]

Could you populate this reference? This is not something to be done in one day, as it is pretty long. Thank you.
http://hyperstake.wikia.com/wiki/RPC

[billotronic]

V1.0.7.3 Crash Information for Billotronic

I only posted the information for the actual thread that crashed. No sense spamming this forum with a lot of unnecessary stuff.

Is this some type of dynamic linking issue? (I´m not very experienced in OS X development, so just a guess here.)

It appears as such though not 100% sure yet... good ol stack overflow has some good suggestions for where I can start to troubleshoot.

Have you tried any other wallet other than 1.3?

Yes. I tried 1.0.6.0 and 1.0.7.0.
Both of these versions crash. 

Damn.

ok. Is bct the easiest way to get a hold of you?

Yes, BCT is easiest for now. I could get myself set up on Freenode. Would that work better?

well tell ya what, let me get something going here for test and I will get back to you.

[billotronic]

ok, I've located my problem now so *hopefully* I will have a fix soon. For some reason, qmake is not setting the target build as 10.5 even though the pro says to.

)(*&!@*#(&!)*(@^#&*)^!@ OSX

[waxo]

hi all , just a small comment about the market .
things are moving on Polo and this is good.
All we need is more pressure on the sell orders, so please for the ones how have some HYP on polo, remove your orders and stake !!!!
There is no point to sell at this current price, panic sell has already passed.
Thanx to presstab,david and the others for being faithful to HYP.

[billotronic]

ok, 'pretty' sure this is fixed. I have no idea why qmake is doing what it's doing... one step at a time

https://mega.co.nz/#!Fw8gBDCJ!X2Tko1rYUngRfax44k0CCRJOcidBZEzsxQ7HcURxhlQ

I invite all OSX users to test this out for me pretty please.

[ruddsd01]

ok, 'pretty' sure this is fixed. I have no idea why qmake is doing what it's doing... one step at a time

https://mega.co.nz/#!Fw8gBDCJ!X2Tko1rYUngRfax44k0CCRJOcidBZEzsxQ7HcURxhlQ

I invite all OSX users to test this out for me pretty please.

I just tried it. Works great on my system.
Thanks!

[billotronic]

and you sir just made my day.

w00t!

[ruddsd01]

and you sir just made my day.

w00t!

Glad to help. This version is a big improvement.