[RFC-0001] Stabilizing PoS block spacing


We recently created a RFC repository for proposing and discussing improvements to peercoin and it’s tools.

I’m proud to announce the first proposal: Exponential PoS Target for Block Time Stabilization

Feel free to post any thoughts or feedback in this thread, or to join the discussion on github.


Social media links:

Peercoin blocks on steriods

@hrobeers told me this is impossible to do with PoW, so it would give a huge advantage to Peercoin if we were able to make our blocks more predictable and consistent/reliable. I personally had to wait about 30 minutes the other night for the next block, very frustrating.


I moved this to the new board to track RFCs. Just to be clear, it is not hidden away on an empty board because any topics in sub-boards will display in the main board, in this case the Peercoin board, so it will receive more eyes.


In some BIPs, https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki, I saw mention of consensus including soft fork, hard fork, etc. https://github.com/bitcoin/bips/blob/master/bip-0099.mediawiki … these could be helpful to incorporate in the Peercoin RFC’s

Peercoin projects now uses RFC format for protocol improvement proposals

After some tests with the modified peercoin node, I decided to redefine the exponential function, so it has the larger difficulty steps in the first seconds after the previous block, so that the difficulty steps follow closer when time progresses.

This ensures that there is little chance to have simultaneous stakes right after a difficulty step.

RFC update following soon.


Updated the RFC!

This graph summarizes the changes :stuck_out_tongue: