πŸ”₯ Trading Boost

What is Solana Trading Boost?

Solana Trading Boost leverages SWQoS (Stake-Weighted Quality of Service) technology and ZAN's staked validator nodes to significantly enhance transaction success rates and speed on the Solana blockchain.

Key Features:

  • βœ… Priority Channels: Tier-based dedicated bandwidth allocation
  • ⚑ Ultra-Low Latency: Prime: 95% transactions confirmed in ≀1 second
  • πŸ›‘οΈ MEV Protection (Beta): Prevents malicious front-running
  • πŸ“Š Real-Time Analytics: Success rate, latency, and consumption metrics

Technical Principle: SWQoS Documentation


Implementation Guide

Endpoints

Region-specific endpoints for optimal performance:

https://api.zan.top/node/v1/solana/mainnet/<your_AK>/prime   # Singapore
https://api-us.zan.top/node/v1/solana/mainnet/<your_AK>/prime  # Virginia
ParameterDescriptionValues
levelAcceleration tierprime (0.5u),
turbo (0.3u),
standard (0.1u)
?isMevMEV Protectiontrue (enable),
false /omit (disable)

πŸ“˜

Note:

πŸ“Œ Transactions default to standard (non-accelerated) without tier parameter.

MEV Protection

To activate MEV protection (at no additional cost), append ?isMev=true to your endpoint URL when initiating transactions.

Example: https://api.zan.top/node/v1/solana/mainnet/<your_AK>/prime?isMev=true

While MEV protection safeguards against transaction front-running, its cryptographic verification process may introduce marginal latency during peak network congestion. We recommend:

  • Benchmarking with/without MEV for your specific use case
  • Reserving activation for high-value transactions where security > speed
  • Monitoring real-time latency metrics via the ZAN Dashboard

API Implementation

python


import requests

url = "https://api.zan.top/node/v1/solana/mainnet/<your_AK>/prime"
payload = {
    "id": 1,
    "jsonrpc": "2.0",
    "method": "sendTransaction",
    "params": ["<signed_transaction_hex>"]
}
headers = {"Content-Type": "application/json"}

response = requests.post(url, json=payload, headers=headers)
print(response.json())

πŸ“˜

Note:

Full API spec: ZAN API Documentation

Pricing & Resource Management

Points System

  • 1 Point = $0.1 USD (dedicated resource unit)
  • Billing Logic:
    • Deducted only upon successful on-chain confirmation
    • Auto-fallback to standard transactions when balance insufficient

Service Tiers

TierPriorityPoints Cost
PrimeDedicated channel5 Points
TurboHigh priority3 Points
StandardShared channel1 Point

Throughput Limits

  • Shared Infrastructure: To minimize operational overhead, Trading Boost shares API Keys (AK) and throughput limits with your existing Chain RPC service.
  • Throughput limit Upgrade Path: If your application requires higher Throughput limit:
    • Contact our solutions team for custom scaling options
    • Upgrade your Chain RPC subscription tier in the ZAN Console
    • Fail-Safe Protocol: Transactions exceeding allocated limits automatically revert to standard non-accelerated processing.

Monitoring & Diagnostics

Dashboard

Log in to the ZAN User Portal β†’ SOL Trading Boost。

MetricDescription
Success RateTier-specific confirmation rate
LatencySubmission β†’ On-chain time (excluding the transmission time of client -> ZAN)
Points BalanceReal-time resource availability

Transaction Verification

  1. Go to Consumption Details in SOL Trading Boost module.
  2. Search by transaction hash.


    πŸ“˜

    Note:

    Absence indicates non-accelerated transaction

FAQ & Support

Q1: Why might (transaction) boost fail?

  • Insufficient Points balance
  • Exceeding TPS limits

Q2: How to verify boost status?

Check hash in Consumption Details (missing = not boosted)

Q3: Is testnet supported?

Currently unavailable


Support Channels:

Telegram | Discord | Feedback Portal