Author

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

legendary
Activity: 1330
Merit: 1000
Blockchain Developer
Yes, I will have numerous block on Monday as I did 17,319 into 1600 blocks and then one with change. On Monday they will be mature so chain will move again. This should help.

Awesome. Also I would recommend that those people that know when their blocks are maturing. Maybe to let a few of them stake and then close the wallet for a few hours, open it and let a few more stake, and repeat. This way we will at least move every few hours instead of move a bunch at once.

We should have good blocks coming in around Monday because everyone bought in at the same time.
sr. member
Activity: 364
Merit: 250
Yes, I will have numerous block on Monday as I did 17,319 into 1600 blocks and then one with change. On Monday they will be mature so chain will move again. This should help.
legendary
Activity: 1330
Merit: 1000
Blockchain Developer
Coin-Swap is probably going to be afk for a day or two so I am guessing it is not the best idea to hardfork so suddenly.

Makes sense. I'd say have it ready, and wait til they are back. Maybe by then it won't be useful. If it is, you got it in the chamber  Grin

I agree with you biomech... Also we will see if we get any blocks trickling in between now and then. I am sure there will be some.  The beauty of pure PoS.
legendary
Activity: 1372
Merit: 1022
Anarchy is not chaos.
Coin-Swap is probably going to be afk for a day or two so I am guessing it is not the best idea to hardfork so suddenly.

Makes sense. I'd say have it ready, and wait til they are back. Maybe by then it won't be useful. If it is, you got it in the chamber  Grin
legendary
Activity: 1330
Merit: 1000
Blockchain Developer
Coin-Swap is probably going to be afk for a day or two so I am guessing it is not the best idea to hardfork so suddenly.
full member
Activity: 158
Merit: 100
Why not use difficulty to let the intervals automatically increases once we have an abundance of mature blocks?
That way, a limit of e.g. 2 days could be used, but as soon as there are plenty of blocks it would automatically take longer and we wouldn't experience HBN-like blockchain bloat.
legendary
Activity: 1372
Merit: 1022
Anarchy is not chaos.
That's clear enough that my ignorant ass can figure it out Tongue Standing by.
legendary
Activity: 1330
Merit: 1000
Blockchain Developer
full member
Activity: 147
Merit: 100
Do it now while it's easy and small enough to do.
legendary
Activity: 1148
Merit: 1000
I would say go for it and i will update my wallet as soon as i go home.
legendary
Activity: 1372
Merit: 1022
Anarchy is not chaos.
Alright I am just going to throw this out there. We can always do an immediate hardfork. Change the stake age to something like 2 days, then in a week have it change to 5 days, then in another week change back to 9 days.  This would require getting coin-swap to update their daemon and everyone would need to immediately update their wallets.

I am here to code for the HYP community, not tell them what to do (ok I like having a little more control than that, but you get the point).

I am in favor if you're willing to do it. At this point, the community is small enough that we can be very flexible. And I think a stuck chain is more of a burden on the coin than a hard fork.
legendary
Activity: 1372
Merit: 1022
Anarchy is not chaos.
Can someone explain this to me?

Quote
Maximum Stake Subsidy - 1,000 HYP

Does this mean even if I own 100,000 HYP the max that can be earned per 9-30 days is 1,000 coins?

yup, unless you make blocks/seperate addresses full of 1'600 hyp( max for 1000 stake) to get the best.

Correct me if I'm misunderstanding you. All one needs to do to get around the 1000 max is to deposit 1,600 into separate addresses to get the full stake amount? So, within the same wallet one could create unlimited addresses and compound to a 100+ billion (or whatever arbitrarily large number)?

is there a efficient way to do this ? can u give a step by step please on how to effectively split your coins in your wallet into 1600 blocks .

Sure. Presstab already linked his guide, but here's a short version for all y'all.

First, in the QT wallet, go to settings, click on "options", an in the last tab, click on activate coin control. Hit apply.

close that out if it don't do it automatically, then click on "send coins".  You'll see a button that says "inputs" click on it. It will bring up the coin control window. You'll see a list of transactions. click on "List Mode" if it's not already there, as tree mode aggregates the inputs and is harder to deal with. It's better if you have a LOT of transactions, though. for my example we will use list mode.

This will show you every single block. On the last column, you'll see "priority" This tells you which coins are the closest to mature. This is the part where you have to make some decisions and calculations, because every coin you move will have it's maturity set back to zero, along with the block it came from. On a short staking coin like HYP, this is probably not a huge deal, but nevertheless, look at it.

Now, check the box next to every block that you are trying to split or combine. If you have a huge single block, as the OP implies, click on that one. Hit ok.

the selected blocks will be the FIRST coins sent when you make a transaction.

Now, having selected which coins to manipulate, close coin control. You'll be on the send tab still. Go to "receive coins" and generate a new address. Give it a label like "consolidation group one" or something like that so you can track it easily. Make as many as you intend to use for the next step.



Grab one of the addresses you just made, go to your "send coins" tab, and paste it in to the Pay To box. Label should come up immediately, the put the amount you wish to be in the new staking block in the Amount box. Hit send. you'll get a send confirmation that shows "send to self". Now, go back to coin control, open it, and you'll see a brand new block with the new amount of coins in it. Again, select the coins you want to move, and repeat until you're happy, assigning EACH STAKING BLOCK a separate address. (this is important to you, not the client. It will store the blocks separately, but it's hard to keep track when they all come to the same address.)

And that is coin control.

A good strategy would be to do this over the course of 9 days. You'll initially lose some coin maturity, but you'll get blocks staking every day after nine days. On staking day, create yet another new address and block, and with a bit of patience, you'll be getting a stake every day. Or more than one as time goes by.

If you like this guide, feel free to tip me Cheesy HYP pFUkpqL3CZXptffp1dm1D8YcacvaD994n7  TEK BmmkHdBj3V9CuGqGPMfwXAB8NRWYiMjmCB
legendary
Activity: 1330
Merit: 1000
Blockchain Developer
Alright I am just going to throw this out there. We can always do an immediate hardfork. Change the stake age to something like 2 days, then in a week have it change to 5 days, then in another week change back to 9 days.  This would require getting coin-swap to update their daemon and everyone would need to immediately update their wallets.

I am here to code for the HYP community, not tell them what to do (ok I like having a little more control than that, but you get the point).


Will this resets the coin age that we already have?

Nope
legendary
Activity: 1148
Merit: 1000
Alright I am just going to throw this out there. We can always do an immediate hardfork. Change the stake age to something like 2 days, then in a week have it change to 5 days, then in another week change back to 9 days.  This would require getting coin-swap to update their daemon and everyone would need to immediately update their wallets.

I am here to code for the HYP community, not tell them what to do (ok I like having a little more control than that, but you get the point).


Will this resets the coin age that we already have?
legendary
Activity: 1330
Merit: 1000
Blockchain Developer
Alright I am just going to throw this out there. We can always do an immediate hardfork. Change the stake age to something like 2 days, then in a week have it change to 5 days, then in another week change back to 9 days.  This would require getting coin-swap to update their daemon and everyone would need to immediately update their wallets.

I am here to code for the HYP community, not tell them what to do (ok I like having a little more control than that, but you get the point).
hero member
Activity: 826
Merit: 500
sr. member
Activity: 434
Merit: 250
legendary
Activity: 1330
Merit: 1000
Blockchain Developer
A preview of my latest treat for the high PoS community:

legendary
Activity: 1330
Merit: 1000
Blockchain Developer
You can actually respend your own blocks in the same block without confs.

Oh, then that would be different from Novacoin - there you can do it once but then you see errors in the log because of trying to use an invalid txid as input (something like that, it was a while back I last did this and refrained from doing so since then). It would be included in the next block after the block in which the first one will be included, though. But the client would not let you create more than 2 of these transactions, because then coin control would be confused. That's why they added a feature to not select zero-confirmed transactions as transaction inputs.
If you managed to solve this with HYP, then that's a fine thing :-)


I just split a block 5 times with 0 confs. It does work it seems. So long as they get confd in a block.

Also you can see it at work in our last block where an address was splitting blocks http://hyp.cryptospread.com:2751/block/c66a0b8225e0e29233d3f19db4ad3ba07cd94cbfc824a584b3c12885692257ec
full member
Activity: 158
Merit: 100
You can actually respend your own blocks in the same block without confs.

Oh, then that would be different from Novacoin - there you can do it once but then you see errors in the log because of trying to use an invalid txid as input (something like that, it was a while back I last did this and refrained from doing so since then). It would be included in the next block after the block in which the first one will be included, though. But the client would not let you create more than 2 of these transactions, because then coin control would be confused. That's why they added a feature to not select zero-confirmed transactions as transaction inputs.
If you managed to solve this with HYP, then that's a fine thing :-)
Jump to: