rBTC Conversion: Peg in and Peg Out
In this article, we explain step by step on how to convert from BTC to rBTC, and vice versa. The process of conversion utilises a Powpeg mechanism. Thus, these conversions are referred to as peg-ins and peg-outs.
- Peg-in:
- A conversion from BTC to rBTC
- Locks BTC in the BTC Federation address
- Releases rBTC in the Rootstock derived address
- Peg-out:
- A conversion from rBTC to BTC
- Locks rBTC on the Rootstock network
- Releases BTC on the Bitcoin network
Address Compatibility
There are two main ways to perform a peg-in:
-
Direct Peg-in (Legacy): You can send funds directly from your wallet to a Federation address or using the PowPeg App. This method is only supported for two specific address types:
- Legacy Addresses (P2PKH): Starts with a
1. These addresses are the original Bitcoin address format. - SegWit Compatible Addresses (P2SH-P2WPKH): Starts with a
3. These addresses support Segregated Witness (SegWit), a type of upgrade to the Bitcoin network.
- Legacy Addresses (P2PKH): Starts with a
-
Using the PowPeg App (Modern): For other address types, a specialized tool like the PowPeg App has been built for smoother UX and faster peg-ins. Required for addresses such as:
- Native SegWit (Bech32): Starts with
bc1. Starts withbc1. This is the newest address format. You cannot use it for a direct peg-in because it requires theOP_RETURNfield to be included in the transaction. Modern tools like the PowPeg App include this field directly from the destination address.
- Native SegWit (Bech32): Starts with
The address verifier on this page is designed to check for direct peg-in compatibility only. If you are using a Native Segwit (Bech32) address, you will need to use a tool like the PowPeg App to perform a peg-in.