Pricing & Billing

Understand the tips-based pricing model, billing rules, and optimization strategies for Trading Boost

Trading Boost uses a Tips model — a transparent, pay-per-use on-chain bidding mechanism.

Billing Details

ItemDescription
Billing ModelPay-per-use via on-chain SOL transfer as tip
Minimum Fee0.0003 SOL per transaction (300,000 lamports)
Charges on FailureNone — tips are only deducted when transactions successfully reach the chain
PriorityHigher tip amounts yield higher transaction priority
MEV ProtectionFree, no additional charges

Tip Strategy Recommendations

ScenarioRecommended Tip AmountExplanation
Standard Acceleration0.0003 SOL (minimum)Baseline priority suitable for most transactions
Moderate Congestion0.001 – 0.005 SOLHigher priority during network congestion
High-value/Time-sensitive0.005 – 0.01+ SOLMaximum priority for critical transactions (large swaps, liquidations, etc.)
📘

Note:

Recommended strategy: Start with minimum tip, increase by 50% on each retry until successful. See the dynamic tip increment example in Tips Mode Integration Guide .

Fee Transparency

  • Acceleration Successful: Tip amount is deducted
  • Acceleration Failed: No charges incurred (tip is not executed on-chain)
  • Transaction Gas Fees: Charged normally, independent of Trading Boost
  • MEV Protection: Free additional feature, no extra cost

Enterprise & Partnership Programs

If you're a high-frequency trading team, market maker, or project with significant daily volume, we offer customized partnership programs:

  • Tip Revenue Sharing — Enjoy tip rebates based on transaction volume
  • Dedicated Support — Priority response and dedicated account management
  • Custom SLAs — Negotiable higher throughput quotas and priority guarantees

Contact us for partnership inquiries:

ChannelLink
Business Inquiryzan.top/home/contact
TelegramZANTeam_official
DiscordZAN Discord

Cost Optimization Tips

  • Dynamic Tip Adjustment — Adjust tips based on network congestion to avoid overpaying
  • Set Tip Caps — Implement maximum tip limits in retry logic to prevent excessive costs in extreme scenarios
  • Optimize Compute Units — Set precise CU limits to reduce overall transaction costs
  • Separate Read/Write Operations — Use free standard RPC for read operations, Trading Boost only for write operations