Update Cloud Wallet docs after latest beta release

Author: danieljperry

docs/getting-started/cloud-wallet/faq.md

@@ -54,15 +54,15 @@ A vault is a new way to custody your assets on Chia's blockchain. Instead of sec
 
 ### What is the advantage of using a vault instead of a wallet?
 
-Standard wallets on Chia as well as other blockchains only have one key. If this key is lost or stolen, then all of the funds custodied in the wallet will also be lost or stolen. The security assumptions surrounding standard wallets are disconcerting to retail and enterprise users alike. By using Chia vaults, users can feel confident that their funds will remain secure even if one of their keys is lost, and often (as discussed below) if it is stolen.
+The Chia reference wallet currently only uses a single key. If this key is lost or stolen, then all of the funds custodied in the wallet will also be lost or stolen. By using Chia vaults, users can feel confident that their funds will remain secure even if one of their keys is lost, and often (as discussed below) if it is stolen.
 
 ### Why do I see “Your vault is being minted, the address will be available soon.” after I create a vault?
 
 A vault needs to be created on the blockchain after you click the “Create” button. We have set up a faucet to handle this automatically. However, it does take a few minutes for the on-chain transaction to be processed. You should receive an address within five minutes.
 
 ### Can I import an existing wallet into the Cloud Wallet by entering a seed phrase?
 
-Not at the moment. Currently the Cloud Wallet only supports vaults. We may add support for standard BLS wallets, but we haven't made that decision yet.
+Not at the moment. Currently the Cloud Wallet only supports vaults. We may add support for BLS wallets, but we haven't made that decision yet.
 
 ### How is signing different with the Chia vault than with the reference wallet?
 
@@ -90,6 +90,10 @@ If you find any bugs, feel free to fill out a [bug report](https://docs.google.c
 
 If you discover any security issues, you can file a report on our [bug bounty site](https://hackerone.com/chia_network). Thanks for your help!
 
+### Why is the `Add Vault` button disabled after I create my first vault?
+
+Currently the only tier you can choose is the `Free` tier, which only allows you to create one vault. In the future we will enable the `Pro` and `Enterprise` tiers, which enable multiple vaults, along with several other features.
+
 ## Recovery
 
 ### What happens if I lose my spend key?
@@ -188,12 +192,14 @@ The two risks for Cloud Wallet end users are:
 
 ### Do vaults always use the same address?
 
-Yes, and this is a departure from the reference wallet, which uses a new address for each transaction. The reason vaults always use the same address is because they are singletons -- the vault itself authorizes the spend of coins under its control, as opposed to standard wallets which are derived from BLS keys.
+Currently, yes. This is a departure from the reference wallet, which uses a new address for each transaction. The reason vaults always use the same address is because they are singletons -- the vault itself authorizes the spend of coins under its control. This is a different approach from the reference wallet, which uses a BLS key to derive its addresses.
 
 Users must carefully consider the privacy (and therefore security) implications of reusing an address. When the address doesn't change, it becomes easier to put together a historical record of transactions. Vaults that hold significant value could therefore be targeted with physical attacks, as explained in [a Bitcoin wiki](https://en.bitcoin.it/wiki/Address_reuse).
 
 Future versions of vaults will have additional security such as multisigs and time locks to mitigate the risk of physical attacks.
 
+In addition, in the future we plan to support vaults with multiple receive addresses. Stay tuned for more info on that topic.
+
 ### Will the Chia Signer app be open source?
 
 Yes

docs/getting-started/cloud-wallet/known-issues.md

@@ -3,42 +3,39 @@ slug: /getting-started/cloud-wallet/known-issues
 title: Known Issues
 ---
 
-This list was last updated on 2024-12-18. Although there are many items in this list, most of them are minor issues or issues that occur rarely. In addition, while we will attempt to keep this list up to date, it may fall behind on occasion. This is not meant to be a comprehensive list.
+This list was last updated on 2025-01-28. Although there are many items in this list, most of them are minor issues or issues that occur rarely. In addition, while we will attempt to keep this list up to date, it may fall behind on occasion. This is not meant to be a comprehensive list.
 
-- Recovery is not yet enabled for vaults that use the Chia Signer app
-- The fee field doesn’t work yet for recovery operations (initiate, cancel, complete)
-- The fiat price of XCH is currently not being displayed
+- The fee field for recovery operations (initiate, complete) isn't actually used
+- When initiating a recovery, you may briefly see "Not Available" minutes remaining until the recovery can be completed, after which the correct timer is displayed
+- From the home screen view, a vault's balance may take over a minute to update after the transaction has been processed on chain
+- Android passkeys don't sync properly to desktop computers that don't have Bluetooth
+- When using the dark theme, hovering over a button such as the Delete button may not provide adequate visual feedback
+- When signing up from an Android device, you may see an `Internal Server Error`
+- After recovering a vault with the Chia Signer app, when a new transaction is confirmed, a `Recovery Timer` screen may briefly flash
+- If you send multiple transactions from the same vault at approximately the same time, the second one might get stuck in the mempool
 - You may see an occasional `Minified React error` when doing various actions in the Cloud Wallet
 - You may have difficulty creating a new Yubikey passkey when using the Cloud Wallet on Android
 - If vault creation fails, you won't be able to create a vault with the same name used with the failed attempt
 - If you send two transactions within the same block, the second transaction will be stuck in the mempool indefinitely
-- Transaction status might not be updated for around 20 seconds after on-chain confirmation
 - When vault minting doesn't succeed (for example, if not enough coins are available), the action is not retried
 - Long vault names are truncated; this is a display issue only
 - Vaults currently can be named with all whitespace (space/tab) characters; this will be disallowed in the future
 - The Chia Signer app is only for signing transactions; the current signup process doesn't make it completely clear that the app cannot be used for logging into the Cloud Wallet. We will make this clearer in the future.
 - The transaction history may not show all incoming transactions, even when the balance is accurate
 - When setting up a vault on an iPhone, the fields for inputting up the clawback timer might not show any numbers
-- If you attempt to add a passkey, but then click the X to close out of the window, it will give you an error
 - If you send funds to your own vault, the transaction will show an amount of 0
 - In rare occurrences, when creating an account, you might see "Internal Server Error"
 - You may see "User not found for this passkey" when attempting to create an account with a passkey
 - We are in the process of updating the mobile UI, so certain buttons and labels may look bad on a mobile device for now
 - Some users have reported seeing "vault.chiatest.net's DNS address could not be found...." when using the Brave browser
 - The previous view of the home screen will briefly flash after a new vault is created; this lasts less than one second until the correct view is displayed
-- After successfully cancelling a recovery, you may see a "Something went wrong" message; refresh your browser window to workaround this issue
-- The initial timer displayed for cancelling a recovery is hardcoded to 15 minutes; however, the actual timer is correct
 - The recovery timer will show "0 minutes" remaining when, in fact, there is less than one minute remaining; this is a simple rounding error which will be resolved when the timer actually reaches 0
 - After a successful recovery, the first transaction in the vault’s history shows an extra mojo
-- The signing modal dialog occasionally takes over 30 seconds to be displayed
 - When sending CATs, the "amount" field is missing a label, and the "fee" field is labeled as "unknown CATs"; these are display issues only
 - CATs sent to the same vault as where they originated are listed as "0 Unknown CATS"
-- If the Cloud Wallet is left inactive for a long time, "Something went wrong" might be displayed; refreshing the browser tab will work around this issue
 - For now, in order to paste a seed phrase when initiating a recovery, you must paste the phrase into the first word field
 - Coins might be locked if certain transactions fail, and it’s not obvious how to unlock them; however, this is an uncommon occurrence
 - On rare occasions, selecting a custody key will result in it not being possible to return to the main screen. \* Log out and log back in to work around this issue for now
 - If a "Fee too low" error is encountered (a rare occurrence), a transaction may enter a "signed" state, but it is not submitted to the mempool
 - Unrecognized CATs (which includes all CATs for now) are each listed as "Unknown CAT2" without an obvious way to differentiate them
-- The balance and transaction count can be out of sync in vaults with hundreds of transactions
-- When creating a vault with a bitwarden passkey, it’s possible to receive a "Memory access out of bounds" error
-- You can’t create a new vault with the same name as a deleted vault
+- You can’t create a new vault with the same name as a deleted vault

docs/getting-started/cloud-wallet/unfinished.md

@@ -8,10 +8,6 @@ import TabItem from '@theme/TabItem';
 
 While the Cloud Wallet public beta has most of its planned features in place, it is currently missing a few things that will be included in the production release.
 
-## Recovery for Chia Signer Vaults
-
-Vaults that use the Chia Signer app as their signer cannot yet perform a recovery. While the APIs for recovering these vaults are working, the GUI is not yet ready. We are actively working on finishing this.
-
 ## Recovery for Unlisted Vaults
 
 Currently, if you lose access to your Cloud Wallet and signer passkey (for example, if you are accessing your account from a smartphone, and this phone is stolen), the app does not have a method for recovering your vault. We are working on implementing this.