π» Validator Reward Claim Instructions
Please use these instructions to claim your rewards!
Validators can now claim their $vPTS rewards using a command-line tool. There are two main options: install from crates.io using Cargo, or clone the GitHub repo and run it from source.
π οΈ Prerequisites
Before starting:
-
Rust must be installed.
Most validators already have Rust installed since itβs required to run a validator. If not, install it via:curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -
Optional but recommended: install or update to the latest stable toolchain.
Arust-toolchain.tomlwill be added to the repo to ensure seamless builds.
π Quick Claim (via Cargo)
-
Install the CLI Tool
Run the following to install the reward claim CLI:
cargo install merkle-distributor-claim-cli -
Run the Claim Command
Replace
<YOUR KEYPAIR FILE PATH>with your actual.jsonkeypair file path. The following examples show how to set environment variables depending on your shell or OS:Unix/macOS/Linux/WSL:
AIRDROP_BASE_URL=https://solanavault.github.io/simd-228-vpts-airdrop/proofs \ DISTRIBUTOR_ADDRESS=BAzvEJH5w7igbbkiRLhCD89b1gLtrZz6B9wxxuh3ocJz \ MINT_ADDRESS=vPtS4ywrbEuufwPkBXsCYkeTBfpzCd6hF52p8kJGt9b \ md-claim <YOUR KEYPAIR FILE PATH>PowerShell:
$env:AIRDROP_BASE_URL="https://solanavault.github.io/simd-228-vpts-airdrop/proofs" $env:DISTRIBUTOR_ADDRESS="BAzvEJH5w7igbbkiRLhCD89b1gLtrZz6B9wxxuh3ocJz" $env:MINT_ADDRESS="vPtS4ywrbEuufwPkBXsCYkeTBfpzCd6hF52p8kJGt9b" md-claim <YOUR KEYPAIR FILE PATH>Command Prompt (cmd.exe):
set AIRDROP_BASE_URL=https://solanavault.github.io/simd-228-vpts-airdrop/proofs set DISTRIBUTOR_ADDRESS=BAzvEJH5w7igbbkiRLhCD89b1gLtrZz6B9wxxuh3ocJz set MINT_ADDRESS=vPtS4ywrbEuufwPkBXsCYkeTBfpzCd6hF52p8kJGt9b md-claim <YOUR KEYPAIR FILE PATH> --url <YOUR RPC>
π» Alternative: Run from Source
-
Clone the Repo
git clone https://github.com/SolanaVault/merkle-distributor-claim-cli cd merkle-distributor-claim-cli -
Check Environment Variables
The required variables (
AIRDROP_BASE_URL,DISTRIBUTOR_ADDRESS,MINT_ADDRESS) are already included in the.envfile. -
Build and Run
cargo run -- <YOUR KEYPAIR FILE PATH>
π Security Notes
- If you have a claim key from the campaign, you must use it. There is no option to use the identity key in that case.
- The claim key can be used with the CLI or the web interface.
- For full transparency, you may inspect the code before signing anything. There is no need to trust blindlyβreview the GitHub code.