The Vault
  • About
    • πŸš€Our Mission
    • πŸ”₯vSOL
    • ✨Points program
    • πŸ€“Contributors
    • πŸ”’Stake pool address
    • 🏦The Vault Fees
    • πŸ“ˆTokenomics
  • Validators
    • πŸ“ŠDelegation Strategy
    • πŸ’«Get stake from the pool!
    • βœ…Validator Allowlist
    • πŸ›‘οΈValidator Shield Initiative
    • 🏦Kamino Multiply Strategy
    • πŸ”Signing A Message
    • πŸͺ™LST Creator
    • βš™οΈLST Creator Widget
    • πŸ“šLST Creator API
    • πŸ›οΈValidator Application Process
    • πŸ“ƒWaitlist Criteria
    • β˜€οΈAllowlist Criteria
    • πŸ’»Validator Reward Claim Instructions
    • πŸ“¦Stake-as-a-Service (SaaS)
  • Users
    • 🎯Validator target stake
    • 🌊Liquid staking
    • πŸ“ˆStaking APY
    • πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘¦Multisig staking
    • πŸ””The Vault Discord
    • β˜€οΈDelayed LST unstaking in Solflare Wallet
    • πŸ‘»Delayed LST unstaking in Phantom Wallet
    • πŸ…Squads
    • πŸŽ–οΈUnits
  • πŸ”Risks
  • πŸ”—Links
Powered by GitBook
On this page
  • πŸ› οΈ Prerequisites
  • πŸš€ Quick Claim (via Cargo)
  • πŸ’» Alternative: Run from Source
  • πŸ” Security Notes
  • πŸ“¦ GitHub Repo
  1. Validators

Validator Reward Claim Instructions

Please use these instructions to claim your rewards!

PreviousAllowlist CriteriaNextStake-as-a-Service (SaaS)

Last updated 1 month ago

Validators can now claim their $vPTS rewards using a command-line tool. There are two main options: install from using Cargo, or clone the GitHub repo and run it from source.


πŸ› οΈ Prerequisites

Before starting:

  1. 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
  2. Optional but recommended: install or update to the latest stable toolchain. A rust-toolchain.toml will be added to the repo to ensure seamless builds.


πŸš€ Quick Claim (via Cargo)

  1. Install the CLI Tool

    Run the following to install the reward claim CLI:

    cargo install merkle-distributor-claim-cli
  2. Run the Claim Command

    Replace <YOUR KEYPAIR FILE PATH> with your actual .json keypair 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

  1. Clone the Repo

    git clone https://github.com/SolanaVault/merkle-distributor-claim-cli
    cd merkle-distributor-claim-cli
  2. Check Environment Variables

    The required variables (AIRDROP_BASE_URL, DISTRIBUTOR_ADDRESS, MINT_ADDRESS) are already included in the .env file.

  3. 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.


πŸ“¦ GitHub Repo

Repo:

πŸ’»
crates.io
SolanaVault/merkle-distributor-claim-cli