Porting PPC to modern Bitcoin codebase using Navcoin?

d5000 · May 19, 2017, 10:55pm

Just a quick question:

I was investigating in the last months which altcoins had already adopted Segwit (the well-known controversial Bitcoin scaling/malleability fix). Some days ago I discovered Navcoin. They seem to have ported Peercoin’s PoS to a modern 0.13 Bitcoin codebase and have recently activated Segwit.

Could that be a base for further Peercoin development? I haven’t checked the details of NAV’s implementation, I admit. But I would love Peercoin to have a more modern codebase and a malleability fix like Segwit on board (No, I’m not a “bitcoin core hardliner”).

Their Github account is here:

Cheers
d5000

Sentinelrv · May 20, 2017, 12:20am

@hrobeers @peerchemist

hrobeers · May 20, 2017, 4:59am

We planning to base Peercoin 0.7 on the latest Bitcoin.

d5000 · May 20, 2017, 6:54am

Thank you for your answer! Looking forward to 0.7 then

Is there a development roadmap? As of now I’ve only found the statement that the development team is now larger and that you’ll focus on PeerAssets now.

hrobeers · May 20, 2017, 7:23am

Actually I’ve been doing quite some work on the upcoming 0.6 release: testing, bugfixing and backporting OP_CODES like CLTV and CSV.

And some protocol proposals you can find here:

github.com

peercoin/rfcs/blob/master/RFCs-by-status.md

# RFCs by current status

A list of all RFCs by their current status.

## Active RFCs


## Proposed RFCs

 - [#0002 Coinstake Transaction Split](./text/0002-split-coinstake-transaction/0002-split-coinstake-transaction.md)
 - [#0003 Multi-signature Minting](./text/0003-multisig-minting/0003-multisig-minting.md)
 - [#0005 Unspendable Zero Outputs](./text/0005-unspendable-zero-outputs/0005-unspendable-zero-outputs.md)
 - [#0006 Remove Proof-of-Work Block Signature](./text/0006-remove-pow-block-signature/0006-remove-pow-block-signature.md)
 - [#0007 Round Transaction Fees Up To 0.001](./text/0007-round-transaction-fees-up-to-0.001/0007-round-transaction-fees-up-to-0.001.md)
 - [#0008 Increase OP_RETURN size limit](./text/0008-increase-op-return-size-limit/0008-increase-op-return-size-limit.md)
 - [#0010 MIN_FEE as standardness rule](./text/0010-min-fee-as-standardness-rule/0010-min-fee-as-standardness-rule.md)

## Agreed RFCs

 - [#0004 Remove Transaction Timestamp](./text/0004-remove-transaction-timestamp/0004-remove-transaction-timestamp.md)

This file has been truncated. show original

skull · May 28, 2017, 12:23am

Yes, please integrate that Segwit stuff, so that Peercoin could be a base for the Lightning Network, which is a great thing and would be a chance for Peercoin to become a sustainable base for fast payment.

As you can see, Lightning Network has a Wikipedia article, where Bitcoin and Litecoin are mentioned (Litecoin because it already has the ability of serving as a base for the Lightning Network). Would be so nice to have the good old Peercoin listed there.

Nagalim · May 28, 2017, 12:44am

We do no intend on implementing segwit at the present. Any maleability fix will allow lightning network.

There are some other OP codes that are needed as well, as far as I understand. Those we do have plans to implement.