diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index e01f5318e40257..cba203730a3c73 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -1 +1 @@ -* @anza-xyz/backport-reviewers +* @x1-xyz/backport-reviewers diff --git a/.gitignore b/.gitignore index 995129e50d16cc..17849d552aaef2 100644 --- a/.gitignore +++ b/.gitignore @@ -9,7 +9,7 @@ target/ **/*.rs.bk .cargo -/config/ +/config .cache @@ -31,3 +31,4 @@ log-*/ .DS_Store # scripts that may be generated by cargo *-bpf commands **/cargo-*-bpf-child-script-*.sh +/config/ diff --git a/.mergify.yml b/.mergify.yml index 5cae9b59853f2f..83b24983d66a82 100644 --- a/.mergify.yml +++ b/.mergify.yml @@ -33,7 +33,7 @@ pull_request_rules: actions: request_reviews: teams: - - "@anza-xyz/community-pr-subscribers" + - "@x1-xyz/community-pr-subscribers" - name: label changes from monorepo-triage conditions: - author≠@core-contributors @@ -98,7 +98,7 @@ pull_request_rules: actions: backport: assignees: &BackportAssignee - - "{{ merged_by|replace('mergify[bot]', label|select('equalto', 'community')|first|default(author)|replace('community', '@anza-xyz/community-pr-subscribers')) }}" + - "{{ merged_by|replace('mergify[bot]', label|select('equalto', 'community')|first|default(author)|replace('community', '@x1-xyz/community-pr-subscribers')) }}" title: "{{ destination_branch }}: {{ title }} (backport of #{{ number }})" ignore_conflicts: true labels: diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 35ea55e913f1af..be5bebf6a24654 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -255,9 +255,9 @@ before the PR can be merged. Here are the steps: name = "solana-" version = "0.0.1" description = "" -authors = ["Anza Maintainers "] -repository = "https://github.com/anza-xyz/agave" -homepage = "https://anza.xyz" +authors = ["X1 Labs maintainers "] +repository = "https://github.com/x1-labs/tachyon" +homepage = "https://x1.xyz" documentation = "https://docs.rs/solana-" license = "Apache-2.0" edition = "2021" diff --git a/Cargo.toml b/Cargo.toml index 3ad09b557ea7a5..ab77e193e56b58 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -139,9 +139,9 @@ resolver = "2" [workspace.package] version = "2.0.21" -authors = ["Anza Maintainers "] -repository = "https://github.com/anza-xyz/agave" -homepage = "https://anza.xyz/" +authors = ["X1 Labs maintainers "] +repository = "https://github.com/x1-labs/tachyon" +homepage = "https://x1.xyz/" license = "Apache-2.0" edition = "2021" diff --git a/RELEASE.md b/RELEASE.md index b3a1b6e77c4c08..f93f16bc7ba680 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -70,7 +70,7 @@ There are three release channels that map to branches as follows: 1. Determine the new branch name. The name should be "v" + the first 2 version fields from Cargo.toml. For example, a Cargo.toml with version = "0.9.0" implies the next branch name is "v0.9". -1. Create the new branch and push this branch to the `agave` repository: +1. Create the new branch and push this branch to the `tachyon` repository: ``` git checkout -b git push -u origin @@ -99,15 +99,15 @@ Alternatively use the Github UI. ### Miscellaneous Clean up 1. Pin the spl-token-cli version in the newly promoted stable branch by setting `splTokenCliVersion` in scripts/spl-token-cli-version.sh to the latest release that depends on the stable branch (usually this will be the latest spl-token-cli release). -1. Update [mergify.yml](https://github.com/anza-xyz/agave/blob/master/.mergify.yml) to add backport actions for the new branch and remove actions for the obsolete branch. -1. Adjust the [Github backport labels](https://github.com/anza-xyz/agave/labels) to add the new branch label and remove the label for the obsolete branch. +1. Update [mergify.yml](https://github.com/x1-labs/tachyon/blob/master/.mergify.yml) to add backport actions for the new branch and remove actions for the obsolete branch. +1. Adjust the [Github backport labels](https://github.com/x1-labs/tachyon/labels) to add the new branch label and remove the label for the obsolete branch. 1. Announce on Discord #development that the release branch exists so people know to use the new backport labels. ## Steps to Create a Release ### Create the Release Tag on GitHub -1. Go to [GitHub Releases](https://github.com/anza-xyz/agave/releases) for tagging a release. +1. Go to [GitHub Releases](https://github.com/x1-labs/tachyon/releases) for tagging a release. 1. Click "Draft new release". The release tag must exactly match the `version` field in `/Cargo.toml` prefixed by `v`. 1. If the Cargo.toml version field is **0.12.3**, then the release tag must be **v0.12.3** @@ -115,7 +115,7 @@ Alternatively use the Github UI. 1. If you want to release v0.12.0, the target branch must be v0.12 1. Fill the release notes. 1. If this is the first release on the branch (e.g. v0.13.**0**), paste in [this - template](https://raw.githubusercontent.com/anza-xyz/agave/master/.github/RELEASE_TEMPLATE.md). Engineering Lead can provide summary contents for release notes if needed. + template](https://raw.githubusercontent.com/x1-labs/tachyon/master/.github/RELEASE_TEMPLATE.md). Engineering Lead can provide summary contents for release notes if needed. 1. If this is a patch release, review all the commits since the previous release on this branch and add details as needed. 1. Click "Save Draft", then confirm the release notes look good and the tag name and branch are correct. 1. Ensure all desired commits (usually backports) are landed on the branch by now. @@ -126,24 +126,24 @@ Alternatively use the Github UI. ### Update release branch with the next patch version -[This action](https://github.com/anza-xyz/agave/blob/master/.github/workflows/increment-cargo-version-on-release.yml) ensures that publishing a release will trigger the creation of a PR to update the Cargo.toml files on **release branch** to the next semantic version (e.g. 0.9.0 -> 0.9.1). Ensure that the created PR makes it through CI and gets submitted. +[This action](https://github.com/x1-labs/tachyon/blob/master/.github/workflows/increment-cargo-version-on-release.yml) ensures that publishing a release will trigger the creation of a PR to update the Cargo.toml files on **release branch** to the next semantic version (e.g. 0.9.0 -> 0.9.1). Ensure that the created PR makes it through CI and gets submitted. Note: As of 2024-03-26 the above action is failing so version bumps are done manually. The version bump script is incorrectly updating hashbrown and proc-macro2 versions which should be reverted. ### Prepare for the next release -1. Go to [GitHub Releases](https://github.com/anza-xyz/agave/releases) and create a new draft release for `X.Y.Z+1` with empty release notes. This allows people to incrementally add new release notes until it's time for the next release +1. Go to [GitHub Releases](https://github.com/x1-labs/tachyon/releases) and create a new draft release for `X.Y.Z+1` with empty release notes. This allows people to incrementally add new release notes until it's time for the next release 1. Also, point the branch field to the same branch and mark the release as **"This is a pre-release"**. ### Verify release automation success -Go to [Agave Releases](https://github.com/anza-xyz/agave/releases) and click on the latest release that you just published. +Go to [Tachyon Releases](https://github.com/x1-labs/tachyon/releases) and click on the latest release that you just published. Verify that all of the build artifacts are present (15 assets), then uncheck **"This is a pre-release"** for the release. Build artifacts can take up to 60 minutes after creating the tag before appearing. To check for progress: -* The `agave-secondary` Buildkite pipeline handles creating the Linux and macOS release artifacts and updated crates. Look for a job under the tag name of the release: https://buildkite.com/anza-xyz/agave-secondary. -* The Windows release artifacts are produced by GitHub Actions. Look for a job under the tag name of the release: https://github.com/anza-xyz/agave/actions. +* The `tachyon-secondary` Buildkite pipeline handles creating the Linux and macOS release artifacts and updated crates. Look for a job under the tag name of the release: https://buildkite.com/x1-labs/tachyon-secondary. +* The Windows release artifacts are produced by GitHub Actions. Look for a job under the tag name of the release: https://github.com/x1-labs/tachyon/actions. -[Crates.io tachyon-validator](https://crates.io/crates/tachyon-validator) should have an updated tachyon-validator version. This can take 2-3 hours, and sometimes fails in the `agave-secondary` job. +[Crates.io tachyon-validator](https://crates.io/crates/tachyon-validator) should have an updated tachyon-validator version. This can take 2-3 hours, and sometimes fails in the `tachyon-secondary` job. If this happens and the error is non-fatal, click "Retry" on the "publish crate" job ### Update software on testnet.solana.com diff --git a/SECURITY.md b/SECURITY.md index b1c898106427d5..c1b88b7b058ed9 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -5,11 +5,11 @@ 2. [Incident Response Process](#process) -## Reporting security problems in the Agave Validator +## Reporting security problems in the Tachyon Validator **DO NOT CREATE A GITHUB ISSUE** to report a security problem. -Instead please use this [Report a Vulnerability](https://github.com/anza-xyz/agave/security/advisories/new) link. +Instead please use this [Report a Vulnerability](https://github.com/x1-labs/tachyon/security/advisories/new) link. Provide a helpful title, detailed description of the vulnerability and an exploit proof-of-concept. Speculative submissions without proof-of-concept will be closed with no further consideration. @@ -25,15 +25,10 @@ Expect a response as fast as possible in the advisory, typically within 72 hours -- If you do not receive a response in the advisory, send an email to -security@anza.xyz with the full URL of the advisory you have created. DO NOT +security@x1.xyz with the full URL of the advisory you have created. DO NOT include attachments or provide detail sufficient for exploitation regarding the security issue in this email. **Only provide such details in the advisory**. -If you do not receive a response from security@anza.xyz please followup with -the team directly. You can do this in the `#core-technology` channel of the -[Solana Tech discord server](https://solana.com/discord), by pinging the `Anza` -role in the channel and referencing the fact that you submitted a security problem. - ## Incident Response Process @@ -42,18 +37,18 @@ followed to contain, respond and remediate: ### 1. Accept the new report In response a newly reported security problem, a member of the -`anza-xyz/admins` group will accept the report to turn it into a draft -advisory. The `anza-xyz/security-incident-response` group should be added to +`x1-xyz/admins` group will accept the report to turn it into a draft +advisory. The `x1-xyz/security-incident-response` group should be added to the draft security advisory, and create a private fork of the repository (grey button towards the bottom of the page) if necessary. If the advisory is the result of an audit finding, follow the same process as above but add the auditor's github user(s) and begin the title with "[Audit]". -If the report is out of scope, a member of the `anza-xyz/admins` group will +If the report is out of scope, a member of the `x1-xyz/admins` group will comment as such and then close the report. ### 2. Triage -Within the draft security advisory, discuss and determine the severity of the issue. If necessary, members of the anza-xyz/security-incident-response group may add other github users to the advisory to assist. +Within the draft security advisory, discuss and determine the severity of the issue. If necessary, members of the x1-xyz/security-incident-response group may add other github users to the advisory to assist. If it is determined that this is not a critical network issue then the advisory should be closed and if more follow-up is required a normal Solana public github issue should be created. ### 3. Prepare Fixes @@ -62,7 +57,7 @@ There is no CI available in the private repository so you must build from source Code review from the reporter is ideal, as well as from multiple members of the core development team. ### 4. Notify Security Group Validators -Once an ETA is available for the fix, a member of the anza-xyz/security-incident-response group should notify the validators so they can prepare for an update using the "Solana Red Alert" notification system. +Once an ETA is available for the fix, a member of the x1-xyz/security-incident-response group should notify the validators so they can prepare for an update using the "Solana Red Alert" notification system. The teams are all over the world and it's critical to provide actionable information at the right time. Don't be the person that wakes everybody up at 2am when a fix won't be available for hours. ### 5. Ship the patch diff --git a/ci/buildkite-pipeline-in-disk.sh b/ci/buildkite-pipeline-in-disk.sh index 6139e613410ac8..9fd837ea491e8d 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/FairCrypto/agave-xolana/releases/$BUILDKITE_TAG" + "https://github.com/x1-labs/tachyon/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/FairCrypto/agave-xolana/$BUILDKITE_BRANCH" + "Github Pull Request: https://github.com/x1-labs/tachyon/$BUILDKITE_BRANCH" pull_or_push_steps exit 0 diff --git a/ci/buildkite-pipeline.sh b/ci/buildkite-pipeline.sh index 8df19b77b07ba2..919531f7e9e022 100755 --- a/ci/buildkite-pipeline.sh +++ b/ci/buildkite-pipeline.sh @@ -384,7 +384,7 @@ if [[ -n $BUILDKITE_TAG ]]; then start_pipeline "Tag pipeline for $BUILDKITE_TAG" annotate --style info --context release-tag \ - "https://github.com/FairCrypto/agave-xolana/releases/$BUILDKITE_TAG" + "https://github.com/X1-labs/tachyon/releases/$BUILDKITE_TAG" # Jump directly to the secondary build to publish release artifacts quickly trigger_secondary_step @@ -402,7 +402,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/FairCrypto/agave-xolana/$BUILDKITE_BRANCH" + "Github Pull Request: https://github.com/X1-labs/tachyon/$BUILDKITE_BRANCH" pull_or_push_steps exit 0 diff --git a/ci/buildkite-solana-private.sh b/ci/buildkite-solana-private.sh index 5becda59f408b5..b7a4195ec28fec 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/FairCrypto/agave-xolana/$BUILDKITE_BRANCH" + "Github Pull Request: https://github.com/X1-labs/tachyon/$BUILDKITE_BRANCH" pull_or_push_steps exit 0 diff --git a/ci/channel-info.sh b/ci/channel-info.sh index 400152728cb1a7..e5cf9ef9c36326 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/FairCrypto/agave-xolana.git +remote=https://github.com/X1-labs/tachyon.git # Fetch all vX.Y.Z tags # diff --git a/ci/publish-installer.sh b/ci/publish-installer.sh index f7d98ffd5ddcf9..323175ecd638a9 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.anza.xyz-install <release.x1.xyz-install <>release.anza.xyz-install +cat install/agave-install-init.sh >>release.x1.xyz-install echo --- GCS: "install" -upload-gcs-artifact "/solana/release.anza.xyz-install" "gs://anza-release/$CHANNEL_OR_TAG/install" +upload-gcs-artifact "/solana/release.x1.xyz-install" "gs://anza-release/$CHANNEL_OR_TAG/install" echo Published to: -ci/format-url.sh https://release.anza.xyz/"$CHANNEL_OR_TAG"/install +ci/format-url.sh https://release.x1.xyz/"$CHANNEL_OR_TAG"/install diff --git a/ci/publish-tarball.sh b/ci/publish-tarball.sh index 4746e9fb2ff94b..1d0f7665a762e7 100755 --- a/ci/publish-tarball.sh +++ b/ci/publish-tarball.sh @@ -122,7 +122,7 @@ for file in "${TARBALL_BASENAME}"-$TARGET.tar.bz2 "${TARBALL_BASENAME}"-$TARGET. upload-gcs-artifact "/solana/$file" gs://anza-release/"$CHANNEL_OR_TAG"/"$file" echo Published to: - $DRYRUN ci/format-url.sh https://release.anza.xyz/"$CHANNEL_OR_TAG"/"$file" + $DRYRUN ci/format-url.sh https://release.x1.xyz/"$CHANNEL_OR_TAG"/"$file" if [[ -n $TAG ]]; then ci/upload-github-release-asset.sh "$file" diff --git a/ci/upload-github-release-asset.sh b/ci/upload-github-release-asset.sh index 8d4f442ffe09a7..07d14f360862d6 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=FairCrypto/agave-xolana +CI_REPO_SLUG=X1-labs/tachyon #if [[ -z $CI_REPO_SLUG ]]; then # echo Error: CI_REPO_SLUG not defined # exit 1 diff --git a/docs/docusaurus.config.js b/docs/docusaurus.config.js index 767c3b18f6bb3e..fe079518a4857c 100644 --- a/docs/docusaurus.config.js +++ b/docs/docusaurus.config.js @@ -1,14 +1,14 @@ const math = require("remark-math"); const katex = require("rehype-katex"); module.exports = { - title: "Agave", + title: "Tachyon", tagline: - "Agave is an open source project implementing a new, high-performance, permissionless blockchain.", - url: "https://docs.anza.xyz", + "Tachyon is an open source project implementing a new, high-performance, permissionless blockchain.", + url: "https://docs.x1.xyz", baseUrl: "/", favicon: "img/favicon.ico", - organizationName: "anza-xyz", // Usually your GitHub org/user name. - projectName: "agave", // Usually your repo name. + organizationName: "x1-labs", // Usually your GitHub org/user name. + projectName: "tachyon", // Usually your repo name. onBrokenLinks: "throw", stylesheets: [ { @@ -93,7 +93,7 @@ module.exports = { position: "right", }, { - href: "https://github.com/anza-xyz/agave/", + href: "https://github.com/x1-labs/tachyon/", // label: "GitHub", className: "header-link-icon header-github-link", "aria-label": "GitHub repository", @@ -141,7 +141,7 @@ module.exports = { }, { label: "GitHub »", - href: "https://github.com/anza-xyz/agave", + href: "https://github.com/x1-labs/tachyon", }, { label: "Discord »", @@ -175,7 +175,7 @@ module.exports = { ], }, ], - copyright: `Copyright © ${new Date().getFullYear()} Anza`, + copyright: `Copyright © ${new Date().getFullYear()} X1 Labs`, }, }, presets: [ diff --git a/docs/publish-docs.sh b/docs/publish-docs.sh index c14e9bc9dc3dea..d158c1e67ba0ca 100755 --- a/docs/publish-docs.sh +++ b/docs/publish-docs.sh @@ -9,15 +9,15 @@ fi CONFIG_FILE=vercel.json if [[ -n $CI_TAG ]]; then - PROJECT_NAME=docs-anza-xyz + PROJECT_NAME=docs-x1-xyz else eval "$(../ci/channel-info.sh)" case $CHANNEL in edge) - PROJECT_NAME=edge-docs-anza-xyz + PROJECT_NAME=edge-docs-x1-xyz ;; beta) - PROJECT_NAME=beta-docs-anza-xyz + PROJECT_NAME=beta-docs-x1-xyz ;; *) PROJECT_NAME=docs diff --git a/docs/src/cli/index.md b/docs/src/cli/index.md index 27deffd485dfc9..c6d34671f0cb1b 100644 --- a/docs/src/cli/index.md +++ b/docs/src/cli/index.md @@ -11,7 +11,7 @@ cluster by delegating stake. To interact with a Solana cluster, we will use its command-line interface, also known as the CLI. We use the command-line because it is the first place the -Anza core team deploys new functionality. The command-line interface is not +X1 Labs core team deploys new functionality. The command-line interface is not necessarily the easiest to use, but it provides the most direct, flexible, and secure access to your Solana accounts. diff --git a/docs/src/cli/install.md b/docs/src/cli/install.md index c9a5c682d40592..8b383c81fdd68d 100644 --- a/docs/src/cli/install.md +++ b/docs/src/cli/install.md @@ -19,26 +19,26 @@ on your preferred workflow: - Open your favorite Terminal application -- Install the Agave release - [LATEST_AGAVE_RELEASE_VERSION](https://github.com/anza-xyz/agave/releases/tag/LATEST_AGAVE_RELEASE_VERSION) +- Install the Tachyon release + [LATEST_TACHYON_RELEASE_VERSION](https://github.com/x1-labs/tachyon/releases/tag/LATEST_TACHYON_RELEASE_VERSION) on your machine by running: ```bash -sh -c "$(curl -sSfL https://release.anza.xyz/LATEST_AGAVE_RELEASE_VERSION/install)" +sh -c "$(curl -sSfL https://release.x1.xyz/LATEST_TACHYON_RELEASE_VERSION/install)" ``` -- You can replace `LATEST_AGAVE_RELEASE_VERSION` with the release tag matching +- You can replace `LATEST_TACHYON_RELEASE_VERSION` with the release tag matching the software version of your desired release, or use one of the three symbolic channel names: `stable`, `beta`, or `edge`. - The following output indicates a successful update: ```text -downloading LATEST_AGAVE_RELEASE_VERSION installer +downloading LATEST_TACHYON_RELEASE_VERSION installer Configuration: /home/solana/.config/solana/install/config.yml Active release directory: /home/solana/.local/share/solana/install/active_release -* Release version: LATEST_AGAVE_RELEASE_VERSION -* Release URL: https://github.com/anza-xyz/agave/releases/download/LATEST_AGAVE_RELEASE_VERSION/solana-release-x86_64-unknown-linux-gnu.tar.bz2 +* Release version: LATEST_TACHYON_RELEASE_VERSION +* Release URL: https://github.com/x1-labs/tachyon/releases/download/LATEST_TACHYON_RELEASE_VERSION/solana-release-x86_64-unknown-linux-gnu.tar.bz2 Update successful ``` @@ -56,7 +56,7 @@ Please update your PATH environment variable to include the solana programs: solana --version ``` -- After a successful install, `agave-install update` may be used to easily +- After a successful install, `tachyon-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.anza.xyz/LATEST_AGAVE_RELEASE_VERSION/agave-install-init-x86_64-pc-windows-msvc.exe --output C:\agave-install-tmp\agave-install-init.exe --create-dirs" +cmd /c "curl https://release.x1.xyz/LATEST_TACHYON_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 @@ -108,7 +108,7 @@ manually download and install the binaries. ### Linux Download the binaries by navigating to -[https://github.com/anza-xyz/agave/releases/latest](https://github.com/anza-xyz/agave/releases/latest), +[https://github.com/x1-labs/tachyon/releases/latest](https://github.com/x1-labs/tachyon/releases/latest), download **solana-release-x86_64-unknown-linux-gnu.tar.bz2**, then extract the archive: @@ -121,7 +121,7 @@ export PATH=$PWD/bin:$PATH ### MacOS Download the binaries by navigating to -[https://github.com/anza-xyz/agave/releases/latest](https://github.com/anza-xyz/agave/releases/latest), +[https://github.com/x1-labs/tachyon/releases/latest](https://github.com/x1-labs/tachyon/releases/latest), download **solana-release-x86_64-apple-darwin.tar.bz2**, then extract the archive: @@ -134,7 +134,7 @@ export PATH=$PWD/bin:$PATH ### Windows - Download the binaries by navigating to - [https://github.com/anza-xyz/agave/releases/latest](https://github.com/anza-xyz/agave/releases/latest), + [https://github.com/x1-labs/tachyon/releases/latest](https://github.com/x1-labs/tachyon/releases/latest), download **solana-release-x86_64-pc-windows-msvc.tar.bz2**, then extract the archive using WinZip or similar. @@ -242,7 +242,7 @@ above. After installing the prerequisites, proceed with building Solana from source, navigate to -[Solana's GitHub releases page](https://github.com/anza-xyz/agave/releases/latest), +[Solana's GitHub releases page](https://github.com/x1-labs/tachyon/releases/latest), and download the **Source Code** archive. Extract the code and build the binaries with: diff --git a/docs/src/index.mdx b/docs/src/index.mdx index 6314ed65581456..d150bd08653080 100644 --- a/docs/src/index.mdx +++ b/docs/src/index.mdx @@ -3,19 +3,19 @@ slug: / id: home title: Home sidebar_label: Home -pagination_label: Agave Validator Documentation Home -description: "Agave is a validator for the Solana blockchain maintained by the Anza core engineering team \ +pagination_label: Tachyon Validator Documentation Home +description: "Tachyon is a validator for the Solana blockchain maintained by the X1 Labs core engineering team \ it is a fork of the original Solana validator software." --- -# Agave Validator Documentation +# Tachyon Validator Documentation Solana is a blockchain built for mass adoption. It's a high performance network that is utilized for a range of use cases, including finance, NFTs, payments, and gaming. Solana operates as a single global state machine, and is open, -interoperable and decentralized. Agave is a fork of the original Solana validator -previously maintained by the Solana Labs team. Agave is now under active development by the -core engineering team at Anza, one of several Solana validator clients. +interoperable and decentralized. Tachyon is a fork of the original Solana validator +previously maintained by the Solana Labs team. Tachyon is now under active development by the +core engineering team at X1 Labs, one of several Solana validator clients. ## Command Line Interface and Tool Suite @@ -44,7 +44,7 @@ works: ## Running a Validator -Explore what it takes to operate an Agave validator and help secure the network. +Explore what it takes to operate an Tachyon validator and help secure the network. - [Validator vs RPC node](./operations/validator-or-rpc-node.md) - Understand the important differences between voting and non-voting validators on the diff --git a/docs/src/operations/best-practices/general.md b/docs/src/operations/best-practices/general.md index 23360c6726f779..86c7f97efb5d41 100644 --- a/docs/src/operations/best-practices/general.md +++ b/docs/src/operations/best-practices/general.md @@ -82,7 +82,7 @@ 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). -### agave-install +### tachyon-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 diff --git a/docs/src/runtime/zk-elgamal-proof.md b/docs/src/runtime/zk-elgamal-proof.md index e3372f03f383fb..6f4af7dae9ed1a 100644 --- a/docs/src/runtime/zk-elgamal-proof.md +++ b/docs/src/runtime/zk-elgamal-proof.md @@ -12,7 +12,7 @@ so that they can be combined to enable a number different applications. - Program id: `ZkE1Gama1Proof11111111111111111111111111111` - Instructions: - [ProofInstruction](https://github.com/anza-xyz/agave/blob/master/zk-sdk/src/zk_elgamal_proof_program/instruction.rs) + [ProofInstruction](https://github.com/x1-labs/tachyon/blob/master/zk-sdk/src/zk_elgamal_proof_program/instruction.rs) ### Pedersen commitments and ElGamal encryption @@ -98,14 +98,14 @@ proofs. - The ElGamal public-key validity proof instruction certifies that an ElGamal public-key is a properly formed public key. - Mathematical description and proof of security: - [[Notes]](https://github.com/anza-xyz/agave/blob/master/docs/src/runtime/zk-docs/pubkey_proof.pdf) + [[Notes]](https://github.com/x1-labs/tachyon/blob/master/docs/src/runtime/zk-docs/pubkey_proof.pdf) - `VerifyZeroCiphertext`: - The zero-ciphertext proof certifies that an ElGamal ciphertext encrypts the number zero. - Mathematical description and proof of security: - [[Notes]](https://github.com/anza-xyz/agave/blob/master/docs/src/runtime/zk-docs/zero_proof.pdf) + [[Notes]](https://github.com/x1-labs/tachyon/blob/master/docs/src/runtime/zk-docs/zero_proof.pdf) #### Equality proofs @@ -114,14 +114,14 @@ proofs. - The ciphertext-commitment equality proof certifies that an ElGamal ciphertext and a Pedersen commitment encode the same message. - Mathematical description and proof of security: - [[Notes]](https://github.com/anza-xyz/agave/blob/master/docs/src/runtime/zk-docs/ciphertext_commitment_equality.pdf) + [[Notes]](https://github.com/x1-labs/tachyon/blob/master/docs/src/runtime/zk-docs/ciphertext_commitment_equality.pdf) - `VerifyCiphertextCiphertextEquality`: - The ciphertext-ciphertext equality proof certifies that two ElGamal ciphertexts encrypt the same message. - Mathematical description and proof of security: - [[Notes]](https://github.com/anza-xyz/agave/blob/master/docs/src/runtime/zk-docs/ciphertext_ciphertext_equality.pdf) + [[Notes]](https://github.com/x1-labs/tachyon/blob/master/docs/src/runtime/zk-docs/ciphertext_ciphertext_equality.pdf) #### Ciphertext Validity proofs @@ -130,4 +130,4 @@ proofs. - The grouped ciphertext validity proof certifies that a grouped ElGamal cipehrtext is well-formed - Mathematical description and proof of security: - [[Notes]](https://github.com/anza-xyz/agave/blob/master/docs/src/runtime/zk-docs/ciphertext_validity.pdf) + [[Notes]](https://github.com/x1-labs/tachyon/blob/master/docs/src/runtime/zk-docs/ciphertext_validity.pdf) diff --git a/install/agave-install-init.sh b/install/agave-install-init.sh index cf2d1babf3c306..6bc726fbc305c0 100755 --- a/install/agave-install-init.sh +++ b/install/agave-install-init.sh @@ -16,9 +16,9 @@ { # this ensures the entire script is downloaded # if [ -z "$SOLANA_DOWNLOAD_ROOT" ]; then - SOLANA_DOWNLOAD_ROOT="https://github.com/anza-xyz/agave/releases/download/" + SOLANA_DOWNLOAD_ROOT="https://github.com/x1-labs/tachyon/releases/download/" fi -GH_LATEST_RELEASE="https://api.github.com/repos/anza-xyz/agave/releases/latest" +GH_LATEST_RELEASE="https://api.github.com/repos/x1-labs/tachyon/releases/latest" set -e diff --git a/install/src/command.rs b/install/src/command.rs index 8a81e1d72337ec..ae5d2b0c33689a 100644 --- a/install/src/command.rs +++ b/install/src/command.rs @@ -568,7 +568,7 @@ pub fn init( fn github_release_download_url(release_semver: &str) -> String { format!( - "https://github.com/anza-xyz/agave/releases/download/v{}/solana-release-{}.tar.bz2", + "https://github.com/x1-labs/tachyon/releases/download/v{}/solana-release-{}.tar.bz2", release_semver, crate::build_env::TARGET ) @@ -576,7 +576,7 @@ fn github_release_download_url(release_semver: &str) -> String { fn release_channel_download_url(release_channel: &str) -> String { format!( - "https://release.anza.xyz/{}/solana-release-{}.tar.bz2", + "https://release.x1.xyz/{}/solana-release-{}.tar.bz2", release_channel, crate::build_env::TARGET ) @@ -584,7 +584,7 @@ fn release_channel_download_url(release_channel: &str) -> String { fn release_channel_version_url(release_channel: &str) -> String { format!( - "https://release.anza.xyz/{}/solana-release-{}.yml", + "https://release.x1.xyz/{}/solana-release-{}.yml", release_channel, crate::build_env::TARGET ) @@ -901,7 +901,7 @@ fn check_for_newer_github_release( while page == 1 || releases.len() == PER_PAGE { let url = reqwest::Url::parse_with_params( - "https://api.github.com/repos/anza-xyz/agave/releases", + "https://api.github.com/repos/x1-labs/tachyon/releases", &[ ("per_page", &format!("{PER_PAGE}")), ("page", &format!("{page}")), diff --git a/ledger-tool/src/main.rs b/ledger-tool/src/main.rs index aa179eb4544360..683704cb0934aa 100644 --- a/ledger-tool/src/main.rs +++ b/ledger-tool/src/main.rs @@ -2123,9 +2123,13 @@ fn main() { }; let bank = if let Some(warp_slot) = warp_slot { - // need to flush the write cache in order to use Storages to calculate - // the accounts hash, and need to root `bank` before flushing the cache - bank.rc.accounts.accounts_db.add_root(bank.slot()); + // Need to flush the write cache in order to use + // Storages to calculate the accounts hash, and need to + // root `bank` before flushing the cache. Use squash to + // root all unrooted parents as well and avoid panicking + // during snapshot creation if we try to add roots out + // of order. + bank.squash(); bank.force_flush_accounts_cache(); Arc::new(Bank::warp_from_parent( bank.clone(), diff --git a/net/net.sh b/net/net.sh index b82872f5046d8e..3f96768a1a0400 100755 --- a/net/net.sh +++ b/net/net.sh @@ -563,7 +563,7 @@ prepareDeploy() { if [[ -n $releaseChannel ]]; then echo "Downloading release from channel: $releaseChannel" rm -f "$SOLANA_ROOT"/solana-release.tar.bz2 - declare updateDownloadUrl=https://release.anza.xyz/"$releaseChannel"/solana-release-x86_64-unknown-linux-gnu.tar.bz2 + declare updateDownloadUrl=https://release.x1.xyz/"$releaseChannel"/solana-release-x86_64-unknown-linux-gnu.tar.bz2 ( set -x curl -L -I "$updateDownloadUrl" diff --git a/programs/sbf/Cargo.toml b/programs/sbf/Cargo.toml index 0b0e8da88fc36a..e6cdc20eb3eab7 100644 --- a/programs/sbf/Cargo.toml +++ b/programs/sbf/Cargo.toml @@ -1,9 +1,9 @@ [workspace.package] version = "2.0.21" description = "Solana SBF test program written in Rust" -authors = ["Anza Maintainers "] -repository = "https://github.com/anza-xyz/agave" -homepage = "https://anza.xyz" +authors = ["X1 Labs maintainers "] +repository = "https://github.com/x1-labs/tachyon" +homepage = "https://x1.xyz" license = "Apache-2.0" edition = "2021" diff --git a/scripts/agave-install-deploy.sh b/scripts/agave-install-deploy.sh index dcdec14ffb635d..c928e927edc9f9 100755 --- a/scripts/agave-install-deploy.sh +++ b/scripts/agave-install-deploy.sh @@ -57,10 +57,10 @@ esac case $TAG in edge|beta) - DOWNLOAD_URL=https://release.anza.xyz/"$TAG"/solana-release-$TARGET.tar.bz2 + DOWNLOAD_URL=https://release.x1.xyz/"$TAG"/solana-release-$TARGET.tar.bz2 ;; *) - DOWNLOAD_URL=https://github.com/anza-xyz/agave/releases/download/"$TAG"/solana-release-$TARGET.tar.bz2 + DOWNLOAD_URL=https://github.com/x1-labs/tachyon/releases/download/"$TAG"/solana-release-$TARGET.tar.bz2 ;; esac diff --git a/scripts/reserve-cratesio-package-name.sh b/scripts/reserve-cratesio-package-name.sh index e172e1640094d0..2170be74908fe8 100755 --- a/scripts/reserve-cratesio-package-name.sh +++ b/scripts/reserve-cratesio-package-name.sh @@ -103,10 +103,10 @@ if pushd "${tmpdir}" &>/dev/null; then name = "${package_name}" version = "0.0.0" description = "reserved for future use" -authors = ["Anza Maintainers "] -repository = "https://github.com/anza-xyz/agave" +authors = ["X1 Labs maintainers "] +repository = "https://github.com/x1-labs/tachyon" license = "Apache-2.0" -homepage = "https://anza.xyz" +homepage = "https://x1.xyz" documentation = "https://docs.rs/${package_name}" edition = "2021" EOF diff --git a/sdk/cargo-build-sbf/tests/crates/fail/Cargo.toml b/sdk/cargo-build-sbf/tests/crates/fail/Cargo.toml index 58cb210aa720f3..5f5f1e14b56d34 100644 --- a/sdk/cargo-build-sbf/tests/crates/fail/Cargo.toml +++ b/sdk/cargo-build-sbf/tests/crates/fail/Cargo.toml @@ -2,10 +2,10 @@ name = "fail" version = "2.0.21" description = "Solana SBF test program written in Rust" -authors = ["Anza Maintainers "] -repository = "https://github.com/anza-xyz/agave" +authors = ["X1 Labs maintainers "] +repository = "https://github.com/x1-labs/tachyon" license = "Apache-2.0" -homepage = "https://anza.xyz" +homepage = "https://x1.xyz" edition = "2021" publish = false diff --git a/sdk/cargo-build-sbf/tests/crates/noop/Cargo.toml b/sdk/cargo-build-sbf/tests/crates/noop/Cargo.toml index e284e43aa56e38..c47ccca082b59f 100644 --- a/sdk/cargo-build-sbf/tests/crates/noop/Cargo.toml +++ b/sdk/cargo-build-sbf/tests/crates/noop/Cargo.toml @@ -2,10 +2,10 @@ name = "noop" version = "2.0.21" description = "Solana SBF test program written in Rust" -authors = ["Anza Maintainers "] -repository = "https://github.com/anza-xyz/agave" +authors = ["X1 Labs maintainers "] +repository = "https://github.com/x1-labs/tachyon" license = "Apache-2.0" -homepage = "https://anza.xyz" +homepage = "https://x1.xyz" edition = "2021" publish = false