HighTower

HighTower Infra is now open to everyone Markets follow narrative, narrative follows data. We built the infrastructure you actually need. All ready to use: — Solana Infra: RPC & Streaming for the low-latency execution you expect. — Data Indexers: Accurate historical data for Solana and Polymarket. — Market Streams: Real-time feeds from X to capture the sentiment you’re missing. Support for Base, BNB, and Hyperliquid is included. Start your free trial for any service👇 https://www.htw.tech/market/rpc

🟩 We're launching Supanode — HighTower's Solana infrastructure now has its own home. If you're running a bot, indexer, dApp, alerting system, trading setup, or backend that depends on fast and reliable Solana data, this is for you. What's inside: • RPC • Yellowstone gRPC • historical data • indexing support • transaction landing infra • dedicated production setups You don't have to run the full stack yourself just to get stable Solana infrastructure. ➡️ Docs, services, pricing, and setup options: https://supanode.xyz ========================= HighTower | Supanode | Get a 48h trial

🟩 Free infra for builders on Solana & Hyperliquid The Supanode Builder Program gives teams 3 full months of free shared endpoints. If your bot, indexer, dApp, trading setup, or backend needs reliable infrastructure on Solana or Hyperliquid, this is for you. What's included: • shared RPC and gRPC endpoints • data access • direct support from our infra team No need to stand up your own nodes just to start building on something stable. 👉 Tell us what you're building and what infra you need: Apply here ========================= HighTower | Supanode | Get a 48h trial

🟩 RPC, streaming, indexing, landing, dedicated nodes: Supanode covers Web3 infra across Solana, Hyperliquid, Polymarket-related workflows and EVM chains. If you're building, testing or scaling, start here: ➡️ Builder Program — 3 months of free shared infra ➡️ 48h trial — for production workloads ➡️ Services, docs & limits ========================= HighTower | Supanode | Get a 48h trial

🟩 Solana API means different things depending on who is debugging it Frontend usually just needs an endpoint URL. Infra teams look at the same layer and see limits, retries, WebSocket behavior, and provider choices. That gap is where production issues start. ➡️ Read the practical guide ========================= HighTower | Supanode | Get a 48h trial

🟩 The frontend bundle is the easiest place to expose a Solana RPC key Bots reuse the endpoint, quota burns, users hit 429s, and the incident starts looking like provider latency. Learn what to check before this becomes a production problem: backend proxies, method allowlists, key separation, confirmation tracking, and WebSocket recovery. ➡️ Read the Solana RPC endpoint security guide ========================= HighTower | Supanode | Get a 48h trial

🟩 Solana RPC infrastructure, from endpoint URL to production setup. A practical map of what sits behind that URL: public access, managed RPC, dedicated nodes, streaming, and production tradeoffs. 👉 Read the Solana RPC infrastructure guide ========================= HighTower | Supanode | Get a 48h trial

🟩 Building trading infra on Solana? Speed there is a property of the full path, from event detection to confirmed execution. RPC latency matters, but so do streams, fee logic, submission paths, and confirmation tracking. ➡️ Read our guide to sniper bots and what actually decides execution ========================= HighTower | Supanode | Get a 48h trial

🟩 Planning to run a Solana app on a free RPC endpoint? Free RPC is a good shortcut while failures are cheap: demos, scripts, devnet work, internal read-only tools. The risk starts when it becomes part of the product path. Real users notice stale balances, stuck confirmations, dropped WebSocket subscriptions, 429s, exposed browser keys, and heavy methods hitting limits. Our guide covers what to check before committing to a free endpoint, how public RPC differs from provider free tiers, and when managed or dedicated Solana RPC becomes the safer option. 👉 Read the free Solana RPC guide ========================= HighTower | Supanode | Get a 48h trial

🟩 Does your Solana trading bot use the same RPC path for reads and writes? It works fine, right up until a trade fails and nobody can tell which layer dropped it. The read path needs broad visibility: account updates, pool state, quotes, logs, WebSocket or gRPC streams, reconnect recovery, and sometimes historical context. The write path is a narrower problem. It needs a fresh blockhash, simulation, compute-unit limits, priority fee logic, a controlled sender path, retry rules, and confirmation tracking. When both paths share the same endpoint and client, very different problems collapse into one vague "RPC issue": stale quote, stream gap, underpriced transaction, expired blockhash, or a sendTransaction response that returned a signature without the trade ever landing. For a production bot, separating reads from writes is mostly about control. The system needs to know whether to re-quote, retry, fail over, rebuild, or stop. ➡️ Read the full trading bot infrastructure guide ========================= HighTower | Supanode | Get a 48h trial

🟩 Before you raise Solana priority fees again, check what you are actually paying for A higher CU price is only half of the fee equation. The other half is the compute-unit limit you request. At the network level: total network fee = base fee + priority fee base fee = signatures × 5,000 lamports priority fee = ceil(CU price × CU limit / 1,000,000) For a transaction with 1 signature, a CU price of 50,000 micro-lamports, and a requested CU limit of 300,000 CUs, the priority fee is: ceil(50,000 × 300,000 / 1,000,000) = 15,000 lamports After adding the 5,000 lamport base fee, the total network fee is 20,000 lamports, or 0.00002 SOL. The practical detail is that priority fee is calculated from the requested CU limit, not from the compute the transaction actually consumes. If simulation shows that a transaction usually needs around 180,000 CUs, but the app requests 600,000 by default, the priority fee is still charged on 600,000. Some margin is useful, but an oversized margin becomes repeated overpayment. For production flows, fee tuning usually means simulating first, setting a realistic CU limit with a controlled buffer, estimating CU price dynamically, and checking whether higher spend actually improves landing. 👉 Read our full guide ========================= HighTower | Supanode | Get a 48h trial

🟩 Choosing a low-latency Solana RPC provider? Do not start with the homepage number The better starting point is where your workload runs and what it actually does. A provider page can show regions, uptime, and latency, but your backend may be in a different cloud region, using heavier RPC methods, sending bursts of requests, tracking confirmations, or relying on fresh streams. A useful benchmark should come from the same VPS or cloud region as the app, use the methods the app actually calls, and measure p50, p95, and p99 under realistic concurrency. It should also include burst traffic, because 429s, stream delay, slot freshness, and confirmation tracking issues often stay invisible in clean single-request tests. ➡️ Read the full guide ========================= HighTower | Supanode | Get a 48h trial

Choosing between managed and self-hosted Solana RPC? Compare the trade-offs before you commit. 👉 Read the guide ========================= HighTower | Supanode | Get a 48h trial

Yellowstone gRPC changes the Solana data path from periodic requests to a live stream of filtered updates. But the stream is only the ingestion layer. Teams still need to handle recovery after disconnects, ordering, deduplication, and storage. ➡️ Full trade-off breakdown ========================= HighTower | Supanode | Get a 48h trial

150 markets × 3 feeds (trades, l2Book, candle) = 450 Hyperliquid WebSocket subscriptions That's before user-specific streams. The public endpoint has a per-IP cap of 1,000 subscriptions and 10 unique users 👉 Limit math and recovery patterns ========================= HighTower | Supanode | Get a 24h trial

A trading system reconstructs and decodes a transaction from raw shreds before execution It gets the intent early, but still does not know whether it actually succeeded. So production stacks often split the job: ShredStream ➡️ early detection gRPC / RPC ➡️ execution result, confirmation, reconciliation 👉 Full breakdown ========================= HighTower | Supanode | Get a 24h trial

HTTP response: 200 RPC response: signature returned Explorer: no transaction found All three can describe the same Solana submission. sendTransaction confirms that the RPC accepted the transaction, not that the leader received, scheduled, or included it. The full submission-to-inclusion path ========================= HighTower | Supanode | Get a 24h trial

Say you need every wallet that bought a token within five minutes of its creation. Once swaps and creation events are decoded into tables, the core of the query becomes a join and a time condition: s.block_time BETWEEN c.block_time AND c.block_time + INTERVAL 5 MINUTE RPC gives you the source transactions. Indexing turns them into tables. Before this query works, the records still have to be backfilled, decoded, normalized, stored, and reprocessed when decoder logic changes. That’s the indexing work. 👉 From raw Solana transactions to queryable data ========================= HighTower | Supanode | Get a 24h trial

logsSubscribe has a scaling detail that matters for wallet monitoring: its mentions filter accepts exactly one Pubkey. Add a second, and the request fails with Invalid params. So an address list becomes many subscriptions, not one wider subscription. Monitoring 2,000 wallets means 2,000 subscription IDs to track, recreate after every reconnect, and check for missed events. WebSocket may still carry the data just fine. But at that point, the simple option has become a subscription management system. 👉 Full breakdown of Solana streaming options ========================= HighTower | Supanode | Get a 24h trial

Follow a Pump.fun token from its first trade to its first PumpSwap swap. That path runs across two Solana programs: Pump handles the bonding curve and migration, while PumpSwap takes over once the pool goes live. Curve completion and migration are separate events. The curve can be full before the PumpSwap pool even exists. 👉 Here’s how to follow every stage using WebSocket or Yellowstone gRPC ========================= HighTower | Supanode | Get a 24h trial

💵 Build, simulate, sign, submit, and confirm a custom Jupiter swap Jupiter /build returns instruction groups instead of a finished transaction. That gives you room for custom logic, while the rest of the transaction lifecycle moves into your application. From there: → add custom instructions without breaking the route’s account-state assumptions → simulate the complete transaction and set its CU limit from measured usage → check onchain status before retrying the same signed transaction or rebuilding and re-signing 👉 The full TypeScript flow, including tx.jup.ag vs your own RPC ========================= HighTower | Supanode | Get a 24h trial

On Hyperliquid, a cancel can be processed before a buy that reached the network first When both enter the same consensus batch, HyperCore processes cancels before actions containing GTC or IOC orders. A resting sell order can therefore be removed before your buy is matched. Your buy executes against the updated book, potentially filling only part of the requested size. For an IOC order, the unfilled remainder is canceled. 👉 The full walkthrough of HyperCore’s batch ordering and matching, with a worked order-book example ========================= HighTower | Supanode | Get a 24h trial

🟢 Supanode now supports Robinhood Chain Available for teams building on the network: → RPC and WebSocket access → Dedicated full and archive nodes → A DEX indexer with SQL access to swap and pool history For live blocks and contract events, use WebSocket RPC with eth_subscribe. Robinhood’s public Sequencer Feed also uses WebSockets, but carries sequencer data for Nitro nodes. 👉 Our guide explains which endpoint your app needs, how to set up subscriptions and how to recover missed events after a disconnect. ========================= HighTower | Supanode | Get a 24h trial