Server Configuration

The system consists of three main servers, each of which performs the following roles:

System Architecture

2.1 Data Server

  • Role: Core server that manages the list of tokens that agents can buy and sell.

  • Main function:

    • Filtering and screening of Tokens based on self-evaluation criteria.

    • Perform classification and labeling based on token attributes (e.g., categories, keywords, use cases, etc.)

    • Utilize various on-chain and off-chain data to construct comprehensive judgment criteria

    • Provide token list and meta-information for agents to utilize for buying and selling

  • Data sources:

    • On-chain metrics: transaction volume, number of holders, creator's transaction activity history, etc.

    • Off-chain metrics: Twitter activity, Sentiment scores, community reactions, etc.

  • Extended data collection methods

    📌 Keyword-based data collection

    • Automated extraction of Ticker and Address from posts of major Twitter accounts

    • Search-based keyword trend analysis to discover hyped tokens

    📌 On-chain/off-chain transaction-based collection

    • Continuously monitor on-chain transactions of specific accounts to analyze transaction patterns

    • Identify investment interest utilizing Reddit, search trends, web mentions, etc.

  • Print and share:

    • The above data is synthesized to form a token list, which is delivered to other servers and agents and utilized as a basis for investment judgment.

    • Some data is shared externally through the following public dashboard:

2.2 Trading Server

  • Role: Buy and sell tokens according to the strategy set by the Agent

  • Input Data:

    • On-chain information (price, volume, etc.)

    • Community signals (number of followers, keyword mentions, tweet views, etc.)

    • Previous trading history

  • Trading method:

    • Initial: Testing strategies with virtual trading

    • Current: Entering live trading phase (based on Anchor Program)

    • In the testing phase, trades are executed via SendAI's Jupiter DEX API

2.3 Web Server

  • Role: Provide API service for Agent-related data and inquiry

  • Main information provided:

    • Agent prompts, trading history

    • Performance information such as token holdings, NAV, PnL, etc.

    • Provides interfaces with external websites and Telegram channels

PreviousOverviewNextClient Configuration

Last updated