Skip to content

Instantly share code, notes, and snippets.

@tigarcia
Last active October 9, 2026 20:44
Show Gist options
  • Select an option

  • Save tigarcia/1ca5b2d53d0606edfe9fec77b4e61474 to your computer and use it in GitHub Desktop.

Select an option

Save tigarcia/1ca5b2d53d0606edfe9fec77b4e61474 to your computer and use it in GitHub Desktop.
Alpenglow Regenesis 2026-10-08

2026-10-08: Alpenglow Regenesis

The Alpenglow community cluster is ready for validators to join! The cluster is currently waiting for super majority to start. Validators will likely join over the next few days.

If you are a part of the initial genesis set please follow these instructions. If you are not part of the genesis set, follow https://docs.anza.xyz/operations/setup-a-validator#create-a-vote-account to create a vote account once the cluster has been started.

Operators should do the following to join the cluster:

  1. IMPORTANT: Stop any existing validator process and delete the ledger directory from the previous cluster run

  2. Checkout the v4.3.0 agave tag or v4.3.0-jito.1 jito tag:

// Agave
git clone -b v4.3.0 https://github.com/anza-xyz/agave agave
cd agave

// Jito
git clone -b v4.3.0-jito.1 https://github.com/jito-foundation/jito-solana.git jito
cd jito
git submodule update --recursive --init
  1. Build the validator from source
CI_COMMIT=$(git rev-parse HEAD) scripts/cargo-install-all.sh --validator-only <install-dir>
  1. Configure the binary for XDP https://www.anza.xyz/blog/agave-xdp-setup-guide
sudo setcap cap_net_raw,cap_bpf,cap_net_admin,cap_perfmon=p <install-dir>/bin/agave-validator
  1. Use the following startup script to join the cluster. Make sure you use the agave-validator binary that you built in step 2.
export SOLANA_METRICS_CONFIG="host=https://metrics.solana.com:8086,db=alpenglow-testnet,u=ag,p=!d.tWEViQRhhP.*be9!a"

<install-dir>/bin/agave-validator \
    --rpc-port 8899 \
    --full-rpc-api \
    --identity <community-cluster-identity> \
    --vote-account <community-cluster-vote-keypair> \
    --log solana-validator.log \
    --ledger <ledger-dir> \
    --accounts <accounts-dir> \
    --dynamic-port-range 9000-12500 \
    --entrypoint 64.130.37.11:8000 \
    --entrypoint 45.152.160.7:9000 \
    --entrypoint 70.40.185.54:9000 \
    --limit-ledger-size \
    --expected-genesis-hash AFMqCwCunorS8z19qekG9jR45Ng2SY3ZHHMFoHiWYrNq \
    --expected-shred-version 8456 \
    --expected-bank-hash 95JPaGbkS8miSh9na2Z2D21f62ydqWQottnA27HgBbCd \
    --wait-for-supermajority 0

For Jito additionally add these flags:

--tip-payment-program-pubkey HTTccZKCPmTJBGBigPFLqevpSJ8EBsqxc5NJnkVB6Ek9 \
--tip-distribution-program-pubkey SawLYLtMVfcKN9UyUfL3rLToBGQbZ1bTFx1ZtzSVuLB \
--merkle-root-upload-authority 7T4inmPmtNBX3MhLwJ9hFsSMnGJYYkKioVABSNTWVRuS \
--commission-bps 100

For BAM:

--bam-url https://198.13.140.247:50056

NOTE: only use BAM if you have a 30ms latency with the BAM Node in Frankfurt ping 198.13.140.247 needs to be < 30ms

NOTE: IF YOU USE --no-port-check I WILL NOT HELP YOU DEBUG ISSUES

  1. Run agave-validator -l <ledger> monitor to make sure your validator is waiting for super majority.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment