Peercoin v0.5.1 RC2 build ready

Protocol
1

Official builds ready for testing:
http://sourceforge.net/projects/ppcoin/files/0.5.1%20RC2/

This release candidate includes patches from v0.4.2 thus should be compatible with the current mainnet blockchain.

$ openssl dgst -sha256 ppcoin-0.5.1*
SHA256(ppcoin-0.5.1ppc.rc2-linux.tgz)= 626344beb58b74f1a46b8dcf9ea6f9ccdc9b87c59dd9d662bf4f1e865ac918fa
SHA256(ppcoin-0.5.1rc2-win32-setup.exe)= cc4a80e30bc30d3d087024ad62fbfa309230398b0a617aae18b2a9d73d6aa067
2

Has peerunity been updated? [member=28683]Ben[/member]

3

I would be interested to know what changes were made in v0.5.1 vs v0.4? Is that listed anywhere?

4

You can download source codes of v0.4 and v0.5.1, and then compare each file using tools like SourceGear DiffMerge.

5

Im interested too. Thanks

6

sahkan, Escalicha

[quote=“Sunny King, post:1, topic:3639”]Weekly Update #160

[ul][li]Peercoin v0.5 protocol is under review this week. The protocol adjustment includes:[/li]
[li]Allow transaction output to have zero value, a requirement to support data transaction usage such as peermessage.[/li]
[li]Protocol adjustment to improve security.[/li]
[li]Expect further review and testing the following week.[/li][/ul]

Have fun![/quote]

Peercoin: v0.5 protocol adjustment

Allow transaction output value to be 0.
Use dynamic stake modifier for kernel generation
Protocol switch schedule:
Testnet switch - Nov 16, 2015
Mainnet switch - Mar 15, 2016

7

Awesome, thanks SK! Time to get moving again on my end.

8

You can download source codes of v0.4 and v0.5.1, and then compare each file using tools like SourceGear DiffMerge.[/quote]

I can go to the GitHub and compare the code, but what is the value added for the code?

9

[quote=“bruter, post:6, topic:3748”]sahkan, Escalicha

[quote=“Sunny King, post:1, topic:3639”]Weekly Update #160

[ul][li]Protocol adjustment to improve security.[/li][/ul][/quote]

Peercoin: v0.5 protocol adjustment

Use dynamic stake modifier for kernel generation

[/quote]

What other protocol adjustments or just 1? What do we mean by “dynamic stake modifier”? What’s the purpose of it?

10

Should we start running it in production?

11
What other protocol adjustments or just 1? What do we mean by "dynamic stake modifier"? What's the purpose of it?

the purpose is to limit the timespan where you can determine when you stake. This is to tackle the long range attack.

12

Hi Sunny,

assuming that one controls large Sha256 Mining-facilities, would it be possible to attack Peercoin within those ~10 minutes that pass between two Proof-of-Stake blocks? What prevents 6 Proof-of-work blocks in sequence to be replaced by 7 secretly minded Proof-of-work blocks?

User Sakhan pointed me to a comment in your code, which mentions that Proof-of-work blocks are immediately checkpointed:

Does that prevent such an attack?
And don’t we need a solution that works without checkpoints?
A simple solution could be to require 6 Proof-of-Stake blocks for a transaction to confirm.

The discussion between Sakhan, me and others is here:
https://www.peercointalk.org/index.php?topic=4383.0

Note also that in our live-network, 8 Proof-of-work blocks in sequence have been found between Blocks 218490 to 218497.

13

look up the long range attack thread.