You control the keys
Wallet generation and transaction signing are performed by local WebAssembly code in your browser.
Keys are created and used in your browser. PHP only proxies requests to configured nodes and automatically switches when a node fails.
A new seed phrase will be generated. Write it down before receiving funds.
If this wallet is not yet known to the synchronization server, it will be scanned from block 0. Known wallets resume from their saved height.
If this wallet is not yet known to the synchronization server, it will be scanned from block 0. Known wallets resume from their saved height.
Open a standard encrypted Monero .keys file.
If this wallet is not yet known to the synchronization server, it will be scanned from block 0. Known wallets resume from their saved height.
The encrypted JSON backup is created in this web wallet and contains recovery data.
Wallet generation and transaction signing are performed by local WebAssembly code in your browser.
The PHP proxy tries configured nodes in order and switches after a network error.
The wallet adds no service fee. The final network fee is shown before sending.
...
Share this address with the sender. Never share your private keys or seed.
A view-only wallet does not contain the spend key and cannot sign transactions. Without key images, it may also fail to detect funds spent in another wallet.
View the seed and private keys or create a separately encrypted backup file.
Move the slider or enter a block or date. The selected point is kept for this wallet until you close it.
The encrypted browser session and its saved synchronization point will be removed. Make sure you have the seed or another backup.