# Table of Contents

- [Welcome to dEdge | Docs](#welcome-to-dedge-docs)
- [Understanding the Metrics | Docs](#understanding-the-metrics-docs)
- [PnL Summary | Docs](#pnl-summary-docs)
- [Trading Fees | Docs](#trading-fees-docs)
- [The execution bot | Docs](#the-execution-bot-docs)
- [What is a copytrading system? | Docs](#what-is-a-copytrading-system-docs)
- [1-to-1 Expert Call | Docs](#1-to-1-expert-call-docs)
- [Basic topics | Docs](#basic-topics-docs)
- [Features | Docs](#features-docs)
- [High delta wallets | Docs](#high-delta-wallets-docs)
- [Copytrade Analyzer | Docs](#copytrade-analyzer-docs)
- [Wallet Batch API | Docs](#wallet-batch-api-docs)
- [The wallet testing phase | Docs](#the-wallet-testing-phase-docs)
- [Advanced Topics | Docs](#advanced-topics-docs)
- [Building a profitable operation | Docs](#building-a-profitable-operation-docs)
- [The research phase | Docs](#the-research-phase-docs)
- [Editor | Docs](#editor-docs)
- [Avoiding Snipers & HFT's | Docs](#avoiding-snipers-hft-s-docs)
- [Starting the bot | Docs](#starting-the-bot-docs)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Wallet Finder | Docs](#wallet-finder-docs)
- [The scale up phase | Docs](#the-scale-up-phase-docs)
- [Images & media | Docs](#images-media-docs)
- [Tips for choosing a wallet | Docs](#tips-for-choosing-a-wallet-docs)
- [SOL Spent, Received and Net SOL | Docs](#sol-spent-received-and-net-sol-docs)
- [Trading Deltas | Docs](#trading-deltas-docs)
- [Curated Wallets | Docs](#curated-wallets-docs)
- [Integrations | Docs](#integrations-docs)
- [Markdown | Docs](#markdown-docs)
- [Analyze Wallet | Docs](#analyze-wallet-docs)
- [Testing execution bots | Docs](#testing-execution-bots-docs)
- [The profitable operation | Docs](#the-profitable-operation-docs)
- [Filtered Wallets | Docs](#filtered-wallets-docs)
- [Tokens Traded, Win Rate & Open Trades | Docs](#tokens-traded-win-rate-open-trades-docs)
- [Tips for setting up the execution bot | Docs](#tips-for-setting-up-the-execution-bot-docs)
- [Unknown](#unknown)
- [OpenAPI | Docs](#openapi-docs)
- [Welcome to dEdge | Docs](#welcome-to-dedge-docs)
- [Unknown](#unknown)
- [Distribution of Trades PnL in percentiles | Docs](#distribution-of-trades-pnl-in-percentiles-docs)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Interactive blocks | Docs](#interactive-blocks-docs)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Basic topics | Docs](#basic-topics-docs)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [1-to-1 Expert Call | Docs](#1-to-1-expert-call-docs)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Wallet Batch API | Docs](#wallet-batch-api-docs)
- [Editor | Docs](#editor-docs)
- [Unknown](#unknown)
- [Unknown](#unknown)
- [Unknown](#unknown)

---

# Welcome to dEdge | Docs

![Page cover](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FDbLXEXIdBeBGunduMYXF%252Fbanner%2520X%2520v2.svg%3Falt%3Dmedia%26token%3D3660033c-6654-4036-834d-daa50746fe13&width=1248&dpr=3&quality=100&sign=73f4efa3&sv=2)

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/readme.md)
.

This guide is designed to help you gain **real trading edge**.

By understanding the key performance metrics provided by our tool, you will be able to identify reliable wallets and make informed decisions when copy trading.

Official links:

Bot - [https://t.me/dEdge\_solana\_bot?start=docs](https://t.me/dEdge_solana_bot?start=docs)

Community - [https://t.me/dEdge\_solana](https://t.me/dEdge_solana)

Twitter - [https://x.com/dEdge\_Solana](https://x.com/dEdge_Solana)

Web - [https://dedge.pro/](https://dedge.pro/)

[NextFeatures](https://dedge-v2.gitbook.io/dedge-docs/getting-started/features)

Last updated 1 year ago

This site uses cookies to deliver its service and to analyze traffic. By browsing this site, you accept the [privacy policy](https://policies.gitbook.com/privacy/cookies)
.

AcceptReject

---

# Understanding the Metrics | Docs

![Page cover](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Fimages.unsplash.com%2Fphoto-1531539134685-27d854339120%3Fcrop%3Dentropy%26cs%3Dsrgb%26fm%3Djpg%26ixid%3DM3wxOTcwMjR8MHwxfHNlYXJjaHwzfHx1bmRlcnN0YW5kaW5nfGVufDB8fHx8MTc0NDgxNzU1M3ww%26ixlib%3Drb-4.0.3%26q%3D85&width=1248&dpr=3&quality=100&sign=65a852ec&sv=2)

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics.md)
.

We will explain how to analyze the metrics.

**This is a very important section!**

Please, ask us questions in the community group if you did not understand anything.

[PreviousFiltered Wallets](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/filtered-wallets)
[NextTokens Traded, Win Rate & Open Trades](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs)

Last updated 1 year ago

---

# PnL Summary | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary.md)
.

This block presents a quick overview of profitability and efficiency

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FqrU8QD2wDdhmIEgF6dEP%252Fimage.png%3Falt%3Dmedia%26token%3Da230890e-4f30-4cc9-aa03-521be523fef5&width=768&dpr=3&quality=100&sign=400b893a&sv=2)

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary#average-pnl)

Average PnL

The mean profit or loss per trade, expressed in SOL and percentage. This value reflects the average outcome of each closed trade, helping you gauge typical performance.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary#average-trading-size-a)

Average Trading Size (A)

The average amount of SOL used per trade. This is useful for understanding the trader's risk appetite — higher values indicate larger trades on average.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary#sum-of-pnl-b)

Sum of PnL (B)

The total realized profit (or loss) in SOL, summing up all closed trades. It shows the net result of the wallet over the analyzed period.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary#pnl-ratio-b-a)

PnL Ratio (B/A)

This ratio divides the Sum of PnL (B) by the Average Trade Size (A), expressed as a percentage.

It measures how efficiently the wallet turns capital into profits.

A higher value here indicates that the wallet is generating strong returns relative to the size of its average trades.

_In the example above:_

His Avg. Trading Size is 0.73 SOL

The Sum of Pnl is 55 SOL

**PnL Ratio is 7580% ! This mean he has made like 75x !**

Which is an awesome return. But remember this is just an indicator.

This block is key to assess not just whether a wallet is profitable, but how effectively it uses capital to achieve that profit.

[PreviousDistribution of Trades PnL in percentiles](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles)
[NextSOL Spent, Received and Net SOL](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/sol-spent-received-and-net-sol)

Last updated 1 year ago

---

# Trading Fees | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-fees.md)
.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FrdgrmWas03tj8XV3zuCi%252Fimage.png%3Falt%3Dmedia%26token%3Df1eaaf75-a456-4261-adb6-a7a95ea660d1&width=768&dpr=3&quality=100&sign=8a0abdb1&sv=2)

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-fees#total-spent-on-fees)

Total Spent on Fees

This is the total amount of SOL the wallet spent on fees when buying and selling tokens.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-fees#average-fee-per-trade)

Average Fee per Trade

This shows the average fee per transaction. It’s calculated by dividing the total fees by the number of trades. This number is useful if you're copytrading. Some traders use high fees to get their transactions confirmed faster.

If you're always behind or transaction failing too much, it might be because your fee is too low. In this case, compare the fee level of other wallets and use something similar or slightly higher.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-fees#tip)

Tip:

If the Average Fee per Trade of the wallet is too high compared to others, it's probably a high-frequency trader or sniper. Avoid it.

[PreviousTrading Deltas](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas)
[NextBasic topics](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics)

Last updated 1 year ago

---

# The execution bot | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot.md)
.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot#in-order-to-start-copytrading-properly-you-need-a-good-execution-bot)

In order to start copytrading properly, you need a good execution bot.

Even if you have the best wallet, if you execution bot sucks, you will fail.

This means the bot you will use for copytrading must be good. We recommend using our partners, you will find them in the bot menu.

And this is very important because the bot has 2 very important tasks:

*   The first is to monitor everything the Lead Wallet is doing at all times
    
*   The second is to send a buy/sell transaction after spotting a transaction made by the Lead wallet
    

For such tasks, the bots use RPCs (that's how they communicate with the blockchain) and there’s considerable differences between them, in terms of speed and reliability.

Expect them to perform poorly sometimes, so the monitoring and transaction landing won't be nailed all the time.

Normally you can expect an execution bot to land a copytrade transaction in 1 to 5 seconds after the lead wallet.

Bad bots can take up to 30seconds or more sometimes.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FM0fJHJeWJmS42Q0AajZO%252Fimage.png%3Falt%3Dmedia%26token%3D92821ea4-23f8-4d5e-9a49-f6fb497b3dd5&width=768&dpr=3&quality=100&sign=e7810e4a&sv=2)

### 

[](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot#considering-this-what-should-i-do)

Considering this, what should I do?

Pick wallets with a slower trading pace ([higher deltas](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas)
) and test execution bots!

With a good bot, consider that it takes 5 seconds to buy and 5 seconds to sell a token when copying another wallet.

Read more on [Choosing a high delta wallet](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets)
 and [Testing execution bots](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/testing-execution-bots)
.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot#what-happens-if-i-blindly-pick-a-wallet-set-a-high-trading-size-and-leave-the-bot-executing-the-trad)

What happens if I blindly pick a wallet, set a high trading size and leave the bot executing the trades?

You will fail, 100% guaranteed. Sooner or later.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot#tips)

Tips

Always read the bots documentations and see what their users are talking about in the chat. Read the support channels to see common problems. Don't blindly trust anyone.

[PreviousWhat is a copytrading system?](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/what-is-a-copytrading-system)
[NextHigh delta wallets](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets)

Last updated 1 year ago

---

# What is a copytrading system? | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/what-is-a-copytrading-system.md)
.

*   It’s composed of a lead wallet (to be copied), your wallet (copytrader) and an execution bot (copytrade bot).
    
*   It’s a system in which a copytrader aims to copy a successful wallet in order to profit similarly. Most beginner traders think they just need a wallet with big profits and high win rate but actually they need more than that.
    
*   You need to test your copytrading system before trading with considerable size. You have to be confident about the execution bot and wallet you are going to follow.
    

[PreviousBasic topics](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics)
[NextThe execution bot](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot)

Last updated 1 year ago

---

# 1-to-1 Expert Call | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call.md)
.

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call#most-traders-lose-money-not-because-they-lack-effort-but-because-they-lack-direction)

Most traders lose money not because they lack effort — but because they lack direction.

You shouldn’t have to burn capital just to learn how copy trading works. That’s why we offer something no one else does: a **personal consultation with a real expert** - not support staff. You’ll speak directly with a **veteran of the financial markets** with over 10 years of experience and a proven track record helping traders build strategies that actually work — in bull markets, bear markets, and everything in between.

* * *

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call#heres-what-youll-get)

Here’s what you’ll get:

*   A **strategic deep dive** into your current copy trading approach
    
*   **Tailored recommendations** based on your goals, time, and capital
    
*   Clarity on **which wallets to follow** — and which ones to avoid
    
*   The understanding of how **professionals copy trade**
    
*   Actionable tips to **minimize risk** and avoid costly beginner traps
    
*   Full walkthrough on how to **maximize your results**
    

* * *

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call#how-it-works)

How It Works:

*   You will find the directions to book it on the bot. (type /start, then click More > How to Use > Book Expert Call)
    
*   Scheduled on demand, subject to availability
    

* * *

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call#feedbacks)

Feedbacks

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FaIO3Oo9NK3I00YhYrhYD%252Fimage.png%3Falt%3Dmedia%26token%3D7b05c274-b58c-4b01-9e50-1f3e3e5ce973&width=768&dpr=3&quality=100&sign=3a14c00f&sv=2)

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FF5ThaZqBFjOyviQNFoBU%252Fimage.png%3Falt%3Dmedia%26token%3Deade1b67-9198-4771-ae38-42063f837bf1&width=768&dpr=3&quality=100&sign=c1aa6bd8&sv=2)

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252F9RRvDAGdMAi8dhiirdKB%252Fimage.png%3Falt%3Dmedia%26token%3De19d13c5-f6a7-4e51-bffd-2511f5a11323&width=768&dpr=3&quality=100&sign=c95c4e4f&sv=2)

[PreviousThe profitable operation](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-profitable-operation)
[NextCopytrade Analyzer](https://dedge-v2.gitbook.io/dedge-docs/copytrade-analyzer)

Last updated 1 year ago

---

# Basic topics | Docs

![Page cover](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Fimages.unsplash.com%2Fphoto-1622186477895-f2af6a0f5a97%3Fcrop%3Dentropy%26cs%3Dsrgb%26fm%3Djpg%26ixid%3DM3wxOTcwMjR8MHwxfHNlYXJjaHw2fHx0aXB8ZW58MHx8fHwxNzQ0ODIxMDQ4fDA%26ixlib%3Drb-4.0.3%26q%3D85&width=1248&dpr=3&quality=100&sign=ce548d02&sv=2)

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics.md)
.

Important points for those starting with Copy Trading.

[PreviousTrading Fees](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-fees)
[NextWhat is a copytrading system?](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/what-is-a-copytrading-system)

Last updated 1 year ago

---

# Features | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/features.md)
.

Founded by a team with over **35 years** of combined expertise in **technology** and **algorithmic trading**, dEdge delivers top-tier analysis to its users through its cutting-edge technology.

Features overview:

*   A powerful algorithm that scans the blockchain 24/7 finding the best performing wallets
    
*   Unprecedent level of depth in wallet analysis (the most reliable & quantitative approach in the market)
    
*   One-click delivery of wallets ([Wallet Finder](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/wallet-finder)
    , [Curated Wallets](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/curated-wallets)
     and [Filtered Wallets](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/filtered-wallets)
    )
    
*   [Copytrade Analyzer](https://dedge-v2.gitbook.io/dedge-docs/copytrade-analyzer)
     to track how you're performing relative to the Lead Wallet (aka wallet you're copying)
    
*   The public community with dozens of professional copy traders
    
*   Alpha group in which there's close contact with founding team and a weekly delivery of a list with hundreds of wallets
    
*   [1-to-1 Expert Calls](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call)
     with our seasoned copy trading expert that has helped hundreds of traders to perform in any market situation
    

[PreviousWelcome to dEdge](https://dedge-v2.gitbook.io/dedge-docs)
[NextStarting the bot](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart)

Last updated 1 year ago

---

# High delta wallets | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets.md)
.

As we just read on [The execution bot](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot)
, we got to find a wallet that will perform even if the execution bot doesn't perform at its best.

Wallets that have a slower trading pace ([higher trading deltas](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas)
) will perform better because they are less dependent on very short-term price changes/volatility.

On average, with a good bot, consider that it takes 5 seconds to buy and 5 seconds to sell a token when copying another wallet.

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets#example-1)

Example 1:

If the wallet 10th Delta Percentile is 600, this means 90% of his trades will last longer than 600 seconds or 10 minutes. This trader edge isn't profiting from a very fast gain, that depends on liquidity or short-term volatility.

This makes him a good target for copying, if everything else in terms of profitability makes sense.

The price I'm buying and selling the token will hardly be much worse than his. Maybe a 5% difference? If on average he's aiming for 50% on a trade and I make 40% by copying him, this is fine.

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets#example-2)

Example 2:

If the wallet 50th Delta Percentile is 100, this means half of his trades takes less than 100 seconds.

This guy definitely has an edge by trading fast. If my bot delays 5 seconds to buy, I could get a price 100% more expensive than his. Or even more than that. And same goes for the selling, 5 seconds could have a huge impact.

So, rule of thumb: Don't copy traders who have fast trading pace / lower trading deltas. It won't work.

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets#example-3)

Example 3:

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252Fs6usW7DSRyiKGhEOwAnZ%252Fimage.png%3Falt%3Dmedia%26token%3Dce94a58b-001f-4d60-8261-955069bf21fb&width=768&dpr=3&quality=100&sign=54256723&sv=2)

This trader has mixed deltas. Some are high, others are low.

25th Percentile tells it all: 25% of the time he will be trading in less than 84 seconds. This means, 25% of the time you will probably lose money. This is not a good start, is it?

[PreviousThe execution bot](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot)
[NextAvoiding Snipers & HFT's](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts)

Last updated 1 year ago

---

# Copytrade Analyzer | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/copytrade-analyzer.md)
.

This an advanced tool for analyzing your copytrading performance.

It's in final steps of construction.

If you want to try it, just type /tracing followed by the wallet you're following (the lead wallet) separated by comma from your wallet (copier wallet) like the example below /tracing leadWallet,copierWallet

it will look like this:

/tracing D37KwuoeLJJqVkD9EPaLD4zfwAZdp7WnH6BoJ5BPJ8rb,58FnazdGmCKZPeiMJ2rzujkeUR1HURr9cJNvVPxechKt

And you will receive a prelaminar report of the effectiveness of you wallet compared to the lead wallet.

If you are having a hard time, reach us on the community group so we can show how it works for you.

[Previous1-to-1 Expert Call](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call)
[NextWallet Batch API](https://dedge-v2.gitbook.io/dedge-docs/api/wallet-batch-api)

Last updated 1 year ago

---

# Wallet Batch API | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/api/wallet-batch-api.md)
.

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/api/wallet-batch-api#to-access-the-api-documentation-click-the-link-below)

To access the API documentation, click the link below

[![Logo](https://dedge-1.gitbook.io/dedge-sol-analyzer/~gitbook/image?url=https%3A%2F%2F577898269-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Forganizations%252FwzESTGHGL2bIiNCKflCu%252Fsites%252Fsite_KBYy6%252Ficon%252FKJ4jJzyXKNhY6ETJRNMU%252Flogo2_400x400.png%3Falt%3Dmedia%26token%3Dbf8f93fe-5b0e-47db-b16c-3a9d38798cc5&width=48&height=48&sign=6aa34b70&sv=2)Wallet Batch API | dEdge Wallet Profitability on Solanadedge-1.gitbook.io](https://dedge-1.gitbook.io/dedge-sol-analyzer/api-documentation/readme/wallet-batch-api)

[PreviousCopytrade Analyzer](https://dedge-v2.gitbook.io/dedge-docs/copytrade-analyzer)

Last updated 1 year ago

---

# The wallet testing phase | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-wallet-testing-phase.md)
.

1.  After finding some good candidates, we will start testing them.
    
2.  You should add from **0 to 2 wallets per day** in your operation. No more than that.
    
3.  If you are new or don't have time, don't copy more than 2-3 wallets at once.
    
4.  **You are not trying to profit at this stage** but rather discover if the wallets you selected are good for copytrading.
    
5.  The **betting size should be minimal**. Do it with something like 0.01 or 0.001 SOL.
    
6.  Keep trading fees at the right level. Doesn't mind if the trading fees are eating up more than trading size at this stage. This is a learning phase. **It's better to lose small here than have an expensive learning** by copying the wrong wallet with a considerable size.
    
7.  Insert the wallets you're using on Ray ([https://t.me/ray\_azure\_bot?start=ref\_Auq2Cy](https://t.me/ray_azure_bot?start=ref_Auq2Cy)
    ), so it will notify when they trade. This way you watch closely how they're performing.
    

[PreviousThe research phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-research-phase)
[NextThe scale up phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-scale-up-phase)

Last updated 1 year ago

---

# Advanced Topics | Docs

![Page cover](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Fimages.unsplash.com%2Fphoto-1597600159211-d6c104f408d1%3Fcrop%3Dentropy%26cs%3Dsrgb%26fm%3Djpg%26ixid%3DM3wxOTcwMjR8MHwxfHNlYXJjaHwyfHxhZHZhbmNlZHxlbnwwfHx8fDE3NDQ4Mjk1Mzh8MA%26ixlib%3Drb-4.0.3%26q%3D85&width=1248&dpr=3&quality=100&sign=5a0c8fde&sv=2)

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics.md)
.

If you are still here, congratulations! This is the ONLY way of making it happen in copytrading!

Keep reading the docs.

[PreviousTips for setting up the execution bot](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-setting-up-the-execution-bot)
[NextTesting execution bots](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/testing-execution-bots)

Last updated 1 year ago

---

# Building a profitable operation | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/building-a-profitable-operation.md)
.

After you are confident about **the power of dEdge quantitative** [**metrics**](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics) and setting up the [execution bot](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot)
, it's time to optimize the operation.

This is a very basic roadmap to follow. We strongly recommend you taking the [1-to-1 Expert Call](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call)
, if you are serious about it.

1.  It all starts with the [research phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-research-phase)
    . Finding wallets to copy.
    
2.  Then, you will test those wallets to see if they're good for copytrading. You won't try to profit here, just learn if the wallet is good. This the [wallet testing phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-wallet-testing-phase).
    
3.  After you found some wallets that are working well, we proceed to the [scale up phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-scale-up-phase) - in which we will start increasing the trading size.
    
4.  A [healthy operation](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-profitable-operation) consists in having multiple profitable wallets working for you rather than just one or two. This is definitely what going to make you successful in the long run.
    

[PreviousTesting execution bots](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/testing-execution-bots)
[NextThe research phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-research-phase)

Last updated 1 year ago

---

# The research phase | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-research-phase.md)
.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-research-phase#the-research-phase)

The research phase:

1.  The easy way: Get wallets from dEdge - Wallet Finder, Curated Wallets, Filtered Wallets and the Weekly List
    
2.  The hard way: Get Top Traders wallets from DexScreener and scan them with dEdge
    
3.  Be careful with other tools you find out there (most of the data isn't reliable and/or isn't enough to assess if the wallet is good for copy trading)
    
4.  Look for reliable wallets. With at least a couple trades to prove they've been doing good.
    
5.  Avoid wallets that made huge profits in a small percent of his trades - this likely **won't happen again**
    
6.  You want wallets that gains with consistency
    
7.  Normally a higher win rate with smaller wins or a lower win rate with some bigger wins - but nothing exaggerated
    
8.  Avoid low [trading delta](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas)
     wallets (high frequency traders)
    
9.  Most of the wallets for copy trading won't look perfect - **they will look just good and that's enough**
    
10.  See the wallet last trades to see graphically how they trade (there's a guide to it on [Avoiding Snipers & HFT](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts)
     section)
    
11.  **Don't be too picky**. But be confident about what to not tolerate. Don't lower your standards to increase trading frequency. Opportunities will always arise, but lost money is hard to recover.
    
12.  Most of the time you are **looking for red flags** to exclude the wallet. If you can't find any, it might be good to copy.
    
13.  With some experience in your operation, you will spot red flags faster.
    
14.  Create a to-do list when analyzing wallets. Add steps to it as you learn.
    

[PreviousBuilding a profitable operation](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/building-a-profitable-operation)
[NextThe wallet testing phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-wallet-testing-phase)

Last updated 1 year ago

---

# Editor | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/basics/editor.md)
.

GitBook has a powerful block-based editor that allows you to seamlessly create, update, and enhance your content.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Fgitbookio.github.io%2Fonboarding-template-images%2Feditor-hero.png&width=768&dpr=3&quality=100&sign=5aa3ebd7&sv=2)

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/editor#writing-content)

Writing content

GitBook offers a range of block types for you to add to your content inline — from simple text and tables, to code blocks and more. These elements will make your pages more useful to readers, and offer extra information and context.

Either start typing below, or press `/` to see a list of the blocks you can insert into your page.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/editor#add-a-new-block)

Add a new block

1

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/editor#open-the-insert-block-menu)

Open the insert block menu

Press `/` on your keyboard to open the insert block menu.

2

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/editor#search-for-the-block-you-need)

Search for the block you need

Try searching for “Stepper”, for exampe, to insert the stepper block.

3

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/editor#insert-and-edit-your-block)

Insert and edit your block

Click or press Enter to insert your block. From here, you’ll be able to edit it as needed.

---

# Avoiding Snipers & HFT's | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts.md)
.

As we just saw, avoiding "speedy" traders is very important because trading bots won't be able to copy them.

High-frequency traders are easy to spot. The buy and sell in a couple seconds. They will have very low trading deltas.

But what about snipers? They can spend a lot on fees to buy the token and are the first ones to buy it. Trading bots won't be able to copy their performance because they enter too early in the trade. But sometimes they don't sell as early, making it harder to spot them.

If you are unsure if the trader is a sniper, just follow the steps below:

1.  Insert the wallet on dEdge bot
    

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252Fpzwlobbo6uFj7dGUJ7Xc%252Fimage.png%3Falt%3Dmedia%26token%3Dc93a32aa-8177-4529-96dc-3c57c0299acb&width=768&dpr=3&quality=100&sign=688028ed&sv=2)

1.  After receiving the summary, click on Last 5 Trades
    

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FeGy0ADzPKrvQGv3CHYl9%252Fimage.png%3Falt%3Dmedia%26token%3Dc3741aea-24d9-4aab-bac4-60ea323e80dd&width=768&dpr=3&quality=100&sign=405d95e9&sv=2)

1.  You will see a list with DexScreener links, click them to see that trading behavior plotted
    

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FFyrbwnNLoD48ABBywcTE%252Fimage.png%3Falt%3Dmedia%26token%3D4211850b-7bdd-472e-bd43-37aaeac4d1ec&width=768&dpr=3&quality=100&sign=22290906&sv=2)

1.  It will open up a chart with his Buy and Sells on it
    

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252F3aK2H1LtlRnUrUysZDcY%252Fimage.png%3Falt%3Dmedia%26token%3D97a17f99-2e8a-4ff7-86dc-6d94d28a15a5&width=768&dpr=3&quality=100&sign=2ce33b42&sv=2)

1.  This is a 1-second candle chart. Snipers will buy tokens on the first minute, which is represented in the red circle. Avoid copying wallets that buy in the first minute of token launch.
    
2.  The example above is ok. The wallet bought after 4 minutes from the launch and sold 2 minutes after that.
    

[PreviousHigh delta wallets](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets)
[NextTips for choosing a wallet](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-choosing-a-wallet)

Last updated 1 year ago

---

# Starting the bot | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart.md)
.

After opening the bot, which can be found on this link - https://t.me/dEdge\_solana\_bot?start=docs

You can type /start and you will see this screen:

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXcRxtkDGYgtTf0NIuvUX0luC9K-0nth-2eGfH41f1qt3cWV8bIxQlqn6Ec_bMQYrFbbteyizQvrhsWcHhir4tm2ypM1TDBQVYPrW3dDZ4mSfrEFHJ-8Lu6DJStChAxVIJIq6QLx%3Fkey%3DXmKkwN575tuH_KlW_bGqh3x1&width=768&dpr=3&quality=100&sign=fbe2faea&sv=2)

If this your first time using dEdge, click **Wallet Finder** or just **paste a wallet and press enter**. These are **free** to use.

Curated Wallets and Filtered wallets are premium features.

[PreviousFeatures](https://dedge-v2.gitbook.io/dedge-docs/getting-started/features)
[NextAnalyze Wallet](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/analyze-wallet)

Last updated 1 year ago

---

# Unknown

\# Docs

## dEdge Docs

- \[Welcome to dEdge\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/readme.md)
- \[Features\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/features.md)
- \[Starting the bot\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart.md)
- \[Analyze Wallet\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/analyze-wallet.md)
- \[Wallet Finder\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/wallet-finder.md)
- \[Curated Wallets\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/curated-wallets.md)
- \[Filtered Wallets\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/filtered-wallets.md)
- \[Understanding the Metrics\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics.md)
- \[Tokens Traded, Win Rate & Open Trades\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs.md)
- \[Distribution of Trades PnL in percentiles\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles.md)
- \[PnL Summary\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary.md)
- \[SOL Spent, Received and Net SOL\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/sol-spent-received-and-net-sol.md)
- \[Trading Deltas\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas.md)
- \[Trading Fees\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-fees.md)
- \[Basic topics\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics.md)
- \[What is a copytrading system?\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/what-is-a-copytrading-system.md)
- \[The execution bot\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot.md)
- \[High delta wallets\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets.md)
- \[Avoiding Snipers & HFT's\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts.md)
- \[Tips for choosing a wallet\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-choosing-a-wallet.md)
- \[Tips for setting up the execution bot\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-setting-up-the-execution-bot.md)
- \[Advanced Topics\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics.md)
- \[Testing execution bots\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/testing-execution-bots.md)
- \[Building a profitable operation\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/building-a-profitable-operation.md)
- \[The research phase\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-research-phase.md)
- \[The wallet testing phase\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-wallet-testing-phase.md)
- \[The scale up phase\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-scale-up-phase.md)
- \[The profitable operation\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-profitable-operation.md)
- \[1-to-1 Expert Call\](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call.md)
- \[Copytrade Analyzer\](https://dedge-v2.gitbook.io/dedge-docs/copytrade-analyzer.md)
- \[Wallet Batch API\](https://dedge-v2.gitbook.io/dedge-docs/api/wallet-batch-api.md)
- \[Editor\](https://dedge-v2.gitbook.io/dedge-docs/basics/editor.md)
- \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/basics/markdown.md)
- \[Images & media\](https://dedge-v2.gitbook.io/dedge-docs/basics/images-and-media.md)
- \[Interactive blocks\](https://dedge-v2.gitbook.io/dedge-docs/basics/interactive-blocks.md)
- \[OpenAPI\](https://dedge-v2.gitbook.io/dedge-docs/basics/openapi.md)
- \[Integrations\](https://dedge-v2.gitbook.io/dedge-docs/basics/integrations.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on a page URL with the \`ask\` query parameter:
\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/readme.md?ask=<question>
\`\`\`
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/readme.md).

# Welcome to dEdge

This guide is designed to help you gain \*\*real trading edge\*\*.

\\
By understanding the key performance metrics provided by our tool, you will be able to identify reliable wallets and make informed decisions when copy trading.

\\
Official links:

Bot -\[ https://t.me/dEdge\\\_solana\\\_bot?start=docs\](https://t.me/dEdge\_solana\_bot?start=docs)

Community -\[ https://t.me/dEdge\\\_solana\](https://t.me/dEdge\_solana)

Twitter -\[ https://x.com/dEdge\\\_Solana\](https://x.com/dEdge\_Solana)

Web -\[ https://dedge.pro/\](https://dedge.pro/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/readme.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Wallet Finder | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/wallet-finder.md)
.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252Fh7Bx2xX8Kpg0yPXV2fIn%252Fimage.png%3Falt%3Dmedia%26token%3De8866687-090d-4f39-8e04-b6607d5cad0a&width=768&dpr=3&quality=100&sign=b0d70223&sv=2)

The Wallet Finder can be used by Free users.

It's just the tip of the iceberg in terms of good & profitables wallets we have.

Just click on the button and you will get a wallet.

[PreviousAnalyze Wallet](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/analyze-wallet)
[NextCurated Wallets](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/curated-wallets)

Last updated 1 year ago

---

# The scale up phase | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-scale-up-phase.md)
.

1.  At least once per day, check all trades. Monitor them on Ray. See how each wallet is performing. Also keeping it on a spreadsheet will help.
    
2.  Some wallets will perform bad. Some will do good.
    
3.  If they're not doing as expected, we got to remove them. But first, **wait at least 3-4 trades** before excluding a wallet from the testing phase. Try to discover why they did not work. This is **very important**.
    
4.  For the wallets doing good, wait at least 3-4 trades before **increasing** the trading size.
    
5.  Analyze their trades on DexScreener. See how this wallet trades. The tokens it trades. When you find similar wallets on the research, you will know it's a good candidate.
    
6.  By using the [Copytrade Analyzer](https://dedge-v2.gitbook.io/dedge-docs/copytrade-analyzer)
     you will be able to know how well you're doing relative to the wallet you're copying (Lead wallet).
    
7.  It is normal to perform worse than the copied wallet. What we are looking for here is to be **profitable**. Don't expect to have the same results as the wallet you are copying.
    
8.  If you are seeing consistent results from a wallet, increase the betting size. Doesn't need to be a lot. Just something reasonable and wait a few trades to see how it performs. If it's still performing well, you can increase even more. **Always analyze the trades before increasing the size.**
    

### 

[](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-scale-up-phase#a-very-important-point-here-scaling-up-5-wallets-to-0.5-sol-trading-size-is-100x-better-and-smarter)

A very important point here: scaling up 5 wallets to 0.5 SOL trading size is **100x BETTER & SMARTER** than scaling up 1 wallet to 2.5 SOL trading size.

[PreviousThe wallet testing phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-wallet-testing-phase)
[NextThe profitable operation](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-profitable-operation)

Last updated 1 year ago

---

# Images & media | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/basics/images-and-media.md)
.

GitBook allows you to add images and media easily to your docs. Simply drag a file into the editor, or use the file manager in the upper right corner to upload multiple images at once.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Fgitbookio.github.io%2Fonboarding-template-images%2Fimages-hero.png&width=768&dpr=3&quality=100&sign=96bfcd0c&sv=2)

Add alt text and captions to your images

You can also add images simply by copying and pasting them directly into the editor — and GitBook will automatically add it to your file manager.

---

# Tips for choosing a wallet | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-choosing-a-wallet.md)
.

This is just the beginning. The more you analyze wallets and copytrade, you'll get more experienced and better at this. But just to start out, when choosing a wallet:

*   Make sure you understand what [Trade Percentiles](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles)
     are.
    
*   Win rate is important but how big the losses are is even more important. If one wallet 10th percentile is -50% while the other is -5%, the second is **MUCH** better.
    
*   Be careful with too many [open trades](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs)
    
*   If his Best Trade is a high % amount of his Sum of Pnl (more than 70-80%, be careful - his profits might be just a lucky shot)
    
*   Prefer [high delta wallets](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets)
    
*   Always check the wallet trading patterns on [DexScreener](https://dexscreener.com/)
     (you can find the direct link as mentioned on [Avoiding Snipers & HFT's](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts)
    ) - imagine your bot will enter a few seconds/candles after the wallet. Would it still be profitable? Also, does the price falls hard after he sells? Or does price increase considerable seconds after he buys? (this could be an indicator that he's being heavily copytraded)
    
*   Read [The research phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-research-phase)
     for more insights on choosing wallets.
    

[PreviousAvoiding Snipers & HFT's](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts)
[NextTips for setting up the execution bot](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-setting-up-the-execution-bot)

Last updated 1 year ago

---

# SOL Spent, Received and Net SOL | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/sol-spent-received-and-net-sol.md)
.

This section breaks down the wallet’s activity in terms of total SOL spent and received trading tokens. It does not matter if the trade is fully closed or still open.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252F5wKzpTYZKklc4l8Zfvol%252Fimage.png%3Falt%3Dmedia%26token%3D39a6c7fe-307c-4e30-9f25-85bf62ccdd18&width=768&dpr=3&quality=100&sign=6b870044&sv=2)

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/sol-spent-received-and-net-sol#sol-spent-buying-tokens-c)

SOL Spent Buying Tokens (C)

The total amount of SOL used to buy tokens. This represents the capital invested across all trades.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/sol-spent-received-and-net-sol#sol-received-selling-tokens-d)

SOL Received Selling Tokens (D)

The total amount of SOL the wallet received when selling tokens. This shows the accumulated return from all positions.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/sol-spent-received-and-net-sol#net-sol-d-c)

Net SOL (D - C)

The difference between the total received and the total spent. If this number is positive, it means the wallet has a net profit in SOL.

This metric is useful for verifying actual profitability in SOL and is one of the most straightforward indicators of a trader’s success over time.

_Usage example:_

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FYZSa82I4cVuQu3F5IyYJ%252Fimage.png%3Falt%3Dmedia%26token%3D2333da1f-3286-4d8e-a4b6-626e0c32963b&width=768&dpr=3&quality=100&sign=3e7b5da9&sv=2)

In the example above, Sum of PnL is 26 and Net SOL is almost 25. This means 1 SOL (the difference) is missing in open trades - which can still have value as token or not. Or might just be an **unrealized loss**.

For a 25 SOL profit, 1 SOL missing is relatively ok. But look at the example below:

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FOj4lCMMgwLIv0oGLBH9h%252Fimage.png%3Falt%3Dmedia%26token%3D01231923-33cd-40fd-81a9-c744a09345df&width=768&dpr=3&quality=100&sign=88389b18&sv=2)

In this case, Sum of Pnl is 8.4 and Net Sol is 4.8 - the difference here is almost 4 SOL, which is relatively much bigger when compared to the PnL. Indicating he may have a considerable unrealized loss.

[PreviousPnL Summary](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary)
[NextTrading Deltas](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas)

Last updated 1 year ago

---

# Trading Deltas | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas.md)
.

Trading Deltas tells the story about how fast the wallet trades.

_If you don't know what percentiles are, head to the section of_ [_Distribtuion of Trades PnL in Percentiles_](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles)
 _as it is explained there. If you still didn't understand, ask us on the community group._

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXc1FwDLQlSNFXWV2Sr-wubvRpHGfUpVS7XSyiqmmjvjgtZC0akhdAzJNKvLIUlTcn-SxaN9ULvAGgoe_jmM0_z3Bfvxfz3cPkn0UplegPN_yb6s8LhqKpqcbHnMaDxOp88bPJE9hg%3Fkey%3DXmKkwN575tuH_KlW_bGqh3x1&width=768&dpr=3&quality=100&sign=1265d7ba&sv=2)

The distribution of Deltas shows how fast the trader open and close his trades.

In the example above, his fastest trade took only 30 seconds. The lengthiest trade took 153 minutes. If you sum all the trading times and divide by the number of trades, it will be 19.7 minutes - but this isn't a good metric because it can be skewed.

Imagine if there was a single trade that took 6 months, the average trading time then would be many days. But all the other trades were much faster. Does it make sense?

That's why percentiles are SO important, because it shows the distribution of all trades, lined up in the best way possible for us to comprehend without having to analyze each trade individually.

*   **The 10th Percentile**: in the example above, it means 10% of his trades took less than 148 seconds. If he traded 20 times, only 2 trades took less than this time.
    
*   **The 25th Percentile**: Again, if he traded 20 times, only 5 of his trades were less than 298 seconds.
    
*   **50th Percentile**: Half of his trades took less than 596 second and half took more than that.
    

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas#what-to-look-for-here)

What to look for here?

Generally speaking, execution bots will fail if the wallet trades too fast. The most important factors here are the 10th, 25th and 50th percentiles. You need to make sure that most of his trades takes at least a couple minutes, so it's not a high frequency trader and the bot will be able to copy properly.

We recommend the 10th percentile to be above 120-200 at least.

Another thing to avoid here are: Snipers! - read the section [Avoiding Snipers & HFTs](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts)

[PreviousSOL Spent, Received and Net SOL](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/sol-spent-received-and-net-sol)
[NextTrading Fees](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-fees)

Last updated 1 year ago

---

# Curated Wallets | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/curated-wallets.md)
.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FkapY2I72NRzOZMUHikNe%252Fimage.png%3Falt%3Dmedia%26token%3D14717ee4-8668-4bda-b41c-e7b6f1309faf&width=768&dpr=3&quality=100&sign=17d1dbc5&sv=2)

Curated Wallets are special wallets.

This is where you will find the top 1% of wallets/traders.

The odds of being profitable copying one of these are highly increased when compared to Wallet Finder.

This is a premium feature.

[PreviousWallet Finder](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/wallet-finder)
[NextFiltered Wallets](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/filtered-wallets)

Last updated 1 year ago

---

# Integrations | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/basics/integrations.md)
.

GitBook integrations allow you to connect your GitBook spaces to some of your favorite platforms and services. You can install integrations into your GitBook page from the _Integrations_ menu in the top left.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Fgitbookio.github.io%2Fonboarding-template-images%2Fintegrations-hero.png&width=768&dpr=3&quality=100&sign=9b58b4b5&sv=2)

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/integrations#types-of-integrations)

Types of integrations

[](https://www.gitbook.com/integrations#analytics)

**Analytics**

Track analytics from your docs

[](https://www.gitbook.com/integrations#support)

**Support**

Add support widgets to your docs

[](https://www.gitbook.com/integrations#interactive)

**Interactive**

Add extra functionality to your docs

[](https://www.gitbook.com/integrations#visitor-authentication)

**Visitor Authentication**

Protect your docs and require sign-in

---

# Markdown | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/basics/markdown.md)
.

GitBook supports many different types of content, and is backed by Markdown — meaning you can copy and paste any existing Markdown files directly into the editor!

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Fgitbookio.github.io%2Fonboarding-template-images%2Fmarkdown-hero.png&width=768&dpr=3&quality=100&sign=d1a9e933&sv=2)

Feel free to test it out and copy the Markdown below by hovering over the code block in the upper right, and pasting into a new line underneath.

Copy

    # Heading
    
    This is some paragraph text, with a [link](https://docs.gitbook.com) to our docs. 
    
    ## Heading 2
    - Point 1
    - Point 2
    - Point 3

If you have multiple files, GitBook makes it easy to import full repositories too — allowing you to keep your GitBook content in sync.

---

# Analyze Wallet | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/analyze-wallet.md)
.

To start analyzing a wallet, just paste it and press enter.

Waiting time is normally from 5 to 30 seconds, depending on how many transactions the wallet has.

You'll receive a wallet summary similar to this one below, which we will explain all the details in this guide.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FuEECQ9X6WZ4hCx7O49te%252Fimage.png%3Falt%3Dmedia%26token%3Dbabb19c8-dcc1-420b-bdf7-981af02539d0&width=768&dpr=3&quality=100&sign=5798854d&sv=2)

This is free to use, up to a limit.

[PreviousStarting the bot](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart)
[NextWallet Finder](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/wallet-finder)

Last updated 1 year ago

---

# Testing execution bots | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/testing-execution-bots.md)
.

Unless you're recommend by someone you trust which bot to use, we recommend you test them. Read the bot documentation then proceed with the test below.

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/testing-execution-bots#this-an-introductory-example-of-how-to-test-a-bot.-chat-with-us-on-the-community-if-you-want-to-dig)

This an introductory example of how to test a bot. Chat with us on the community if you want to dig deeper.

1.  Pick a wallet to copy
    
2.  Pick at least 2 bots you want to test (so you can compare them, at least)
    
3.  Set that wallet to be copied on the bots you are testing
    
4.  Make sure you are using same amount of fees and a very small trading size, this is just for test purpose, you are not trying to make money but rather avoiding to lose it in the future
    
5.  After each trade, verify how long it took for them to buy and sell
    

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/testing-execution-bots#how-to-verify-how-long-it-took-to-replicate)

How to verify how long it took to replicate?

Easy. You need to see in which block the transaction landed.

1.  Go to solscan.io
    
2.  Insert the wallet
    
3.  Click on Balance Changes
    

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FTFfsSNSdZ8SqawR1z7iO%252Fimage.png%3Falt%3Dmedia%26token%3D9dae8c95-afd0-4038-b364-34a375a1146a&width=768&dpr=3&quality=100&sign=4c98e438&sv=2)

4\. In the picture, the line below is the buy transaction (amount in green) and the line above it is the sell transaction.

1.  The block numbers 333276164 and 333276285 are when the token was Bought and Sold.
    
2.  Compare the difference between blocks for the wallet being copied and the wallets from the bots you are testing. Each block in Solana is around 400miliseconds.
    
3.  Do this from time to time to make sure the bot you are using isn't leaving you behind.
    

[PreviousAdvanced Topics](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics)
[NextBuilding a profitable operation](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/building-a-profitable-operation)

Last updated 1 year ago

---

# The profitable operation | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-profitable-operation.md)
.

After working daily on research, testing and scaling up, you should have a few profitable wallets at least.

**Congratulations! You're building a portfolio of wallets!**

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252F11K7VfCOd39qvq2dicv3%252Fimage.png%3Falt%3Dmedia%26token%3D77b01690-a45a-4c1a-9e42-de398eda4848&width=768&dpr=3&quality=100&sign=8e8f41cb&sv=2)

#### 

[](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-profitable-operation#its-good-youre-seeing-a-well-deserved-success-but-there-are-some-important-points)

It's good you're seeing a well-deserved success but there are some important points:

1.  Your goal is not to become rich overnight. Trading too big is too risky and won't work in the long run.
    
2.  Focus on researching, testing and scaling, do it daily. Keep adding new wallets. Analyzing them. Figuring out a method that works for you.
    
3.  They right way to go is by increasing the number of profitable wallets you run.
    
4.  For most of the wallets, the performance will be ok to good. With some negative results sometimes. You should set a maximum trading size. Don't risk too much. Focus on adding more wallets.
    
5.  On rare occasions, you will find a very special wallet. After 10 trades it's performing super. You will be tempted to trade BIG on this one. And you probably should. But set a maximum risk parameter. Be careful. And good luck!
    

[PreviousThe scale up phase](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-scale-up-phase)
[Next1-to-1 Expert Call](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call)

Last updated 1 year ago

---

# Filtered Wallets | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/filtered-wallets.md)
.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FEfFSQND21lcehGgIpvOt%252Fimage.png%3Falt%3Dmedia%26token%3D7bd202f9-160e-4c05-9843-1966648862b2&width=768&dpr=3&quality=100&sign=ecc70819&sv=2)

If you want to set your own filters, this is the right tool for you.

After clicking the button, you will get a wallet with standard filters.

On the bottom, you will see these buttons:

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252F1QjT6EWlJZj9n1eNN23N%252Fimage.png%3Falt%3Dmedia%26token%3D443a7534-5b78-4b9e-81f7-586ac6a924a1&width=768&dpr=3&quality=100&sign=157233eb&sv=2)

You can adjust the filters by click on **Adjust Filters.**

You will see the menu below:

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252F8AXNC2X9KsecPTammNc6%252Fimage.png%3Falt%3Dmedia%26token%3Ddb701028-51e1-46b7-a43b-90039c1abfe9&width=768&dpr=3&quality=100&sign=6d0718d3&sv=2)

You will see the standard values for filtered wallets.

By using the shown commands, you are able to define the filters the way you like.

The [50th Percentile Delta](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas)
 is too low for copytrading. Let's change it to 200.

Just type /set\_50th\_delta 200

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FPp7tV8fx3iS2RTc3D7RK%252Fimage.png%3Falt%3Dmedia%26token%3Dfd66becb-bbfa-43d0-ba5f-e31e0d429321&width=768&dpr=3&quality=100&sign=f6f2414e&sv=2)

And now it is 200 seconds, much better.

We also recommend increasing [Closed Trades](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs)
 to at least 15. And you could also increase win rate to 60%.

Bear in mind there is no right filters - it's just a matter of trying different numbers out and seeing if you're getting good wallets.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/filtered-wallets#general-tips-for-filtering)

**General tips for filtering**

*   If [win rate](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs)
     is too high, like 90%+ you will likely get a lot of bots that can't be copied.
    
*   If [50th Percentile Delta](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas)
     is too low, your execution bot won't be able to copy it properly. Leave it at least on 200 and you can try higher numbers like 500 or 1000 as well to find slower paced traders.
    
*   The more trades the wallet has, the more you can be confident of its results. The performance of a wallet with 30 trades is more reliable than a wallet with 5 trades. But there is a trade-off here: it's very common for professionals to change wallets often, so this guys wont have wallets with a lot of trades. Started by analyzing wallets with higher number of trades but don't just skip the one's with a lower number of trades.
    

Before changing filters, it's good to understand what these metrics means. Keep reading the docs so you [understand them properly](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics)
.

[PreviousCurated Wallets](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/curated-wallets)
[NextUnderstanding the Metrics](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics)

Last updated 1 year ago

---

# Tokens Traded, Win Rate & Open Trades | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs.md)
.

These metrics help you understand the trader’s behavior and historical performance.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdDIcjZbwua-AQRLwrcRjtkDfVHG7DB_EefQN6q8ntAODlzTpxrDjp8Uq5jrum2e26SL8h91qWUFRMq0iPHSnQvWnSZX4Ws5Mfhxncv_ah94igGbZxNa_wDjq2XWB5fmQFp-16B_Q%3Fkey%3DXmKkwN575tuH_KlW_bGqh3x1&width=768&dpr=3&quality=100&sign=14c64513&sv=2)

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs#unique-tokens-traded)

Unique Tokens Traded

Shows how many different tokens the wallet has traded. A **higher number** often means a more diversified approach or a longer trading history, which is **good**. Be cautious if the number is too high in a short time — this could indicate _high-frequency trading,_ which is not ideal for copytrading as it’s hard to replicate.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs#winners-losses-win-rate)

Winners / Losses / Win Rate

Winners are trades with realized profit, and Losses are trades with realized losses. The Win Rate tells you what percentage of **closed trades** were profitable. This is a key metric to measure consistency, which is **important**. However, a **high win rate alone doesn’t guarantee profitability** — always analyze the full picture.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs#open-trades)

Open Trades

These are positions that haven’t been closed yet — meaning the tokens hasn't been sold. Be careful with wallets that have too many open trades: the realized performance might look good while hiding large unrealized losses. Zero or a low number of open trades is generally a **positive** sign.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs#token-holdings)

Token Holdings

Token Holdings represents the current value of all tokens that the wallet still holds and has not sold. These are unrealized positions, meaning the profit or loss from these tokens has not yet been captured.

This metric helps you assess how much of the wallet's performance is still **pending realization**. A wallet may appear profitable based on its holdings, but if those tokens significantly drop in value, the overall result can change dramatically.

Pay attention to wallets with a large value in Token Holdings compared to their realized PnL. It may suggest that their current performance is heavily dependent on tokens they haven't exited yet. For copytrading, it's often safer to prioritize wallets with strong **realized results** rather than those relying too much on unsold positions.

[PreviousUnderstanding the Metrics](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics)
[NextDistribution of Trades PnL in percentiles](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles)

Last updated 1 year ago

---

# Tips for setting up the execution bot | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-setting-up-the-execution-bot.md)
.

After choosing an execution bot, you have to configure how you want the copytrading operation to work.

When setting up the bot:

*   Always set a trading size in sol amounts (that makes sense for you). Don't use % relative to the trader (this could wipe your account buying much more than you expected)
    
*   Selling execution is **WAY MORE IMPORTANT** than buying when copytrading. If the bot you're using doesn't buy a token, that's ok - there will be more opportunities. But if the bot doesn't sell, you're screwed. You will likely have a large loss. **Keep that always in mind**.
    
*   Consider a low slippage when buying, 5 or 10% should be fine. If you're not buying anything, increase to 15%. Don't go over it unless you know what you're doing.
    
*   Buying fees should be normal, look at average trading fees of the wallets you're copying, and it should be ok.
    
*   When selling, consider using a high slippage, like 50%. You really don't want to lose the sell execution because your slippage was too low. 50% slippage doesn't mean that will be the slippage but rather the tolerance for it - most of the time it will hardly reach 10-20%.
    
*   When analyzing the wallet trading patterns, look at the tokens it usually trades. See how much liquidity there is. The more, the better (you'll be less affected by slippage).
    
*   On some [bots](https://t.me/TradeWiz_Solbot?start=r-26BH26XA23) you can set a minimum market cap and/or liquidity for the tokens you will buy - this a useful feature, especially if you're getting bigger losses compared to the wallet you're copying.
    
*   Selling fees could be higher than buying fees as well, so you're less likely to fail when selling.
    
*   If you are not trading big, you don't need any kind of MEV protection. This will only slow down your trading.
    

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Fimages.unsplash.com%2Fphoto-1521217155737-0d5632e9813f%3Fcrop%3Dentropy%26cs%3Dsrgb%26fm%3Djpg%26ixid%3DM3wxOTcwMjR8MHwxfHNlYXJjaHw5fHxzbG93fGVufDB8fHx8MTc0NTM2MTk3NXww%26ixlib%3Drb-4.0.3%26q%3D85&width=768&dpr=3&quality=100&sign=d5e30e48&sv=2)

MEV-enabled trader

*   Some bots offer Retries. This is a transaction retry, in case it fails. It's very good for selling transactions but not good for buying. When the wallet sells, you want to sell at all costs. But when the wallet buys, you only want to buy if you're getting in the position fast and at a similar price - retrying will make the buy timing/price worse.
    
*   If the bot has a retry for buying and a retry for selling, keep the buy retry at 0 and the sell retry 3 (or any other positive number)
    
*   If the bot just has a single retry entry, this will be retrying for buy and sell. Keep in mind how this affects your trading and do some tests to figure out your preference. Retry also slightly slows down you transaction speed.
    
*   **NEVER** buy unrenounced or unburned tokens. If you don't know what this means, don't worry. Just remember it. And ask us in the chat if you want to know.
    
*   You can set to follow the buys and sells of the wallet or define your own stop loss and take profit parameters.
    
*   If you're starting out and risk averse, perhaps setting a stop loss and/or take profit is a good option. Setting a 25% stop loss and let the wallet ride for profits itself is a good start.
    
*   An even better idea would be setting it up at a reasonable level according to [wallet trades percentiles](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles)
    . Think about the numbers you see. If the 50% percentile is 70% - setting this level of take profit will likely hit 50% of the time. Think statistically (if you're not really good at this, just ask for tips in the chat and we'll help you out).
    
*   Setting at 70% take profit for a wallet that has its 90th percentile at 50%, it won't likely hit often, do you get it?
    
*   Same goes for setting a stop loss if you want. But always be extra careful with the risk you're taking. Avoid losing too much. Be very conservative if you're new to it.
    

[PreviousTips for choosing a wallet](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-choosing-a-wallet)
[NextAdvanced Topics](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics)

Last updated 1 year ago

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics.md).

# Understanding the Metrics

We will explain how to analyze the metrics.&#x20;

\*\*This is a very important section!\*\*&#x20;

Please, ask us questions in the community group if you did not understand anything.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# OpenAPI | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/basics/openapi.md)
.

You can sync GitBook pages with an OpenAPI or Swagger file or a URL to include auto-generated API methods in your documentation.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/openapi#openapi-block)

OpenAPI block

GitBook's OpenAPI block is powered by [Scalar](https://scalar.com/)
, so you can test your APIs directly from your docs.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/openapi#post-pet)

Add a new pet to the store.

post

/api/v3/pet

Add a new pet to the store.

Required scopes

This endpoint requires the following scopes:

*   `write:pets`: modify pets in your account
*   `read:pets`: read your pets

Authorizations

petstore\_auth

petstore\_auth

OAuth2implicitRequired

Authorization URL: https://petstore3.swagger.io/oauth/authorize

Body

application/json

application/jsonapplication/xmlapplication/x-www-form-urlencoded

idinteger · int64OptionalExample: `10`

namestringRequiredExample: `doggie`

categoryobjectOptional

Show properties

photoUrlsstring\[\]Required

tagsobject\[\]Optional

Show properties

statusstring · enumOptional

pet status in the store

Possible values: `available``pending``sold`

Responses

200

Successful operation

application/json

application/jsonapplication/xml

idinteger · int64OptionalExample: `10`

namestringRequiredExample: `doggie`

categoryobjectOptional

Show properties

photoUrlsstring\[\]Required

tagsobject\[\]Optional

Show properties

statusstring · enumOptional

pet status in the store

Possible values: `available``pending``sold`

400

Invalid input

422

Validation exception

default

Unexpected error

post

/pet

HTTP

HTTPcURLJavaScriptPython

Copy

    POST /api/v3/pet HTTP/1.1
    Authorization: Bearer YOUR_OAUTH2_TOKEN
    Content-Type: application/json
    Accept: */*
    Content-Length: 133
    
    {
      "id": 10,
      "name": "doggie",
      "category": {
        "id": 1,
        "name": "Dogs"
      },
      "photoUrls": [\
        "text"\
      ],
      "tags": [\
        {\
          "id": 1,\
          "name": "text"\
        }\
      ],
      "status": "available"
    }

application/json

application/jsonapplication/xmlapplication/x-www-form-urlencoded

200

Successful operation

Copy

    {
      "id": 10,
      "name": "doggie",
      "category": {
        "id": 1,
        "name": "Dogs"
      },
      "photoUrls": [\
        "text"\
      ],
      "tags": [\
        {\
          "id": 1,\
          "name": "text"\
        }\
      ],
      "status": "available"
    }

application/json

---

# Welcome to dEdge | Docs

This site uses cookies to deliver its service and to analyze traffic. By browsing this site, you accept the [privacy policy](https://policies.gitbook.com/privacy/cookies)
.

AcceptReject

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary.md).

# PnL Summary

This block presents a quick overview of profitability and efficiency

<br>

<figure><img src="/files/wqAVXYZA70BZFmqPMm0W" alt=""><figcaption></figcaption></figure>

### Average PnL

The mean profit or loss per trade, expressed in SOL and percentage. This value reflects the average outcome of each closed trade, helping you gauge typical performance.\\ <br>

### Average Trading Size (A)

The average amount of SOL used per trade. This is useful for understanding the trader's risk appetite — higher values indicate larger trades on average.\\ <br>

### Sum of PnL (B)

The total realized profit (or loss) in SOL, summing up all closed trades. It shows the net result of the wallet over the analyzed period.\\ <br>

### PnL Ratio (B/A)

This ratio divides the Sum of PnL (B) by the Average Trade Size (A), expressed as a percentage.&#x20;

It measures how efficiently the wallet turns capital into profits.

A higher value here indicates that the wallet is generating strong returns relative to the size of its average trades.

\*In the example above:\*

His Avg. Trading Size is 0.73 SOL

The Sum of Pnl is 55 SOL

\*\*PnL Ratio is 7580% ! This mean he has made like 75x !\*\*&#x20;

Which is an awesome return. But remember this is just an indicator.&#x20;

This block is key to assess not just whether a wallet is profitable, but how effectively it uses capital to achieve that profit.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Distribution of Trades PnL in percentiles | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles.md)
.

> [](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles#the-real-edge-lies-in-knowing-quantitatively-how-the-wallet-performs-this-is-very-important-to-under)
> 
> The real edge lies in knowing quantitatively how the wallet performs - THIS IS VERY IMPORTANT TO UNDERSTAND
> 
> 
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FDcHcZ2jSmCwZmao5XZtv%252Fimage.png%3Falt%3Dmedia%26token%3D52614d00-77b4-4b1a-8f84-7a7ed3f1314b&width=768&dpr=3&quality=100&sign=4b03eca9&sv=2)

Percentiles provide a representation of the distribution of trade outcomes.

This metric shows how the wallet's trades are distributed in terms of profit and loss (PnL), using percentiles to reflect performance consistency. It shows both in Solana and in %.

The number in Sol is important so you understand how big he trades and the number in % is important because you can understand how far his trades generally goes.

If you don't know what percentiles are, we will explain it below. You can also watch this 2-minute video to learn how it works.

Each line indicates how a portion of the wallet’s trades performed, **helping you understand both upside potential and downside risk**:

*   **Min**: **The worst trade** in the analyzed period, showing the maximum realized loss. It was 0.37 SOL / -75% on that trade.
    
*   **10th Percentile**: 10% of trades performed worse (lower PnL) than this value. Useful to understand how bad the losing side gets. In the case above, 10% of his trades lost more than 0.15 SOL / -36%!
    
*   **25th Percentile**: 25% of trades performed worse than this value, while 75% performed better. Helps identify poor but not extreme outcomes. In the case above, 25% of his trades were worse than -6%.
    
*   **50th Percentile (Median)**: The midpoint of all trades. Half of the trades had a lower PnL, and half had a higher PnL. In the case above, 50% of his trades were more profitable than 10%. While the other half, made less than that.
    
*   **75th and 90th percentile**: Show how good the best trades are. As per the image above, 75th means 25% of his trades made more than 28% and 90th means that 10% of his trades made more than 63%!
    
*   **Max**: The best trade made by the wallet, he made 0.96 SOL or 135% as in the example.
    

**Always analyze percentiles** to see if the trader is **consistent**. The example above is ok.

But the example below is even more consistent, as his 10th and 25th percentiles are already positive.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2F2825569279-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FLaijJ82Fy5KFhyXS6leK%252Fuploads%252FMa47PIG2f8mNSrjD3hoW%252Fimage.png%3Falt%3Dmedia%26token%3Dd0fe4945-3e1f-4a92-9914-3e1532c69416&width=768&dpr=3&quality=100&sign=985fcdc6&sv=2)

And by his 50th percentile, you can expect that half the trades will make more than 26% and half the trades will make less than that.

[PreviousTokens Traded, Win Rate & Open Trades](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs)
[NextPnL Summary](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/pnl-summary)

Last updated 1 year ago

This site uses cookies to deliver its service and to analyze traffic. By browsing this site, you accept the [privacy policy](https://policies.gitbook.com/privacy/cookies)
.

AcceptReject

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-fees.md).

# Trading Fees

<figure><img src="/files/1jAMNO8TGo1rgdfQowV2" alt=""><figcaption></figcaption></figure>

### Total Spent on Fees

This is the total amount of SOL the wallet spent on fees when buying and selling tokens.

### Average Fee per Trade

This shows the average fee per transaction. It’s calculated by dividing the total fees by the number of trades.\\
This number is useful if you're copytrading. Some traders use high fees to get their transactions confirmed faster.&#x20;

If you're always behind or transaction failing too much, it might be because your fee is too low. In this case, compare the fee level of other wallets and use something similar or slightly higher.<br>

### Tip:

If the Average Fee per Trade of the wallet is too high compared to others, it's probably a high-frequency trader or sniper. Avoid it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-fees.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot.md).

# The execution bot

### In order to start copytrading properly, you need a good execution bot.&#x20;

Even if you have the best wallet, if you execution bot sucks, you will fail.

This means the bot you will use for copytrading must be good. We recommend using our partners, you will find them in the bot menu.&#x20;

And this is very important because the bot has 2 very important tasks:

\* The first is to monitor everything the Lead Wallet is doing at all times
\* The second is to send a buy/sell transaction after spotting a transaction made by the Lead wallet

For such tasks, the bots use RPCs (that's how they communicate with the blockchain) and there’s considerable differences between them, in terms of speed and reliability.&#x20;

Expect them to perform poorly sometimes, so the monitoring and transaction landing won't be nailed all the time.

Normally you can expect an execution bot to land a copytrade transaction in 1 to 5 seconds after the lead wallet.

Bad bots can take up to 30seconds or more sometimes.

<figure><img src="/files/mGsfXkVnZd25xr1oBpKn" alt=""><figcaption></figcaption></figure>

### Considering this, what should I do?

Pick wallets with a slower trading pace (\[higher deltas\](/dedge-docs/getting-started/understanding-the-metrics/trading-deltas.md)) and test execution bots!

With a good bot, consider that it takes 5 seconds to buy and 5 seconds to sell a token when copying another wallet.

Read more on \[Choosing a high delta wallet\](/dedge-docs/tutorials/basic-topics/high-delta-wallets.md) and \[Testing execution bots\](/dedge-docs/advanced-topics/testing-execution-bots.md).

### What happens if I blindly pick a wallet, set a high trading size and leave the bot executing the trades?

You will fail, 100% guaranteed. Sooner or later.

### Tips

Always read the bots documentations and see what their users are talking about in the chat. Read the support channels to see common problems. Don't blindly trust anyone.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/the-execution-bot.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/what-is-a-copytrading-system.md).

# What is a copytrading system?

\* It’s composed of a lead wallet (to be copied), your wallet (copytrader) and an execution bot (copytrade bot).
\* It’s a system in which a copytrader aims to copy a successful wallet in order to profit similarly. Most beginner traders think they just need a wallet with big profits and high win rate but actually they need more than that.
\* You need to test your copytrading system before trading with considerable size. You have to be confident about the execution bot and wallet you are going to follow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/what-is-a-copytrading-system.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Interactive blocks | Docs

For the complete documentation index, see [llms.txt](https://dedge-v2.gitbook.io/dedge-docs/llms.txt)
. This page is also available as [Markdown](https://dedge-v2.gitbook.io/dedge-docs/basics/interactive-blocks.md)
.

In addition to the default Markdown you can write, GitBook has a number of out-of-the-box interactive blocks you can use. You can find interactive blocks by pressing `/` from within the editor.

![](https://dedge-v2.gitbook.io/dedge-docs/~gitbook/image?url=https%3A%2F%2Fgitbookio.github.io%2Fonboarding-template-images%2Finteractive-hero.png&width=768&dpr=3&quality=100&sign=6718cf8c&sv=2)

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/interactive-blocks#tabs)

Tabs

First tab

Second tab

Each tab is like a mini page — it can contain multiple other blocks, of any type. So you can add code blocks, images, integration blocks and more to individual tabs in the same tab block.

Add images, embedded content, code blocks, and more.

Copy

    const handleFetchEvent = async (request, context) => {
        return new Response({message: "Hello World"});
    };

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/interactive-blocks#expandable-sections)

Expandable sections

Click me to expand[](https://dedge-v2.gitbook.io/dedge-docs/basics/interactive-blocks#click-me-to-expand)

Expandable blocks are helpful in condensing what could otherwise be a lengthy paragraph. They are also great in step-by-step guides and FAQs.

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/interactive-blocks#drawings)

Drawings

### 

[](https://dedge-v2.gitbook.io/dedge-docs/basics/interactive-blocks#embedded-content)

Embedded content

GitBook supports thousands of embedded websites out-of-the-box, simply by pasting their links. Feel free to check out which ones [are supported natively](https://iframely.com/).

This site uses cookies to deliver its service and to analyze traffic. By browsing this site, you accept the [privacy policy](https://policies.gitbook.com/privacy/cookies)
.

AcceptReject

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call.md).

# 1-to-1 Expert Call

#### Most traders lose money not because they lack effort — but because they lack direction.

You shouldn’t have to burn capital just to learn how copy trading works. That’s why we offer something no one else does: a \*\*personal consultation with a real expert\*\* - not support staff.\\
You’ll speak directly with a \*\*veteran of the financial markets\*\* with over 10 years of experience and a proven track record helping traders build strategies that actually work — in bull markets, bear markets, and everything in between.

\*\*\*

#### Here’s what you’ll get:

\* A \*\*strategic deep dive\*\* into your current copy trading approach
\* \*\*Tailored recommendations\*\* based on your goals, time, and capital
\* Clarity on \*\*which wallets to follow\*\* — and which ones to avoid
\* The understanding of how \*\*professionals copy trade\*\*
\* Actionable tips to \*\*minimize risk\*\* and avoid costly beginner traps
\* Full walkthrough on how to \*\*maximize your results\*\*

\*\*\*

#### How It Works:

\* You will find the directions to book it on the bot.  (type /start, then click More > How to Use > Book Expert Call)
\* Scheduled on demand, subject to availability

\*\*\*

#### Feedbacks

<figure><img src="/files/l2aEyMRT5JOdjIoTM3s0" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/qSHIYvGqqOvUF0jdpH7n" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/llNLvOfZ6skZpLvQvl4i" alt="" width="375"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/extras/1-to-1-expert-call.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics.md).

# Basic topics

Important points for those starting with Copy Trading.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/features.md).

# Features

Founded by a team with over \*\*35 years\*\* of combined expertise in \*\*technology\*\* and \*\*algorithmic trading\*\*, dEdge delivers top-tier analysis to its users through its cutting-edge technology.

Features overview:

\* A powerful algorithm that scans the blockchain 24/7 finding the best performing wallets&#x20;
\* Unprecedent level of depth in wallet analysis (the most reliable & quantitative approach in the market)
\* One-click delivery of wallets (\[Wallet Finder\](/dedge-docs/getting-started/quickstart/wallet-finder.md), \[Curated Wallets\](/dedge-docs/getting-started/quickstart/curated-wallets.md) and \[Filtered Wallets\](/dedge-docs/getting-started/quickstart/filtered-wallets.md))
\* \[Copytrade Analyzer\](/dedge-docs/copytrade-analyzer.md) to track how you're performing relative to the Lead Wallet (aka wallet you're copying)
\* The public community with dozens of professional copy traders
\* Alpha group in which there's close contact with founding team and a weekly delivery of a list with hundreds of wallets
\* \[1-to-1 Expert Calls\](/dedge-docs/extras/1-to-1-expert-call.md) with our seasoned copy trading expert that has helped hundreds of traders to perform in any market situation


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/features.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart.md).

# Starting the bot

After opening the bot, which can be found on this link - <https://t.me/dEdge\\\\\_solana\\\\\_bot?start=docs>

You can type /start and you will see this screen:

<br>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD\_4nXcRxtkDGYgtTf0NIuvUX0luC9K-0nth-2eGfH41f1qt3cWV8bIxQlqn6Ec\_bMQYrFbbteyizQvrhsWcHhir4tm2ypM1TDBQVYPrW3dDZ4mSfrEFHJ-8Lu6DJStChAxVIJIq6QLx?key=XmKkwN575tuH\_KlW\_bGqh3x1" alt=""><figcaption></figcaption></figure>

If this your first time using dEdge, click \*\*Wallet Finder\*\* or just \*\*paste a wallet and press enter\*\*. These are \*\*free\*\* to use.&#x20;

Curated Wallets and Filtered wallets are premium features.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics.md).

# Advanced Topics

If you are still here, congratulations! This is the ONLY way of making it happen in copytrading!

Keep reading the docs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/advanced-topics.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/basics/editor.md).

# Editor

GitBook has a powerful block-based editor that allows you to seamlessly create, update, and enhance your content.

<figure><img src="https://gitbookio.github.io/onboarding-template-images/editor-hero.png" alt=""><figcaption></figcaption></figure>

### Writing content

GitBook offers a range of block types for you to add to your content inline — from simple text and tables, to code blocks and more. These elements will make your pages more useful to readers, and offer extra information and context.

Either start typing below, or press \`/\` to see a list of the blocks you can insert into your page.

### Add a new block

{% stepper %}
{% step %}

### Open the insert block menu

Press \`/\` on your keyboard to open the insert block menu.
{% endstep %}

{% step %}

### Search for the block you need&#x20;

Try searching for “Stepper”, for exampe, to insert the stepper block.
{% endstep %}

{% step %}

### Insert and edit your block

Click or press Enter to insert your block. From here, you’ll be able to edit it as needed.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/basics/editor.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets.md).

# High delta wallets

As we just read on \[The execution bot\](/dedge-docs/tutorials/basic-topics/the-execution-bot.md), we got to find a wallet that will perform even if the execution bot doesn't perform at its best.&#x20;

Wallets that have a slower trading pace (\[higher trading deltas\](/dedge-docs/getting-started/understanding-the-metrics/trading-deltas.md)) will perform better because they are less dependent on very short-term price changes/volatility.&#x20;

On average, with a good bot, consider that it takes 5 seconds to buy and 5 seconds to sell a token when copying another wallet.

#### Example 1:

If the wallet 10th Delta Percentile is 600, this means 90% of his trades will last longer than 600 seconds or 10 minutes. This trader edge isn't profiting from a very fast gain, that depends on liquidity or short-term volatility.&#x20;

This makes him a good target for copying, if everything else in terms of profitability makes sense.

The price I'm buying and selling the token will hardly be much worse than his. Maybe a 5% difference? \\
If on average he's aiming for 50% on a trade and I make 40% by copying him, this is fine.&#x20;

#### Example 2:

If the wallet 50th Delta Percentile is 100, this means half of his trades takes less than 100 seconds.&#x20;

This guy definitely has an edge by trading fast. If my bot delays 5 seconds to buy, I could get a price 100% more expensive than his. Or even more than that. And same goes for the selling, 5 seconds could have a huge impact.&#x20;

So, rule of thumb: Don't copy traders who have fast trading pace / lower trading deltas. It won't work.

#### Example 3:

<figure><img src="/files/IqJxIlDC4fDRJ8yLgjHT" alt=""><figcaption></figcaption></figure>

This trader has mixed deltas. Some are high, others are low.

25th Percentile tells it all: 25% of the time he will be trading in less than 84 seconds. This means, 25% of the time you will probably lose money. This is not a good start, is it?

\*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/high-delta-wallets.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/copytrade-analyzer.md).

# Copytrade Analyzer

This an advanced tool for analyzing your copytrading performance.

It's in final steps of construction.

If you want to try it, just type /tracing followed by the wallet you're following (the lead wallet) separated by comma from your wallet (copier wallet) like the example below /tracing leadWallet,copierWallet

it will look like this:

/tracing D37KwuoeLJJqVkD9EPaLD4zfwAZdp7WnH6BoJ5BPJ8rb,58FnazdGmCKZPeiMJ2rzujkeUR1HURr9cJNvVPxechKt

And you will receive a prelaminar report of the effectiveness of you wallet compared to the lead wallet.

If you are having a hard time, reach us on the community group so we can show how it works for you.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/copytrade-analyzer.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts.md).

# Avoiding Snipers & HFT's

As we just saw, avoiding "speedy" traders is very important because trading bots won't be able to copy them.

High-frequency traders are easy to spot. The buy and sell in a couple seconds. They will have very low trading deltas.&#x20;

But what about snipers? They can spend a lot on fees to buy the token and are the first ones to buy it. Trading bots won't be able to copy their performance because they enter too early in the trade. But sometimes they don't sell as early, making it harder to spot them.

If you are unsure if the trader is a sniper, just follow the steps below:

1. Insert the wallet on dEdge bot&#x20;

<figure><img src="/files/T6qjQwQyfIuDCOqd4LFp" alt=""><figcaption></figcaption></figure>

2. After receiving the summary, click on Last 5 Trades

<figure><img src="/files/drzZKqVggXqEGkktwORP" alt=""><figcaption></figcaption></figure>

3. You will see a list with DexScreener links, click them to see that trading behavior plotted

<figure><img src="/files/P7na30XFrPuYvZziU5TO" alt=""><figcaption></figcaption></figure>

4. It will open up a chart with his Buy and Sells on it

<figure><img src="/files/Ah4Gdc1NrPLmFRCyRKbb" alt=""><figcaption></figcaption></figure>

5. This is a 1-second candle chart. Snipers will buy tokens on the first minute, which is represented in the red circle. Avoid copying wallets that buy in the first minute of token launch.&#x20;
6. The example above is ok. The wallet bought after 4 minutes from the launch and sold 2 minutes after that. &#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-research-phase.md).

# The research phase

### The research phase:

1. The easy way: Get wallets from dEdge - Wallet Finder, Curated Wallets, Filtered Wallets and the Weekly List
2. The hard way: Get Top Traders wallets from DexScreener and scan them with dEdge
3. Be careful with other tools you find out there (most of the data isn't reliable and/or isn't enough to assess if the wallet is good for copy trading)
4. Look for reliable wallets. With at least a couple trades to prove they've been doing good.
5. Avoid wallets that made huge profits in a small percent of his trades - this likely \*\*won't happen again\*\*
6. You want wallets that gains with consistency&#x20;
7. Normally a higher win rate with smaller wins or a lower win rate with some bigger wins - but nothing exaggerated
8. Avoid low \[trading delta\](/dedge-docs/getting-started/understanding-the-metrics/trading-deltas.md) wallets (high frequency traders)
9. Most of the wallets for copy trading won't look perfect - \*\*they will look just good and that's enough\*\*
10. See the wallet last trades to see graphically how they trade (there's a guide to it on \[Avoiding Snipers & HFT\](/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts.md) section)
11. \*\*Don't be too picky\*\*. But be confident about what to not tolerate. Don't lower your standards to increase trading frequency. Opportunities will always arise, but lost money is hard to recover.
12. Most of the time you are \*\*looking for red flags\*\* to exclude the wallet. If you can't find any, it might be good to copy.
13. With some experience in your operation, you will spot red flags faster.
14. Create a to-do list when analyzing wallets. Add steps to it as you learn.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-research-phase.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/api/wallet-batch-api.md).

# Wallet Batch API

#### To access the API documentation, click the link below

{% embed url="<https://dedge-1.gitbook.io/dedge-sol-analyzer/api-documentation/readme/wallet-batch-api>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/api/wallet-batch-api.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-wallet-testing-phase.md).

# The wallet testing phase

1. After finding some good candidates, we will start testing them.&#x20;
2. You should add from \*\*0 to 2 wallets per day\*\* in your operation. No more than that.&#x20;
3. If you are new or don't have time, don't copy more than 2-3 wallets at once.&#x20;
4. \*\*You are not trying to profit at this stage\*\* but rather discover if the wallets you selected are good for copytrading.&#x20;
5. The \*\*betting size should be minimal\*\*. Do it with something like 0.01 or 0.001 SOL.
6. Keep trading fees at the right level. Doesn't mind if the trading fees are eating up more than trading size at this stage. This is a learning phase. \*\*It's better to lose small here than have an expensive learning\*\* by copying the wrong wallet with a considerable size.
7. Insert the wallets you're using on Ray (<https://t.me/ray\_azure\_bot?start=ref\_Auq2Cy>), so it will notify when they trade. This way you watch closely how they're performing.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-wallet-testing-phase.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/building-a-profitable-operation.md).

# Building a profitable operation

After you are confident about \*\*the power of dEdge quantitative\*\* \[\*\*metrics\*\* \](/dedge-docs/getting-started/understanding-the-metrics.md)and setting up the \[execution bot\](/dedge-docs/tutorials/basic-topics/the-execution-bot.md), it's time to optimize the operation.

This is a very basic roadmap to follow. We strongly recommend you taking the \[1-to-1 Expert Call\](/dedge-docs/extras/1-to-1-expert-call.md), if you are serious about it.

1. It all starts with the \[research phase\](/dedge-docs/advanced-topics/the-research-phase.md). Finding wallets to copy.
2. Then, you will test those wallets to see if they're good for copytrading. You won't try to profit here, just learn if the wallet is good. This the\[ wallet testing phase\](/dedge-docs/advanced-topics/the-wallet-testing-phase.md).
3. After you found some wallets that are working well, we proceed to the\[ scale up phase\](/dedge-docs/advanced-topics/the-scale-up-phase.md) - in which we will start increasing the trading size.
4. A\[ healthy operation\](/dedge-docs/advanced-topics/the-profitable-operation.md) consists in having multiple profitable wallets working for you rather than just one or two. This is definitely what going to make you successful in the long run.

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/building-a-profitable-operation.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/wallet-finder.md).

# Wallet Finder

<figure><img src="/files/zWdf2qOHw287nBoX16om" alt=""><figcaption></figcaption></figure>

The Wallet Finder can be used by Free users.&#x20;

It's just the tip of the iceberg in terms of good & profitables wallets we have.&#x20;

Just click on the button and you will get a wallet.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/wallet-finder.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-scale-up-phase.md).

# The scale up phase

1. At least once per day, check all trades. Monitor them on Ray. See how each wallet is performing.  Also keeping it on a spreadsheet will help.
2. Some wallets will perform bad. Some will do good.&#x20;
3. If they're not doing as expected, we got to remove them. But first, \*\*wait at least 3-4 trades\*\* before excluding a wallet from the testing phase. Try to discover why they did not work. This is \*\*very important\*\*.
4. For the wallets doing good, wait at least 3-4 trades before \*\*increasing\*\* the trading size.&#x20;
5. Analyze their trades on DexScreener. See how this wallet trades. The tokens it trades. When you find similar wallets on the research, you will know it's a good candidate.&#x20;
6. By using the \[Copytrade Analyzer\](/dedge-docs/copytrade-analyzer.md) you will be able to know how well you're doing relative to the wallet you're copying (Lead wallet).
7. It is normal to perform worse than the copied wallet. What we are looking for here is to be \*\*profitable\*\*. Don't expect to have the same results as the wallet you are copying.&#x20;
8. If you are seeing consistent results from a wallet, increase the betting size. Doesn't need to be a lot. Just something reasonable and wait a few trades to see how it performs. If it's still performing well, you can increase even more. \*\*Always analyze the trades before increasing the size.\*\*

### A very important point here: scaling up 5 wallets to 0.5 SOL trading size is \*\*100x BETTER & SMARTER\*\* than scaling up 1 wallet to 2.5 SOL trading size.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-scale-up-phase.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/basics/images-and-media.md).

# Images & media

GitBook allows you to add images and media easily to your docs. Simply drag a file into the editor, or use the file manager in the upper right corner to upload multiple images at once.

<figure><img src="https://gitbookio.github.io/onboarding-template-images/images-hero.png" alt=""><figcaption><p>Add alt text and captions to your images</p></figcaption></figure>

{% hint style="info" %}
You can also add images simply by copying and pasting them directly into the editor — and GitBook will automatically add it to your file manager.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/basics/images-and-media.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-choosing-a-wallet.md).

# Tips for choosing a wallet

This is just the beginning. The more you analyze wallets and copytrade, you'll get more experienced and better at this. But just to start out, when choosing a wallet:

\* Make sure you understand what \[Trade Percentiles\](/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles.md) are.
\* Win rate is important but how big the losses are is even more important. If one wallet 10th percentile is -50% while the other is -5%, the second is \*\*MUCH\*\* better.&#x20;
\* Be careful with too many \[open trades\](/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs.md)
\* If his Best Trade is a high % amount of his Sum of Pnl (more than 70-80%, be careful - his profits might be just a lucky shot)
\* Prefer \[high delta wallets\](/dedge-docs/tutorials/basic-topics/high-delta-wallets.md)
\* Always check the wallet trading patterns on \[DexScreener\](https://dexscreener.com/) (you can find the direct link as mentioned on \[Avoiding Snipers & HFT's\](/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts.md)) - imagine your bot will enter a few seconds/candles after the wallet. Would it still be profitable? Also, does the price falls hard after he sells? Or does price increase considerable seconds after he buys? (this could be an indicator that he's being heavily copytraded)
\* Read \[The research phase\](/dedge-docs/advanced-topics/the-research-phase.md) for more insights on choosing wallets.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-choosing-a-wallet.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Basic topics | Docs

This site uses cookies to deliver its service and to analyze traffic. By browsing this site, you accept the [privacy policy](https://policies.gitbook.com/privacy/cookies)
.

AcceptReject

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/sol-spent-received-and-net-sol.md).

# SOL Spent, Received and Net SOL

This section breaks down the wallet’s activity in terms of total SOL spent and received trading tokens. \\
It does not matter if the trade is fully closed or still open.

<figure><img src="/files/ilbmf9T8QdllU0og8X5h" alt=""><figcaption></figcaption></figure>

### SOL Spent Buying Tokens (C)

The total amount of SOL used to buy tokens. This represents the capital invested across all trades.

### SOL Received Selling Tokens (D)

The total amount of SOL the wallet received when selling tokens. This shows the accumulated return from all positions.

### Net SOL (D - C)

The difference between the total received and the total spent. If this number is positive, it means the wallet has a net profit in SOL.

\\
This metric is useful for verifying actual profitability in SOL and is one of the most straightforward indicators of a trader’s success over time.

\*Usage example:\*

<figure><img src="/files/vXdqZqTihorxUvhCxkoR" alt=""><figcaption></figcaption></figure>

In the example above, Sum of PnL is 26 and Net SOL is almost 25. This means 1 SOL (the difference) is missing in open trades - which can still have value as token or not. Or might just be an \*\*unrealized loss\*\*.&#x20;

For a 25 SOL profit, 1 SOL missing is relatively ok. But look at the example below:

<figure><img src="/files/ve8rpTA76Fv8qhXWzUlr" alt=""><figcaption></figcaption></figure>

In this case, Sum of Pnl is 8.4 and Net Sol is 4.8 - the difference here is almost 4 SOL, which is relatively much bigger when compared to the PnL. Indicating he may have a considerable unrealized loss.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/sol-spent-received-and-net-sol.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/curated-wallets.md).

# Curated Wallets

<figure><img src="/files/DBVgU4xn0sSsNhdmbr0n" alt=""><figcaption></figcaption></figure>

Curated Wallets are special wallets.&#x20;

This is where you will find the top 1% of wallets/traders.&#x20;

The odds of being profitable copying one of these are highly increased when compared to Wallet Finder.

This is a premium feature.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/curated-wallets.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas.md).

# Trading Deltas

Trading Deltas tells the story about how fast the wallet trades.

\*If you don't know what percentiles are, head to the section of\* \[\*Distribtuion of Trades PnL in Percentiles\*\](/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles.md) \*as it is explained there. If you still didn't understand, ask us on the community group.\*

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD\_4nXc1FwDLQlSNFXWV2Sr-wubvRpHGfUpVS7XSyiqmmjvjgtZC0akhdAzJNKvLIUlTcn-SxaN9ULvAGgoe\_jmM0\_z3Bfvxfz3cPkn0UplegPN\_yb6s8LhqKpqcbHnMaDxOp88bPJE9hg?key=XmKkwN575tuH\_KlW\_bGqh3x1" alt=""><figcaption></figcaption></figure>

The distribution of Deltas shows how fast the trader open and close his trades.

In the example above, his fastest trade took only 30 seconds. The lengthiest trade took 153 minutes. If you sum all the trading times and divide by the number of trades, it will be 19.7 minutes - but this isn't a good metric because it can be skewed.&#x20;

Imagine if there was a single trade that took 6 months, the average trading time then would be many days. But all the other trades were much faster. Does it make sense?&#x20;

That's why percentiles are SO important, because it shows the distribution of all trades, lined up in the best way possible for us to comprehend without having to analyze each trade individually.

\* \*\*The 10th Percentile\*\*: in the example above, it means 10% of his trades took less than 148 seconds. If he traded 20 times, only 2 trades took less than this time.
\* \*\*The 25th Percentile\*\*: Again, if he traded 20 times, only 5 of his trades were less than 298 seconds.
\* \*\*50th Percentile\*\*: Half of his trades took less than 596 second and half took more than that.

### What to look for here?

Generally speaking, execution bots will fail if the wallet trades too fast. The most important factors here are the 10th, 25th and 50th percentiles. You need to make sure that most of his trades takes at least a couple minutes, so it's not a high frequency trader and the bot will be able to copy properly.

We recommend the 10th percentile to be above 120-200 at least.&#x20;

Another thing to avoid here are: Snipers! - read the section \[Avoiding Snipers & HFTs\](/dedge-docs/tutorials/basic-topics/avoiding-snipers-and-hfts.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/trading-deltas.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# 1-to-1 Expert Call | Docs

This site uses cookies to deliver its service and to analyze traffic. By browsing this site, you accept the [privacy policy](https://policies.gitbook.com/privacy/cookies)
.

AcceptReject

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/analyze-wallet.md).

# Analyze Wallet

To start analyzing a wallet, just paste it and press enter.&#x20;

Waiting time is normally from 5 to 30 seconds, depending on how many transactions the wallet has.&#x20;

You'll receive a wallet summary similar to this one below, which we will explain all the details in this guide.

<figure><img src="/files/qIMtFSfaZg2zWGBokXNm" alt=""><figcaption></figcaption></figure>

This is free to use, up to a limit.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/analyze-wallet.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/basics/integrations.md).

# Integrations

GitBook integrations allow you to connect your GitBook spaces to some of your favorite platforms and services. You can install integrations into your GitBook page from the \*Integrations\* menu in the top left.

<figure><img src="https://gitbookio.github.io/onboarding-template-images/integrations-hero.png" alt=""><figcaption></figcaption></figure>

### Types of integrations

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>Analytics</strong></td><td>Track analytics from your docs</td><td><a href="https://www.gitbook.com/integrations#analytics">https://www.gitbook.com/integrations#analytics</a></td><td></td><td></td></tr><tr><td><strong>Support</strong></td><td>Add support widgets to your docs</td><td><a href="https://www.gitbook.com/integrations#support">https://www.gitbook.com/integrations#support</a></td><td></td><td></td></tr><tr><td><strong>Interactive</strong></td><td>Add extra functionality to your docs</td><td><a href="https://www.gitbook.com/integrations#interactive">https://www.gitbook.com/integrations#interactive</a></td><td></td><td></td></tr><tr><td><strong>Visitor Authentication</strong></td><td>Protect your docs and require sign-in</td><td><a href="https://www.gitbook.com/integrations#visitor-authentication">https://www.gitbook.com/integrations#visitor-authentication</a></td><td></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/basics/integrations.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/testing-execution-bots.md).

# Testing execution bots

Unless you're recommend by someone you trust which bot to use, we recommend you test them. Read the bot documentation then proceed with the test below.

#### This an introductory example of how to test a bot. Chat with us on the community if you want to dig deeper.

1. Pick a wallet to copy
2. Pick at least 2 bots you want to test (so you can compare them, at least)
3. Set that wallet to be copied on the bots you are testing
4. Make sure you are using same amount of fees and a very small trading size, this is just for test purpose, you are not trying to make money but rather avoiding to lose it in the future
5. After each trade, verify how long it took for them to buy and sell

#### How to verify how long it took to replicate?

Easy. You need to see in which block the transaction landed.

1. Go to solscan.io
2. Insert the wallet
3. Click on Balance Changes

<figure><img src="/files/RV4BcmzhS3s7vljpeaYx" alt=""><figcaption></figcaption></figure>

&#x20;4\\. In the picture, the line below is the buy transaction (amount in green) and the line above it is the sell transaction.

5. The block numbers 333276164 and 333276285 are when the token was Bought and Sold.&#x20;
6. Compare the difference between blocks for the wallet being copied and the wallets from the bots you are testing. Each block in Solana is around 400miliseconds.
7. Do this from time to time to make sure the bot you are using isn't leaving you behind.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/testing-execution-bots.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/filtered-wallets.md).

# Filtered Wallets

<figure><img src="/files/naocIvzt9GSN4hcWt9dQ" alt=""><figcaption></figcaption></figure>

If you want to set your own filters, this is the right tool for you.&#x20;

After clicking the button, you will get a wallet with standard filters.

On the bottom, you will see these buttons:

<figure><img src="/files/FKux6HXWMf91dedoF4mw" alt=""><figcaption></figcaption></figure>

You can adjust the filters by click on \*\*Adjust Filters.\*\*

You will see the menu below:

<figure><img src="/files/qnz100vHSpQ7Io2rlpSV" alt=""><figcaption></figcaption></figure>

You will see the standard values for filtered wallets.

By using the shown commands, you are able to define the filters the way you like.

The \[50th Percentile Delta\](/dedge-docs/getting-started/understanding-the-metrics/trading-deltas.md) is too low for copytrading. Let's change it to 200.

Just type /set\\\_50th\\\_delta 200

<figure><img src="/files/JTHU1BgzG08LbgwOZ9NI" alt=""><figcaption></figcaption></figure>

And now it is 200 seconds, much better.

We also recommend increasing \[Closed Trades\](/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs.md) to at least 15. And you could also increase win rate to 60%.&#x20;

Bear in mind there is no right filters - it's just a matter of trying different numbers out and seeing if you're getting good wallets.&#x20;

### \*\*General tips for filtering\*\*

\* If \[win rate\](/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs.md) is too high, like 90%+ you will likely get a lot of bots that can't be copied.
\* If \[50th Percentile Delta\](/dedge-docs/getting-started/understanding-the-metrics/trading-deltas.md) is too low, your execution bot won't be able to copy it properly. Leave it at least on 200 and you can try higher numbers like 500 or 1000 as well to find slower paced traders.
\* The more trades the wallet has, the more you can be confident of its results. The performance of a wallet with 30 trades is more reliable than a wallet with 5 trades. But there is a trade-off here: it's very common for professionals to change wallets often, so this guys wont have wallets with a lot of trades. Started by analyzing wallets with higher number of trades but don't just skip the one's with a lower number of trades.

Before changing filters, it's good to understand what these metrics means. Keep reading the docs so you \[understand them properly\](/dedge-docs/getting-started/understanding-the-metrics.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/quickstart/filtered-wallets.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-profitable-operation.md).

# The profitable operation

After working daily on research, testing and scaling up, you should have a few profitable wallets at least.&#x20;

&#x20;\*\*Congratulations! You're building a portfolio of wallets!\*\*

<figure><img src="/files/SOjTJthxIj7eSfZX349h" alt=""><figcaption></figcaption></figure>

#### It's good you're seeing a well-deserved success but there are some important points:

1. Your goal is not to become rich overnight. Trading too big is too risky and won't work in the long run.
2. Focus on researching, testing and scaling, do it daily. Keep adding new wallets. Analyzing them. Figuring out a method that works for you.
3. They right way to go is by increasing the number of profitable wallets you run.&#x20;
4. For most of the wallets, the performance will be ok to good. With some negative results sometimes. You should set a maximum trading size. Don't risk too much. Focus on adding more wallets.
5. On rare occasions, you will find a very special wallet. After 10 trades it's performing super. You will be tempted to trade BIG on this one. And you probably should. But set a maximum risk parameter. Be careful. And good luck!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/advanced-topics/the-profitable-operation.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs.md).

# Tokens Traded, Win Rate & Open Trades

These metrics help you understand the trader’s behavior and historical performance.

<br>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD\_4nXdDIcjZbwua-AQRLwrcRjtkDfVHG7DB\_EefQN6q8ntAODlzTpxrDjp8Uq5jrum2e26SL8h91qWUFRMq0iPHSnQvWnSZX4Ws5Mfhxncv\_ah94igGbZxNa\_wDjq2XWB5fmQFp-16B\_Q?key=XmKkwN575tuH\_KlW\_bGqh3x1" alt=""><figcaption></figcaption></figure>

### Unique Tokens Traded

Shows how many different tokens the wallet has traded. A \*\*higher number\*\* often means a more diversified approach or a longer trading history, which is \*\*good\*\*.
\\
Be cautious if the number is too high in a short time — this could indicate \*high-frequency trading,\* which is not ideal for copytrading as it’s hard to replicate.

### Winners / Losses / Win Rate

Winners are trades with realized profit, and Losses are trades with realized losses.\\
The Win Rate tells you what percentage of \*\*closed trades\*\* were profitable.\\
This is a key metric to measure consistency, which is \*\*important\*\*.\\
However, a \*\*high win rate alone doesn’t guarantee profitability\*\* — always analyze the full picture.<br>

### Open Trades

These are positions that haven’t been closed yet — meaning the tokens hasn't been sold. \\
Be careful with wallets that have too many open trades: the realized performance might look good while hiding large unrealized losses.\\
Zero or a low number of open trades is generally a \*\*positive\*\* sign.

### Token Holdings

Token Holdings represents the current value of all tokens that the wallet still holds and has not sold. These are unrealized positions, meaning the profit or loss from these tokens has not yet been captured.

This metric helps you assess how much of the wallet's performance is still \*\*pending realization\*\*. A wallet may appear profitable based on its holdings, but if those tokens significantly drop in value, the overall result can change dramatically.

Pay attention to wallets with a large value in Token Holdings compared to their realized PnL. It may suggest that their current performance is heavily dependent on tokens they haven't exited yet. For copytrading, it's often safer to prioritize wallets with strong \*\*realized results\*\* rather than those relying too much on unsold positions.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/publish-your-docs.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/basics/markdown.md).

# Markdown

GitBook supports many different types of content, and is backed by Markdown — meaning you can copy and paste any existing Markdown files directly into the editor!

<figure><img src="https://gitbookio.github.io/onboarding-template-images/markdown-hero.png" alt=""><figcaption></figcaption></figure>

Feel free to test it out and copy the Markdown below by hovering over the code block in the upper right, and pasting into a new line underneath.

\`\`\`markdown
# Heading

This is some paragraph text, with a \[link\](https://docs.gitbook.com) to our docs. 

## Heading 2
- Point 1
- Point 2
- Point 3
\`\`\`

{% hint style="info" %}
If you have multiple files, GitBook makes it easy to import full repositories too — allowing you to keep your GitBook content in sync.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/basics/markdown.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-setting-up-the-execution-bot.md).

# Tips for setting up the execution bot

After choosing an execution bot, you have to configure how you want the copytrading operation to work.

When setting up the bot:

\* Always set a trading size in sol amounts (that makes sense for you). Don't use % relative to the trader (this could wipe your account buying much more than you expected)
\* Selling execution is \*\*WAY MORE IMPORTANT\*\* than buying when copytrading. If the bot you're using doesn't buy a token, that's ok - there will be more opportunities. But if the bot doesn't sell, you're screwed. You will likely have a large loss. \*\*Keep that always in mind\*\*.
\* Consider a low slippage when buying, 5 or 10% should be fine. If you're not buying anything, increase to 15%. Don't go over it unless you know what you're doing.
\* Buying fees should be normal, look at average trading fees of the wallets you're copying, and it should be ok.
\* When selling, consider using a high slippage, like 50%. You really don't want to lose the sell execution because your slippage was too low. 50% slippage doesn't mean that will be the slippage but rather the tolerance for it - most of the time it will hardly reach 10-20%.&#x20;
\* When analyzing the wallet trading patterns, look at the tokens it usually trades. See how much liquidity there is. The more, the better (you'll be less affected by slippage).
\* On some \[bots \](https://t.me/TradeWiz\_Solbot?start=r-26BH26XA23)you can set a minimum market cap and/or liquidity for the tokens you will buy - this a useful feature, especially if you're getting bigger losses compared to the wallet you're copying.
\* Selling fees could be higher than buying fees as well, so you're less likely to fail when selling.
\* If you are not trading big, you don't need any kind of MEV protection. This will only slow down your trading.

<figure><img src="https://images.unsplash.com/photo-1521217155737-0d5632e9813f?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHw5fHxzbG93fGVufDB8fHx8MTc0NTM2MTk3NXww&#x26;ixlib=rb-4.0.3&#x26;q=85" alt=""><figcaption><p>MEV-enabled trader</p></figcaption></figure>

\* Some bots offer Retries. This is a transaction retry, in case it fails. It's very good for selling transactions but not good for buying. When the wallet sells, you want to sell at all costs. But when the wallet buys, you only want to buy if you're getting in the position fast and at a similar price - retrying will make the buy timing/price worse.
\* If the bot has a retry for buying and a retry for selling, keep the buy retry at 0 and the sell retry 3 (or any other positive number)
\* If the bot just has a single retry entry, this will be retrying for buy and sell. Keep in mind how this affects your trading and do some tests to figure out your preference. Retry also slightly slows down you transaction speed.
\* \*\*NEVER\*\* buy unrenounced or unburned tokens. If you don't know what this means, don't worry. Just remember it. And ask us in the chat if you want to know.
\* You can set to follow the buys and sells of the wallet or define your own stop loss and take profit parameters.
\* If you're starting out and risk averse, perhaps setting a stop loss and/or take profit is a good option. Setting a 25% stop loss and let the wallet ride for profits itself is a good start.
\* An even better idea would be setting it up at a reasonable level according to \[wallet trades percentiles\](/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles.md). Think about the numbers you see. If the 50% percentile is 70% - setting this level of take profit will likely hit 50% of the time. Think statistically (if you're not really good at this, just ask for tips in the chat and we'll help you out).&#x20;
\* Setting at 70% take profit for a wallet that has its 90th percentile at 50%, it won't likely hit often, do you get it?&#x20;
\* Same goes for setting a stop loss if you want. But always be extra careful with the risk you're taking. Avoid losing too much. Be very conservative if you're new to it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/tutorials/basic-topics/tips-for-setting-up-the-execution-bot.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Wallet Batch API | Docs

This site uses cookies to deliver its service and to analyze traffic. By browsing this site, you accept the [privacy policy](https://policies.gitbook.com/privacy/cookies)
.

AcceptReject

---

# Editor | Docs

This site uses cookies to deliver its service and to analyze traffic. By browsing this site, you accept the [privacy policy](https://policies.gitbook.com/privacy/cookies)
.

AcceptReject

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/basics/openapi.md).

# OpenAPI

You can sync GitBook pages with an OpenAPI or Swagger file or a URL to include auto-generated API methods in your documentation.

### OpenAPI block

GitBook's OpenAPI block is powered by \[Scalar\](https://scalar.com/), so you can test your APIs directly from your docs.

{% openapi src="<https://petstore3.swagger.io/api/v3/openapi.json>" path="/pet" method="post" %}
<https://petstore3.swagger.io/api/v3/openapi.json>
{% endopenapi %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/basics/openapi.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles.md).

# Distribution of Trades PnL in percentiles

> ## The real edge lies in knowing quantitatively how the wallet performs - THIS IS VERY IMPORTANT TO UNDERSTAND

<figure><img src="/files/2cgodNGLNLf0mQL3hOHy" alt=""><figcaption><p>Percentiles provide a representation of the distribution of trade outcomes.</p></figcaption></figure>

This metric shows how the wallet's trades are distributed in terms of profit and loss (PnL), using percentiles to reflect performance consistency. It shows both in Solana and in %.&#x20;

The number in Sol is important so you understand how big he trades and the number in % is important because you can understand how far his trades generally goes.&#x20;

If you don't know what percentiles are, we will explain it below. You can also watch this 2-minute video to learn how it works.

{% embed url="<https://www.youtube.com/watch?v=s6cMpDEzq\_4>" %}

Each line indicates how a portion of the wallet’s trades performed, \*\*helping you understand both upside potential and downside risk\*\*:

\* \*\*Min\*\*: \*\*The worst trade\*\* in the analyzed period, showing the maximum realized loss. It was 0.37 SOL / -75% on that trade.
\* \*\*10th Percentile\*\*: 10% of trades performed worse (lower PnL) than this value. Useful to understand how bad the losing side gets. In the case above, 10% of his trades lost more than 0.15 SOL / -36%!
\* \*\*25th Percentile\*\*: 25% of trades performed worse than this value, while 75% performed better. Helps identify poor but not extreme outcomes. In the case above, 25% of his trades were worse than -6%.
\* \*\*50th Percentile (Median)\*\*: The midpoint of all trades. Half of the trades had a lower PnL, and half had a higher PnL. In the case above, 50% of his trades were more profitable than 10%. While the other half, made less than that.&#x20;
\* \*\*75th and 90th percentile\*\*: Show how good the best trades are. As per the image above, 75th means 25% of his trades made more than 28% and 90th means that 10% of his trades made more than 63%!
\* \*\*Max\*\*: The best trade made by the wallet, he made 0.96 SOL or 135% as in the example.

\*\*Always analyze percentiles\*\* to see if the trader is \*\*consistent\*\*. The example above is ok.&#x20;

But the example below is even more consistent, as his 10th and 25th percentiles are already positive.

<figure><img src="/files/Rd1QBGfkSa04I2AQZJzW" alt=""><figcaption></figcaption></figure>

And by his 50th percentile, you can expect that half the trades will make more than 26% and half the trades will make less than that. <br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/getting-started/understanding-the-metrics/distribution-of-trades-pnl-in-percentiles.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---

# Unknown

\> For the complete documentation index, see \[llms.txt\](https://dedge-v2.gitbook.io/dedge-docs/llms.txt). Markdown versions of documentation pages are available by appending \`.md\` to page URLs; this page is available as \[Markdown\](https://dedge-v2.gitbook.io/dedge-docs/basics/interactive-blocks.md).

# Interactive blocks

In addition to the default Markdown you can write, GitBook has a number of out-of-the-box interactive blocks you can use. You can find interactive blocks by pressing \`/\` from within the editor.

<figure><img src="https://gitbookio.github.io/onboarding-template-images/interactive-hero.png" alt=""><figcaption></figcaption></figure>

### Tabs

{% tabs %}
{% tab title="First tab" %}
Each tab is like a mini page — it can contain multiple other blocks, of any type. So you can add code blocks, images, integration blocks and more to individual tabs in the same tab block.
{% endtab %}

{% tab title="Second tab" %}
Add images, embedded content, code blocks, and more.

\`\`\`javascript
const handleFetchEvent = async (request, context) => {
    return new Response({message: "Hello World"});
};
\`\`\`

{% endtab %}
{% endtabs %}

### Expandable sections

<details>

<summary>Click me to expand</summary>

Expandable blocks are helpful in condensing what could otherwise be a lengthy paragraph. They are also great in step-by-step guides and FAQs.

</details>

### Drawings

<img alt="" class="gitbook-drawing">

### Embedded content

{% embed url="<https://www.youtube.com/watch?v=YILlrDYzAm4>" %}

{% hint style="info" %}
GitBook supports thousands of embedded websites out-of-the-box, simply by pasting their links. Feel free to check out which ones\[ are supported natively\](https://iframely.com).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the \`ask\` query parameter:

\`\`\`
GET https://dedge-v2.gitbook.io/dedge-docs/basics/interactive-blocks.md?ask=<question>
\`\`\`

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

---