# rabnail-sol/solana-raydium-sniper architecture

> Architecture diagram of the GitHub repository rabnail-sol/solana-raydium-sniper, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-03). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/rabnail-sol/solana-raydium-sniper
- Repository: https://github.com/rabnail-sol/solana-raydium-sniper

## Overview

##### Recognize the Project Type & Purpose
- This is a specialized trading/bot application designed for automated pool detection and rapid transaction processing on the Solana blockchain.

##### File Structure and Identify Main Components
- Entry Points & Core Logic:
- buy.js: Likely the main entry point to initialize the bot’s functionality.
- monitor.js: Possibly a module that continuously monitors pool changes or market conditions.
- Executor Module:
- Located in the executor folder with files like jito.js, jitoWithAxios.js, and legacy.js. These files indicate multiple strategies for executing transactions, with a focus on integrating the Jito block engine.
- Liquidity & Market Data Handling:
- liquidity folder (liquidity.js, index.js) and market folder (market.js, index.js) likely handle pool detection and market information gathering.
- Token Filtering:
- tokenFilter folder (index.js) suggests a dedicated component for filtering tokens based on various criteria.
- Constants, Types, and Utilities:
- The constants folder and files like constants.js provide configuration settings; the types folder defines data models (for example, mint types); and the utils folder supports helper functions (e.g., logging, fetching pool keys, etc.).
- Environment Setup:
- The .env file plays an essential role in configuring runtime parameters (private keys, RPC endpoints, Jito settings, etc.), which affect nearly every component.

##### Mapping Out Component Interactions
b. An “Environment & Configuration” module that loads settings from the .env file and shared constants.
c. Following downstream modules:
- Market & Liquidity Modules:
- Token Filter:
- Filtration process which screens tokens based on user-defined filters (e.g., checking mint conditions, pool sizes, etc.).
- Executor:
- A node that selects the appropriate executor (Jito, JitoWithAxios, or legacy) to handle the purchase with a connection to an external Jito API (a block engine service).
- Monitor:
- An optional module for frequently checking on the current state (price, status of transactions) and triggering appropriate actions like auto-sell.
- From “Environment Configuration” towards all modules (as they rely on the input settings).
- From “Market/Liquidity” to “Token Filter”, and then to “Executor”.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Orchestrator
    subgraph "Orchestrator"
        B1["buy.js"]:::orchestrator
        M1["monitor.js"]:::orchestrator
    end

    %% Environment & Configuration
    subgraph "Environment & Configuration"
        ENV[".env"]:::config
        CONST["Constants"]:::config
    end

    %% Market & Liquidity Data Handlers
    subgraph "Market & Liquidity Data Handlers"
        LIQ["Liquidity Manager"]:::core
        MRK["Market Manager"]:::core
    end

    %% Business Logic
    subgraph "Business Logic"
        TF["Token Filter"]:::business
        EXE["Transaction Executor"]:::business
    end

    %% Support Modules
    subgraph "Support"
        UT["Utilities"]:::support
        DM["Data Models"]:::support
    end

    %% External Service
    JB["Jito Block Engine"]:::external

    %% Connections from Orchestrator to Market Modules
    B1 -->|"initiate pool detection"| LIQ
    B1 -->|"initiate market data"| MRK

    %% Configuration feeding into system modules
    ENV -->|"provides config"| LIQ
    ENV -->|"provides config"| MRK
    ENV -->|"provides config"| TF
    ENV -->|"provides config"| EXE

    CONST -->|"provides constants"| LIQ
    CONST -->|"provides constants"| MRK
    CONST -->|"provides constants"| TF
    CONST -->|"provides constants"| EXE

    %% Data flows from Market & Liquidity to Token Filter
    LIQ -->|"pool data"| TF
    MRK -->|"market data"| TF

    %% Utilities and Data Models assisting Business Logic
    UT -->|"helper functions"| TF
    UT -->|"helper functions"| EXE
    DM -->|"data models"| TF
    DM -->|"data models"| EXE

    %% Token Filter to Transaction Executor
    TF -->|"filtered token data"| EXE

    %% Monitor contributes to execution adjustments
    M1 -->|"monitor transactions"| EXE

    %% Transaction Executor calls External Jito Service
    EXE -->|"execute transaction"| JB

    %% Click Events
    click B1 "https://github.com/rabnail-sol/solana-raydium-sniper/blob/main/buy.js"
    click M1 "https://github.com/rabnail-sol/solana-raydium-sniper/blob/main/monitor.js"
    click ENV "https://github.com/rabnail-sol/solana-raydium-sniper/blob/main/.env"
    click CONST "https://github.com/rabnail-sol/solana-raydium-sniper/tree/main/constants/"
    click LIQ "https://github.com/rabnail-sol/solana-raydium-sniper/tree/main/liquidity/"
    click MRK "https://github.com/rabnail-sol/solana-raydium-sniper/tree/main/market/"
    click TF "https://github.com/rabnail-sol/solana-raydium-sniper/blob/main/tokenFilter/index.js"
    click EXE "https://github.com/rabnail-sol/solana-raydium-sniper/tree/main/executor/"
    click UT "https://github.com/rabnail-sol/solana-raydium-sniper/tree/main/utils/"
    click DM "https://github.com/rabnail-sol/solana-raydium-sniper/tree/main/types/"

    %% Styles
    classDef orchestrator fill:#cce5ff,stroke:#004085,stroke-width:2px;
    classDef config fill:#d4edda,stroke:#155724,stroke-width:2px;
    classDef core fill:#cce5ff,stroke:#004085,stroke-width:2px;
    classDef business fill:#d1ecf1,stroke:#0c5460,stroke-width:2px;
    classDef support fill:#f8d7da,stroke:#721c24,stroke-width:2px;
    classDef external fill:#fff3cd,stroke:#856404,stroke-width:2px;
```
