As there's no pool, just for the kicks, I've made one at dbpool.mooo.com.

For those with trouble syncing, delete yojur p2pstate.bin while the daemon isn't running, then start the daemon again, that should help.

The seed at ddns.net is already set in the source as a default.

This daemon seems to also die on exit, so save before exiting to avoid having to resync.

The hashing rate could be decreased from 1 per second to, eg, 1 per 10 seconds. This would be an easy way to decrease the CPU usage (assuming it comes mostly from hashing). This would likely increase the variance of staking times though.

Elsewhere, I also read that you'd like to speed up syncing. Old blocks will still have to be verified using the existing method, so any speedup will show gradually as the "new style" blocks increase in proportion to total blocks in the chain. So a change will not mean faster syncing, but merely a lesser increase as times goes.

Last, someone mentioned ASIC friendly. I doubt anyone will stake HYP on an ASIC, so I would not think this to be an interesting property for deciding on a replacement.

In the end I don't really have a theoretical preference for which hash to use. I'd favor a simple one for which good code already is there. And since you said SHA256 is already used for coinstake...

Half a monero is 500000000000. You'll want that for minPayment. Either set denomination to the same, or to 100000000000 (0.1 monero).

For the transfer fee, I am not sure. If you have the fixed 0.1 version it'd be 100000000000 but if you have the per kB fee version I think (but I'm not certain) it'd be ignored.

Last month wasn't paid, but:

Posts: 151 (+11, +9 within the campaign rules)
Activity: 151
SSRC: SeCJkBRKg5Xs6pyGRBXTY51CT5EQs7kDXj

Thanks

It might also be that your computer is not keeping time properly. Some chains are known to reject blocks with timestamps that are too "off", though I'm not sure if Hyperstake is harsh about those. Using NTP to sync to a common time source would fix this, if that were the cause. No clue how you'd do that on Windows though.

I would have two comments:

First, the wavy blobs leaving Alice are maybe conveying the wrong impression. To me, they "look" worse than the darkcoin case: it feels like handwaving - literally. I would suggest making all but one of those blobs come from another direction entirely - not from Alice, to represent the inclusion of unrelated outputs in the ring signature. Then I guess you can have the wavy thing. Or maybe move them to be superimposed, then out again, with all but one disintegrating, to represent the fact than all but one are not in fact spendable by Alice on this transaction.

Second, the square blocks hiding Alice's and Bob's balances at the bottom aren't particularly visible, and you might consider a way to attract some attention to them in some way - maybe with a color change ?
 
That said, it is well done

For this to work, the server would have to know what that passphrase was.

It does not, so any captcha generation would have to be client side. This is pointless for a captcha.

Hmm, you are right.
I'll stand out

I'd love to read more about this, if you can elaborate. I view this as interest too. Is the distinction you are making about "new" coins rather than payment from existing coins from the loanee ?

I love hyperstake for two reasons.

The first one is presstab. He's like a beaver squirelling away at it, if you'll forgive the animal mixture. He doesn't hype, or pump and dump, he constantly gets on with the job of making hyperstake better. This is not unique of course, but it is not that frequent around crypto. davidlatapie is also constantly looking for ways to make this coin better in non coding ways. Both are trying to make something interesting rather than focusing on The Price first and foremost.

The second reason is the 750% rate. While I expect many people to maybe get seduced into thinking this 750% will translate to profits by assuming a constant price, the reason why this does it for me is that there is this constant (ok, not so constant) trickle of stakes coming in, and growing your stack. It's just a dumb psychological thing, but it is addictive

Yes. HYP original distribution was based on the state of the TRK blockchain sometime in july.


Yes.


No. What you do with your TRK wallet now has no influence on your HYP. Only the balance you had at the fork block matters. Simiarly, if you bought TRK after the fork block, you don't get extra HYP either. And once you sell some HYP, you can't get them back by manipulating your TRK or HYP wallet.

Please be more precise with "only hyperblue is working".

Do you get the other themes listed in the themes menu ?
If so, does selecting them change anything (ie, only parts change) ?
If not, have you made sure the directories for those are in the themes directory where the binary is (ie, you might be running another binary, IIRC the binary is now in a release subdirectory)
Are there any errors on the terminal when you select one of the other themes ?
If so, what are they (copy/paste exact messages) ?

Sure:

Find that tx in the transaction list
Right click
Select copy txid
Go to the debug console
Type "getstaketx ", then paste that txid you just copied, enter
Multiply the "Days to Stake" value minus 8.8 by the "Original Amount" value
That's the weight it had when it staked

Maybe a bit pedantic, but, assuming I did the numbers right, which is not a given:


You can only compound at 8.8 days at the earliest:
750*8.8/365 = 18.08219% per 8.8 day period,
1.1808219 ^ ( 365/8.8 ) = 986.3068
100*(986.3-1) = 98530% a year compounded

That sounds like a lot! Let's sanity check it:

I have 1000 HYP, which I will optimistically assume stake after 8.8 days like clockwork, yielding 18% every time, reinvested:
day 0: 1000 HYP
day 8.8 1180 HYP
day 17.6: 1392 HYP
day 26.4: 1643 HYP
day 35.2: 1938 HYP
day 44: 2287 HYP
day 52.8: 2700 HYP
day 61.6: 3185 HYP
day 70.4: 3759 HYP
day 79.2: 4435 HYP
day 88: 5234 HYP

Three months, and already 420%, I'll skip:

day 132: 11974 HYP
day 176: 27393 HYP
day 264: 143370 HYP
day 361: 885446 HYP

In a year, the best possible staking (which is quite unachieavable since it requires perfect compounding by staking each time at 8.8 days) gets your stash from 1000 HYP to 885k HUP. That's about 88400%. Close enough (4 days missing, half a stake period!).


In a week, the optimal rate according to what I said above is 0.18 * 7 / 8.8 = 14.3%. I'm actually not sure whether this number of yours makes more sense here. Close enough anyway.

Posts: 140 (+16, +12 within the campaign rules)
Activity: 140
SSRC: SeCJkBRKg5Xs6pyGRBXTY51CT5EQs7kDXj

Thanks.

You put in the address, name, and signature ?
Same address as the one you signed with ?
Took care that you don't include extra newlines, spaces, etc, in the name/message ?
In any case, "I get an error" isn't very helpful. The actual error would be helpful.

Next time you consolidate a block, just include those small inputs as well as what you'd normally use.
Any number of inputs (within reason) can be used there.

More info can be found in the tutorial from presstab:

https://cryptocointalk.com/topic/13257-splitting-and-combining-blocks-using-coin-control/

When you receive a stake, the staking block gets destroyed, and you receive in its stead two blocks, each about half the value of the sum of the old block plus its stake. For instance, if you had a 1000 HYP block, and it staked after 12 days, the stake will be roughly 240 HYP, the new total will be 1240 HYP, so the 1000 HYP block will go and be replaced with two blocks of around 620 HYP.

You can merge them if they get too small: in coin cointrol, select those blocks (any set which you want to merge - for instance, in the example above. select these two 620 HYP blocks), then send the "after fee" value (top right of the send screen) to yourself. These blocks will disappear and be replaced by a 1240 block.

I usually merge staked blocks if the total value is less than 3000 to 4000.

About 2.05% a day.