.env Setup Guide

Configuring your .env file:

  1. Open the folder in VS code after extracting the ZIP

  2. Copy the template below and fill in your values

.emv Example
What it is
Notes

SOLANA_RPC_URL

Your RPC URL

Use a paid one - replace the default with your own

DEPLOYER_KEY

Your dev wallet private key

Must be in JSON array format - e.g [245,97,112,200,...]

FUNDER_KEY

Your funder wallet private key

Must be in JSON array format - e.g [245,97,112,200,...]

block_engine_urls

JITO block engine URL

Use the URL closer to you - see JITO docs for others

LUT_ADDRESS

Lookup Table address

DO NOT CHANGE - Bot will paste it in when created

JITO_TIP

Jito tip amount

In SOL - Aim for 95th percentile or higher

LICENSE_KEY

Your key to use the bot

Get it from Moon Bot in the Discord with /getkey

Private Key Format

Moon Scripts Bundler requires private keys in array format, not Base58:

DEPLOYER_KEY=[245,97,112,200,...]

Important: This is different from Phantom's export format - Solflare is recommended. Your private key must be an array of numbers enclosed in square brackets.

RPC Configuration

Choosing an RPC

  • If you use a free RPC you will be rate limited and the bot may not work properly

  • Recommended: Premium RPC service for better performance

RPC Requirements

  • Should have high rate limits for bundling operations

Wallet Configuration:

Deployer Wallet

  • This wallet is your dev wallet - it launches tokens and buys in with 1 dev buy

Funder Wallet

  • This wallet funds bundle subwallets and signs transactions

Important Notes

  • Overfund wallets to avoid insufficient fund errors

  • Keep extra SOL for transaction fees and priority fees

  • Monitor wallet balances regularly

Lookup Table (LUT)

The LUT_ADDRESS is automatically managed by the bot:

  • Created when you run "Create Address Lookup Table"

  • Optimizes transaction size and reduces costs

  • DO NOT MODIFY once created

Security Best Practices

⚠️ Never share your .env file or private keys

  • Keep your .env file secure and private

  • Use a dedicated wallet for the bot, not your main wallet

  • Backup your keys securely offline

Troubleshooting/Errors

"Missing .env file" error

  • Ensure the file is named exactly .env with the dot

  • Place it in the same folder as bundler-bot.exe

  • Check file is not named .env.txt (Windows may hide extensions)

"Invalid private key format" error

  • Verify your key is in array format: [num,num,num,...]

  • Ensure all values are numbers separated by commas

  • Check that brackets are properly closed

  • Remove any quotes around the array

"Endpoint URL must start with http:// or https://" error

  • Check SOLANA_RPC_URL starts with http:// or https://

  • Remove any trailing spaces or quotes

  • Ensure URL format is correct

"LICENSE_KEY must be set" error

  • Verify LICENSE_KEY is present in your .env file

  • Check for typos in the variable name

  • Ensure no extra spaces around the equals sign

"DEPLOYER_KEY must be a valid JSON array" error

  • Private key must be in array format, not Base58

  • Convert from Phantom format to array format

  • Check JSON syntax is valid with proper brackets

"Insufficient funds" errors

  • Ensure deployer wallet has sufficient SOL (5+ recommended)

  • Account for transaction fees and priority fees

  • Check wallet balance before operations

"Connection failed" errors

  • Verify RPC URL is working and accessible

  • Try switching to a different RPC provider

  • Check internet connection and firewall settings

Next Steps

After configuring your .env file:

  1. Restart your bot and run npm start in your terminal

  2. You're ready to use the bot!

Last updated