Skip to content

Commit

Permalink
Merge pull request #483 from oasisprotocol/matevz/remove-bitpie
Browse files Browse the repository at this point in the history
Remove BitPie chapter
  • Loading branch information
matevz authored Aug 3, 2023
2 parents 81a4d5a + 9a70b9e commit d43491a
Show file tree
Hide file tree
Showing 19 changed files with 118 additions and 118 deletions.
Binary file removed docs/general/images/wallet/bitpie/google_play.png
Binary file not shown.
Binary file removed docs/general/images/wallet/bitpie/icon.png
Binary file not shown.
Binary file removed docs/general/images/wallet/bitpie/playstore.png
Binary file not shown.
Binary file removed docs/general/images/wallet/bitpie/screen1.png
Binary file not shown.
Binary file removed docs/general/images/wallet/bitpie/screen2.png
Binary file not shown.
Binary file removed docs/general/images/wallet/bitpie/screen3.png
Binary file not shown.
Binary file removed docs/general/images/wallet/bitpie/screen4.png
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed docs/general/images/wallet/bitpie/testnet1.png
Binary file not shown.
Binary file removed docs/general/images/wallet/bitpie/testnet2.png
Binary file not shown.
Binary file removed docs/general/images/wallet/bitpie/testnet3.png
Binary file not shown.
2 changes: 0 additions & 2 deletions docs/general/manage-tokens/README.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,6 @@ This documentation will guide you on how to use your ROSE tokens, where to keep

* For **self-custody**, we recommend using one of our **official** [**Oasis Wallets**](oasis-wallets/README.mdx), [Web](oasis-wallets/web.md) or [Browser Extension](oasis-wallets/browser-extension.md).
* ROSE is supported via three [**custody providers**](holding-rose-tokens/custody-providers.md): [Copper.co](https://copper.co), [Anchorage](https://anchorage.com) and [Finoa](https://finoa.io).
* If you want a self-custody **mobile app**, we recommend [Bitpie Wallet](holding-rose-tokens/bitpie-wallet.md).
* For extra security with self-custody, we recommend using the [Ledger](https://www.ledger.com) wallet with one of our official [Oasis Wallets](oasis-wallets/README.mdx).
* For experienced developers/power users, we offer [Oasis CLI Tools](advanced/oasis-cli-tools/README.md).

Expand All @@ -27,6 +26,5 @@ For your own security and peace of mind, please only use wallets that are listed
findSidebarItem('/general/manage-tokens/oasis-wallets/'),
findSidebarItem('/general/manage-tokens/advanced/oasis-cli-tools/'),
findSidebarItem('/general/manage-tokens/holding-rose-tokens/custody-providers'),
findSidebarItem('/general/manage-tokens/holding-rose-tokens/bitpie-wallet'),
findSidebarItem('/general/manage-tokens/holding-rose-tokens/ledger-wallet'),
]} />
123 changes: 107 additions & 16 deletions docs/general/manage-tokens/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,36 +3,110 @@
This documents answers frequently asked questions about Oasis Wallets and 3rd
party wallets & custody providers supporting ROSE tokens.

### How can I transfer ROSE tokens from my [BitPie wallet](holding-rose-tokens/bitpie-wallet.md) to my Oasis Wallet?
### How can I transfer ROSE tokens from my BitPie wallet to my Oasis Wallet?

:::caution

BitPie wallet doesn't use the standardized account key generation process specified in [ADR 0008](../../adrs/0008-standard-account-key-generation.md). Consequently, your **Bitpie wallet's mnemonic phrase will not open the same account in Oasis Wallet**.
BitPie wallet doesn't use the [standardized Oasis mnemonic derivation][adr8].
Consequently, your **Bitpie wallet's mnemonic phrase will not open the same
account in the Oasis Wallet**.

:::

The **preferred way** is to create a new wallet with an Oasis Wallet and transfer the tokens to this new address using your BitPie wallet. The cost (i.e. transaction fee) should be negligible.
As of May 2023, the newer versions of BitPie wallet [do not support transferring
tokens on the Oasis network anymore][bitpie-announcement]. Previously, sending
tokens from the BitPie wallet to the address generated by the Oasis wallet was
the preferred migration procedure.

If your tokens are staked/delegated, then you need to debond them first which will take approximately 14 days. Afterwards, you can transfer them to the new Oasis Wallet address and stake/delegate them via an Oasis Wallet again.
Thus, the only way to access your tokens stored on your BitPie wallet is to
obtain the private key of your BitPie's wallet in one of the two ways:

**Alternatively** however, if you do not want to transfer the tokens over the network, you can export the private key from your BitPie wallet and import it in Oasis Wallet in 2 steps:
- [Export private key from a working BitPie wallet](#how-can-i-export-oasis-private-key-from-a-working-bitpie-wallet)
- [Convert BitPie mnemonic to Oasis private key offline](#how-can-i-export-oasis-private-key-if-bitpie-doesnt-show-my-rose-account-anymore)

1. [Export your BitPie wallet's Oasis account private key](faq.md#how-can-i-export-my-bitpie-wallets-oasis-account-private-key)
2. [Open your Oasis wallet via exported private key in Oasis Wallet - Web](../../general/manage-tokens/oasis-wallets/web.md#open-wallet-via-private-key)
Once you obtained the private key, you can
[import it to the Oasis wallet][oasis-wallet-import-private-key] and access
your assets.

### How can I export my [BitPie wallet](holding-rose-tokens/bitpie-wallet.md)'s Oasis account private key?
[bitpie-announcement]: https://medium.com/bitpie/announcement-on-suspension-of-support-for-algo-and-rose-fc35cb322617
[adr8]: ../../adrs/0008-standard-account-key-generation.md
[oasis-wallet-import-private-key]: ../../general/manage-tokens/oasis-wallets/web.md#open-wallet-via-private-key

### How can I export Oasis private key from a working BitPie wallet?

:::tip

Chinese users can follow the [official BitPie support article] on how to export
the Oasis private key from your BitPie wallet.

[official BitPie support article]: https://bitpie.zendesk.com/hc/zh-cn/articles/6796209839503

:::

If you have an existing ROSE account in your BitPie wallet, you can obtain the
wallet's private key by following the steps below.

On the main BitPie wallet screen, click on the "Receive" button.

![](../images/wallet/bitpie/mainscreen.png)
![BitPie main screen](../images/wallet/bitpie/mainscreen.png)

The QR code with your ROSE address will appear. Then, in the top right corner, tap on the kebab menu "⋮" and select "Display Private Key"_._

![](../images/wallet/bitpie/show_private_key.png)
![BitPie show private key](../images/wallet/bitpie/show_private_key.png)

BitPie wallet will now ask you to enter your PIN to access the private key.

Finally, your account's private key will be shown to you encoded in Base64 format (e.g. `YgwGOfrHG1TVWSZBs8WM4w0BUjLmsbk7Gqgd7IGeHfSqdbeQokEhFEJxtc3kVQ4KqkdZTuD0bY7LOlhdEKevaQ==`) which you can [import into Oasis Wallet](oasis-wallets/web.md#access-an-existing-wallet).
Finally, your account's private key will be shown to you encoded in Base64
format (e.g.
`YgwGOfrHG1TVWSZBs8WM4w0BUjLmsbk7Gqgd7IGeHfSqdbeQokEhFEJxtc3kVQ4KqkdZTuD0bY7LOlhdEKevaQ==`)
which you can
[import into Oasis Wallet][oasis-wallet-import-private-key].

### How can I export Oasis private key, if BitPie doesn't show my ROSE account anymore?

If you reinstalled BitPie or restored it with a mnemonic on a new device, you
may not have your ROSE account present anymore. In this case, you will have
to convert your BitPie mnemonic to the Oasis private key using the [Oasis
unmnemonic CLI tool].

You will have to pick Bitpie algorithm, then enter the number of mnemonics
(typically 12), the private key index (start with 0 and gradually increase it by
1, if the resulting account does not contain any tokens) and the output
directory where the file containing the Oasis private key should be stored into.
For example:

```
$ ./unmnemonic
unmnemonic - Recover Oasis Network signing keys from mnemonics
? Which algorithm does your wallet use Bitpie
? How many words is your mnemonic 12
? Enter word 1 *****
? Enter word 2 ******
? Enter word 3 ******
? Enter word 4 *******
? Enter word 5 *****
? Enter word 6 *******
? Enter word 7 *******
? Enter word 8 ****
? Enter word 9 *****
? Enter word 10 ******
? Enter word 11 *****
? Enter word 12 ******
? Wallet index(es) (comma separated) 0
Index[0]: oasis1qp8d9kuduq0zutuatjsgltpugxvl38cuaq3gzkmn
? Write the keys to disk Yes
? Output directory /home/user/unmnemonic/wallet-export-2023-05-01
Index[0]: oasis1qp8d9kuduq0zutuatjsgltpugxvl38cuaq3gzkmn.private.pem - done
Done writing wallet keys to disk, goodbye.
```

Open the generated file, copy the Base64-encoded key wrapped with
`-----BEGIN ED25519 PRIVATE KEY-----` and `-----END ED25519 PRIVATE KEY-----`,
and [import it to the Oasis wallet][oasis-wallet-import-private-key].

[Oasis unmnemonic CLI tool]: https://github.com/oasisprotocol/tools/tree/main/unmnemonic

### Chromium under Ubuntu does not recognize my Ledger device. What is the problem?

Expand Down Expand Up @@ -114,11 +188,28 @@ If you checked all of the above and the keyphrase still cannot be imported, plea
### I imported my wallet with mnemonics. The wallet should contain funds, but the balance is empty. What can I do?
First, check your wallet address. If the address equals the one that you expected your funds on, then the key derivation from mnemonics worked correctly. Make sure you have a working internet connection so that the wallet can fetch the latest balance. Then check that the correct network (Mainnet or Testnet) is selected. These are completely separated networks and although the wallet address can be the same, the transactions and consequently the balances may differ. Finally, there might be a temporary problem with the [Oasis Monitor service](https://oasismonitor.com) itself which observes the network and indexes transactions. Oasis Wallets rely on that service and once it is back up and running, you should be able to see the correct balance.
If your wallet address is different than the one you used to transfer your funds to, then you used one of the wallets that don't implement the standardized key derivation path defined in [ADR 0008](../../adrs/0008-standard-account-key-generation.md). If you were using the BitPie wallet see [this question](faq.md#how-can-i-export-my-bitpie-wallets-oasis-account-private-key). Ledger hardware wallet users should refer to [this question](faq.md#how-can-i-use-my-oasis-wallet-mnemonics-in-ledger).

If you still cannot access your funds, please contact Oasis support.
First, check your wallet address. If the address equals the one that you
expected your funds on, then the key derivation from mnemonics worked correctly.
Make sure you have a working internet connection so that the wallet can fetch
the latest balance. Then check that the correct network (Mainnet or Testnet) is
selected. These are completely separated networks and although the wallet
address can be the same, the transactions and consequently the balances may
differ. Finally, there might be a temporary problem with the
[Oasis Monitor service](https://oasisscan.com) itself which observes the network
and indexes transactions. Oasis Wallets rely on that service and once it is back
up and running, you should be able to see the correct balance.
If your wallet address is different than the one you used to transfer your funds
to, then you used one of the wallets that don't implement the [standardized key
derivation path][adr-8]. If you were using the BitPie wallet see
[this question](#how-can-i-export-oasis-private-key-from-a-working-bitpie-wallet).
Ledger hardware wallet users should refer to
[this question](#ledger-derivation-paths).

If you still cannot access your funds, please contact Oasis support on [#wallets
Discord channel][discord].

[discord]: https://oasis.io/discord

### I sent my ROSE to BinanceStaking address. Are they staked? Are they lost? What can I do?

Expand Down
93 changes: 0 additions & 93 deletions docs/general/manage-tokens/holding-rose-tokens/bitpie-wallet.md

This file was deleted.

2 changes: 1 addition & 1 deletion docs/node/mainnet/previous-upgrades/mainnet-upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ In order to transition from Mainnet Beta to Mainnet, community members have coll
* [x] At least one qualified custodian supports the native ROSE token.
* _Currently, Anchorage and Finoa support the ROSE token. See_ [_Custody Providers_](../../../general/manage-tokens/holding-rose-tokens/custody-providers.md) _part of our docs._
* [x] At least one web wallet or hardware wallet supports native ROSE token.
* _Currently, Bitpie mobile wallet and RockX Ledger-backed web wallet are available and support ROSE token transfers. Support for staking and delegation is in development. See_ [_Mobile Wallets_](../../../general/manage-tokens/holding-rose-tokens/bitpie-wallet.md) _and_ [_Web Wallets_](../../../general/manage-tokens/oasis-wallets/README.mdx) _parts of our docs._
* _Currently, Bitpie mobile wallet and RockX Ledger-backed web wallet are available and support ROSE token transfers. Support for staking and delegation is in development. See_ [_3rd Party Wallets_](../../../general/manage-tokens/holding-rose-tokens/) _and_ [_Oasis Wallets_](../../../general/manage-tokens/oasis-wallets/README.mdx) _parts of our docs._

[archived - block explorers]: https://github.com/oasisprotocol/docs/blob/0aeeb93a6e7c9001925923661e4eb3340ec4fb4b/docs/general/community-resources/community-made-resources.md#block-explorers--validator-leaderboards-block-explorers-validator-leaderboards

Expand Down
2 changes: 1 addition & 1 deletion external/adrs
13 changes: 9 additions & 4 deletions redirects.js
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,11 @@ const redirectsOptions = {
'/general/manage-tokens/how-to-transfer-rose-into-evm-paratime', // #200 Restructure docs
],
},
// #475 Delete bitpie-wallet.md
{
to: '/general/manage-tokens/faq', // #how-can-i-transfer-rose-tokens-from-my-bitpie-wallet-to-my-oasis-wallet
from: '/general/manage-tokens/holding-rose-tokens/bitpie-wallet',
},
// #200 Restructure docs
{
to: '/adrs',
Expand Down Expand Up @@ -51,14 +56,14 @@ const redirectsOptions = {
to: '/dapp/cipher/',
from: '/oasis-sdk/contract/getting-started',
},
{
{
to: '/dapp/sapphire/',
from: '/general/developer-resources/sapphire-paratime',
},
{
},
{
to: '/dapp/sapphire/quickstart',
from: ['/general/developer-resources/sapphire-paratime/writing-dapps-on-sapphire', '/dapp/sapphire/writing-dapps-on-sapphire'], // #218 Add sapphire tutorial
},
},
{
to: '/general/oasis-network/faq',
from: '/general/faq/oasis-network-faq',
Expand Down
1 change: 0 additions & 1 deletion sidebarGeneral.js
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,6 @@ const sidebars = {
},
items: [
'general/manage-tokens/holding-rose-tokens/custody-providers',
'general/manage-tokens/holding-rose-tokens/bitpie-wallet',
'general/manage-tokens/holding-rose-tokens/ledger-wallet',
]
},
Expand Down

0 comments on commit d43491a

Please sign in to comment.