blockworks-foundation
/
solana
mirror of https://github.com/blockworks-foundation/solana.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

rename testnet.solana.com to devnet.solana.com

This commit is contained in:
Michael Vines 2020-02-19 14:04:34 -07:00
parent ccad5d5aaf
commit e3cebcf82d
13 changed files with 36 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -126,7 +126,7 @@ Start your own testnet locally, instructions are in the book [Solana: Blockchain
Remote Testnets Remote Testnets
--- ---
* `testnet` - public stable testnet accessible via testnet.solana.com. Runs 24/7 * `testnet` - public stable testnet accessible via devnet.solana.com. Runs 24/7
## Deploy process ## Deploy process

6
RELEASE.md
View File

@ -140,9 +140,9 @@ TODO: Documentation update procedure is WIP as we move to gitbook
Document the new recommended version by updating `book/src/running-archiver.md` and `book/src/validator-testnet.md` on the release (beta) branch to point at the `solana-install` for the upcoming release version. Document the new recommended version by updating `book/src/running-archiver.md` and `book/src/validator-testnet.md` on the release (beta) branch to point at the `solana-install` for the upcoming release version.
### Update software on testnet.solana.com ### Update software on devnet.solana.com
The testnet running on testnet.solana.com is set to use a fixed release tag The testnet running on devnet.solana.com is set to use a fixed release tag
which is set in the Buildkite testnet-management pipeline. which is set in the Buildkite testnet-management pipeline.
This tag needs to be updated and the testnet restarted after a new release This tag needs to be updated and the testnet restarted after a new release
tag is created. tag is created.
@ -182,4 +182,4 @@ TESTNET_OP=create-and-start
### Alert the community ### Alert the community
Notify Discord users on #validator-support that a new release for Notify Discord users on #validator-support that a new release for
testnet.solana.com is available devnet.solana.com is available

2
book/src/building-from-source.md
View File

@ -154,7 +154,7 @@ The stream will output a series of JSON objects:
In this example the client connects to our public testnet. To run validators on the testnet you would need to open udp ports `8000-10000`. In this example the client connects to our public testnet. To run validators on the testnet you would need to open udp ports `8000-10000`.
```bash ```bash
$ NDEBUG=1 ./multinode-demo/bench-tps.sh --entrypoint testnet.solana.com:8001 --faucet testnet.solana.com:9900 --duration 60 --tx_count 50 $ NDEBUG=1 ./multinode-demo/bench-tps.sh --entrypoint devnet.solana.com:8001 --faucet devnet.solana.com:9900 --duration 60 --tx_count 50
``` ```
You can observe the effects of your client's transactions on our [dashboard](https://metrics.solana.com:3000/d/testnet/testnet-hud?orgId=2&from=now-30m&to=now&refresh=5s&var-testnet=testnet) You can observe the effects of your client's transactions on our [dashboard](https://metrics.solana.com:3000/d/testnet/testnet-hud?orgId=2&from=now-30m&to=now&refresh=5s&var-testnet=testnet)

2
book/src/implemented-proposals/installer.md
View File

@ -154,7 +154,7 @@ FLAGS:
OPTIONS: OPTIONS:
-d, --data_dir <PATH> Directory to store install data [default: .../Library/Application Support/solana] -d, --data_dir <PATH> Directory to store install data [default: .../Library/Application Support/solana]
-u, --url <URL> JSON RPC URL for the solana cluster [default: http://testnet.solana.com:8899] -u, --url <URL> JSON RPC URL for the solana cluster [default: http://devnet.solana.com:8899]
-p, --pubkey <PUBKEY> Public key of the update manifest [default: 9XX329sPuskWhH4DQh6k16c87dHKhXLBZTL3Gxmve8Gp] -p, --pubkey <PUBKEY> Public key of the update manifest [default: 9XX329sPuskWhH4DQh6k16c87dHKhXLBZTL3Gxmve8Gp]
``` ```

2
book/src/paper-wallet/usage.md
View File

@ -106,7 +106,7 @@ networked machine.
Next, configure the `solana` CLI tool to connect to a particular cluster: Next, configure the `solana` CLI tool to connect to a particular cluster:
```bash ```bash
solana config set --url <CLUSTER URL> # (i.e. http://testnet.solana.com:8899) solana config set --url <CLUSTER URL> # (i.e. http://devnet.solana.com:8899)
``` ```
Finally, to check the balance, run the following command: Finally, to check the balance, run the following command:

14
book/src/running-archiver.md
View File

@ -8,9 +8,9 @@ Please note some of the information and instructions described here may change i
Archivers are specialized light clients. They download a part of the ledger \(a.k.a Segment\) and store it. They earn rewards for storing segments. Archivers are specialized light clients. They download a part of the ledger \(a.k.a Segment\) and store it. They earn rewards for storing segments.
The testnet features a validator running at testnet.solana.com, which serves as the entrypoint to the cluster for your archiver node. The testnet features a validator running at devnet.solana.com, which serves as the entrypoint to the cluster for your archiver node.
Additionally there is a blockexplorer available at [http://testnet.solana.com/](http://testnet.solana.com/). Additionally there is a blockexplorer available at [http://devnet.solana.com/](http://devnet.solana.com/).
The testnet is configured to reset the ledger daily, or sooner should the hourly automated cluster sanity test fail. The testnet is configured to reset the ledger daily, or sooner should the hourly automated cluster sanity test fail.
@ -29,10 +29,10 @@ Before starting an archiver node, sanity check that the cluster is accessible to
Fetch the current 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://testnet.solana.com:8899 curl -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1, "method":"getTransactionCount"}' http://devnet.solana.com:8899
``` ```
Inspect the blockexplorer at [http://testnet.solana.com/](http://testnet.solana.com/) for activity. Inspect the blockexplorer at [http://devnet.solana.com/](http://devnet.solana.com/) for activity.
View the [metrics dashboard](https://metrics.solana.com:3000/d/testnet-beta/testnet-monitor-beta?var-testnet=testnet) for more detail on cluster activity. View the [metrics dashboard](https://metrics.solana.com:3000/d/testnet-beta/testnet-monitor-beta?var-testnet=testnet) for more detail on cluster activity.
@ -95,7 +95,7 @@ Download the binaries by navigating to [https://github.com/solana-labs/solana/re
Try running following command to join the gossip network and view all the other nodes in the cluster: Try running following command to join the gossip network and view all the other nodes in the cluster:
```bash ```bash
solana-gossip spy --entrypoint testnet.solana.com:8001 solana-gossip spy --entrypoint devnet.solana.com:8001
# Press ^C to exit # Press ^C to exit
``` ```
@ -138,7 +138,7 @@ Note: Every time the testnet restarts, run the steps to setup the archiver accou
To start the archiver: To start the archiver:
```bash ```bash
solana-archiver --entrypoint testnet.solana.com:8001 --identity-keypair archiver-keypair.json --storage-keypair storage-keypair.json --ledger archiver-ledger solana-archiver --entrypoint devnet.solana.com:8001 --identity-keypair archiver-keypair.json --storage-keypair storage-keypair.json --ledger archiver-ledger
``` ```
## Verify Archiver Setup ## Verify Archiver Setup
@ -146,7 +146,7 @@ solana-archiver --entrypoint testnet.solana.com:8001 --identity-keypair archiver
From another console, confirm the IP address and **identity pubkey** of your archiver is visible in the gossip network by running: From another console, confirm the IP address and **identity pubkey** of your archiver is visible in the gossip network by running:
```bash ```bash
solana-gossip spy --entrypoint testnet.solana.com:8001 solana-gossip spy --entrypoint devnet.solana.com:8001
``` ```
Provide the **storage account pubkey** to the `solana storage-account` command to view the recent mining activity from your archiver: Provide the **storage account pubkey** to the `solana storage-account` command to view the recent mining activity from your archiver:

4
book/src/running-validator/README.md
View File

@ -13,9 +13,7 @@ serve as the entrypoint to the cluster for your validator.
Current testnet entrypoints: Current testnet entrypoints:
* Stable, testnet.solana.com * Developer testnet, devnet.solana.com
* Beta, beta.testnet.solana.com
* Edge, edge.testnet.solana.com
Solana may launch special testnets for validator participation; we will provide Solana may launch special testnets for validator participation; we will provide
you with a specific entrypoint URL to use. you with a specific entrypoint URL to use.

10
book/src/running-validator/validator-monitor.md
View File

@ -6,7 +6,7 @@ Confirm the IP address and **identity pubkey** of your validator is visible in
the gossip network by running: the gossip network by running:
```bash ```bash
solana-gossip spy --entrypoint testnet.solana.com:8001 solana-gossip spy --entrypoint devnet.solana.com:8001
``` ```
## Check Your Balance ## Check Your Balance
@ -35,13 +35,13 @@ cluster, as well as the health of the cluster:
```bash ```bash
# Similar to solana-gossip, you should see your validator in the list of cluster nodes # Similar to solana-gossip, you should see your validator in the list of cluster nodes
curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"getClusterNodes"}' http://testnet.solana.com:8899 curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"getClusterNodes"}' http://devnet.solana.com:8899
# If your validator is properly voting, it should appear in the list of `current` vote accounts. If staked, `stake` should be > 0 # If your validator is properly voting, it should appear in the list of `current` vote accounts. If staked, `stake` should be > 0
curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"getVoteAccounts"}' http://testnet.solana.com:8899 curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"getVoteAccounts"}' http://devnet.solana.com:8899
# Returns the current leader schedule # Returns the current leader schedule
curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"getLeaderSchedule"}' http://testnet.solana.com:8899 curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"getLeaderSchedule"}' http://devnet.solana.com:8899
# Returns info about the current epoch. slotIndex should progress on subsequent calls. # Returns info about the current epoch. slotIndex should progress on subsequent calls.
curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"getEpochInfo"}' http://testnet.solana.com:8899 curl -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"getEpochInfo"}' http://devnet.solana.com:8899
``` ```

12
book/src/running-validator/validator-start.md
View File

@ -6,11 +6,11 @@ The solana cli includes `get` and `set` configuration commands to automatically
set the `--url` argument for cli commands. For example: set the `--url` argument for cli commands. For example:
```bash ```bash
solana config set --url http://testnet.solana.com:8899 solana config set --url http://devnet.solana.com:8899
``` ```
\(You can always override the set configuration by explicitly passing the \(You can always override the set configuration by explicitly passing the
`--url` argument with a command, eg: `solana --url http://beta.testnet.solana.com:8899 balance`\) `--url` argument with a command, eg: `solana --url http://beta.devnet.solana.com:8899 balance`\)
## Confirm The Testnet Is Reachable ## Confirm The Testnet Is Reachable
@ -33,7 +33,7 @@ Try running following command to join the gossip network and view all the other
nodes in the cluster: nodes in the cluster:
```bash ```bash
solana-gossip spy --entrypoint testnet.solana.com:8001 solana-gossip spy --entrypoint devnet.solana.com:8001
# Press ^C to exit # Press ^C to exit
``` ```
@ -107,7 +107,7 @@ You should see the following output:
```text ```text
Wallet Config Updated: /home/solana/.config/solana/wallet/config.yml Wallet Config Updated: /home/solana/.config/solana/wallet/config.yml
* url: http://testnet.solana.com:8899 * url: http://devnet.solana.com:8899
* keypair: /home/solana/validator-keypair.json * keypair: /home/solana/validator-keypair.json
``` ```
@ -155,7 +155,7 @@ Connect to a testnet cluster by running:
```bash ```bash
solana-validator --identity-keypair ~/validator-keypair.json --voting-keypair ~/validator-vote-keypair.json \ solana-validator --identity-keypair ~/validator-keypair.json --voting-keypair ~/validator-vote-keypair.json \
--ledger ~/validator-ledger --rpc-port 8899 --entrypoint testnet.solana.com:8001 \ --ledger ~/validator-ledger --rpc-port 8899 --entrypoint devnet.solana.com:8001 \
--limit-ledger-size --limit-ledger-size
``` ```
@ -166,7 +166,7 @@ Confirm your validator connected to the network by opening a new terminal and
running: running:
```bash ```bash
solana-gossip spy --entrypoint testnet.solana.com:8001 solana-gossip spy --entrypoint devnet.solana.com:8001
``` ```
If your validator is connected, its public key and IP address will appear in the list. If your validator is connected, its public key and IP address will appear in the list.

9
book/src/running-validator/validator-testnet.md
View File

@ -5,8 +5,7 @@ that serves as an entrypoint to the cluster.
Current testnet entrypoints: Current testnet entrypoints:
* Stable: testnet.solana.com * Stable: devnet.solana.com
* Beta: beta.testnet.solana.com
Application developers should target the Stable testnet. Key differences Application developers should target the Stable testnet. Key differences
between the Stable testnet and what will be mainnet: between the Stable testnet and what will be mainnet:
@ -28,13 +27,13 @@ You can submit a JSON-RPC request to see the specific software version of the
cluster. Use this to specify [the software version to install](validator-software.md). cluster. Use this to specify [the software version to install](validator-software.md).
```bash ```bash
curl -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1, "method":"getVersion"}' testnet.solana.com:8899 curl -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1, "method":"getVersion"}' devnet.solana.com:8899
``` ```
Example result: Example result:
`{"jsonrpc":"2.0","result":{"solana-core":"0.21.0"},"id":1}` `{"jsonrpc":"2.0","result":{"solana-core":"0.21.0"},"id":1}`
## Using a Different Testnet ## Using a Different Testnet
This guide is written in the context of testnet.solana.com, our most stable This guide is written in the context of devnet.solana.com, our most stable
cluster. To participate in another testnet, modify the commands in the following cluster. To participate in another testnet, modify the commands in the following
pages, replacing `testnet.solana.com` with your desired testnet. pages, replacing `devnet.solana.com` with your desired testnet.

6
ci/testnet-manager.sh
View File

@ -261,7 +261,7 @@ deploy() {
set -x set -x
ci/testnet-deploy.sh -p edge-testnet-solana-com -C gce -z us-west1-b \ ci/testnet-deploy.sh -p edge-testnet-solana-com -C gce -z us-west1-b \
-t "$CHANNEL_OR_TAG" -n 3 -c 0 -u -P \ -t "$CHANNEL_OR_TAG" -n 3 -c 0 -u -P \
-a edge-testnet-solana-com --letsencrypt edge.testnet.solana.com \ -a edge-testnet-solana-com --letsencrypt edge.devnet.solana.com \
--limit-ledger-size \ --limit-ledger-size \
${skipCreate:+-e} \ ${skipCreate:+-e} \
${skipStart:+-s} \ ${skipStart:+-s} \
@ -274,7 +274,7 @@ deploy() {
set -x set -x
ci/testnet-deploy.sh -p beta-testnet-solana-com -C gce -z us-west1-b \ ci/testnet-deploy.sh -p beta-testnet-solana-com -C gce -z us-west1-b \
-t "$CHANNEL_OR_TAG" -n 3 -c 0 -u -P \ -t "$CHANNEL_OR_TAG" -n 3 -c 0 -u -P \
-a beta-testnet-solana-com --letsencrypt beta.testnet.solana.com \ -a beta-testnet-solana-com --letsencrypt beta.devnet.solana.com \
--limit-ledger-size \ --limit-ledger-size \
${skipCreate:+-e} \ ${skipCreate:+-e} \
${skipStart:+-s} \ ${skipStart:+-s} \
@ -287,7 +287,7 @@ deploy() {
set -x set -x
ci/testnet-deploy.sh -p testnet-solana-com -C gce -z us-west1-b \ ci/testnet-deploy.sh -p testnet-solana-com -C gce -z us-west1-b \
-t "$CHANNEL_OR_TAG" -n 0 -c 0 -u -P \ -t "$CHANNEL_OR_TAG" -n 0 -c 0 -u -P \
-a testnet-solana-com --letsencrypt testnet.solana.com \ -a testnet-solana-com --letsencrypt devnet.solana.com \
--limit-ledger-size \ --limit-ledger-size \
${skipCreate:+-e} \ ${skipCreate:+-e} \
${skipStart:+-s} \ ${skipStart:+-s} \

2
install/src/defaults.rs
View File

@ -1,4 +1,4 @@
pub const JSON_RPC_URL: &str = "http://testnet.solana.com:8899"; pub const JSON_RPC_URL: &str = "http://devnet.solana.com:8899";
lazy_static! { lazy_static! {
pub static ref CONFIG_FILE: Option<String> = { pub static ref CONFIG_FILE: Option<String> = {

4
scripts/solana-install-deploy.sh
View File

@ -46,10 +46,10 @@ esac
case $URL in case $URL in
edge|beta) edge|beta)
URL=http://$URL.testnet.solana.com:8899 URL=http://$URL.devnet.solana.com:8899
;; ;;
stable) stable)
URL=http://testnet.solana.com:8899 URL=http://devnet.solana.com:8899
;; ;;
localhost) localhost)
URL=http://localhost:8899 URL=http://localhost:8899