Trojan and Maestro document a base fee of 1% per successful trade: buying and later selling are separate chargeable operations. But “1% twice” does not describe the entire round-trip cost. Route and network expenses add to it, while execution affects the amount received. In the hypothetical model below, the token needs to rise approximately 2.94% in SOL to cover costs before cashback. That result depends on stated assumptions; it is not a universal profit threshold. Trojan fees, Maestro fees.
The comparison covers Telegram bots and manual buys and sells on Solana. It does not transfer terms from Trojan's web terminal, Arena, automatic sniping or other networks. Official fee documentation was checked on October 5, 2026; no live trades or comparative execution tests were performed.
What each bot charges
| Solana condition | Trojan on Telegram | Maestro Bot |
|---|---|---|
| Base trading fee | 1% per successful transaction | 1% on every successful buy and sell |
| Collection | During swap routing | Within the same transaction |
| Cashback on trading fees | 20% under the Telegram documentation | Bronze 15%, Silver 20%, Gold 25%, Diamond 30% |
| What is not an upfront discount | An unconfirmed offer on another page or expected cashback | A payment to the referrer or cashback not yet received |
Collection terms are documented in Using Trojan on Solana and Maestro Monetization; rebates are described in Trojan Rewards Program and Maestro Cashback.
Trojan has a relevant documentation discrepancy: its official comparison article quotes 0.9% and an effective 0.72%, while the current Telegram documentation states 1% with separate 20% cashback. This calculation therefore uses 1%. That does not prove every discount has been withdrawn; it means you should not assume 0.9% or 0.72% without confirmed terms for your account and product.
Maestro's share of up to 25% under its referral program belongs to the referrer. It does not establish that your fee falls from 1% to 0.75%. Nor should its accumulation of unpaid fees up to a threshold on other chains be applied to Solana: Solana collection occurs within the transaction.
The two products have the same base rate. Comparing actual costs requires comparable amounts, routes and network settings. The fee table alone cannot establish which bot delivers cheaper execution.
Costs beyond the bot's percentage
DEX fees. The pool or swap route has its own charge. Raydium, for example, lists 0.25% for AMM v4, while A pool that exchanges two tokens under the x × y = k model. Token reserves determine the price; a swap adds one token and removes the other. Raydium also labels this model Standard AMM. and CLMM have multiple tiers. That makes 0.25% a specific fee, not a universal charge for Solana swaps. Allocations of a pool's total fee to liquidity providers and the protocol should not be added to the total again. Some routes can also involve creator fees or token transfer charges. Raydium fee comparison, Trojan FAQ.
Network, priority and tips. Solana's base fee is 5,000 lamports per signature, or 0.000005 SOL for one signature. That is not the total price of every transaction: priority fees and a delivery-route tip may also apply. Solana Fees, Jito Transaction Send.
This is an easy place to double-count. Trojan's documentation distinguishes separate gas and tip settings for its sniper from a combined gas setting for manual swaps. Do not take a manual trade's combined budget and add its already included tip again. Maestro's Solana Gas Delta is added to the base fee. Compare actual components, not merely similarly named settings. Trojan's settings distinction, Maestro Buy Settings.
Execution price. Price impact and realized The difference between the price shown before confirmation and the execution price. Settings usually specify the maximum allowed deviation; the swap fails if it is exceeded. change the tokens received. Slippage tolerance is a permitted boundary for deterioration, not a percentage automatically charged. If a quote or actual output already includes DEX fees and the trade's price impact, do not subtract them again.
Token-account balance. Creating a token account can require SOL to remain reserved for rent. That balance may be recovered when the account is closed, so it should not automatically be classified as an irreversible fee. It still affects the available balance required. Solana: rent funding.
No bot fee on an unsuccessful trade does not mean a free attempt: a failed transaction processed by the network can still incur network fees. Rejection before inclusion in a block is a different case. Solana Fee Structure.
One round trip with a hypothetical 1 SOL swap amount
Because both bots have a 1% base fee, use one shared model. It explains cash flows; it does not reproduce a particular bot's Buy input or actual routing.
Define N = 1 SOL as the amount directed to the swap before the DEX fee. Budget the bot's buy fee separately on top. If an interface instead deducts that fee from the entered amount, first establish how much of the input corresponds to N. Do not automatically equate the Buy field with N.
| Model input | Assumed amount and fee base |
|---|---|
| Swap amount N | 1 SOL before the DEX fee |
| Buy bot fee b | 1% of N, paid on top |
| Sell bot fee s | 1% of the DEX output on sale |
| DEX fee d | 0.25% on each leg; an assumption, not a verified route for either bot |
| Fixed costs G | 0.002005 SOL per successful operation |
G consists of a hypothetical 0.000005 SOL base fee + 0.001 SOL priority fee + 0.001 SOL tip, with one signature. These are illustrative actual components, not recommended settings. Do not add them again to a bot budget that already includes them.
Other assumptions: exactly two successful operations and existing token accounts. There are no transfer taxes, creator fees, price impact, market slippage, CEX withdrawals, bridges, premium subscriptions or cashback. The token is priced in SOL; changes in SOL's dollar price are outside the calculation. Trades use a linear price under the stated fees.
First calculate the round trip with no change in the token's SOL price:
| Stage | Calculation | SOL |
|---|---|---|
| Total entry expenditure C | N × (1 + b) + G | 1.012005 |
| DEX output after the buy and sell, before the sell bot fee | A = N × (1 − d)² | 0.99500625 |
| Sell bot fee | A × s | 0.0099500625 |
| Amount remaining after sale and its fixed costs | A × (1 − s) − G | 0.9830511875 |
| Round-trip loss | C − 0.9830511875 | 0.0289538125 |
You spend 1.012005 SOL, and approximately 0.983051 SOL remains after exit and its expenses. The difference is about 0.028954 SOL. The buy and sell percentages apply to different bases, so simply adding two percentages does not reproduce the result.
What price increase covers the costs?
Let g be the token's price increase in SOL between buying and selling. Holding the model's assumptions constant, DEX output becomes A × (1 + g), and the sell bot fee rises with it. Breaking even requires:
A × (1 + g) × (1 − s) − G = C.
Therefore:
g = (C + G) ÷ [A × (1 − s)] − 1
= (1.012005 + 0.002005) ÷ (0.99500625 × 0.99) − 1 ≈ 2.9393%.
Rounded, that is a 2.94% increase in SOL before cashback. It does not guarantee profit on a real trade: different routes, sizes and execution change the result. Fixed costs also consume a larger share of a smaller trade, so this threshold cannot be applied to every amount.
Treat cashback as a separate receipt
20% cashback on a 1% fee returns 20% of the fee, not 20% of trade volume. In the unchanged-price scenario above, total bot fees are:
0.01 + 0.0099500625 = 0.0199500625 SOL.
Applying the documented rebate shares gives these accruals:
| Condition | Calculation based on fees | Accrued SOL |
|---|---|---|
| Trojan, 20% | 0.0199500625 × 0.20 | 0.0039900125 |
| Maestro Bronze, 15% | 0.0199500625 × 0.15 | 0.002992509375 |
These are not guaranteed final wallet receipts. Maestro permits a claim after the relevant network threshold, and deducts the claim's network fee from the amount received. This comparison does not establish a payout time for Trojan's Telegram cashback; the referral payment schedule cannot automatically be treated as the cashback schedule. Maestro Cashback, Trojan Rewards Program.
A future rebate does not replace the balance needed to trade now. Add only amounts actually received to a realized cash-flow result, not accrued points or the referrer's income. The 2.94% threshold above is before cashback. You cannot simply subtract the unchanged-price scenario's rebate from it: a different sale output changes both the sell fee and the rebate base.
Applying the calculation to your own transaction
For an existing trade, record the amount actually directed to the swap, the bot fee and separate network payments. Then identify actual sale proceeds, its deducted fee and cashback already received. If the output is already net of fees, do not deduct them twice. Track reserved and recovered rent separately from irreversible expenses.
Reconcile those entries with the SOL changes for the corresponding wallet transactions, separating Periodic payments between buyers and sellers of perpetual futures. Buyers pay when the rate is positive; sellers pay when it is negative. This mechanism keeps the contract price closer to the underlying asset price. transfers and unrelated activity. A PnL screen can use a different basis: Maestro's Initial Includes Fees, for example, changes fee treatment in the entry price. A positive number on a trade card therefore does not replace cash-flow reconciliation. Maestro General Settings.
To check networks, interfaces and restrictions, use Yieldo's terminal directory, which includes Maestro. It is a product reference, not an execution calculator for the two bots. If you still need to withdraw SOL from an exchange, separately compare SOL withdrawal fees and select the native Solana network. Funding costs belong to getting assets into the wallet: a single CEX withdrawal should not be charged again to every subsequent buy and sell.