@@ -113,35 +113,3 @@ problem is solved by this code?" On the other hand, if a test does fail and you
better way to solve the same problem, a Pull Request with your solution would most certainly be
welcome! Likewise, if rewriting a test can better communicate what code it's protecting, please
send us that patch!
-
-# Disclaimer
-
-All claims, content, designs, algorithms, estimates, roadmaps,
-specifications, and performance measurements described in this project
-are done with the Solana Labs, Inc. (“SL”) good faith efforts. It is up to
-the reader to check and validate their accuracy and truthfulness.
-Furthermore, nothing in this project constitutes a solicitation for
-investment.
-
-Any content produced by SL or developer resources that SL provides are
-for educational and inspirational purposes only. SL does not encourage,
-induce or sanction the deployment, integration or use of any such
-applications (including the code comprising the Solana blockchain
-protocol) in violation of applicable laws or regulations and hereby
-prohibits any such deployment, integration or use. This includes the use of
-any such applications by the reader (a) in violation of export control
-or sanctions laws of the United States or any other applicable
-jurisdiction, (b) if the reader is located in or ordinarily resident in
-a country or territory subject to comprehensive sanctions administered
-by the U.S. Office of Foreign Assets Control (OFAC), or (c) if the
-reader is or is working on behalf of a Specially Designated National
-(SDN) or a person subject to similar blocking or denied party
-prohibitions.
-
-The reader should be aware that U.S. export control and sanctions laws prohibit
-U.S. persons (and other persons that are subject to such laws) from transacting
-with persons in certain countries and territories or that are on the SDN list.
-Accordingly, there is a risk to individuals that other persons using any of the
-code contained in this repo, or a derivation thereof, may be sanctioned persons
-and that transactions with such persons would be a violation of U.S. export
-controls and sanctions law.
diff --git a/cargo-registry/Cargo.toml b/cargo-registry/Cargo.toml
index 4e13f477ee5e2d..395493a8e85f00 100644
--- a/cargo-registry/Cargo.toml
+++ b/cargo-registry/Cargo.toml
@@ -1,7 +1,7 @@
[package]
-name = "solana-cargo-registry"
+name = "agave-cargo-registry"
description = "Solana cargo registry"
-documentation = "https://docs.rs/solana-cargo-registry"
+documentation = "https://docs.rs/agave-cargo-registry"
version = { workspace = true }
authors = { workspace = true }
repository = { workspace = true }
diff --git a/ci/buildkite-pipeline-in-disk.sh b/ci/buildkite-pipeline-in-disk.sh
index ad12e1fc000a89..2ce8af0432106b 100755
--- a/ci/buildkite-pipeline-in-disk.sh
+++ b/ci/buildkite-pipeline-in-disk.sh
@@ -289,7 +289,7 @@ if [[ -n $BUILDKITE_TAG ]]; then
start_pipeline "Tag pipeline for $BUILDKITE_TAG"
annotate --style info --context release-tag \
- "https://github.com/solana-labs/solana/releases/$BUILDKITE_TAG"
+ "https://github.com/anza-xyz/agave/releases/$BUILDKITE_TAG"
# Jump directly to the secondary build to publish release artifacts quickly
trigger_secondary_step
@@ -307,7 +307,7 @@ if [[ $BUILDKITE_BRANCH =~ ^pull ]]; then
# Add helpful link back to the corresponding Github Pull Request
annotate --style info --context pr-backlink \
- "Github Pull Request: https://github.com/solana-labs/solana/$BUILDKITE_BRANCH"
+ "Github Pull Request: https://github.com/anza-xyz/agave/$BUILDKITE_BRANCH"
if [[ $GITHUB_USER = "dependabot[bot]" ]]; then
command_step dependabot "ci/dependabot-pr.sh" 5
diff --git a/ci/buildkite-pipeline.sh b/ci/buildkite-pipeline.sh
index d40273863cc7a3..4ae00c9feab586 100755
--- a/ci/buildkite-pipeline.sh
+++ b/ci/buildkite-pipeline.sh
@@ -121,8 +121,8 @@ EOF
trigger_secondary_step() {
cat >> "$output_file" <<"EOF"
- - name: "Trigger Build on solana-secondary"
- trigger: "solana-secondary"
+ - name: "Trigger Build on agave-secondary"
+ trigger: "agave-secondary"
branches: "!pull/*"
async: true
soft_fail: true
@@ -315,7 +315,7 @@ if [[ -n $BUILDKITE_TAG ]]; then
start_pipeline "Tag pipeline for $BUILDKITE_TAG"
annotate --style info --context release-tag \
- "https://github.com/solana-labs/solana/releases/$BUILDKITE_TAG"
+ "https://github.com/anza-xyz/agave/releases/$BUILDKITE_TAG"
# Jump directly to the secondary build to publish release artifacts quickly
trigger_secondary_step
@@ -333,7 +333,7 @@ if [[ $BUILDKITE_BRANCH =~ ^pull ]]; then
# Add helpful link back to the corresponding Github Pull Request
annotate --style info --context pr-backlink \
- "Github Pull Request: https://github.com/solana-labs/solana/$BUILDKITE_BRANCH"
+ "Github Pull Request: https://github.com/anza-xyz/agave/$BUILDKITE_BRANCH"
if [[ $GITHUB_USER = "dependabot[bot]" ]]; then
command_step dependabot "ci/dependabot-pr.sh" 5
diff --git a/ci/buildkite-solana-private.sh b/ci/buildkite-solana-private.sh
index 70d8e4bfe4f59f..e5886a314eb27c 100755
--- a/ci/buildkite-solana-private.sh
+++ b/ci/buildkite-solana-private.sh
@@ -287,7 +287,7 @@ if [[ $BUILDKITE_BRANCH =~ ^pull ]]; then
# Add helpful link back to the corresponding Github Pull Request
annotate --style info --context pr-backlink \
- "Github Pull Request: https://github.com/solana-labs/solana/$BUILDKITE_BRANCH"
+ "Github Pull Request: https://github.com/anza-xyz/agave/$BUILDKITE_BRANCH"
if [[ $GITHUB_USER = "dependabot[bot]" ]]; then
command_step dependabot "ci/dependabot-pr.sh" 5
diff --git a/ci/channel-info.sh b/ci/channel-info.sh
index c82806454d012c..2bb808365653c6 100755
--- a/ci/channel-info.sh
+++ b/ci/channel-info.sh
@@ -11,7 +11,7 @@ here="$(dirname "$0")"
# shellcheck source=ci/semver_bash/semver.sh
source "$here"/semver_bash/semver.sh
-remote=https://github.com/solana-labs/solana.git
+remote=https://github.com/anza-xyz/agave.git
# Fetch all vX.Y.Z tags
#
diff --git a/ci/dependabot-pr.sh b/ci/dependabot-pr.sh
index 91ecd5948c9a43..bb019001a0bcfa 100755
--- a/ci/dependabot-pr.sh
+++ b/ci/dependabot-pr.sh
@@ -21,7 +21,7 @@ fi
echo --- "(FAILING) Backpropagating dependabot-triggered Cargo.lock updates"
name="dependabot-buildkite"
-api_base="https://api.github.com/repos/solana-labs/solana/pulls"
+api_base="https://api.github.com/repos/anza-xyz/agave/pulls"
pr_num=$(echo "$BUILDKITE_BRANCH" | grep -Eo '[0-9]+')
branch=$(curl -s "$api_base/$pr_num" | python3 -c 'import json,sys;print(json.load(sys.stdin)["head"]["ref"])')
diff --git a/ci/localnet-sanity.sh b/ci/localnet-sanity.sh
index e6734e180aa2da..b01eca31d50d81 100755
--- a/ci/localnet-sanity.sh
+++ b/ci/localnet-sanity.sh
@@ -202,8 +202,8 @@ killNodes() {
# Try to use the RPC exit API to cleanly exit the first two nodes
# (dynamic nodes, -x, are just killed)
echo "--- RPC exit"
- $solana_validator --ledger "$SOLANA_CONFIG_DIR"/bootstrap-validator exit --force || true
- $solana_validator --ledger "$SOLANA_CONFIG_DIR"/validator exit --force || true
+ $agave_validator --ledger "$SOLANA_CONFIG_DIR"/bootstrap-validator exit --force || true
+ $agave_validator --ledger "$SOLANA_CONFIG_DIR"/validator exit --force || true
# Give the nodes a splash of time to cleanly exit before killing them
sleep 2
diff --git a/ci/publish-installer.sh b/ci/publish-installer.sh
index 4b5345ae0d26fe..f7d98ffd5ddcf9 100755
--- a/ci/publish-installer.sh
+++ b/ci/publish-installer.sh
@@ -26,14 +26,14 @@ fi
# upload install script
source ci/upload-ci-artifact.sh
-cat >release.solana.com-install <release.anza.xyz-install <>release.solana.com-install
+cat install/agave-install-init.sh >>release.anza.xyz-install
-echo --- AWS S3 Store: "install"
-upload-s3-artifact "/solana/release.solana.com-install" "s3://release.solana.com/$CHANNEL_OR_TAG/install"
+echo --- GCS: "install"
+upload-gcs-artifact "/solana/release.anza.xyz-install" "gs://anza-release/$CHANNEL_OR_TAG/install"
echo Published to:
-ci/format-url.sh https://release.solana.com/"$CHANNEL_OR_TAG"/install
+ci/format-url.sh https://release.anza.xyz/"$CHANNEL_OR_TAG"/install
diff --git a/ci/publish-tarball.sh b/ci/publish-tarball.sh
index ff72bb7da2d066..da5862fb3de1d2 100755
--- a/ci/publish-tarball.sh
+++ b/ci/publish-tarball.sh
@@ -93,7 +93,7 @@ echo --- Creating release tarball
tar cvf "${TARBALL_BASENAME}"-$TARGET.tar "${RELEASE_BASENAME}"
bzip2 "${TARBALL_BASENAME}"-$TARGET.tar
- cp "${RELEASE_BASENAME}"/bin/solana-install-init solana-install-init-$TARGET
+ cp "${RELEASE_BASENAME}"/bin/agave-install-init agave-install-init-$TARGET
cp "${RELEASE_BASENAME}"/version.yml "${TARBALL_BASENAME}"-$TARGET.yml
)
@@ -110,7 +110,7 @@ fi
source ci/upload-ci-artifact.sh
-for file in "${TARBALL_BASENAME}"-$TARGET.tar.bz2 "${TARBALL_BASENAME}"-$TARGET.yml solana-install-init-"$TARGET"* $MAYBE_TARBALLS; do
+for file in "${TARBALL_BASENAME}"-$TARGET.tar.bz2 "${TARBALL_BASENAME}"-$TARGET.yml agave-install-init-"$TARGET"* $MAYBE_TARBALLS; do
if [[ -n $DO_NOT_PUBLISH_TAR ]]; then
upload-ci-artifact "$file"
echo "Skipped $file due to DO_NOT_PUBLISH_TAR"
@@ -118,11 +118,11 @@ for file in "${TARBALL_BASENAME}"-$TARGET.tar.bz2 "${TARBALL_BASENAME}"-$TARGET.
fi
if [[ -n $BUILDKITE ]]; then
- echo --- AWS S3 Store: "$file"
- upload-s3-artifact "/solana/$file" s3://release.solana.com/"$CHANNEL_OR_TAG"/"$file"
+ echo --- GCS Store: "$file"
+ upload-gcs-artifact "/solana/$file" gs://anza-release/"$CHANNEL_OR_TAG"/"$file"
echo Published to:
- $DRYRUN ci/format-url.sh https://release.solana.com/"$CHANNEL_OR_TAG"/"$file"
+ $DRYRUN ci/format-url.sh https://release.anza.xyz/"$CHANNEL_OR_TAG"/"$file"
if [[ -n $TAG ]]; then
ci/upload-github-release-asset.sh "$file"
diff --git a/ci/run-sanity.sh b/ci/run-sanity.sh
index 8108d13a061fd5..88a6f40b1adf28 100755
--- a/ci/run-sanity.sh
+++ b/ci/run-sanity.sh
@@ -31,7 +31,7 @@ while [[ $latest_slot -le $((snapshot_slot + 1)) ]]; do
latest_slot=$($solana_cli --url http://localhost:8899 slot --commitment processed)
done
-$solana_validator --ledger config/ledger exit --force || true
+$agave_validator --ledger config/ledger exit --force || true
wait $pid
diff --git a/ci/rust-version.sh b/ci/rust-version.sh
index 3321f1d5ecb6a1..97ebb1c7935006 100644
--- a/ci/rust-version.sh
+++ b/ci/rust-version.sh
@@ -37,7 +37,7 @@ export rust_stable="$stable_version"
export rust_nightly=nightly-"$nightly_version"
-export ci_docker_image="solanalabs/ci:rust_${rust_stable}_${rust_nightly}"
+export ci_docker_image="anzaxyz/ci:rust_${rust_stable}_${rust_nightly}"
[[ -z $1 ]] || (
diff --git a/ci/test-coverage.sh b/ci/test-coverage.sh
index 44231cd338a13e..ffd362acd287b8 100755
--- a/ci/test-coverage.sh
+++ b/ci/test-coverage.sh
@@ -32,5 +32,5 @@ else
codecov -t "${CODECOV_TOKEN}"
annotate --style success --context codecov.io \
- "CodeCov report: https://codecov.io/github/solana-labs/solana/commit/${CI_COMMIT:0:9}"
+ "CodeCov report: https://codecov.io/github/anza-xyz/agave/commit/${CI_COMMIT:0:9}"
fi
diff --git a/ci/upload-ci-artifact.sh b/ci/upload-ci-artifact.sh
index 1236da9f27114a..e7cc34ab2b2d8c 100644
--- a/ci/upload-ci-artifact.sh
+++ b/ci/upload-ci-artifact.sh
@@ -40,3 +40,13 @@ upload-s3-artifact() {
docker run "${args[@]}"
)
}
+
+upload-gcs-artifact() {
+ echo "--- artifact: $1 to $2"
+ docker run --rm \
+ -v "$GCS_RELEASE_BUCKET_WRITER_CREDIENTIAL:/application_default_credentials.json" \
+ -v "$PWD:/solana" \
+ -e CLOUDSDK_AUTH_CREDENTIAL_FILE_OVERRIDE=/application_default_credentials.json \
+ gcr.io/google.com/cloudsdktool/google-cloud-cli:latest \
+ gcloud storage cp "$1" "$2"
+}
diff --git a/ci/upload-github-release-asset.sh b/ci/upload-github-release-asset.sh
index ca2ae2a8f60443..229fb8993edafd 100755
--- a/ci/upload-github-release-asset.sh
+++ b/ci/upload-github-release-asset.sh
@@ -26,7 +26,7 @@ fi
# Force CI_REPO_SLUG since sometimes
# BUILDKITE_TRIGGERED_FROM_BUILD_PIPELINE_SLUG is not set correctly, causing the
# artifact upload to fail
-CI_REPO_SLUG=solana-labs/solana
+CI_REPO_SLUG=anza-xyz/agave
#if [[ -z $CI_REPO_SLUG ]]; then
# echo Error: CI_REPO_SLUG not defined
# exit 1
diff --git a/docs/src/backwards-compatibility.md b/docs/src/backwards-compatibility.md
index 4a3c60b8e129bd..0fdc388ea2dbae 100644
--- a/docs/src/backwards-compatibility.md
+++ b/docs/src/backwards-compatibility.md
@@ -76,7 +76,7 @@ Major releases:
- [`solana-program`](https://docs.rs/solana-program/) - Rust SDK for writing programs
- [`solana-client`](https://docs.rs/solana-client/) - Rust client for connecting to RPC API
- [`solana-cli-config`](https://docs.rs/solana-cli-config/) - Rust client for managing Solana CLI config files
-- [`solana-geyser-plugin-interface`](https://docs.rs/solana-geyser-plugin-interface/) - Rust interface for developing Solana Geyser plugins.
+- [`agave-geyser-plugin-interface`](https://docs.rs/agave-geyser-plugin-interface/) - Rust interface for developing Solana Geyser plugins.
Patch releases:
diff --git a/docs/src/cli/install.md b/docs/src/cli/install.md
index 3667c733e3f4d4..20f6516314fb02 100644
--- a/docs/src/cli/install.md
+++ b/docs/src/cli/install.md
@@ -56,7 +56,7 @@ Please update your PATH environment variable to include the solana programs:
solana --version
```
-- After a successful install, `solana-install update` may be used to easily
+- After a successful install, `agave-install update` may be used to easily
update the Solana software to a newer version at any time.
---
@@ -74,7 +74,7 @@ solana --version
installer into a temporary directory:
```bash
-cmd /c "curl https://release.solana.com/LATEST_SOLANA_RELEASE_VERSION/solana-install-init-x86_64-pc-windows-msvc.exe --output C:\solana-install-tmp\solana-install-init.exe --create-dirs"
+cmd /c "curl https://release.solana.com/LATEST_SOLANA_RELEASE_VERSION/agave-install-init-x86_64-pc-windows-msvc.exe --output C:\agave-install-tmp\agave-install-init.exe --create-dirs"
```
- Copy and paste the following command, then press Enter to install the latest
@@ -82,7 +82,7 @@ cmd /c "curl https://release.solana.com/LATEST_SOLANA_RELEASE_VERSION/solana-ins
to allow the program to run.
```bash
-C:\solana-install-tmp\solana-install-init.exe LATEST_SOLANA_RELEASE_VERSION
+C:\agave-install-tmp\agave-install-init.exe LATEST_SOLANA_RELEASE_VERSION
```
- When the installer is finished, press Enter.
@@ -97,12 +97,12 @@ C:\solana-install-tmp\solana-install-init.exe LATEST_SOLANA_RELEASE_VERSION
solana --version
```
-- After a successful install, `solana-install update` may be used to easily
+- After a successful install, `agave-install update` may be used to easily
update the Solana software to a newer version at any time.
## Download Prebuilt Binaries
-If you would rather not use `solana-install` to manage the install, you can
+If you would rather not use `agave-install` to manage the install, you can
manually download and install the binaries.
### Linux
@@ -255,7 +255,7 @@ You can then run the following command to obtain the same result as with
prebuilt binaries:
```bash
-solana-install init
+agave-install init
```
## Use Homebrew
diff --git a/docs/src/clusters/available.md b/docs/src/clusters/available.md
index dfbca41672b499..52a7d469ad0cc5 100644
--- a/docs/src/clusters/available.md
+++ b/docs/src/clusters/available.md
@@ -41,10 +41,10 @@ export SOLANA_METRICS_CONFIG="host=https://metrics.solana.com:8086,db=devnet,u=s
solana config set --url https://api.devnet.solana.com
```
-##### Example `solana-validator` command-line
+##### Example `agave-validator` command-line
```bash
-$ solana-validator \
+$ agave-validator \
--identity validator-keypair.json \
--vote-account vote-account-keypair.json \
--known-validator dv1ZAGvdsz5hHLwWXsVnM94hWf1pjbKVau1QVkaMJ92 \
@@ -93,10 +93,10 @@ export SOLANA_METRICS_CONFIG="host=https://metrics.solana.com:8086,db=tds,u=test
solana config set --url https://api.testnet.solana.com
```
-##### Example `solana-validator` command-line
+##### Example `agave-validator` command-line
```bash
-$ solana-validator \
+$ agave-validator \
--identity validator-keypair.json \
--vote-account vote-account-keypair.json \
--known-validator 5D1fNXzvv5NjV1ysLjirC4WY92RNsVH18vjmcszZd8on \
@@ -145,10 +145,10 @@ export SOLANA_METRICS_CONFIG="host=https://metrics.solana.com:8086,db=mainnet-be
solana config set --url https://api.mainnet-beta.solana.com
```
-##### Example `solana-validator` command-line
+##### Example `agave-validator` command-line
```bash
-$ solana-validator \
+$ agave-validator \
--identity ~/validator-keypair.json \
--vote-account ~/vote-account-keypair.json \
--known-validator 7Np41oeYqPefeNQEHSv1UDhYrehxin3NStELsSKCT4K2 \
diff --git a/docs/src/clusters/benchmark.md b/docs/src/clusters/benchmark.md
index d913f9e5f16392..35978cdd0967dd 100644
--- a/docs/src/clusters/benchmark.md
+++ b/docs/src/clusters/benchmark.md
@@ -108,7 +108,7 @@ For example
Generally we are using `debug` for infrequent debug messages, `trace` for potentially frequent messages and `info` for performance-related logging.
-You can also attach to a running process with GDB. The leader's process is named _solana-validator_:
+You can also attach to a running process with GDB. The leader's process is named _agave-validator_:
```bash
sudo gdb
diff --git a/docs/src/implemented-proposals/installer.md b/docs/src/implemented-proposals/installer.md
index a3ad797171c5b8..c052aa7b4e54e5 100644
--- a/docs/src/implemented-proposals/installer.md
+++ b/docs/src/implemented-proposals/installer.md
@@ -13,16 +13,16 @@ This document proposes an easy to use software install and updater that can be u
The easiest install method for supported platforms:
```bash
-$ curl -sSf https://raw.githubusercontent.com/solana-labs/solana/v1.0.0/install/solana-install-init.sh | sh
+$ curl -sSf https://raw.githubusercontent.com/solana-labs/solana/v1.0.0/install/agave-install-init.sh | sh
```
-This script will check github for the latest tagged release and download and run the `solana-install-init` binary from there.
+This script will check github for the latest tagged release and download and run the `agave-install-init` binary from there.
If additional arguments need to be specified during the installation, the following shell syntax is used:
```bash
-$ init_args=.... # arguments for `solana-install-init ...`
-$ curl -sSf https://raw.githubusercontent.com/solana-labs/solana/v1.0.0/install/solana-install-init.sh | sh -s - ${init_args}
+$ init_args=.... # arguments for `agave-install-init ...`
+$ curl -sSf https://raw.githubusercontent.com/solana-labs/solana/v1.0.0/install/agave-install-init.sh | sh -s - ${init_args}
```
### Fetch and run a pre-built installer from a Github release
@@ -30,9 +30,9 @@ $ curl -sSf https://raw.githubusercontent.com/solana-labs/solana/v1.0.0/install/
With a well-known release URL, a pre-built binary can be obtained for supported platforms:
```bash
-$ curl -o solana-install-init https://github.com/solana-labs/solana/releases/download/v1.0.0/solana-install-init-x86_64-apple-darwin
-$ chmod +x ./solana-install-init
-$ ./solana-install-init --help
+$ curl -o agave-install-init https://github.com/solana-labs/solana/releases/download/v1.0.0/agave-install-init-x86_64-apple-darwin
+$ chmod +x ./agave-install-init
+$ ./agave-install-init --help
```
### Build and run the installer from source
@@ -51,16 +51,16 @@ Given a solana release tarball \(as created by `ci/publish-tarball.sh`\) that ha
```bash
$ solana-keygen new -o update-manifest.json # <-- only generated once, the public key is shared with users
-$ solana-install deploy http://example.com/path/to/solana-release.tar.bz2 update-manifest.json
+$ agave-install deploy http://example.com/path/to/solana-release.tar.bz2 update-manifest.json
```
### Run a validator node that auto updates itself
```bash
-$ solana-install init --pubkey 92DMonmBYXwEMHJ99c9ceRSpAmk9v6i3RdvDdXaVcrfj # <-- pubkey is obtained from whoever is deploying the updates
-$ export PATH=~/.local/share/solana-install/bin:$PATH
+$ agave-install init --pubkey 92DMonmBYXwEMHJ99c9ceRSpAmk9v6i3RdvDdXaVcrfj # <-- pubkey is obtained from whoever is deploying the updates
+$ export PATH=~/.local/share/agave-install/bin:$PATH
$ solana-keygen ... # <-- runs the latest solana-keygen
-$ solana-install run solana-validator ... # <-- runs a validator, restarting it as necessary when an update is applied
+$ agave-install run agave-validator ... # <-- runs a validator, restarting it as necessary when an update is applied
```
## On-chain Update Manifest
@@ -87,9 +87,9 @@ pub struct SignedUpdateManifest {
}
```
-Note that the `manifest` field itself contains a corresponding signature \(`manifest_signature`\) to guard against man-in-the-middle attacks between the `solana-install` tool and the solana cluster RPC API.
+Note that the `manifest` field itself contains a corresponding signature \(`manifest_signature`\) to guard against man-in-the-middle attacks between the `agave-install` tool and the solana cluster RPC API.
-To guard against rollback attacks, `solana-install` will refuse to install an update with an older `timestamp_secs` than what is currently installed.
+To guard against rollback attacks, `agave-install` will refuse to install an update with an older `timestamp_secs` than what is currently installed.
## Release Archive Contents
@@ -101,17 +101,17 @@ A release archive is expected to be a tar file compressed with bzip2 with the fo
- `/bin/` -- directory containing available programs in the release.
- `solana-install` will symlink this directory to
+ `agave-install` will symlink this directory to
- `~/.local/share/solana-install/bin` for use by the `PATH` environment
+ `~/.local/share/agave-install/bin` for use by the `PATH` environment
variable.
- `...` -- any additional files and directories are permitted
-## solana-install Tool
+## agave-install Tool
-The `solana-install` tool is used by the user to install and update their cluster software.
+The `agave-install` tool is used by the user to install and update their cluster software.
It manages the following files and directories in the user's home directory:
@@ -122,11 +122,11 @@ It manages the following files and directories in the user's home directory:
### Command-line Interface
```text
-solana-install 0.16.0
+agave-install 0.16.0
The solana cluster software installer
USAGE:
- solana-install [OPTIONS]
+ agave-install [OPTIONS]
FLAGS:
-h, --help Prints help information
@@ -145,11 +145,11 @@ SUBCOMMANDS:
```
```text
-solana-install-init
+agave-install-init
initializes a new installation
USAGE:
- solana-install init [OPTIONS]
+ agave-install init [OPTIONS]
FLAGS:
-h, --help Prints help information
@@ -161,11 +161,11 @@ OPTIONS:
```
```text
-solana-install info
+agave-install info
displays information about the current installation
USAGE:
- solana-install info [FLAGS]
+ agave-install info [FLAGS]
FLAGS:
-h, --help Prints help information
@@ -173,11 +173,11 @@ FLAGS:
```
```text
-solana-install deploy
+agave-install deploy
deploys a new update
USAGE:
- solana-install deploy
+ agave-install deploy
FLAGS:
-h, --help Prints help information
@@ -188,22 +188,22 @@ ARGS:
```
```text
-solana-install update
+agave-install update
checks for an update, and if available downloads and applies it
USAGE:
- solana-install update
+ agave-install update
FLAGS:
-h, --help Prints help information
```
```text
-solana-install run
+agave-install run
Runs a program while periodically checking and applying software updates
USAGE:
- solana-install run [program_arguments]...
+ agave-install run [program_arguments]...
FLAGS:
-h, --help Prints help information
diff --git a/docs/src/implemented-proposals/rpc-transaction-history.md b/docs/src/implemented-proposals/rpc-transaction-history.md
index 54288ad9659bd7..607a79ce658b98 100644
--- a/docs/src/implemented-proposals/rpc-transaction-history.md
+++ b/docs/src/implemented-proposals/rpc-transaction-history.md
@@ -68,7 +68,7 @@ the results of BigTable queries more complicated but is not a significant issue.
## Data Population
The ongoing population of instance data will occur on an epoch cadence through
-the use of a new `solana-ledger-tool` command that will convert rocksdb data for
+the use of a new `agave-ledger-tool` command that will convert rocksdb data for
a given slot range into the instance schema.
The same process will be run once, manually, to backfill the existing ledger
diff --git a/docs/src/operations/best-practices/general.md b/docs/src/operations/best-practices/general.md
index 29ef42c81b7f5f..3e531b0160c571 100644
--- a/docs/src/operations/best-practices/general.md
+++ b/docs/src/operations/best-practices/general.md
@@ -23,12 +23,12 @@ watch past workshops through the
## Help with the validator command line
-From within the Solana CLI, you can execute the `solana-validator` command with
+From within the Solana CLI, you can execute the `agave-validator` command with
the `--help` flag to get a better understanding of the flags and sub commands
available.
```
-solana-validator --help
+agave-validator --help
```
## Restarting your validator
@@ -49,14 +49,14 @@ solana leader-schedule
Based on the current slot and the leader schedule, you can calculate open time
windows where your validator is not expected to produce blocks.
-Assuming you are ready to restart, you may use the `solana-validator exit`
+Assuming you are ready to restart, you may use the `agave-validator exit`
command. The command exits your validator process when an appropriate idle time
window is reached. Assuming that you have systemd implemented for your validator
process, the validator should restart automatically after the exit. See the
below help command for details:
```
-solana-validator exit --help
+agave-validator exit --help
```
## Upgrading
@@ -75,28 +75,28 @@ process.
It is a best practice to always build your Solana binaries from source. If you
build from source, you are certain that the code you are building has not been
tampered with before the binary was created. You may also be able to optimize
-your `solana-validator` binary to your specific hardware.
+your `agave-validator` binary to your specific hardware.
If you build from source on the validator machine (or a machine with the same
CPU), you can target your specific architecture using the `-march` flag. Refer
to the following doc for
[instructions on building from source](../../cli/install.md#build-from-source).
-### solana-install
+### agave-install
If you are not comfortable building from source, or you need to quickly install
a new version to test something out, you could instead try using the
-`solana-install` command.
+`agave-install` command.
Assuming you want to install Solana version `1.14.17`, you would execute the
following:
```
-solana-install init 1.14.17
+agave-install init 1.14.17
```
This command downloads the executable for `1.14.17` and installs it into a
-`.local` directory. You can also look at `solana-install --help` for more
+`.local` directory. You can also look at `agave-install --help` for more
options.
> **Note** this command only works if you already have the solana cli installed.
@@ -106,7 +106,7 @@ options.
### Restart
For all install methods, the validator process will need to be restarted before
-the newly installed version is in use. Use `solana-validator exit` to restart
+the newly installed version is in use. Use `agave-validator exit` to restart
your validator process.
### Verifying version
@@ -132,13 +132,13 @@ have state locally. In other cases such as restarts for upgrades, a snapshot
download should be avoided.
To avoid downloading a snapshot on restart, add the following flag to the
-`solana-validator` command:
+`agave-validator` command:
```
--no-snapshot-fetch
```
-If you use this flag with the `solana-validator` command, make sure that you run
+If you use this flag with the `agave-validator` command, make sure that you run
`solana catchup ` after your validator starts to make sure that the
validator is catching up in a reasonable time. After some time (potentially a
few hours), if it appears that your validator continues to fall behind, then you
@@ -199,7 +199,7 @@ It is important that you do not accidentally run out of funds in your identity
account, as your node will stop voting. It is also important to note that this
account keypair is the most vulnerable of the three keypairs in a vote account
because the keypair for the identity account is stored on your validator when
-running the `solana-validator` software. How much SOL you should store there is
+running the `agave-validator` software. How much SOL you should store there is
up to you. As a best practice, make sure to check the account regularly and
refill or deduct from it as needed. To check the account balance do:
@@ -207,7 +207,7 @@ refill or deduct from it as needed. To check the account balance do:
solana balance validator-keypair.json
```
-> **Note** `solana-watchtower` can monitor for a minimum validator identity
+> **Note** `agave-watchtower` can monitor for a minimum validator identity
> balance. See [monitoring best practices](./monitoring.md) for details.
## Withdrawing From The Vote Account
diff --git a/docs/src/operations/best-practices/monitoring.md b/docs/src/operations/best-practices/monitoring.md
index 6d04fc38487be7..a0f2ef9df9fa22 100644
--- a/docs/src/operations/best-practices/monitoring.md
+++ b/docs/src/operations/best-practices/monitoring.md
@@ -4,34 +4,34 @@ sidebar_label: Monitoring
pagination_label: "Best Practices: Validator Monitoring"
---
-It is essential that you have monitoring in place on your validator. In the event that your validator is delinquent (behind the rest of the network) you want to respond immediately to fix the issue. One very useful tool to monitor your validator is [`solana-watchtower`](#solana-watchtower).
+It is essential that you have monitoring in place on your validator. In the event that your validator is delinquent (behind the rest of the network) you want to respond immediately to fix the issue. One very useful tool to monitor your validator is [`agave-watchtower`](#agave-watchtower).
## Solana Watchtower
-Solana Watchtower is an extremely useful monitoring tool that will regularly monitor the health of your validator. It can monitor your validator for delinquency then notify you on your application of choice: Slack, Discord, Telegram or Twilio. Additionally, `solana-watchtower` has the ability to monitor the health of the entire cluster so that you can be aware of any cluster wide problems.
+Solana Watchtower is an extremely useful monitoring tool that will regularly monitor the health of your validator. It can monitor your validator for delinquency then notify you on your application of choice: Slack, Discord, Telegram or Twilio. Additionally, `agave-watchtower` has the ability to monitor the health of the entire cluster so that you can be aware of any cluster wide problems.
### Getting Started
-To get started with Solana Watchtower, run `solana-watchtower --help`. From the help menu, you can see the optional flags and an explanation of the command.
+To get started with Solana Watchtower, run `agave-watchtower --help`. From the help menu, you can see the optional flags and an explanation of the command.
Here is a sample command that will monitor a validator node with an identity public key of `2uTk98rqqwENevkPH2AHHzGHXgeGc1h6ku8hQUqWeXZp`:
```
-solana-watchtower --monitor-active-stake --validator-identity \
+agave-watchtower --monitor-active-stake --validator-identity \
2uTk98rqqwENevkPH2AHHzGHXgeGc1h6ku8hQUqWeXZp
```
-The command will monitor your validator, but you will not get notifications unless you added the environment variables mentioned in `solana-watchtower --help`. Since getting each of these services setup for notifications is not straight forward, the next section will walk through [setting up watchtower notifications on Telegram](#setup-telegram-notifications).
+The command will monitor your validator, but you will not get notifications unless you added the environment variables mentioned in `agave-watchtower --help`. Since getting each of these services setup for notifications is not straight forward, the next section will walk through [setting up watchtower notifications on Telegram](#setup-telegram-notifications).
### Best Practices
-It is a best practice to run the `solana-watchtower` command on a separate server from your validator.
+It is a best practice to run the `agave-watchtower` command on a separate server from your validator.
-In the case that you run `solana-watchtower` on the same computer as your `solana-validator` process, then during catastrophic events like a power outage, you will not be aware of the issue, because your `solana-watchtower` process will stop at the same time as your `solana-validator` process.
+In the case that you run `agave-watchtower` on the same computer as your `agave-validator` process, then during catastrophic events like a power outage, you will not be aware of the issue, because your `agave-watchtower` process will stop at the same time as your `agave-validator` process.
-Additionally, while running the `solana-watchtower` process manually with environment variables set in the terminal is a good way to test out the command, it is not operationally sound because the process will not be restarted when the terminal closes or during a system restart.
+Additionally, while running the `agave-watchtower` process manually with environment variables set in the terminal is a good way to test out the command, it is not operationally sound because the process will not be restarted when the terminal closes or during a system restart.
-Instead, you could run your `solana-watchtower` command as a system process similar to `solana-validator`. In the system process file, you can specify the environment variables for your bot.
+Instead, you could run your `agave-watchtower` command as a system process similar to `agave-validator`. In the system process file, you can specify the environment variables for your bot.
### Setup Telegram Notifications
@@ -41,7 +41,7 @@ To send validator health notifications to your Telegram account, we are going to
2. Send a message to the bot
3. Create a Telegram group that will get the watchtower notifications
4. Add the environment variables to your command line environment
-5. Restart the `solana-watchtower` command
+5. Restart the `agave-watchtower` command
#### Create a Bot Using BotFather
@@ -61,7 +61,7 @@ In Telegram, click on the new message icon and then select new group. Find your
Now that you have a bot setup, you will need to set the environment variables for the bot so that watchtower can send notifications.
-First, recall the chat message that you got from _@BotFather_. In the message, there was an HTTP API token for your bot. The token will have this format: `389178471:MMTKMrnZB4ErUzJmuFIXTKE6DupLSgoa7h4o`. You will use that token to set the `TELEGRAM_BOT_TOKEN` environment variable. In the terminal where you plan to run `solana-watchtower`, run the following:
+First, recall the chat message that you got from _@BotFather_. In the message, there was an HTTP API token for your bot. The token will have this format: `389178471:MMTKMrnZB4ErUzJmuFIXTKE6DupLSgoa7h4o`. You will use that token to set the `TELEGRAM_BOT_TOKEN` environment variable. In the terminal where you plan to run `agave-watchtower`, run the following:
```
export TELEGRAM_BOT_TOKEN=
@@ -73,14 +73,14 @@ Next, in your browser, go to `https://api.telegram.org/bot/getUp
The response should be in JSON. Search for the string `"chat":` in the JSON. The `id` value of that chat is your `TELEGRAM_CHAT_ID`. It will be a negative number like: `-781559558`. Remember to include the negative sign! If you cannot find `"chat":` in the JSON, then you may have to remove the bot from your chat group and add it again.
-With your Telegram chat id in hand, export the environment variable where you plan to run `solana-watchtower`:
+With your Telegram chat id in hand, export the environment variable where you plan to run `agave-watchtower`:
```
export TELEGRAM_CHAT_ID=
```
-#### Restart solana-watchtower
+#### Restart agave-watchtower
-Once your environment variables are set, restart `solana-watchtower`. You should see output about your validator.
+Once your environment variables are set, restart `agave-watchtower`. You should see output about your validator.
To test that your Telegram configuration is working properly, you could stop your validator briefly until it is labeled as delinquent. Up to a minute after the validator is delinquent, you should receive a message in the Telegram group from your bot. Start the validator again and verify that you get another message in your Telegram group from the bot. The message should say `all clear`.
\ No newline at end of file
diff --git a/docs/src/operations/guides/restart-cluster.md b/docs/src/operations/guides/restart-cluster.md
index 85d4731d604c65..cda3f30a5a016d 100644
--- a/docs/src/operations/guides/restart-cluster.md
+++ b/docs/src/operations/guides/restart-cluster.md
@@ -11,7 +11,7 @@ pagination_label: "Validator Guides: Restart a Cluster"
In Solana 1.14 or greater, run the following command to output the latest
optimistically confirmed slot your validator observed:
```bash
-solana-ledger-tool -l ledger latest-optimistic-slots
+agave-ledger-tool -l ledger latest-optimistic-slots
```
In Solana 1.13 or less, the latest optimistically confirmed can be found by looking for the more recent occurrence of
@@ -34,11 +34,11 @@ instead.
### Step 4. Create a new snapshot for slot `SLOT_X` with a hard fork at slot `SLOT_X`
```bash
-$ solana-ledger-tool -l --snapshot-archive-path --incremental-snapshot-archive-path create-snapshot SLOT_X --hard-fork SLOT_X
+$ agave-ledger-tool -l --snapshot-archive-path --incremental-snapshot-archive-path create-snapshot SLOT_X --hard-fork SLOT_X
```
The snapshots directory should now contain the new snapshot.
-`solana-ledger-tool create-snapshot` will also output the new shred version, and bank hash value,
+`agave-ledger-tool create-snapshot` will also output the new shred version, and bank hash value,
call this NEW_SHRED_VERSION and NEW_BANK_HASH respectively.
Adjust your validator's arguments:
@@ -68,7 +68,7 @@ Post something like the following to #announcements (adjusting the text as appro
> 2. a. Preferred method, start from your local ledger with:
>
> ```bash
-> solana-validator
+> agave-validator
> --wait-for-supermajority SLOT_X # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
> --expected-bank-hash NEW_BANK_HASH # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
> --hard-fork SLOT_X # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
@@ -84,7 +84,7 @@ Post something like the following to #announcements (adjusting the text as appro
> b. If your validator doesn't have ledger up to slot SLOT_X or if you have deleted your ledger, have it instead download a snapshot with:
>
> ```bash
-> solana-validator
+> agave-validator
> --wait-for-supermajority SLOT_X # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
> --expected-bank-hash NEW_BANK_HASH # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
> --entrypoint entrypoint.testnet.solana.com:8001
@@ -95,7 +95,7 @@ Post something like the following to #announcements (adjusting the text as appro
> ... # <-- your other --identity/--vote-account/etc arguments
> ```
>
-> You can check for which slots your ledger has with: `solana-ledger-tool -l path/to/ledger bounds`
+> You can check for which slots your ledger has with: `agave-ledger-tool -l path/to/ledger bounds`
>
> 3. Wait until 80% of the stake comes online
>
@@ -122,7 +122,7 @@ and create a new snapshot with additional `--destake-vote-account `
arguments for each of the non-responsive validator's vote account address
```bash
-$ solana-ledger-tool -l ledger create-snapshot SLOT_X ledger --hard-fork SLOT_X \
+$ agave-ledger-tool -l ledger create-snapshot SLOT_X ledger --hard-fork SLOT_X \
--destake-vote-account \
--destake-vote-account \
.
diff --git a/docs/src/operations/guides/validator-failover.md b/docs/src/operations/guides/validator-failover.md
index 168a1a4312cec0..b7b3fea568194b 100644
--- a/docs/src/operations/guides/validator-failover.md
+++ b/docs/src/operations/guides/validator-failover.md
@@ -85,11 +85,11 @@ For more information on etcd TLS setup, please refer to
https://etcd.io/docs/v3.5/op-guide/security/#example-2-client-to-server-authentication-with-https-client-certificates
### Primary Validator
-The following additional `solana-validator` parameters are required to enable
+The following additional `agave-validator` parameters are required to enable
tower storage into etcd:
```
-solana-validator ... \
+agave-validator ... \
--tower-storage etcd \
--etcd-cacert-file certs/etcd-ca.pem \
--etcd-cert-file certs/validator.pem \
@@ -103,7 +103,7 @@ that your etcd endpoint remain accessible at all times.
### Secondary Validator
Configure the secondary validator like the primary with the exception of the
-following `solana-validator` command-line argument changes:
+following `agave-validator` command-line argument changes:
* Generate and use a secondary validator identity: `--identity secondary-validator-keypair.json`
* Add `--no-check-vote-account`
* Add `--authorized-voter validator-keypair.json` (where
@@ -114,8 +114,8 @@ When both validators are running normally and caught up to the cluster, a
failover from primary to secondary can be triggered by running the following
command on the secondary validator:
```bash
-$ solana-validator wait-for-restart-window --identity validator-keypair.json \
- && solana-validator set-identity validator-keypair.json
+$ agave-validator wait-for-restart-window --identity validator-keypair.json \
+ && agave-validator set-identity validator-keypair.json
```
The secondary validator will acquire a lock on the tower in etcd to ensure
@@ -131,7 +131,7 @@ exit. However if/when the secondary validator restarts, it will do so using the
secondary validator identity and thus the restart cycle is broken.
## Triggering a failover via monitoring
-Monitoring of your choosing can invoke the `solana-validator set-identity
+Monitoring of your choosing can invoke the `agave-validator set-identity
validator-keypair.json` command mentioned in the previous section.
It is not necessary to guarantee the primary validator has halted before failing
diff --git a/docs/src/operations/guides/validator-start.md b/docs/src/operations/guides/validator-start.md
index 378783798b3ce8..d86c714be4e6a6 100644
--- a/docs/src/operations/guides/validator-start.md
+++ b/docs/src/operations/guides/validator-start.md
@@ -32,7 +32,7 @@ detail on cluster activity.
## Enabling CUDA
If your machine has a GPU with CUDA installed \(Linux-only currently\), include
-the `--cuda` argument to `solana-validator`.
+the `--cuda` argument to `agave-validator`.
When your validator is started look for the following log message to indicate
that CUDA is enabled: `"[ solana::validator] CUDA is enabled"`
@@ -47,7 +47,7 @@ the following commands.
#### **Optimize sysctl knobs**
```bash
-sudo bash -c "cat >/etc/sysctl.d/21-solana-validator.conf </etc/sysctl.d/21-agave-validator.conf <`
-argument to `solana-validator`. You can specify multiple ones by repeating the argument `--known-validator --known-validator `.
+argument to `agave-validator`. You can specify multiple ones by repeating the argument `--known-validator --known-validator `.
This has two effects, one is when the validator is booting with `--only-known-rpc`, it will only ask that set of
known nodes for downloading genesis and snapshot data. Another is that in combination with the `--halt-on-known-validators-accounts-hash-mismatch` option,
it will monitor the merkle root hash of the entire accounts state of other known nodes on gossip and if the hashes produce any mismatch,
@@ -277,13 +277,13 @@ account state divergence.
Connect to the cluster by running:
```bash
-solana-validator \
+agave-validator \
--identity ~/validator-keypair.json \
--vote-account ~/vote-account-keypair.json \
--rpc-port 8899 \
--entrypoint entrypoint.devnet.solana.com:8001 \
--limit-ledger-size \
- --log ~/solana-validator.log
+ --log ~/agave-validator.log
```
To force validator logging to the console add a `--log -` argument, otherwise
@@ -296,7 +296,7 @@ The ledger will be placed in the `ledger/` directory by default, use the
> [paper wallet seed phrase](../../cli/wallets/paper.md)
> for your `--identity` and/or
> `--authorized-voter` keypairs. To use these, pass the respective argument as
-> `solana-validator --identity ASK ... --authorized-voter ASK ...`
+> `agave-validator --identity ASK ... --authorized-voter ASK ...`
> and you will be prompted to enter your seed phrases and optional passphrase.
Confirm your validator is connected to the network by opening a new terminal and
@@ -312,7 +312,7 @@ If your validator is connected, its public key and IP address will appear in the
By default the validator will dynamically select available network ports in the
8000-10000 range, and may be overridden with `--dynamic-port-range`. For
-example, `solana-validator --dynamic-port-range 11000-11020 ...` will restrict
+example, `agave-validator --dynamic-port-range 11000-11020 ...` will restrict
the validator to ports 11000-11020.
### Limiting ledger size to conserve disk space
@@ -366,8 +366,8 @@ WantedBy=multi-user.target
```
Now create `/home/sol/bin/validator.sh` to include the desired
-`solana-validator` command-line. Ensure that the 'exec' command is used to
-start the validator process (i.e. "exec solana-validator ..."). This is
+`agave-validator` command-line. Ensure that the 'exec' command is used to
+start the validator process (i.e. "exec agave-validator ..."). This is
important because without it, logrotate will end up killing the validator
every time the logs are rotated.
@@ -394,14 +394,14 @@ to be reverted and the issue reproduced before help can be provided.
#### Log rotation
-The validator log file, as specified by `--log ~/solana-validator.log`, can get
+The validator log file, as specified by `--log ~/agave-validator.log`, can get
very large over time and it's recommended that log rotation be configured.
The validator will re-open its log file when it receives the `USR1` signal, which is the
basic primitive that enables log rotation.
If the validator is being started by a wrapper shell script, it is important to
-launch the process with `exec` (`exec solana-validator ...`) when using logrotate.
+launch the process with `exec` (`exec agave-validator ...`) when using logrotate.
This will prevent the `USR1` signal from being sent to the script's process
instead of the validator's, which will kill them both.
@@ -409,13 +409,13 @@ instead of the validator's, which will kill them both.
An example setup for the `logrotate`, which assumes that the validator is
running as a systemd service called `sol.service` and writes a log file at
-/home/sol/solana-validator.log:
+/home/sol/agave-validator.log:
```bash
# Setup log rotation
cat > logrotate.sol </etc/sysctl.d/21-solana-validator.conf </etc/sysctl.d/21-agave-validator.conf < For more explanation on the flags used in the command, refer to the `solana-validator --help` command
+> For more explanation on the flags used in the command, refer to the `agave-validator --help` command
```
#!/bin/bash
-exec solana-validator \
+exec agave-validator \
--identity /home/sol/validator-keypair.json \
--known-validator 5D1fNXzvv5NjV1ysLjirC4WY92RNsVH18vjmcszZd8on \
--known-validator dDzy5SR3AXdYWVqbDEkVFdvSPCtS9ihF5kJkHCtXoFs \
diff --git a/docs/src/validator/geyser.md b/docs/src/validator/geyser.md
index 769856303767d6..efea2e18e30269 100644
--- a/docs/src/validator/geyser.md
+++ b/docs/src/validator/geyser.md
@@ -24,20 +24,20 @@ implementation for the PostgreSQL database.
### Important Crates:
-- [`solana-geyser-plugin-interface`] — This crate defines the plugin
+- [`agave-geyser-plugin-interface`] — This crate defines the plugin
interfaces.
- [`solana-accountsdb-plugin-postgres`] — The crate for the referential
plugin implementation for the PostgreSQL database.
-[`solana-geyser-plugin-interface`]: https://docs.rs/solana-geyser-plugin-interface
+[`agave-geyser-plugin-interface`]: https://docs.rs/agave-geyser-plugin-interface
[`solana-accountsdb-plugin-postgres`]: https://docs.rs/solana-accountsdb-plugin-postgres
[`solana-sdk`]: https://docs.rs/solana-sdk
[`solana-transaction-status`]: https://docs.rs/solana-transaction-status
## The Plugin Interface
-The Plugin interface is declared in [`solana-geyser-plugin-interface`]. It
+The Plugin interface is declared in [`agave-geyser-plugin-interface`]. It
is defined by the trait `GeyserPlugin`. The plugin should implement the
trait and expose a "C" function `_create_plugin` to return the pointer to this
trait. For example, in the referential implementation, the following code
@@ -166,7 +166,7 @@ please refer to [`solana-sdk`] and [`solana-transaction-status`]
The `slot` points to the slot the transaction is executed at.
For more details, please refer to the Rust documentation in
-[`solana-geyser-plugin-interface`].
+[`agave-geyser-plugin-interface`].
## Example PostgreSQL Plugin
diff --git a/geyser-plugin-interface/Cargo.toml b/geyser-plugin-interface/Cargo.toml
index af99758b47d630..56f42fd4612cec 100644
--- a/geyser-plugin-interface/Cargo.toml
+++ b/geyser-plugin-interface/Cargo.toml
@@ -1,7 +1,7 @@
[package]
-name = "solana-geyser-plugin-interface"
+name = "agave-geyser-plugin-interface"
description = "The Solana Geyser plugin interface."
-documentation = "https://docs.rs/solana-geyser-plugin-interface"
+documentation = "https://docs.rs/agave-geyser-plugin-interface"
version = { workspace = true }
authors = { workspace = true }
repository = { workspace = true }
diff --git a/geyser-plugin-interface/src/geyser_plugin_interface.rs b/geyser-plugin-interface/src/geyser_plugin_interface.rs
index 037aedf8b87e89..d9a3b00f8dc4c8 100644
--- a/geyser-plugin-interface/src/geyser_plugin_interface.rs
+++ b/geyser-plugin-interface/src/geyser_plugin_interface.rs
@@ -327,7 +327,7 @@ pub trait GeyserPlugin: Any + Send + Sync + std::fmt::Debug {
/// # Examples
///
/// ```
- /// use solana_geyser_plugin_interface::geyser_plugin_interface::{GeyserPlugin,
+ /// use agave_geyser_plugin_interface::geyser_plugin_interface::{GeyserPlugin,
/// GeyserPluginError, Result};
///
/// #[derive(Debug)]
diff --git a/geyser-plugin-manager/Cargo.toml b/geyser-plugin-manager/Cargo.toml
index d905248150b717..ebef2f637f642d 100644
--- a/geyser-plugin-manager/Cargo.toml
+++ b/geyser-plugin-manager/Cargo.toml
@@ -10,6 +10,7 @@ license = { workspace = true }
edition = { workspace = true }
[dependencies]
+agave-geyser-plugin-interface = { workspace = true }
bs58 = { workspace = true }
crossbeam-channel = { workspace = true }
json5 = { workspace = true }
@@ -20,7 +21,6 @@ log = { workspace = true }
serde_json = { workspace = true }
solana-accounts-db = { workspace = true }
solana-entry = { workspace = true }
-solana-geyser-plugin-interface = { workspace = true }
solana-ledger = { workspace = true }
solana-measure = { workspace = true }
solana-metrics = { workspace = true }
diff --git a/geyser-plugin-manager/src/accounts_update_notifier.rs b/geyser-plugin-manager/src/accounts_update_notifier.rs
index 7c7e3370fc00eb..90ab0b7998a35c 100644
--- a/geyser-plugin-manager/src/accounts_update_notifier.rs
+++ b/geyser-plugin-manager/src/accounts_update_notifier.rs
@@ -1,14 +1,14 @@
/// Module responsible for notifying plugins of account updates
use {
crate::geyser_plugin_manager::GeyserPluginManager,
+ agave_geyser_plugin_interface::geyser_plugin_interface::{
+ ReplicaAccountInfoV3, ReplicaAccountInfoVersions,
+ },
log::*,
solana_accounts_db::{
account_storage::meta::StoredAccountMeta,
accounts_update_notifier_interface::AccountsUpdateNotifierInterface,
},
- solana_geyser_plugin_interface::geyser_plugin_interface::{
- ReplicaAccountInfoV3, ReplicaAccountInfoVersions,
- },
solana_measure::measure::Measure,
solana_metrics::*,
solana_sdk::{
diff --git a/geyser-plugin-manager/src/block_metadata_notifier.rs b/geyser-plugin-manager/src/block_metadata_notifier.rs
index 76d203c5e0ed44..87f15f41fc0ae0 100644
--- a/geyser-plugin-manager/src/block_metadata_notifier.rs
+++ b/geyser-plugin-manager/src/block_metadata_notifier.rs
@@ -3,10 +3,10 @@ use {
block_metadata_notifier_interface::BlockMetadataNotifier,
geyser_plugin_manager::GeyserPluginManager,
},
- log::*,
- solana_geyser_plugin_interface::geyser_plugin_interface::{
+ agave_geyser_plugin_interface::geyser_plugin_interface::{
ReplicaBlockInfoV3, ReplicaBlockInfoVersions,
},
+ log::*,
solana_measure::measure::Measure,
solana_metrics::*,
solana_sdk::{clock::UnixTimestamp, pubkey::Pubkey, reward_info::RewardInfo},
diff --git a/geyser-plugin-manager/src/entry_notifier.rs b/geyser-plugin-manager/src/entry_notifier.rs
index ea14592b615db8..da9a9698ed1540 100644
--- a/geyser-plugin-manager/src/entry_notifier.rs
+++ b/geyser-plugin-manager/src/entry_notifier.rs
@@ -1,11 +1,11 @@
/// Module responsible for notifying plugins about entries
use {
crate::geyser_plugin_manager::GeyserPluginManager,
- log::*,
- solana_entry::entry::EntrySummary,
- solana_geyser_plugin_interface::geyser_plugin_interface::{
+ agave_geyser_plugin_interface::geyser_plugin_interface::{
ReplicaEntryInfoV2, ReplicaEntryInfoVersions,
},
+ log::*,
+ solana_entry::entry::EntrySummary,
solana_ledger::entry_notifier_interface::EntryNotifier,
solana_measure::measure::Measure,
solana_metrics::*,
diff --git a/geyser-plugin-manager/src/geyser_plugin_manager.rs b/geyser-plugin-manager/src/geyser_plugin_manager.rs
index a15f9e1318075d..3d0abe16899637 100644
--- a/geyser-plugin-manager/src/geyser_plugin_manager.rs
+++ b/geyser-plugin-manager/src/geyser_plugin_manager.rs
@@ -1,9 +1,9 @@
use {
+ agave_geyser_plugin_interface::geyser_plugin_interface::GeyserPlugin,
jsonrpc_core::{ErrorCode, Result as JsonRpcResult},
jsonrpc_server_utils::tokio::sync::oneshot::Sender as OneShotSender,
libloading::Library,
log::*,
- solana_geyser_plugin_interface::geyser_plugin_interface::GeyserPlugin,
std::{
ops::{Deref, DerefMut},
path::Path,
@@ -442,8 +442,8 @@ mod tests {
crate::geyser_plugin_manager::{
GeyserPluginManager, LoadedGeyserPlugin, TESTPLUGIN2_CONFIG, TESTPLUGIN_CONFIG,
},
+ agave_geyser_plugin_interface::geyser_plugin_interface::GeyserPlugin,
libloading::Library,
- solana_geyser_plugin_interface::geyser_plugin_interface::GeyserPlugin,
std::sync::{Arc, RwLock},
};
diff --git a/geyser-plugin-manager/src/slot_status_notifier.rs b/geyser-plugin-manager/src/slot_status_notifier.rs
index 587abe2f79d4de..1557bb2d4d8c36 100644
--- a/geyser-plugin-manager/src/slot_status_notifier.rs
+++ b/geyser-plugin-manager/src/slot_status_notifier.rs
@@ -1,7 +1,7 @@
use {
crate::geyser_plugin_manager::GeyserPluginManager,
+ agave_geyser_plugin_interface::geyser_plugin_interface::SlotStatus,
log::*,
- solana_geyser_plugin_interface::geyser_plugin_interface::SlotStatus,
solana_measure::measure::Measure,
solana_metrics::*,
solana_sdk::clock::Slot,
diff --git a/geyser-plugin-manager/src/transaction_notifier.rs b/geyser-plugin-manager/src/transaction_notifier.rs
index ab821e811047d2..b757c1202b377d 100644
--- a/geyser-plugin-manager/src/transaction_notifier.rs
+++ b/geyser-plugin-manager/src/transaction_notifier.rs
@@ -1,10 +1,10 @@
/// Module responsible for notifying plugins of transactions
use {
crate::geyser_plugin_manager::GeyserPluginManager,
- log::*,
- solana_geyser_plugin_interface::geyser_plugin_interface::{
+ agave_geyser_plugin_interface::geyser_plugin_interface::{
ReplicaTransactionInfoV2, ReplicaTransactionInfoVersions,
},
+ log::*,
solana_measure::measure::Measure,
solana_metrics::*,
solana_rpc::transaction_notifier_interface::TransactionNotifier,
diff --git a/install/Cargo.toml b/install/Cargo.toml
index 588d4315df5f35..c40a0ee6e9eee3 100644
--- a/install/Cargo.toml
+++ b/install/Cargo.toml
@@ -1,7 +1,7 @@
[package]
-name = "solana-install"
+name = "agave-install"
description = "The solana cluster software installer"
-documentation = "https://docs.rs/solana-install"
+documentation = "https://docs.rs/agave-install"
version = { workspace = true }
authors = { workspace = true }
repository = { workspace = true }
diff --git a/install/solana-install-init.sh b/install/agave-install-init.sh
similarity index 86%
rename from install/solana-install-init.sh
rename to install/agave-install-init.sh
index db36dc61e2ff30..cf2d1babf3c306 100755
--- a/install/solana-install-init.sh
+++ b/install/agave-install-init.sh
@@ -10,25 +10,25 @@
# except according to those terms.
# This is just a little script that can be downloaded from the internet to
-# install solana-install. It just does platform detection, downloads the installer
+# install agave-install. It just does platform detection, downloads the installer
# and runs it.
{ # this ensures the entire script is downloaded #
if [ -z "$SOLANA_DOWNLOAD_ROOT" ]; then
- SOLANA_DOWNLOAD_ROOT="https://github.com/solana-labs/solana/releases/download/"
+ SOLANA_DOWNLOAD_ROOT="https://github.com/anza-xyz/agave/releases/download/"
fi
-GH_LATEST_RELEASE="https://api.github.com/repos/solana-labs/solana/releases/latest"
+GH_LATEST_RELEASE="https://api.github.com/repos/anza-xyz/agave/releases/latest"
set -e
usage() {
cat 1>&2 < --pubkey
+ agave-install-init [FLAGS] [OPTIONS] --data_dir --pubkey
FLAGS:
-h, --help Prints help information
@@ -81,7 +81,7 @@ main() {
esac
TARGET="${_cputype}-${_ostype}"
- temp_dir="$(mktemp -d 2>/dev/null || ensure mktemp -d -t solana-install-init)"
+ temp_dir="$(mktemp -d 2>/dev/null || ensure mktemp -d -t agave-install-init)"
ensure mkdir -p "$temp_dir"
# Check for SOLANA_RELEASE environment variable override. Otherwise fetch
@@ -101,8 +101,8 @@ main() {
fi
fi
- download_url="$SOLANA_DOWNLOAD_ROOT/$release/solana-install-init-$TARGET"
- solana_install_init="$temp_dir/solana-install-init"
+ download_url="$SOLANA_DOWNLOAD_ROOT/$release/agave-install-init-$TARGET"
+ solana_install_init="$temp_dir/agave-install-init"
printf 'downloading %s installer\n' "$release" 1>&2
@@ -111,7 +111,7 @@ main() {
ensure chmod u+x "$solana_install_init"
if [ ! -x "$solana_install_init" ]; then
printf '%s\n' "Cannot execute $solana_install_init (likely because of mounting /tmp as noexec)." 1>&2
- printf '%s\n' "Please copy the file to a location where you can execute binaries and run ./solana-install-init." 1>&2
+ printf '%s\n' "Please copy the file to a location where you can execute binaries and run ./agave-install-init." 1>&2
exit 1
fi
@@ -130,7 +130,7 @@ main() {
}
err() {
- printf 'solana-install-init: %s\n' "$1" >&2
+ printf 'agave-install-init: %s\n' "$1" >&2
exit 1
}
diff --git a/install/install-help.sh b/install/install-help.sh
index 9fb08afa6d14c9..7604777e378677 100755
--- a/install/install-help.sh
+++ b/install/install-help.sh
@@ -4,11 +4,11 @@ set -e
cd "$(dirname "$0")"/..
cargo="$(readlink -f "./cargo")"
-"$cargo" build --package solana-install
+"$cargo" build --package agave-install
export PATH=$PWD/target/debug:$PATH
echo "\`\`\`manpage"
-solana-install --help
+agave-install --help
echo "\`\`\`"
echo ""
@@ -16,7 +16,7 @@ commands=(init info deploy update run)
for x in "${commands[@]}"; do
echo "\`\`\`manpage"
- solana-install "${x}" --help
+ agave-install "${x}" --help
echo "\`\`\`"
echo ""
done
diff --git a/install/src/bin/solana-install-init.rs b/install/src/bin/agave-install-init.rs
similarity index 92%
rename from install/src/bin/solana-install-init.rs
rename to install/src/bin/agave-install-init.rs
index ec888d8f452090..84c154ac12b35e 100644
--- a/install/src/bin/solana-install-init.rs
+++ b/install/src/bin/agave-install-init.rs
@@ -16,7 +16,7 @@ fn press_enter() {
}
fn main() {
- solana_install::main_init().unwrap_or_else(|err| {
+ agave_install::main_init().unwrap_or_else(|err| {
println!("Error: {err}");
press_enter();
exit(1);
diff --git a/install/src/command.rs b/install/src/command.rs
index d7b92c17690bda..4ae9e7ee38cedd 100644
--- a/install/src/command.rs
+++ b/install/src/command.rs
@@ -540,7 +540,7 @@ pub fn init(
explicit_release: Option,
) -> Result<(), String> {
let config = {
- // Write new config file only if different, so that running |solana-install init|
+ // Write new config file only if different, so that running |agave-install init|
// repeatedly doesn't unnecessarily re-download
let mut current_config = Config::load(config_file).unwrap_or_default();
current_config.current_update_manifest = None;
@@ -572,7 +572,7 @@ pub fn init(
fn github_release_download_url(release_semver: &str) -> String {
format!(
- "https://github.com/solana-labs/solana/releases/download/v{}/solana-release-{}.tar.bz2",
+ "https://github.com/anza-xyz/agave/releases/download/v{}/solana-release-{}.tar.bz2",
release_semver,
crate::build_env::TARGET
)
@@ -580,7 +580,7 @@ fn github_release_download_url(release_semver: &str) -> String {
fn release_channel_download_url(release_channel: &str) -> String {
format!(
- "https://release.solana.com/{}/solana-release-{}.tar.bz2",
+ "https://release.anza.xyz/{}/solana-release-{}.tar.bz2",
release_channel,
crate::build_env::TARGET
)
@@ -588,7 +588,7 @@ fn release_channel_download_url(release_channel: &str) -> String {
fn release_channel_version_url(release_channel: &str) -> String {
format!(
- "https://release.solana.com/{}/solana-release-{}.yml",
+ "https://release.anza.xyz/{}/solana-release-{}.yml",
release_channel,
crate::build_env::TARGET
)
@@ -870,7 +870,7 @@ fn check_for_newer_github_release(
prerelease_allowed: bool,
) -> Result