AlgoAgent
  • WHITEPAPER
  • 1. Digital Currency Quantitative Trading
    • 1.1 Quantitative Trading
    • 1.2 Digital currency and quantitative trading are a natural fit
    • 1.3 The prospects for digital currency quantitative trading are enormous
    • 1.4 The current situation of the quantitative trading market
      • 1.4.1 A large number of exchanges, chaotic trading rules
      • 1.4.2 The trading time is excessively long
      • 1.4.3 Extremely Immature Technology Infrastructure
  • 2. AI Agent Quantitative Intelligent Trading
    • 2.1 Artificial intelligence is the trend of the future
    • 2.2 Quantitative intelligent trading of digital currencies using AI Agents will become a trend
  • 3. AlgoAgent
    • 3.1 AlgoAgent Introduction
    • 3.2 AlgoAgent Development History
    • 3.3 Trading strategies and indicators supported by AlgoAgent
    • 3.4 AlgoAgent AI Agent Quantitative Trading Algorithms
      • 3.4.1 Sell-off Detection
      • 3.4.2 Wall Detection
      • 3.4.3 Variable shooting (buying spike kill)
    • 3.5 AlgoAgent Advantages
      • 3.5.1 Full range of management services
      • 3.5.2 Multiple security protections
      • 3.5.3 Asset appreciation
      • 3.5.4 Multi-language support
      • 3.5.5 Simple and convenient transactions
      • 3.5.6 Risk-Free High-Frequency Automated Quantitative Trading of Digital Assets
      • 3.5.7 Convenient Funding
    • 3.6 AlgoAgent Service Carrier
      • 3.6.1 AlgoAgent Intelligent Platform
      • 3.6.2 Digital Asset Bank Card
      • 3.6.3 AlgoAgent Contract Token
  • 4. Tokenomics
  • 5. Roadmap
  • 6. Team Introduction
  • 7. Risk Warning
  • 8. Disclaimer
Powered by GitBook
On this page
  1. 3. AlgoAgent
  2. 3.4 AlgoAgent AI Agent Quantitative Trading Algorithms

3.4.2 Wall Detection

The method consistently shows TOKENs with a large number of buy orders (support). Example below:

Configure parameters to specify a period to check how long the support has been there, and the bot will execute the task.

For the above wall strategy example: Copy the following text and paste it into the bot.

##Begin_Strategy

Active=-1

StrategyName=Walls Test

Comment=apollo

SignalType=W allsDetection

ChannelName=

ChannelKey=

SilentNoCharts=NO

ReportToTelegram=YES

CoinsWhiteList=

CoinsBlackList=TRX,NBT

MinVolume=10

MaxVolume=500

AutoBuy=NO

MaxActiveOrders= 10

AutoCancelBuy= 180

BuyType=Buy OrderSize=0.00000000 buyPrice=-3.00000000 • SellPrice=4.00000000 UseStopLoss=NO

StopLoss= 1.00000000

PanicSellSpread=0.10000000

AllowedDrop=0.00000000

UseTralllng=YES

TralllngPersent=-1.00000000

UseT akeProfIt= YE S

TakeProfit=2.50000000

DropsMaxT ime=600

DropsPrIceMA= 1

DropsL astPriceMA= 1

DropsPriceDelta=1.00000000

DropsPriceIsLow=NO

W allsMaxT ime=3600

WallsPriceDelta=4.00000000

WallBuyVolDeep=2.00000000

W allBuyVolume= 10

WallBuyVolToDAI AgentlyVol=10.00000000

WallSellVolToBuy=75.00000000

WallSellVolDeep=15.00000000

##End_Strategy#

Currently, only one volatility detection strategy can be activated, although users can configure many parameters within it.

It is recommended to use volatility detection only when the exact timing of the volatility is known. Open it 15 seconds before the volatility announcement and close it immediately afterward.

Warning! The risk of false detection is very high! Although you can configure many parameters to avoid this, there is still a possibility of mistaking certain market activities for volatility.

The recommended joint pump detection parameter values in the MegaPump Group's actual pump example are as follows:

PumpPriceRAI Agents = 7: This indicates a price increase of 7% within the last 30 seconds. The higher this value is set, the lower the likelihood of false detection. On the other hand, when the price increase is not very significant, you may want to detect the pump as quickly as possible.

PumpBuysPerSec=20;

PumpVolPerSec = 0.8: The initial increase in the number of buyers. The higher this value is, the lower the chance of false detection.

PumpBuyersPerSecMax = 4: Our goal is to immediately detect the pump when 2 to 4 people start buying the TOKEN.

PumpBuyersPerSecMin = 2: If only one buyer occasionally purchases some TOKENs unrelated to the volatility, the case will be rejected.

Previous3.4.1 Sell-off DetectionNext3.4.3 Variable shooting (buying spike kill)

Last updated 4 months ago