minor grooming

This commit is contained in:
Michael Vines
2019-04-18 07:31:42 -07:00
parent 2f4a3ed190
commit 2c0afe71b2

View File

@ -12,8 +12,8 @@ serves as the entrypoint to the cluster for your validator.
Additionally there is a blockexplorer available at Additionally there is a blockexplorer available at
[http://beta.testnet.solana.com/](http://beta.testnet.solana.com/). [http://beta.testnet.solana.com/](http://beta.testnet.solana.com/).
The beta testnet is configured to reset the ledger every 24hours, or sooner The beta testnet is configured to reset the ledger daily, or sooner
should an hourly automated sanity test fail. should the hourly automated cluster sanity test fail.
### Machine Requirements ### Machine Requirements
Since the beta testnet is not intended for stress testing of max transaction Since the beta testnet is not intended for stress testing of max transaction
@ -28,11 +28,11 @@ MacOS or WSL users may build from source.
#### Confirm The Testnet Is Reachable #### Confirm The Testnet Is Reachable
Before attaching a validator node, sanity check that the cluster is accessible Before attaching a validator node, sanity check that the cluster is accessible
to your machine by running some simple wallet commands. If any of these to your machine by running some simple commands. If any of the commands fail,
commands fail, please retry 5-10 minutes later to confirm the testnet is not please retry 5-10 minutes later to confirm the testnet is not just restarting
just restarting itself before debugging further. itself before debugging further.
Fetch the current testnet transaction count over JSON RPC: Fetch the current transaction count over JSON RPC:
```bash ```bash
$ curl -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1, "method":"getTransactionCount"}' http://beta.testnet.solana.com:8899 $ curl -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1, "method":"getTransactionCount"}' http://beta.testnet.solana.com:8899
``` ```
@ -73,18 +73,21 @@ software to a newer version.
##### Download Prebuilt Binaries ##### Download Prebuilt Binaries
Binaries are available for Linux x86_64 systems. Binaries are available for Linux x86_64 systems.
Download the binaries by navigating to https://github.com/solana-labs/solana/releases/latest, download Download the binaries by navigating to
**solana-release-x86_64-unknown-linux-gnu.tar.bz2**, then extract the archive: [https://github.com/solana-labs/solana/releases/latest](https://github.com/solana-labs/solana/releases/latest),
download **solana-release-x86_64-unknown-linux-gnu.tar.bz2**, then extract the
archive:
```bash ```bash
$ tar jxf solana-release-x86_64-unknown-linux-gnu.tar.bz2 $ tar jxf solana-release-x86_64-unknown-linux-gnu.tar.bz2
$ cd solana-release/ $ cd solana-release/
$ export PATH=$PWD/bin:$PATH $ export PATH=$PWD/bin:$PATH
``` ```
##### Build From Source ##### Build From Source
If you are unable to use the prebuilt binaries or prefer to build it yourself from source, navigate to: If you are unable to use the prebuilt binaries or prefer to build it yourself
> https://github.com/solana-labs/solana/releases/latest from source, navigate to
[https://github.com/solana-labs/solana/releases/latest](https://github.com/solana-labs/solana/releases/latest),
Download the source code tarball (solana-*[release]*.tar.gz) from our latest release tag. Extract the code and build the binaries with: and download the **Source Code** archive. Extract the code and build the
binaries with:
```bash ```bash
$ ./scripts/cargo-install-all.sh . $ ./scripts/cargo-install-all.sh .
$ export PATH=$PWD/bin:$PATH $ export PATH=$PWD/bin:$PATH
@ -128,7 +131,7 @@ validator to ports 11000-11011.
From another console, confirm the IP address of your validator is visible in the From another console, confirm the IP address of your validator is visible in the
gossip network by running: gossip network by running:
```bash ```bash
solana-gossip --network edge.testnet.solana.com:8001 $ solana-gossip --network edge.testnet.solana.com:8001
``` ```
When `fullnode.sh` starts, it will output a fullnode configuration that looks When `fullnode.sh` starts, it will output a fullnode configuration that looks