Sanctum Gateway FAQs

Sanctum Gateway is a one‑stop hub to send, optimize, and observe Solana transactions. If your app triggers any transaction on Solana, you can route it through Gateway for higher reliability, lower cost, and better visibility.

Benefit: Spend less on tips.

• Auto‑optimization sets compute units & priority fees automatically so your users don’t overpay for landing transactions.
• Jito Tip Refunds: When we submit to both RPC and Jito (with a small, controlled delay), if the tx confirms via RPC, we refund the Jito tip automatically to the transaction signer. Jupiter saves hundreds of thousands of dollars annually with this alone.

Benefit: Higher, more consistent delivery with graceful degradation.

• Transaction Routing can send through multiple delivery paths (different RPCs, Jito, etc.) and load‑balance/fallback when a path degrades, improving end‑to‑end success rate and reducing variance.

Benefit: Faster triage and shorter time‑to‑fix.

• World‑class observability simplifies why transactions are failing

Example debugging flow (realistic scenario):

1. Transactions are failing intermittently in production.
2. Gateway logs flags: “Rate limit exceeded” for one of the delivery methods
3. Engineer quickly updates and adds a new delivery method.
4. Delivery stabilizes within minutes instead of digging through logs & explorers for hours.

~15 minutes to drop‑in. It’s plug‑n‑play; configure once and forget.

We charge a minimal 0.00005 SOL per transaction sent through Gateway.

Gateway runs on Cloudflare Workers globally. Our sendTransaction median response typically sits around 0–20ms, which is negligible for end users.

1. In most cases, Gateway increases your reliability, because it routes through multiple RPCs and senders automatically.
2. Gateway itself is very unlikely to go down, because it's built by a very battle-hardened and trusted team that built Ironforge (handles over 300,000,000 requests per day).

We send your transaction to RPC and Jito concurrently (with a controlled delay). If the RPC path confirms the transaction, Gateway issues a Jito tip refund to the signer automatically. If the Jito submission is the one that lands, signer avoids paying a tip unnecessarily.

• Higher delivery rate under network variability.
• Load balancing to avoid provider hotspots.
• Automatic failover when one route degrades (e.g., rate‑limits, or RPC hiccups).
• Test a new sender or delivery method without having to send all your traffic to it

• Project Overalls:
  • Number of Transactions
  • Priority Fees Paid
  • Landing Rates & Status
  • Fee Breakdown
  • Transaction Distribution
  • Slot Latency
• Individual Transaction:
  • Timestamp
  • Transaction ID
  • Program Logs
  • Delivery Method Used

Refer to the screenshots of the observability dashboard:

• Docs: gateway.sanctum.so/docs
• Get Started: https://gateway.sanctum.so/