[ANN] [PPC] PPCoin 0.3.0 Release - Upgrade Required

[H@ml3t]

Just use any standard bitcoin miner. Largest pool is http://ppcpool.bitparking.com/pool

[Sunny King]

2 days left before protocol switch to v0.3. Please upgrade to 0.3.0 as soon as possible if you haven't done so.

[coinotron]

This morning  I performed upgrade. Coinotron is using version 0.3.0 now.

[Sunny King]

Final reminder: less than 1 day before protocol switch. Upgrade as soon as possible to v0.3.0 if you haven't done so. I will be watching the switch on the network tomorrow.

[mr_random]

Upgraded.

[doublec]

What is the exact switch over time?

[Sunny King]

Exact switch time is
Wed 20 Mar 2013 17:20:00 UTC

[SalvorHardin]

Is there anything strange about PPC block 38018 to 38040?  Someone generated like 20 blocks of Proof of Stakes in around 10 minutes, using 250/500 PPC as stake.  Is it related to the old vulnerabilities where you can speed up PoS block generation, discovered by Jutarul?     We are suppose to upgrade to the new version by today too.

[doublec]

We are suppose to upgrade to the new version by today too.

The upgrade hasn't happened yet. About 14 hours to go.

[Jutarul]

Is there anything strange about PPC block 38018 to 38040?  Someone generated like 20 blocks of Proof of Stakes in around 10 minutes, using 250/500 PPC as stake.  Is it related to the old vulnerabilities where you can speed up PoS block generation, discovered by Jutarul?    We are suppose to upgrade to the new version by today too.

The new protocol proposed by Sunny should "smoothen out" the effect of putting offline stake online. However, the fact that these rapid block generation cycles occur may not be a problem of the POS scheme itself, it's rather an outcome of non-competitive mining. Obviously, we need a more aggressive POS mining landscape. Maybe the incentives are too low right now?

[SalvorHardin]

The fast generation of PoS block is still ongoing, about 55 out of last 60 blocks, and in the amount of 250/500 PPC, so I presume it's the same person.  Is this normal or something that can be safely ignored?  Or in Jutarul's word, this can actually be "good" for PPC, attracting more people (including potential offenders) to generate PoS blocks and thus making the PPC network more secure, and not someone exploiting the vulnerability by hastening the cycle?

[doublec]

The fast generation of PoS block is still ongoing, about 55 out of last 60 blocks, and in the amount of 250/500 PPC, so I presume it's the same person.

This is me. It's a wallet I created by sending approximately 250-500 PPC every 5-10 minutes over the period of a month. The actual amount and time depended on how much PPC I had available. I kept this running on a 24x7 node and it averaged about 150 blocks immature constantly after about 40 days. The machine it was on had a hard drive failure and it's been offline for a week or so. Having recovered the wallet from backup I've fired it up again and I guess it's catching up. For the curious the ppcoind node this runs on uses about 80% CPU idling - I assume that POS stack code takes a bit of CPU while cycling through so many transactions.

[SalvorHardin]

The fast generation of PoS block is still ongoing, about 55 out of last 60 blocks, and in the amount of 250/500 PPC, so I presume it's the same person.

This is me. It's a wallet I created by sending approximately 250-500 PPC every 5-10 minutes over the period of a month. The actual amount and time depended on how much PPC I had available. I kept this running on a 24x7 node and it averaged about 150 blocks immature constantly after about 40 days. The machine it was on had a hard drive failure and it's been offline for a week or so. Having recovered the wallet from backup I've fired it up again and I guess it's catching up. For the curious the ppcoind node this runs on uses about 80% CPU idling - I assume that POS stack code takes a bit of CPU while cycling through so many transactions.

Thanks for the details on how the system actually works.  As most of us would not have had enough PPC or the time dedicated to test it empirically.

[Sunny King]

This is me. It's a wallet I created by sending approximately 250-500 PPC every 5-10 minutes over the period of a month. The actual amount and time depended on how much PPC I had available. I kept this running on a 24x7 node and it averaged about 150 blocks immature constantly after about 40 days. The machine it was on had a hard drive failure and it's been offline for a week or so. Having recovered the wallet from backup I've fired it up again and I guess it's catching up. For the curious the ppcoind node this runs on uses about 80% CPU idling - I assume that POS stack code takes a bit of CPU while cycling through so many transactions.

Hi Chris, when you generate these blocks which version of the client were you running? Is it the latest v0.3 client?

The protocol has been switched over to 0.3 today. The situation should improve gradually. Like Jutarul said, stake participation rate might have also contributed to the problem.

The average age of stake is meant to be eventually closer to 90 days than 30 days. In 0.3 protocol a change was made so that the weighting starts from 0 at the 30-day minimum age. This should help strengthen proof-of-stake protection when difficulty is still low.

[Bennmann]

How does a newb like me use GUIminer to simply and quickly with minimal typing and -flags start mining PPC? There are no guides in the Wiki, and all other guides are for bitcoin directories....

[peepee]

Is there a way to see how old the coins are in each address and/or how long they've been sitting?

[btcusr]

I will be following up with PPC, and I like PPC better than litecoin and ripples now.

so, my favorites are now;  bitcoin, ppcoin, ripple, litecoin; in the same order.

This blog was informative,

http://themisescircle.org/blog/2013/06/24/the-proof-of-work-concept/

[joinmicah]

OK I am screwed I Lost several PPC  14.393888 PPC It seems I never updated the Client before March 20th which I could of sworn that I did.
I am getting a Unexpected Visual C++ Runtime Error twice in a row and than the Client Closes.

[samson]

OK I am screwed I Lost several PPC  14.393888 PPC It seems I never updated the Client before March 20th which I could of sworn that I did.
I am getting a Unexpected Visual Basic Runtime Error twice in a row and than the Client Closes.

Upgrade it then

[joinmicah]

PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
DB_LOGC->get: LSN: 1384/5911106: read: DB_RUNRECOVERY: Fatal error, run database recovery
DB_TXN->abort: log undo failed for LSN: 1384 5911106: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: fatal region error detected; run recovery