Time to read: 1 min
完全なドキュメント索引については llms.txt
Frequently Asked Questions (FAQs)
Here, you can find a list of frequently asked questions (FAQs) about the PowPeg App.
Summary
Frequently asked questions about the PowPeg App. For prerequisites, supported wallets, and supported browsers, see the linked guides below.
Questions and answers
| # | Question | Answer |
|---|---|---|
| 1 | Requirements to use PowPeg App? | See prerequisites |
| 2 | Common peg-out errors? | See peg-out common errors |
| 3 | Derive BTC private key after peg-out? | See deriving electrum |
| 4 | SegWit vs Legacy addresses? | Legacy is the original format. SegWit separates witness data and has lower fees |
| 5 | Address types for peg-in? | See supported addresses |
| 6 | Why use PowPeg App vs protocol directly? | Simpler peg-in UX. See overview |
| 7 | Supported browsers? | See supported browsers |
| 8 | Supported wallets? | See supported wallets |
| 9 | Native peg-in completion time? | ~17 hours |
| 10 | Fast Mode peg-in time? | ~20 minutes via liquidity providers |
| 11 | Native peg-out completion time? | ~34 hours |
| 12 | Fast Mode peg-out time? | ~20 minutes via liquidity providers |
| 13 | Peg-in min and max? | Min 0.005 BTC. Max 10 BTC |
| 14 | Peg-out min and max? | Min 0.004 rBTC. Max 10 rBTC |
| 15 | Native peg-out BTC destination? | Derived from your signature. See derivation details |
| 16 | Trezor "Forbidden key path" error? | Set Perform Safety Checks to PROMPT in Trezor Suite |
| 17 | Cannot connect Trezor? | Allow pop-ups for PowPeg domain. Confirm Trezor Suite safety checks. Retry connection |
| 18 | Peg-out complete but no BTC in Trezor/Electrum? | Use Electrum with correct derivation path. See deriving electrum troubleshooting |
Related guides
- To know more about the requirements, see prerequisites
- To know more about the common errors, see common errors.
- See section on deriving electrum for how to export a private key.
- Legacy address is the original BTC address while SegWit is the newer address format with lower fees. SegWit means Segregated Witness, where Segregated is to separate and Witness is the transaction signatures involved with a specific transaction.
- For information on the type of addresses to use when performing a peg-in transaction
- See the supported addresses page.
- The PowPeg app has a lot of benefits including enabling easier and simplified peg-in transactions.
- See why use the PowPeg? for a list of benefits when you use the application.
- To know more about the supported browsers
- See the supported browsers.
- To know more about the requirements;
- See supported wallets.
- native pegin needs 17 hours to be completed
- Using fast mode, pegin time has been significantly reduced to ~20 mins. Note: In Fast Mode, we utilize Liquidity Providers (LPs) to expedite the transfer of funds to end users. These third-party providers can set their own transfer times. This information is displayed on the screen, allowing users to select the LP that offers the most suitable transfer speed for their needs.
- native pegout needs 34 hours to be completed
- Using fast mode, pegout time has been significantly reduced to ~20 mins. Note: In Fast Mode, we utilize Liquidity Providers (LPs) to expedite the transfer of funds to end users. These third-party providers can set their own transfer times. This information is displayed on the screen, allowing users to select the LP that offers the most suitable transfer speed for their needs.
- The minimum values allowed when creating a peg-in transaction is 0.005 BTC.
- The maximum values allowed when creating a peg-in transaction is 10 BTC.
- The minimum values allowed when creating a peg-out transaction is 0.004 RBTC.
- The maximum values allowed when creating a peg-out transaction is 10 RBTC.
- During the pegout process, the destination address of your BTC is derived from your signature, this enables one to know which address will receive the BTCs.
- See the Derivation details page
- The latest versions of Trezor Suite have implemented a security rule to disable its use with non-standard key paths. Therefore, the user must explicitly set Perform Safety Checks to PROMPT option in Trezor Suite in order to use the Trezor wallet in the PowPeg application.
- If is not enabled you will receive this error
- This video explains how to enable Perform Safety Checks to PROMPT on Trezor Suite Enabling Prompt for Key Path

- The PowPeg App uses Trezor Connect in a browser pop-up. Allow pop-ups for
https://powpeg.rootstock.io(Mainnet) orhttps://powpeg.testnet.rootstock.io(Testnet). See Trezor will not connect (browser pop-up blocked).- Confirm Perform Safety Checks is set to PROMPT in Trezor Suite. See FAQ 16 below.
- Unplug and replug your Trezor, unlock it with your PIN, and click Retry in the PowPeg App.
- Trezor Suite cannot show peg-out Bitcoin addresses at the custom derivation path. Use Electrum as described in Viewing a derived bitcoin address.
- If you do not use a BIP39 passphrase on Trezor, leave the passphrase fields empty in Electrum. Entering a value there opens a different wallet and the balance can look like zero.
- Electrum may prompt for a passphrase if Passphrase is enabled in Trezor Suite (Settings → Device → Passphrase). You can still leave the fields empty when you do not use a passphrase wallet.
- See Troubleshooting: peg-out completed but balance is zero and common errors.
Next
See Glossary section for explanation of terms.

