You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With RSKIP-170, implemented in the Iris hard fork, it is now possible to peg-in to any address. However, on the peg-out side, users can still only peg-out to the P2PKH bitcoin address that is derived from the Rootstock address that made the peg-out request. This poses an inconvenience to users, and is also somewhat detrimental to privacy as it forces address re-use.
I propose that Rootstock enables peg-outs to any bitcoin address, ideally in all of the widely-used legacy and modern formats (P2PKH, P2SH, P2WPKH, P2WSH, and P2TR -- excluding P2PK since no one uses this).
The text was updated successfully, but these errors were encountered:
With RSKIP-170, implemented in the Iris hard fork, it is now possible to peg-in to any address. However, on the peg-out side, users can still only peg-out to the P2PKH bitcoin address that is derived from the Rootstock address that made the peg-out request. This poses an inconvenience to users, and is also somewhat detrimental to privacy as it forces address re-use.
I propose that Rootstock enables peg-outs to any bitcoin address, ideally in all of the widely-used legacy and modern formats (P2PKH, P2SH, P2WPKH, P2WSH, and P2TR -- excluding P2PK since no one uses this).
The text was updated successfully, but these errors were encountered: