[HYP] HyperStake | Generous Reward Staking | Advanced Staking Controls & Wallet - page 72.

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: ?? on ??

hello - its been a while ! I have been out of the crypto world for a while now, but now have more time to commit.

HYP was my first "real" coin i got involved in so would love to see it succeed again - I am starting from a 0 HYP position (unless there is something lurking in one of my wallets which I am trying to get all synced up again!) so nothing to gain in the short term.

Please let me know if there are any active projects which I can help with ?

jaybeeuk great to see you back here. I myself have stayed pretty busy with a lot of other crypto-currency 'for hire' jobs, and have unfortunately not had time to develop HYP within the last year. Fortunately it was left in a great state and still works very well. I am starting up with a few ideas and looking over the codebase.

I don't know if there are any active projects, I would guess not. But let me know if you start working on something.

I would personally like to work on some code for staking activated governance system implemented in HyperStake. It would allow us to make decisions for HYP without as much smoke and mirrors. For example, there is absolutely no reason to continue hashing the block header in X11 instead of sha256, it just adds over 11 times more strain to the syncing process and no additional security.

BitsifyOfficial

sr. member

Activity: 284

Merit: 250

Quote from: bitmaster1x on May 23, 2017, 05:54:26 AM

Quote from: ?? on ??

hello - its been a while ! I have been out of the crypto world for a while now, but now have more time to commit.

HYP was my first "real" coin i got involved in so would love to see it succeed again - I am starting from a 0 HYP position (unless there is something lurking in one of my wallets which I am trying to get all synced up again!) so nothing to gain in the short term.

Please let me know if there are any active projects which I can help with ?

Welcome back into the fold. You can go, but you can never leave. Grin

Lol so true! It haunts you till the day you die Cheesy

bitmaster1x

legendary

Activity: 1288

Merit: 1000

CRYPTO-CITY.COM 🌟 Communities

Quote from: ?? on ??

hello - its been a while ! I have been out of the crypto world for a while now, but now have more time to commit.

HYP was my first "real" coin i got involved in so would love to see it succeed again - I am starting from a 0 HYP position (unless there is something lurking in one of my wallets which I am trying to get all synced up again!) so nothing to gain in the short term.

Please let me know if there are any active projects which I can help with ?

Welcome back into the fold. You can go, but you can never leave. Grin

bitmaster1x

legendary

Activity: 1288

Merit: 1000

CRYPTO-CITY.COM 🌟 Communities

Quote from: presstab on May 22, 2017, 10:36:30 AM

Quote from: iantunc on May 21, 2017, 03:32:38 PM

Quote from: presstab on May 21, 2017, 01:28:05 PM

The best thing to do is to not create transactions that large. I think there is even a limit to transaction size, I will have to look that up in the code.

I have looked in the code. There is a limit of 100 kb per wallet transaction in the bitcoin code (manual transactions can be as big as the max block size). I haven't found such limit in the HYP code yet. Anyway, I also think that it's not a good practice to create too heavy transactions which consume not only disk space but CPU resources of every node and can potentially be an attack vector.

Yes I agree, just be a responsible HYPster and create smaller transactions if possible.

On another note, has anyone thought about the possibility of using segwit with PoS? I have begun looking through the segwit code for bitcoin. Although we don't have a scaling problem, segwit solves some other problems such as malleability. It could be interesting subject to explore.

That does sound interesting, I've not seen anyone try to push HYP to its limits yet... However, I'm sure if it gets popular someone would likely try.

Something that might be of interest to look into over time is the wallets inability to deal a large number of records in the wallet.dat. This isn't HYP specific, but a general crypto wallet DB issue. Maybe a new parallel DB core engine and schema? Someone might have fun with this.

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: iantunc on May 21, 2017, 03:32:38 PM

Quote from: presstab on May 21, 2017, 01:28:05 PM

The best thing to do is to not create transactions that large. I think there is even a limit to transaction size, I will have to look that up in the code.

I have looked in the code. There is a limit of 100 kb per wallet transaction in the bitcoin code (manual transactions can be as big as the max block size). I haven't found such limit in the HYP code yet. Anyway, I also think that it's not a good practice to create too heavy transactions which consume not only disk space but CPU resources of every node and can potentially be an attack vector.

Yes I agree, just be a responsible HYPster and create smaller transactions if possible.

On another note, has anyone thought about the possibility of using segwit with PoS? I have begun looking through the segwit code for bitcoin. Although we don't have a scaling problem, segwit solves some other problems such as malleability. It could be interesting subject to explore.

iantunc

sr. member

Activity: 433

Merit: 250

We are the first to program your future (c)

Quote from: presstab on May 21, 2017, 01:28:05 PM

Quote from: bitmaster1x on May 20, 2017, 06:12:36 PM

Quote from: iantunc on May 20, 2017, 03:27:27 AM

Quote from: bitmaster1x on May 19, 2017, 05:54:53 PM

Quote from: presstab on May 19, 2017, 04:26:13 PM

Quote from: bitmaster1x on May 19, 2017, 02:54:45 PM

Quote from: presstab on May 19, 2017, 02:25:17 PM

Quote from: bitmaster1x on May 19, 2017, 01:55:59 PM

@Presstab.

I've noticed that when selecting coins for splitting. If the inputs are over 400-500 (I can't remember the exact number) it will fail.

Yeah thats way too large. Honestly it has a hard time if it is more than 100, maybe I should put a hard cap in there.

The majority of crypto wallets suffer from this DB issue and once the file size gets to around 500MB or more it virtually becomes unusable.

Wait i thought you meant splitting into 400-500 inputs. Is that not what you meant?

Sorry about that... the latter stuff is just the byproduct of all the stuff combined (as a large wallet.dat file), but yes, the number of inputs is the main culprit which basically affect the wallets ability to send, combine or split because after a certain number of inputs it fails whether it is selected from the coin control or automatically.

If the big number of UTXO's is your staking strategy (mine too), and that makes your life difficult, you can scale the wallet horizontally, i.e., set up a second staking machine and move a part of UTXO's there. It also adds extra security. I'm starting to think about it

Ya. I have like 10 machines, but it definitely is an issue when sending a transaction and if it includes over a certain number of blocks (over 500) it will fail to create the transaction.