This client is compatible with the Peercoin network as long as SegWit is not activated. If SegWit goes live on the network this client will be updated with a checkpoint that will reject the SegWit fork. We hope that forking won’t be necessary due to lack of support for SegWit, but we must prepare for the worst. If push comes to shove we hope most users will gather behind PeercoinOG and a Segwit free chain.
Maybe a better description on the Github page about pros and cons of segwit would be useful. I’m thinking to myself why couldn’t I trust the existing peercoin team/client to make the right decision and it’s not clear to me why I should switch to this new client.
Stating what made you build this in the first place might be beneficial aside from I’m afraid of something which might or might not come?
If it’s a mirror copy of the existing client it will be maintained forever in parallel just in case segwit comes even if the peercoin team does not want segwit and for the next x years until you feel comfortable that the threat has passed?
Note that I have not been following anything about segwit but if you’re looking for mass adoption of PeercoinOG more details would be useful.
I made this client since some people are pushing for SegWit in Peercoin. You have to do your own research to find out if you are for or against SegWit. If you are against SegWit like me, you now have a client to run that will fork off if SegWit activates on the Peercoin network.
Segwit is not needed for lightning, but it is the fastest way there. Lightning is useful for PA and other applications. Keeping up with a modern codebase is important, if OG can do that, then it may garner support. I don’t think ‘attack’ is the right word for any of this, it doesn’t have to be antagonistic.
Interesting development, will follow this thread and any further developments on Github.
It is good to have choices over having choices been made for you. Looking forward to further pros and cons of “to Segwit or not to Segwit” on the Peercoin blockchain.