Update docs wrt new wallet and rpc functionality (#5528)
This commit is contained in:
parent
827f2b3a5c
commit
1fe1550a30
|
@ -23,7 +23,7 @@ $ solana-gossip --entrypoint testnet.solana.com:8001 spy
|
|||
```
|
||||
|
||||
## Check Vote Activity
|
||||
The vote pubkey for the validator can also be found by running:
|
||||
The vote pubkey for the validator can be found by running:
|
||||
```bash
|
||||
$ solana-keygen pubkey ~/validator-vote-keypair.json
|
||||
```
|
||||
|
@ -38,7 +38,7 @@ $ solana-wallet show-vote-account 2ozWvfaXQd1X6uKh8jERoRGApDqSqcEy6fF1oN13LL2G
|
|||
Your lamport balance should decrease by the transaction fee amount as your
|
||||
validator submits votes, and increase after serving as the leader:
|
||||
```bash
|
||||
$ solana-wallet --keypair ~/validator-keypair.json
|
||||
$ solana-wallet balance
|
||||
```
|
||||
|
||||
## Check Slot Number
|
||||
|
|
|
@ -34,20 +34,38 @@ $ solana-gossip --entrypoint testnet.solana.com:8001 spy
|
|||
```
|
||||
|
||||
## Start your Validator
|
||||
Now create an identity keypair for your validator by running:
|
||||
Create an identity keypair for your validator by running:
|
||||
```bash
|
||||
$ solana-keygen new -o ~/validator-keypair.json
|
||||
```
|
||||
and airdrop yourself some lamports to get started:
|
||||
|
||||
### Wallet Configuration
|
||||
You can set solana-wallet configuration to use your validator keypair for all
|
||||
following commands:
|
||||
```bash
|
||||
$ solana-wallet set --keypair ~/validator-keypair.json
|
||||
```
|
||||
|
||||
**All following solana-wallet commands assume you have set `--keypair` config to
|
||||
**your validator identity keypair.**
|
||||
If you haven't, you will need to add the `--keypair` argument to each command, like:
|
||||
```bash
|
||||
$ solana-wallet --keypair ~/validator-keypair.json airdrop 1000
|
||||
```
|
||||
(You can always override the set configuration by explicitly passing the
|
||||
`--keypair` argument with a command.)
|
||||
|
||||
### Validator Start
|
||||
Airdrop yourself some lamports to get started:
|
||||
```bash
|
||||
$ solana-wallet airdrop 1000
|
||||
```
|
||||
|
||||
Your validator will need a vote account. Create it now with the following
|
||||
commands:
|
||||
```bash
|
||||
$ solana-keygen new -o ~/validator-vote-keypair.json
|
||||
$ solana-wallet --keypair ~/validator-keypair.json create-vote-account ~/validator-vote-keypair.json ~/validator-keypair.json 1
|
||||
$ solana-wallet create-vote-account ~/validator-vote-keypair.json ~/validator-keypair.json 1
|
||||
```
|
||||
|
||||
Then use one of the following commands, depending on your installation
|
||||
|
|
|
@ -11,6 +11,13 @@ software, which may feature breaking changes. Generally, the edge testnet tracks
|
|||
the tip of master, beta tracks the latest tagged minor release, and stable
|
||||
tracks the most stable tagged release.
|
||||
|
||||
### Get Testnet Version
|
||||
You can submit a JSON-RPC request to see the specific version of the cluster.
|
||||
```bash
|
||||
$ curl -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1, "method":"getVersion"}' edge.testnet.solana.com:8899
|
||||
{"jsonrpc":"2.0","result":{"solana-core":"0.18.0-pre1"},"id":1}
|
||||
```
|
||||
|
||||
## Using a Different Testnet
|
||||
This guide is written in the context of testnet.solana.com, our most stable
|
||||
cluster. To participate in another testnet, you will need to modify some of the
|
||||
|
@ -42,6 +49,16 @@ different testnet. For instance:
|
|||
$ solana-wallet --url http://beta.testnet.solana.com:8899 balance
|
||||
```
|
||||
|
||||
Solana-wallet includes `get` and `set` configuration commands to automatically
|
||||
set the `--url` argument for future wallet commands.
|
||||
For example:
|
||||
```bash
|
||||
$ solana-wallet set --url http://beta.testnet.solana.com:8899
|
||||
$ solana-wallet balance # Same result as command above
|
||||
```
|
||||
(You can always override the set configuration by explicitly passing the `--url`
|
||||
argument with a command.)
|
||||
|
||||
Solana-gossip and solana-validator commands already require an explicit
|
||||
`--entrypoint` argument. Simply replace testnet.solana.com in the examples with
|
||||
an alternate url to interact with a different testnet. For example:
|
||||
|
|
Loading…
Reference in New Issue