| rskip | title | created | author | purpose | layer | complexity | status | description |
|---|---|---|---|---|---|---|---|---|
374 |
Reestablish the number of block confirmations for a PowPeg migration period |
15-FEB-23 |
MI |
Usa,Sec |
Core |
1 |
Adopted |
| RSKIP | 374 |
|---|---|
| Title | Reestablish the number of block confirmations for a PowPeg migration period |
| Created | 15-FEB-23 |
| Author | MI |
| Purpose | Usa,Sec |
| Layer | Core |
| Complexity | 1 |
| Status | Adopted |
This RSKIP proposes a change to the number of block confirmations required for a PowPeg migration period.
As described in RSKIP357 [1], as part of the efforts done to solve the peg-outs service incident [2] it was necessary to increase the PowPeg migration period from 10,585 to 172,800 blocks to give enough time for a mining pool to process the non-standard transactions before the migration period finishes.
Once the issue with the peg-outs has been solved, all migration transactions have been mined and the service has been resumed, this RSKIP proposes to restore the PowPeg migration period back to its original value of 10,585 blocks.
The number of block confirmations for a PowPeg migration period is changed back to 10,585 blocks. Since this change is a hard fork, the new value should become active only when activated by the network upgrade that includes this change.
This change is a hard fork and therefore all full nodes must be updated.
[1] RSKIP 357
[2] Incident report: RSK peg-out service outage
Copyright and related rights waived via CC0.