Refactor file and URL paths in docusaurus (#11080)
* Fix introduction link * Restore staking guide pages * Remove Edit this page link * Fix broken wallet guide link * Restore lost images * Fixup URL paths to match gitbook style * Refactor wallet guide READMEs and clean up URLs * Remove lingering gitbook files * Refactor all README files to keep consistent linking * Updte homepage tile links Co-authored-by: publish-docs.sh <maintainers@solana.com>
This commit is contained in:
62
docs/src/wallet-guide.md
Normal file
62
docs/src/wallet-guide.md
Normal file
@@ -0,0 +1,62 @@
|
||||
---
|
||||
title: Solana Wallet Guide
|
||||
---
|
||||
|
||||
This document describes the different wallet options that are available to users
|
||||
of Solana who want to be able to send, receive and interact with
|
||||
SOL tokens on the Solana blockchain.
|
||||
|
||||
## What is a Wallet?
|
||||
|
||||
A crypto wallet is a device or application that stores a collection of keys and
|
||||
can be used to send, receive,
|
||||
and track ownership of cryptocurrencies. Wallets can take many forms.
|
||||
A wallet might be a directory or file in your computer's file system,
|
||||
a piece of paper, or a specialized device called a _hardware wallet_.
|
||||
There are also various smartphone apps and computer programs
|
||||
that provide a user-friendly way to create and manage wallets.
|
||||
|
||||
A _keypair_ is a securely generated _private key_ and its
|
||||
cryptographically-derived _public key_. A private key and its corresponding
|
||||
public key are together known as a _keypair_.
|
||||
A wallet contains a collection of one or more keypairs and provides some means
|
||||
to interact with them.
|
||||
|
||||
The _public key_ (commonly shortened to _pubkey_) is known as the wallet's
|
||||
_receiving address_ or simply its _address_. The wallet address **may be shared
|
||||
and displayed freely**. When another party is going to send some amount of
|
||||
cryptocurrency to a wallet, they need to know the wallet's receiving address.
|
||||
Depending on a blockchain's implementation, the address can also be used to view
|
||||
certain information about a wallet, such as viewing the balance,
|
||||
but has no ability to change anything about the wallet or withdraw any tokens.
|
||||
|
||||
The _private key_ is required to digitally sign any transactions to send
|
||||
cryptocurrencies to another address or to make any changes to the wallet.
|
||||
The private key **must never be shared**. If someone gains access to the
|
||||
private key to a wallet, they can withdraw all the tokens it contains.
|
||||
If the private key for a wallet is lost, any tokens that have been sent
|
||||
to that wallet's address are **permanently lost**.
|
||||
|
||||
Different wallet solutions offer different approaches to keypair security and
|
||||
interacting with the keypair and sign transactions to use/spend the tokens.
|
||||
Some are easier to use than others.
|
||||
Some store and back up private keys more securely.
|
||||
Solana supports multiple types of wallets so you can choose the right balance
|
||||
of security and convenience.
|
||||
|
||||
**If you want to be able to receive SOL tokens on the Solana blockchain,
|
||||
you first will need to create a wallet.**
|
||||
|
||||
## Supported Wallets
|
||||
|
||||
Solana supports supports several types of wallets in the Solana native
|
||||
command-line app as well as wallets from third-parties.
|
||||
|
||||
For the majority of users, we recommend using one of the
|
||||
[app wallets](apps.md), which will provide a more familiar user
|
||||
experience rather than needing to learn command line tools.
|
||||
|
||||
For advanced users or developers, the [command-line wallets](cli.md)
|
||||
may be more appropriate, as new features on the Solana blockchain will always be
|
||||
supported on the command line first before being integrated into third-party
|
||||
solutions.
|
||||
Reference in New Issue
Block a user