SegWit = Space travel door ways
-
Just throwing this out there, sorry way beyond my know how… What is the chances FTC devs could create a version of segwit that fixes malleability problem, but is simplified and doesn’t do the scaling things that aren’t needed?
-
It is quite credible that FTC will need to adjust the parameters for Seg-wit, to be in line with FTC block times , or other settings … For instance, Bitcoin suggest a block size (for 10mins) we may require to change that to 1/10, because we do 10 blocks in 10 mins, etc etc …
But these are all the customizations the “Devs” need to do, i.e. chores, which absolutely necessary to make the forked, Bitcoin designed features, work with FTC settings. The process is needed to have, at least someone, a guide or references, so anyone researching can understand these features as well.
One draw back is, it was @Lizhi who has done a lot of research in this area, Seg-Wit, but wasn’t bringing along support, or producing the full package of documentation and finish, releasing unofficial and buggy binaries, that has slowed us down. From my comms @Lizhi isn’t available to do the high quantity of code (has was paid for), would continue to assist and advice and run his Chinese FTC site.
Certainly his mining of v4 database compatible blocks has caused us issues, which we have a backlog to fix to get back to square one, so his work is accepted, and he is still an Admin on FTC Github, everyone must comply with a release procedure and @Wellenreiter is overseeing that. It’s a minimum requirement of being involved in a (community) software project, even admins or rockstar programmers, follow some sensible guidelines.
