Zaun Usage Manual
  • Intro
  • Installation
  • Configurations
  • Navigation
  • Concepts
  • Quick Start
  • Zaun Tracker
  • Common Issues
  • Security
Powered by GitBook
On this page
  • Environment Config
  • Global Config

Configurations

PreviousInstallationNextNavigation

Last updated 2 months ago

Environment Config

After following the steps in Installationand unpacking the files, you will find a file named .env. This file mostly contains security sensitive and essential configuration values for running the application. The current configuration values (subject to change) are:

  • RPC_HTTPS_ENDPOINT_URL

    • A gateway to interact with the Solana blockchain.

    • Allows querying data, submitting transactions, and executing programs.

    • Provided by a Solana node or third-party service.

    • Example: https://api.mainnet-beta.solana.com.

    • notable service providers:

    • Make sure that your RPC endpoint has a minimum of 20 RPS (requests per second) cap.

  • RPC_WSS_ENDPOINT_URL

    • Necessary websocket connection endpoint.

    • Allows for listening to program events and account data changes.

    • Usually found with the HTTPS endpoint in your RPC provider dashboard.

    • Example: wss://api.mainnet-beta.solana.com

  • SUBSCRIPTION_WALLET_PRIVATE_KEY

    • Wallet used to gain access to Zaun.

    • Must be a Base 58 private key.

  • FUNDING_WALLET_PRIVATE_KEY

    • The main wallet of you application.

    • It funds most operations, as the name implies.

    • Responsible for paying transaction fees and Jito tips.

    • Must be a Base 58 private key.

  • DEV_WALLET_PRIVATE_KEY

    • Wallet acting as the Dev wallet for your coin.

    • Must be a Base 58 private key.

  • CAPSOLVER_API_KEY

    • API key for captcha solving operations.

    • you can get yours .

      • recommend: always keep $5 in funding and add when necessary.

Global Config

These configuration values are global across all modules and vary in usage. Everything can be edited in the application settings UI. The current configuration values (subject to change) are:

  • JITO_TIP_STREAM_PERCENTILE

    • Percentile group used to determine how much you are gonna pay in Jito tips.

    • The higher the percentile group, the faster your bundles will land.

  • JITO_MAX_TIP

    • The max amount your are willing pay for tips on any bundle

    • Overrides the tip acquired from the tip stream with your configured percentile group.

  • FUNDING_STRATEGY

    • Determines the funding of your wallets in bundle launches.

    • Two strategies are currently available:

      • In-contract: Use a smart contract to calculate the needed sol and fund them during the token launch bundle.

      • Pre-fund: Funds the wallets with your choosen amount of sol pre launch.

  • BUNDLE_TIMEOUT

    • The timeout for when bundle confirmation will expire.

  • USE_VIDEO

    • describes your intent of wanting to use video media for your token launch

  • PUMP_COMMENTS_INTENSITY

    • The speed at which comments are sent

    • Currently due to the current captcha implementation by pump. commenting is speed is heavily reduced.

  • DEBUG

    • Enable or disable debug logging.

  • SKIP_RPC_HEALTH_CHECK

    • Enable or disable RPC health checks when starting the application.

https://www.helius.dev
https://www.quicknode.com
https://x.com/sharksnode
here