How to self-recover assets?
Your Ownbit crypto assets are generic and highly available, and their security and availability are not dependent on Ownbit. This article teaches you how to recover crypto assets through self-service when there is a downtime or other unexpected situation on the Ownbit server.
1. Recovery by mnemonics
Ownbit's mnemonic conforms to the BIP39 standard, and the address generation path conforms to the BIP44 standard. Therefore, the mnemonic can be imported into a wallet that meets the above criteria (most mainstream wallets are compatible), and the crypto assets can be easily recovered. See the specific BIP44 path for details: https://ownbit.io/en/resource/coins-spec/
2. Restore by private key import
Ownbit supports export of private keys (wallet management -> export private key), and imports the private key into other wallets that support the import of the corresponding coin, which can easily recover the assets at the corresponding address.
3. Recovery of BTC Segregated Witness Assets
Ownbit supports Legacy, SegWit Compatible and Native (1 address, 3 address, bc1 address). Other mainstream wallets generally only support one of them, so please confirm the type of address you use before importing. In Ownbit, their address generation paths conform to the BIP44, BIP49, and BIP84 standards, respectively.
4. Recovery of BCH/BSV assets
BCH/BSV uses the same address as BTC Legacy, the generation path conforms to BIP44, and the coinType is 0 instead of 145 or 236.
5. Recovery of ETH/ETC assets
ETH/ETC uses the same address, the address generation path conforms to BIP44, and the coinType is 60.
6. Recovery of USDT (ERC20) and other ERC20 assets
The mainstream Ethereum wallet supports ERC20 tokens, and restores the corresponding ETH address, which can restore the corresponding ERC20 assets.
7. Recovery of USDT (Omni) assets
Ownbit supports USDT (Omni) addresses start with 1 and 3, corresponding to BTC's Legacy address and SegWit compatible address (BIP44 and BIP49 respectively), imported into Bitcoin wallet supporting USDT (Omni), and restored corresponding With the BTC address, the corresponding USDT asset can be recovered.
8. Recovery of XMR assets
By exporting the XMR private key (wallet management -> export private key), you get the XMR View key and Spend key, which can be imported into any mainstream XMR wallet (example: The official wallet or Cake Wallet for XMR) to easily recover XMR assets.
9. Recovery of ADA assets
ADA does not support private key export for the time being. ADA assets can be recovered through mnemonic words in other wallets that support ADA (eg Yoroi wallet, adalite.io).
Note: The above mentioned wallet only supports English mnemonic words. If you use Chinese (or other non-English) mnemonic words, you need to program recovery by yourself (generate Entropy through mnemonic words, the remaining logic is the same as recovery ADA assets by English mnemonic).
10. Recovery of ONT assets
The address of the Ownbit ONT asset is the same as the NEO asset address (the coinType: 888 is used to generate the address), so restoring ONT assets in other wallets through mnemonic words may result in inconsistent addresses. You can use the private key import method to restore ONT assets.
11. Other assets
Other unmentioned assets are BIP44 compliant and can be easily restored in the corresponding supported wallet.
12. Other situations that cannot be recovered
Use a wallet that is too frequent (such as sent many times), or use a refresh address when receiving (relatively more times), in other wallets, asset recovery may be incomplete or unrecoverable, which is due to the corresponding wallet pair Caused by imperfect multi-address support. In this case, the private key can be imported to specifically recover the unrecovered assets.
13. Chinese and other non-English mnemonics
English mnemonics are the most versatile. If you are using Chinese mnemonics or other non-English languages, you may encounter unrecognized situations when other wallets recover assets. The solution is to find a wallet that supports the corresponding mnemonic language or restore it by importing a private key (private key import is always common).