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

[presstab]

Everyone please update to the latest build. If you are minting at least a few HYP blocks per day, then this should be considered a near mandatory update. Currently Win32 build is available, more builds will be added to the release page throughout the day/week.

https://github.com/hyperstake/HyperStake/releases/tag/v1.1.2

Changelog:
- Fix potential tx malleability issues
- update hard coded checkpoints
- add ability to turn off dust combination code
- keep stake coins set in memory instead of reiterating constantly
- Do not query MintableCoins() as frequently
- fix cclistcoins potential stake calculations
- gettxfee RPC call
- add MultiSend CoinStake (experimental, don't use to an exchange or automated service)
- remove old legacy irc code

Win64 Daemon and QT just built and added to the release page. Thanks iDunk!!

PS - this now includes a new way to use HyperStake with the setup/install means instead of just copying in the .exe . iDunk gave us both the traditional exe and a 'setup' exe.

[billotronic]

i have 2 wallets ruining on 2 computers 100000 hyp + 60000   (first does multisend to the snd) and sins a week both wallet crash  2-3 times a week  

Ok, what else can you tell us? What OS? What wallet version? Daemon or Qt? What does the log say? How much wood could a wood chuck chuck if a wood chuck could chuck wood?

I have received some information about this. It is believed to be transaction malleability testing on the HYP network, which can send in transactions that are not able to be handled by certain builds of the wallet (for example Windows 32 bit builds). Apparently PeerCoin suffered from this style of attack last month which caused a major fork in the chain essentially between different operating systems (as I understand it). I am testing the patched peercoin code that is believed to handle this, and will commit it to the repo and release a new version of the wallet if all goes well.

I'm lazy AND ignorant, link for that? TOTALLY didn't hear about it..

OSX wallet will be up in a few boss.

[presstab]

i have 2 wallets ruining on 2 computers 100000 hyp + 60000   (first does multisend to the snd) and sins a week both wallet crash  2-3 times a week  

Ok, what else can you tell us? What OS? What wallet version? Daemon or Qt? What does the log say? How much wood could a wood chuck chuck if a wood chuck could chuck wood?

I have received some information about this. It is believed to be transaction malleability testing on the HYP network, which can send in transactions that are not able to be handled by certain builds of the wallet (for example Windows 32 bit builds). Apparently PeerCoin suffered from this style of attack last month which caused a major fork in the chain essentially between different operating systems (as I understand it). I am testing the patched peercoin code that is believed to handle this, and will commit it to the repo and release a new version of the wallet if all goes well.

I'm lazy AND ignorant, link for that? TOTALLY didn't hear about it..

OSX wallet will be up in a few boss.

Few links for ya sir.

original description from Pieter Wuille - https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009697.html
peercoins problems - https://github.com/ppcoin/ppcoin/issues/100

[billotronic]

i have 2 wallets ruining on 2 computers 100000 hyp + 60000   (first does multisend to the snd) and sins a week both wallet crash  2-3 times a week  

Ok, what else can you tell us? What OS? What wallet version? Daemon or Qt? What does the log say? How much wood could a wood chuck chuck if a wood chuck could chuck wood?

I have received some information about this. It is believed to be transaction malleability testing on the HYP network, which can send in transactions that are not able to be handled by certain builds of the wallet (for example Windows 32 bit builds). Apparently PeerCoin suffered from this style of attack last month which caused a major fork in the chain essentially between different operating systems (as I understand it). I am testing the patched peercoin code that is believed to handle this, and will commit it to the repo and release a new version of the wallet if all goes well.

I'm lazy AND ignorant, link for that? TOTALLY didn't hear about it..

OSX wallet will be up in a few boss.

Few links for ya sir.

original description from Pieter Wuille - https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009697.html
peercoins problems - https://github.com/ppcoin/ppcoin/issues/100

oooo toilet reading. Thank you very much.

and

Care to elaborate on "MultiSend CoinStake" ?

[presstab]

Care to elaborate on "MultiSend CoinStake" ?

You didnt hear the news??!!!!?? I added a special functionality to MultiSend that lets you send the multisend tx in the actual staked block instead of waiting for all those confirms and then sending. I am 97% sure this needs extra work to make it compatible with exchanges, as it is now the daemon will see it as a minted transaction rather than received from another address.

[Tranz]

Care to elaborate on "MultiSend CoinStake" ?

You didnt hear the news??!!!!?? I added a special functionality to MultiSend that lets you send the multisend tx in the actual staked block instead of waiting for all those confirms and then sending. I am 97% sure this needs extra work to make it compatible with exchanges, as it is now the daemon will see it as a minted transaction rather than received from another address.

I didn't hear, till just now. Wow, nicely done! This was always my goal, but I have gotten to far away from the code recently, to be able to even think about it. 

Impressed sir, keep it up!

[4x13]

That would be freaking sweet!!

[presstab]

Care to elaborate on "MultiSend CoinStake" ?

You didnt hear the news??!!!!?? I added a special functionality to MultiSend that lets you send the multisend tx in the actual staked block instead of waiting for all those confirms and then sending. I am 97% sure this needs extra work to make it compatible with exchanges, as it is now the daemon will see it as a minted transaction rather than received from another address.

I didn't hear, till just now. Wow, nicely done! This was always my goal, but I have gotten to far away from the code recently, to be able to even think about it.  

Impressed sir, keep it up!

Hey Tranz good to see you around!

Yes I was able to get it into the coinstake tx, but I did get inspiration from some of Dooglus' work on CLAM. That being said, this is still experimental and I need to change the code of the receiving party to not see this as a transaction minted, and thus it would also mean an exchange or other automated party would need to update once the code is complete.

Edit - also I forgot to mention the best part. Free transactions

[billotronic]

Care to elaborate on "MultiSend CoinStake" ?

You didnt hear the news??!!!!?? I added a special functionality to MultiSend that lets you send the multisend tx in the actual staked block instead of waiting for all those confirms and then sending. I am 97% sure this needs extra work to make it compatible with exchanges, as it is now the daemon will see it as a minted transaction rather than received from another address.

ya know, that sounds vaguely familiar but in all honesty, I was probably drunk at the time.

that is pretty damn sexy.

[dalistar]

My wallet coin age are 10 days old
till now still minting and didnt pay out 

[fragilefungi]

My wallet coin age are 10 days old
till now still minting and didnt pay out  

My last four stakes were 55.7 days, 41.2 days, 28.6 days, and 112 days old.  HYP coins keep gaining weight for 30 days.  The coins just START staking after 8.8 days and the probability at that time is >0% but still not very high.

[Kushedout]

My wallet coin age are 10 days old
till now still minting and didnt pay out  

Hope this makes you feel better



http://imgur.com/QdoTbSP

[billotronic]

Patience is key

[Kushedout]

iDunks wallet



MinerFTWs wallet

[dalistar]

Patience is key

they said paid each 8 days ,,,,
I am no patient

so i will quit

[presstab]

Patience is key

they said paid each 8 days ,,,,
I am no patient

so i will quit

It is 8 days minimum. HYP is one of the highest difficulty PoS coins. If you are not patient, then yes you are correct it is not for you. If you are patient, you get a fairly generous stake reward.

[billotronic]

Patience is key

they said paid each 8 days ,,,,
I am no patient

so i will quit

It is 8 days minimum. HYP is one of the highest difficulty PoS coins. If you are not patient, then yes you are correct it is not for you. If you are patient, you get a fairly generous stake reward.

speaking of which, would there be any sort of universal way we could compare that across different coins? I vaguely remember chatting with you about net diff once and how its not always calculated the same ways... or did I just dream that?

[Tranz]

Care to elaborate on "MultiSend CoinStake" ?

You didnt hear the news??!!!!?? I added a special functionality to MultiSend that lets you send the multisend tx in the actual staked block instead of waiting for all those confirms and then sending. I am 97% sure this needs extra work to make it compatible with exchanges, as it is now the daemon will see it as a minted transaction rather than received from another address.

I didn't hear, till just now. Wow, nicely done! This was always my goal, but I have gotten to far away from the code recently, to be able to even think about it.  

Impressed sir, keep it up!

Hey Tranz good to see you around!

Yes I was able to get it into the coinstake tx, but I did get inspiration from some of Dooglus' work on CLAM. That being said, this is still experimental and I need to change the code of the receiving party to not see this as a transaction minted, and thus it would also mean an exchange or other automated party would need to update once the code is complete.

Edit - also I forgot to mention the best part. Free transactions

Yes the free transaction part was what I envisioned would be beneficial for S4C. I never dug deep enough to get that far, I always assumed it would require a fork to get it fully implemented, but so far not looking that way.

[presstab]

Care to elaborate on "MultiSend CoinStake" ?

You didnt hear the news??!!!!?? I added a special functionality to MultiSend that lets you send the multisend tx in the actual staked block instead of waiting for all those confirms and then sending. I am 97% sure this needs extra work to make it compatible with exchanges, as it is now the daemon will see it as a minted transaction rather than received from another address.

I didn't hear, till just now. Wow, nicely done! This was always my goal, but I have gotten to far away from the code recently, to be able to even think about it.  

Impressed sir, keep it up!

Hey Tranz good to see you around!

Yes I was able to get it into the coinstake tx, but I did get inspiration from some of Dooglus' work on CLAM. That being said, this is still experimental and I need to change the code of the receiving party to not see this as a transaction minted, and thus it would also mean an exchange or other automated party would need to update once the code is complete.

Edit - also I forgot to mention the best part. Free transactions

Yes the free transaction part was what I envisioned would be beneficial for S4C. I never dug deep enough to get that far, I always assumed it would require a fork to get it fully implemented, but so far not looking that way.

I thought the same myself, but when looking deeper you find that it is totally within the bounds of the protocol.

[altcoiner-]

This coins daemon is 100% impossible to sync...

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 31a471982f272fefaae842dbaa0ab1507b014162c40310c4dde0087714a66675
received block df1f9b6cb2da78fa9fbf
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block df1f9b6cb2da78fa9fbf7a651f5936e29d02b2fc0949d824524019e78521c45d
received block 2d9d163b348d29d5d66f
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 2d9d163b348d29d5d66f8c65497ce481a26c776c7dcc0a565bcabd75ba34af5b
received block f1385230f46c3040bce6
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block f1385230f46c3040bce674e0b6787729e311429ebf60226081dc2ceba9a48d24
received block 30f335481d6b4831eddb
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 30f335481d6b4831eddbd0151abe01db5efc63e5c2ae92b2a1ac7da9b8c70aeb
received block db95163b1389a1fed6ae
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block db95163b1389a1fe

I've synced around 170k blocks in 24 hours, at this rate it will take me over 10 days to sync the whole 1.9m blocks.

Is it just me or is this normal?