ROSE Wallet

Built by the community, for the community: Open-source and user-friendly. The ROSE Wallet makes it easy to hold, stake, send, and receive ROSE tokens.

Wallet In Use

The ROSE Wallet is the official, non-custodial wallet for storing, sending and receiving digital assets on the Oasis Network. With Oasis Safe by ProtoFire and Transak, ROSE Wallet users have access to industry-leading custody options and on-ramps into the ecosystem.

The Entry Point into Oasis

Use the official non-custodial web wallet or browser extension wallet for the Oasis Network.

  • Browser Extension or Website

  • Cold Wallet, Non-Custodial, Open-Source

  • Create a public-private key pair to control your assets

  • Transfer ROSE tokens between ParaTime layers

  • Staking (delegate and undelegate tokens on the network)

  • Industry-leading custodial and on-off ramps integrated into Oasis (Transak for buying ROSE)

  • Support for Metamask, Ledger, Privy, and other EVM-compatible wallets

Compatible with EVM Wallets

The ROSE Wallet supports Metamask, Brave Browser, Trust, Privy, Owallet, and other EVM Wallets. Interact with a world of dApps:

  • Control the Oasis Network assets stored in your MetaMask wallet.

  • Enjoy full compatibility on Oasis Sapphire and Emerald runtimes.

  • Unlock access from MetaMask to dApps on Oasis.

  • Navigate through NFT marketplaces, games, and more on Oasis!

Compatible with Ledger

The ROSE Wallet supports Ledger. Your keys, your coins:

  • Open source software running on Ledger devices

  • Hardware wallet that supports Oasis Network tokens

  • Easy setup and connectivity from Ledger to Oasis dApps

  • Navigate through NFT marketplaces, games, and more on Oasis!

What’s New?

Check the latest updates and improvements about Rose Wallet

Staking on ROSE Wallet

Stake ROSE, earn rewards, and contribute to the to the security and decentralization of the network.

Explorers

Oasis Explorer enables a comprehensive look into the activity on Oasis Sapphire and Oasis Emerald, whereas Oasis Scan gives users a detailed view into the activity on the Oasis Network’s consensus layer.

FAQs

I withdrew ROSE from Emerald to an exchange (Binance, KuCoin), but my deposit is not there. What should I do?

Withdrawals from Emerald are slightly different from regular staking.Transfer transactions used to send ROSE on the consensus layer. If you withdrew your ROSE directly to an exchange and you were not funded there, contact the exchange support and provide them the link to your account on the Oasis Scan where they can verify all transactions. To learn more about this issue, read the Manage tokens chapter.

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

If you just make a Send transaction to BinanceStaking address oasis1qqekv2ymgzmd8j2s2u7g0hhc7e77e654kvwqtjwm then your ROSE coins are not staked. They are now owned by BinanceStaking, which means they are not lost but only owned and managed by them. In this case, you should contact Binance via their Support Center or Submit a request.

Info: Sending ROSE is different than staking it! With the staking transaction you lend your ROSE to the chosen validator and you are rewarded for that. Sending your ROSE to the receiving address you enter means that only the person who owns the private key (e.g. mnemonics) of that receiving address can manage these tokens and no one else. To learn more, read the Staking and Delegating chapter.

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 itself which observes the network and indexes transactions. The ROSE Wallet relies 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. If you were using the BitPie wallet see this question. Ledger hardware wallet users should refer to this question.

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

The wallet gives me Invalid keyphrase error when importing my wallet from mnemonics. How do I solve it?

Please check that:

  • All mnemonics were spelled correctly. The ROSE Wallet uses English mnemonic phrase words as defined in BIP39. You can find a complete list of valid phrase words here.
  • The mnemonics were input in correct order.
  • All mnemonics were provided. The keyphrase should be either 12, 15, 18, 21, or 24 words long.

If you checked all of the above and the keyphrase still cannot be imported, please contact Oasis support.

Which derivation path should I use on Ledger? ADR-8 or Legacy?

To convert your mnemonic phrase into a private key for signing trasactions, each wallet (hardware or software) performs a key derivation. The Oasis Protocol Foundation standardized the key derivation for the official ROSE Wallet in a document called ADR-8 back in January 2021. However, the Ledger hardware wallet already supported signing transactions at that time using a custom (we now call it legacy) derivation path which is incompatible with the one defined in ADR-8. Later, in Oasis app for Ledger v2.3.1 support for ADR-8 was added so the wallet can request either derivation from the Ledger device.

The key derivation path defined in ADR-8 has the following advantages compared to the legacy one:

  • Derivation path is shorter which results in approximately twice as fast key derivation (and transaction signing) without compromising security.
  • In case your Ledger device is broken or lost and you are unable to retrieve a new one, you will be able to import your Ledger mnemonic and restore your private key in a ROSE Wallet which implements ADR-8.

For reasons above, we recommend the usage of ADR-8. However, since there are no security considerations at stake, the ROSE Wallet will support legacy derivation on Ledger for the foreseeable future.

Are the Ethereum and ROSE wallets that different? I can use the same mnemonics with both, right?

Yes, both ROSE and Ethereum wallets make use of the mnemonics as defined in BIP39 and they even use the same wordlist to derive the keypairs for your wallet. However, they use a different signature scheme and a derivation path, so the addresses and the private keys are incompatible.

Here's a task for you:

  1. Visit https://iancoleman.io/bip39/ to generate a BIP39 mnemonic.
  2. Select ETH token and copy the hex-encoded private key of the first derived account, for example 0xab2c4f3bc70d40f12f6030750fe452448b5464114cbfc46704edeef2cd06da74.
  3. Import the Ethereum-compatible account with the private key obtained above to your ROSE Wallet.
  4. Notice the Ethereum address of the account, for example 0x58c72Eb040Dd0DF10882aA87a39851c21Ae5F331.
  5. Now in the Account management screen, select this account and click on the "Export private key" button. Confirm the risk warning.
  6. You will notice the private key of the Ethereum-compatible account, the hex-encoded address and the very same address encoded in the Oasis Bech32 format, in our case oasis1qpaj6hznytpvyvalmsdg8vw5fzlpftpw7g7ku0h0.
  7. Now let's use the private key from step 2 to import the account. First, convert the hex-encoded key to base64 format, for example by using this service. In our example, that would be qyxPO8cNQPEvYDB1D+RSRItUZBFMv8RnBO3u8s0G2nQ=.
  8. Next, import this base64-encoded private key to the ROSE Wallet Browser Extension.
  9. You should see your newly imported account and the Oasis address. In our case oasis1qzaf9zd8rlmchywmkkqmy00wrczstugfxu9q09ng.
  10. Observe that this account address is different than the Bech32-encoded version of the Ethereum-compatible address despite using the same private key to import the wallet with, because of a different signature scheme.

As an additional exercise, you can also create an Oasis account using the BIP39 mnemonic from the step 1 above. You will notice that the imported account's base64-encoded private key in the account details screen is different from the one in step 7 above. That's because Oasis uses a different derivation path than Ethereum.

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

First check that you added the Ledger udev device descriptors as mentioned in the Linux installation guide. Next, check that your Ledger wallet is recognized by the Oasis CLI. You should be able to add your Ledger account to the Oasis CLI wallet by running:

oasis wallet create oscar

If all of the above works, then the issue is most likely that Chromium does not have the permission to access your Ledger device. Starting with Ubuntu 20.04 the Chromium browser is installed via snap package by default. Snap is more convenient for upstream developers to deploy their software and it also adds additional layer of security by using apparmor. In our case however, it prevents Chromium to access arbitrary USB devices with WebUSB API including your Ledger device. A workaround for this issue is to install Chromium natively using the official Chormium beta PPA or the official Google Chrome .deb package.

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 tool (64-bit binaries available for Linux, MacOS and Windows).

Follow the steps as described here.

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

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

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

2. 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".

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

4. Finally, your account's private key will be shown to you encoded in Base64 format (e.g. YgwGOfrHG1TVWSZBs8WM4w0BUjLmsbk7Gqgd7IGeHfSqdbeQokEhFEJxtc3kVQ4KqkdZTuD0bY7LOlhdEKevaQ==) which you can import into ROSE Wallet.

How can I transfer ROSE tokens from my BitPie wallet to my ROSE Wallet?

In May 2023, the BitPie team removed support for the Oasis network. 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:

Once you obtained the private key, you can import it to the ROSE Wallet and access your assets.

Stay Up to Date in

Stay Up to Date in Web3 & AI Privacy

Web3 & AI Privacy

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

More than just a newsletter, Oasis provides key insights into the Web3 privacy landscape, updates for the Oasis, ecosystem, community, and more.

How we use cookies?

At Oasis Foundation we believe in your privacy, so you can choose to browse our site without any tracking or by clicking “Accept”, you help us to improve our site and help us grow our ecosystem. View our Privacy Policy for more information.