Whitepaper

How FeeShield works. All of it.

No marketing spin. This is a full technical breakdown of what FeeShield does, how it does it, what we see, what we don't, and how we plan to make money. If you're going to trust us with your trades, you deserve to know everything.

Last updated: February 2026

01

The Problem

Every major Solana trading platform charges a fee on every trade. When you buy or sell a token on Axiom, Uxento, or RapidLaunch, the platform silently adds a fee instruction to your transaction before it hits the blockchain. These fees range from 0.75% to 1.25% per trade.

For a trader doing 20 trades a day at 10 SOL per trade, that's 48 to 75 SOL per month going to the platform. At current SOL prices, that's thousands of dollars a month extracted from your trading activity.

These aren't Solana network fees (those are fractions of a cent). These are platform fees — the trading platform's revenue model, baked into every transaction you submit. FeeShield eliminates them.

02

What FeeShield Actually Is

FeeShield is a Chrome extension that sits between your browser and the trading platform's servers. When you click "Buy" or "Sell" on a supported platform, FeeShield intercepts the network request before it reaches the platform's backend.

Instead of letting the platform build your transaction (and bake their fee into it), FeeShield routes the trade through our own backend. Our backend builds the same transaction — same token, same amount, same slippage — but without the platform's fee instruction. The transaction goes directly to Solana.

After the trade executes, FeeShield sends a valid-looking success response back to the platform, so its UI updates normally. The platform sees a completed trade. You see a completed trade. The only difference: the fee that would have gone to the platform stays in your wallet.

03

How Interception Works

FeeShield uses a Chrome Manifest V3 content script that injects into supported trading platform pages. The extension operates at two levels:

Network-Level Interception

A MAIN world content script overrides the browser's native fetch() and XMLHttpRequest APIs, as well as the WebSocket constructor. This allows FeeShield to inspect every outgoing request and determine if it's a trade-related API call.

Per-Platform Translators

Each supported platform has its own translator module. These translators understand the platform's specific API format — REST endpoints, WebSocket events, request/response shapes — and convert them into a common internal format. When a trade request is intercepted, the translator extracts the token address, amount, trade type, and other parameters, then forwards them to our backend.

Platform-Specific Details

  • Axiom — Intercepts fetch, XHR, WebSocket, and beacon requests. Parses serialized transactions from the request body. Wallet keys captured via crypto.subtle.decrypt() override.
  • Uxento — Intercepts Socket.IO events (swap, create token). Uses Turnkey session relay for wallet access.
  • RapidLaunch — Intercepts REST fetch/XHR calls. Wallet access via localStorage token.
FeeShield only activates on supported trading platforms. It does not intercept, monitor, or modify traffic on any other website. Non-trade requests on supported platforms (loading the page, fetching charts, etc.) pass through untouched.
04

The Trade Flow

Here's the exact sequence of events when you make a trade with FeeShield active:

1

You click Buy/Sell

On Axiom, Uxento, or RapidLaunch

2

FeeShield intercepts

Network request caught before it leaves your browser

3

Backend builds TX

Transaction constructed without platform fee addresses

4

Your browser signs

Private key signs locally, never sent to any server

5

TX submitted to Solana

Sent via Jito bundles + RPC fallback simultaneously

6

Platform gets response

Valid success response returned — platform sees nothing

7

On-chain audit

Automated verification: no platform fee addresses in TX

Transaction Submission

Every trade is submitted through two paths simultaneously for maximum reliability:

  • Jito bundle submission — Transaction bundled and sent to Jito block engine for MEV-protected inclusion
  • Standard RPC fallback — Simultaneously sent to Solana RPC as backup

Priority Fees

Transactions include a compute budget of 400,000 compute units with a configurable priority fee. This is the standard Solana priority fee mechanism — it goes to validators, not to us. We also support optional Astralane tips for landing priority when needed.

05

Platform Fee Rates

These are the exact fee rates each platform charges. We verified these by inspecting on-chain transactions and platform source code. Every one of these fees is eliminated when you trade through FeeShield.

PlatformBuy FeeSell FeeCreate FeeMin FeeWith FeeShield
AxiomAxiom
0.80%0.80%--0.01 SOL0%
UxentoUxento
0.75%0.75%1.25%0.01 SOL0%
RapidLaunchRapidLaunch
1.00%1.00%1.00%0.01 SOL0%

How Savings Are Calculated

Fee the platform would charge:
  platformFee = max(tradeAmount × feeRate, minFee)

Example: 10 SOL buy on RapidLaunch (1% fee rate):
  platformFee = max(10 × 0.01, 0.01) = 0.1 SOL

FeeShield fee (during launch): 0%
  feeShieldFee = 0 SOL

Your savings:
  saved = 0.1 - 0 = 0.1 SOL per trade

At 20 trades/day for 30 days:
  monthly savings = 0.1 × 600 = 60 SOL

Savings are calculated immediately when the trade is intercepted (estimated), then verified 5-15 seconds later by reading the actual on-chain transaction balances. Both values are stored — the verified number is what shows in your savings dashboard.

06

Security Model

Key Handling

FeeShield supports two signing modes depending on the platform:

  • Client-side signing — Our backend builds an unsigned transaction and returns the message bytes to your browser. The extension signs the message locally using your captured wallet key, then sends only the signed transaction back for submission. Your private key never leaves the browser.
  • Server-side signing — For certain platforms where the wallet credential is a session token (like Uxento's Turnkey sessions), the session is relayed to our backend which uses it to sign and submit the transaction. The session token is used only for the duration of the trade and is not stored.

Wallet Capture

To sign transactions, FeeShield needs access to the wallet the platform is using. Each platform stores wallet credentials differently:

  • Axiom — Keys are encrypted in the browser using crypto.subtle. FeeShield intercepts the decryption call to capture the key when the platform itself decrypts it for signing.
  • Uxento — Uses Turnkey MPC wallet sessions. FeeShield relays the session token.
  • RapidLaunch — Uses a token stored in localStorage.
We're transparent about this: FeeShield accesses your wallet credentials to execute trades on your behalf. This is the same access the platform itself has. The difference is we use it to save you fees, not charge them.

Authentication

FeeShield accounts use email + OTP verification or Phantom wallet authentication. Sessions are managed with JWT refresh tokens that rotate on each use. All communication between the extension and our backend uses HTTPS. You can log out at any time to revoke all active sessions.

07

On-Chain Verification

We don't just claim we removed the fee — we verify it on-chain. Five seconds after every trade, our automated fee audit system:

  1. 1.Fetches the confirmed transaction from Solana
  2. 2.Calculates SOL balance changes for every account in the transaction
  3. 3.Classifies each recipient: your wallet, Jito tips, Solana protocol fees, DEX fees
  4. 4.Checks every recipient against known platform fee addresses
  5. 5.Flags any transaction where a platform fee address received SOL

If a platform fee address is detected in any transaction, it triggers an immediate alert in our monitoring system. This has never happened in production — but the check runs on every single trade.

Known Fee Addresses We Monitor

Axiom:        axm2JQY1FKEktAwgXWqjGYkkWsWPfwKzgbnGVt5kiP4
Uxento:       uxtoRPdPjRekYmxs1uUqVRZWh38iqonc9KgPuZXPeSY
RapidLaunch:  rapidXMVLw5uBieKHDGvF9k4xSSDXyD2FC5wLTAajaJV

If any of these addresses appear as recipients in a FeeShield-routed transaction, our system logs a fee leak alert. We also flag any unknown recipient that receives more than 5,000 lamports (0.000005 SOL) for manual review.

08

What We See & What We Don't

Full transparency on what data FeeShield processes:

What we see

  • Your email address (for account login)
  • Trade details: token address, amount, trade type (buy/sell/create)
  • Transaction signatures (public on-chain data)
  • Your wallet public address
  • Which platform you traded on
  • Extension diagnostics: errors, timing data, platform detection
  • Fee savings calculations

What we don't see (or store)

  • Your browsing history on any site
  • Non-trade network requests (even on supported platforms)
  • Traffic on non-supported websites — the extension doesn't activate
  • Your portfolio balances or holdings
  • Personal information beyond your email
  • Private keys are not stored on our servers beyond transaction signing window
We log intercepted trade requests for debugging and reliability purposes. These logs are retained for up to 90 days and include request/response data for trades we process. We do not sell, share, or monetize this data. See our Privacy Policy for full details.
09

Revenue Model

During launch, FeeShield charges 0% fees. You keep 100% of the savings. This is not a limited trial — it's our launch phase while we build the user base and prove the product works.

Future Revenue

When we do introduce fees, here's exactly how it will work:

  • FeeShield will take a small percentage of each trade — significantly less than the platform fee it replaces
  • The fee will be clearly disclosed before it takes effect — no surprise charges
  • You'll always save money compared to using the platform directly — that's the entire value proposition
  • The fee is collected on-chain through our fee program (feesNomk...uL8), making it fully auditable

Our fee program supports tiered pricing (Bronze, Silver, Gold, Platinum, Diamond) and affiliate revenue sharing, though these features are not currently active. When enabled, high-volume traders will get lower rates, and referral partners can earn a share of fees from users they bring in.

10

Referral Program

FeeShield offers a referral program where you earn 10% of the fee savings generated by users you refer. Here's how it works:

  • Generate a custom referral code from your FeeShield dashboard
  • When someone signs up with your code and trades, you earn 10% of their savings
  • Rewards are tracked per trade and can be claimed from the referral dashboard
  • The referred user keeps their full savings — referral rewards come from FeeShield, not from the user
Example:
  Your referral signs up and buys 10 SOL on Axiom (0.8% fee)
  Their savings: 0.08 SOL
  Your reward:   0.008 SOL (10% of their savings)

  If they do 600 trades/month at 10 SOL:
  Their monthly savings: 48 SOL
  Your monthly reward:   4.8 SOL
11

Supported Platforms

FeeShield currently supports three Solana trading platforms. We are not affiliated with, endorsed by, or partnered with any of them.

Axiom
Axiomaxiom.trade

Token trading (buy/sell). Interception covers all trade types including quick buys and limit orders.

Uxento
Uxentoapp.uxento.io

Token swaps and token creation. Both swap and create events are intercepted via Socket.IO.

RapidLaunch
RapidLaunchrapidlaunch.io

Token trading and token creation via REST API interception.

On any non-supported platform, FeeShield is completely inactive. Your trades go through normally with no interception.

12

What Could Go Wrong

We believe in telling you the risks, not hiding them:

Platform API changes

If a platform changes their API format, our translators may temporarily break. Trades would fail (not execute incorrectly) until we update. We monitor for this continuously.

Platform detection

A platform could theoretically detect FeeShield by analyzing traffic patterns. We design our responses to be indistinguishable from legitimate platform responses, but the risk exists.

Transaction failure

Like any Solana transaction, trades can fail due to slippage, network congestion, or insufficient balance. FeeShield handles failures the same way platforms do — you get an error and can retry.

Price difference

Because our trade routes through a different path than the platform's backend, there may be minor timing differences in execution price. In practice this is negligible (milliseconds).

Extension context death

Chrome can terminate extension service workers under memory pressure. FeeShield includes a heartbeat system to detect this and reconnect, but a trade initiated during the dead window would fall through to the platform normally (with fees).

Backend downtime

If our backend is unreachable, trades fall through to the platform unmodified. You'd pay the normal platform fee, but your trade still executes. FeeShield failing never blocks you from trading.

13

Roadmap

Where FeeShield is heading:

1

Now

  • Axiom, Uxento, RapidLaunch support
  • 0% FeeShield fees
  • Client-side signing
  • Referral program
  • Fee savings dashboard
2

Next

  • GMGN, Photon, BullX support
  • Chrome Web Store listing
  • Volume-based tier pricing
  • Affiliate revenue sharing
3

Later

  • Swap aggregator support
  • Twitter/X embedded trading
  • Cross-chain expansion
  • Mobile browser support

Questions?

If something in this document is unclear, or if you want to know something we didn't cover, reach out. We're building FeeShield on transparency, and that starts with answering every question honestly.