From ed203c6fc455a8169d1765f0ae4e18f006a18f20 Mon Sep 17 00:00:00 2001
From: kaminskyelina <45590119+kaminskyelina@users.noreply.github.com>
Date: Mon, 22 Apr 2019 13:42:37 +0300
Subject: [PATCH] Update README.md

---
 README.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 5e334be3..dc8342d9 100644
--- a/README.md
+++ b/README.md
@@ -23,10 +23,14 @@ Things that make BEAM special include:
 - April 2019    : Mainnet release
 
 # Current status
-- First Testnet development started
+- Mainnet released
 
 # Known limitations and workarounds:
-- Restore flow is not implemented on mobile, yet the funds can be restored from the desktop wallet using the same seed the mobile wallet was created with
+- When sending beams from mobile to desktop wallet, the QR code scanning works from desktop wallet version 2.0
+- The app will always choose a random node to connect to; connecting to specific node will be added later.
+- Restore flow (which requires integrated or dedicated node) is currently implemented on desktop only, hence to restore mobile funds use desktop wallet with the same seed the mobile wallet was created with.
+- In case the user has both mobile and a desktop wallets which are using the same seed phrase, the funds sent to the desktop wallet won’t appear on the mobile wallet. If the desktop wallet is running a local node, it will see funds sent to both wallets. The reason is that the local node (integrated into desktop wallet) always monitors the blockchain for UTXOs related to the seed of the wallet. The mobile wallet does not run a local node and thus can only monitor transactions sent to its specific SBBS addresses. Of course, no funds will be lost in any event.
+- If multiple wallets are restored from the same seed phrase, transaction history and addresses will not be shared among the wallets.
 
 # How to build