| rskip | title | created | author | purpose | layer | complexity | status | description |
|---|---|---|---|---|---|---|---|---|
376 |
Set version 2 to PowPeg migration transactions |
12-DEC-23 |
MI |
Usa |
Core |
1 |
Adopted |
| RSKIP | 376 |
|---|---|
| Title | Set version 2 to PowPeg migration transactions |
| Created | 12-DEC-23 |
| Author | MI |
| Purpose | Usa |
| Layer | Core |
| Complexity | 1 |
| Status | Adopted |
Since the implementation of RSKIP201 [1], peg-out transactions are created with version number 2 following the specification in BIP68 [2]. This RSKIP proposes that also PowPeg migration transactions are created with version 2 to be consistent with peg-out transactions.
Peg-out and migration transactions should be treatead equally by the Bridge and should both have the same format.
When a PowPeg composition change is executed and the migration process starts in the Bridge, migration transactions sending funds from the retiring to the newly active PowPeg address should be created using version 2.
This change is a hard fork and therefore all full nodes must be updated.
[1] RSKIP201
[2] BIP68
Copyright and related rights waived via CC0.