Skip to main content

​
env

Display current environment setup including wallet, RPC endpoint, active vault, and configuration details. 
glam-cli env

​
Examples

glam-cli env

​
Example Output

GLAM Protocol program: GLAMpgMS8sJFJD8HtZeEV6FLvCcFFkC7DxU2vfYc3zy
Staging: false
Wallet connected: 9zW8xYvAbCdEfGhIjKlMnOpQrStUvWxYz111222333
RPC endpoint: https://api.mainnet-beta.solana.com
Priority fee: { micro_lamports: 50000, level: 'high' }
Jupiter API key: configured
GLAM state: 8x7Y9kLmAbCdEfGhIjKlMnOpQrStUvWxYz123456789
Vault PDA: 5hN23pQrAbCdEfGhIjKlMnOpQrStUvWxYz987654321
Vault name: My Fund

​
Output Details

GLAM Protocol program: The public key of the GLAM Protocol program being used. Staging: Whether the staging environment is enabled. Wallet connected: The public key of the connected wallet used to sign transactions. RPC endpoint: The Solana RPC endpoint URL being used for network communication. Priority fee: Configuration for transaction priority fees. Shows either:
  • micro_lamports: Fixed priority fee amount in micro-lamports
  • level: Dynamic priority level (e.g., ‘low’, ‘medium’, ‘high’, ‘veryHigh’)
Jupiter API key: Indicates whether a Jupiter API key is configured (shows “configured” or “not configured”). GLAM state: The public key of the currently active GLAM state account (if one is set). Vault PDA: The public key of the vault PDA associated with the active GLAM state. Vault name: The human-readable name of the active vault.

​
When No Vault is Set

If no GLAM vault is currently configured, the output will show: 
GLAM Protocol program: GLAMpgMS8sJFJD8HtZeEV6FLvCcFFkC7DxU2vfYc3zy
Staging: false
Wallet connected: 9zW8xYvAbCdEfGhIjKlMnOpQrStUvWxYz111222333
RPC endpoint: https://api.mainnet-beta.solana.com
Priority fee: { micro_lamports: 50000 }
Jupiter API key: not configured
No active GLAM vault configured.

​
Use Cases

  • Verify configuration: Check that your CLI is configured correctly before executing commands
  • Debug connection issues: Verify RPC endpoint and wallet connectivity
  • Confirm active vault: Ensure you’re operating on the correct vault before making changes
  • Check environment: Verify you’re on the correct network (mainnet, devnet, localnet)

Build docs developers (and LLMs) love

Get started for freeTalk to us