Joined March 2024
340 Photos and videos
Flux RPC retweeted
Don’t have $500m? @FluxRPC provides more performant, fresher data than any other provider Get ahead of the pack without the crazy barriers to entry for “priority RPC”
Introducing Frontier Traders An exclusive global community for elite firms and traders at the frontier of emerging assets. Members can access rewards across Solana trading venues, dedicated infra, and a voice in shaping Solana’s market structure.
1
3
22
2,118
Flux RPC retweeted
Picking a Solana RPC provider is a mess! And it's the billing, not just the tech. - Some bill credits, compute units, or per request. - Others require deposits & charge per call premiums. - They all mark up or restrict heavy calls in some way. - Most restrict gRPC/Streaming. You can never line up two quotes and know which is actually cheaper, because they don't want you to. So I built a matrix that runs them all on the same customizable workloads: Example - 10.85M calls/credits - 243.62 GB on the wire ~109M compute units Same data. Same @Solana. Wildly different bills. In the video I toggle streaming gRPC on and off and cycle through a few RPS tiers. The competitors trade places. @FluxRPC stays cheapest across all of them.
8
4
25
4,070
Flux RPC retweeted
Solana RPC pricing 101: Credit RPC: 10 or 500 credits per call. Optimize your payload, save nothing. PAYG RPC: $0.05 per 1k calls. 30 req/s = $3,900/mo. @FluxRPC: $38/mo, 250 GB, flat. 30 req/s = $38/mo. Optimize, pay less.
1
2
10
833
Flux RPC retweeted
The hidden math of @solana RPC pricing Most providers charge per credit or per call. We charge per byte. Here's what that actually means... ━━━━━━━━━━━━━━━ Per 1,000 getAccountInfo calls (Solana's most-called method): @FluxRPC → $0.0000234 Credit provider → $0.05 PAYG provider → $0.01 FluxRPC vs Credit provider: 2,133× cheaper FluxRPC vs PAYG provider: 428× cheaper ━━━━━━━━━━━━━━━ "But surely on heavy calls you lose?" getProgramAccounts (5 MB payload): FluxRPC → $0.293 per 1k calls Credit provider → $0.500 per 1k calls PAYG provider → $0.401 per 1k calls Why? One charges 10 credits per gPA call. The other charges $10 per million calls flat. FluxRPC just charges for the bytes. ━━━━━━━━━━━━━━━ Plan-for-plan capacity: $38/mo FluxRPC = 655M getAccountInfo calls $49/mo credit provider = 10M calls $849/mo FluxRPC = 40.3B getAccountInfo calls $999/mo credit provider = 200M calls 201x more calls. $150 cheaper. ━━━━━━━━━━━━━━━ gRPC streaming (1 TB/mo): FluxRPC → $61.44 Credit provider → $157.29 PAYG provider → $81.92 Same gRPC. Different bill. ━━━━━━━━━━━━━━━ And here's the part nobody talks about. Just to ACCESS mainnet gRPC: FluxRPC → $38/mo (Develop plan) PAYG provider → $125 prepaid minimum Credit provider → $499/mo (Business plan) 13x price gap before you stream a single byte. Same data. Just paywalled differently. ━━━━━━━━━━━━━━━ No credit games. No method weighting. No per-call fee addon. No overage premiums. No absurd gRPC paywall.
3
3
9
640
Flux RPC retweeted
Looking forward to this - Would be happy to do a talk on RPC & what we have been up too around improving developer experiencei
Back by popular demand... Scale Or Die is coming to London on November 14th. If deep technical programming, hands-on workshops, and focused time with @solana 's most cracked builders sounds like a good time, then this is the event for you.
2
3
16
2,416
And our dev plan is now only $15 for the first month. The includes Yellowstone gRPC!
gPA on OreV2 TTFB - @FluxRPC is - 2x faster vs next best. - 3x faster vs 3rd place. - 8x faster vs 4th best. Total Time - FluxRPC is - 2x faster vs next best. - 4x faster vs 3rd best. - 5x faster vs 4th best. Higher RPS, No credits, Faster. If you haven't already - try it out!
3
2
19
2,844
HTTP/3 QUIC is now live on every @FluxRPC endpoint. The upgrades you'll feel: → Faster connections - fewer round trips before your first request lands → Independent parallel streams - one slow request no longer blocks the others → Better performance on mobile, bad wifi, packet loss, and cross-region traffic → Connection migration - survives wifi-to-cellular switches without dropping → Lower tail latency at scale Whether you're shipping a dApp, running a trading desk, indexing onchain data, or powering a backend service... your stack just got faster.
3
4
16
2,120
Your users don't see the 17 slot blackout on some legacy RPCs. They eat the slippage. They feel it. The missed fills. The worse exit. The later entry. And they blame your dapp. Not the RPC quietly costing them every trade. They move to someone serving true real time data. Users pay your RPC bill, they don't care who the provider is. They care about price speed reliable execution. If you choose to serve them stale data, they will eventually choose to spend elsewhere.
Up to 7 seconds. 17 slots. That's how long your "fast" RPC can make you wait before the first byte of a gPA response lands. Your RPC provider is selling you latency and calling it data. While you (your users) wait: prices move, liquidations clear, pools shift, opportunities die. Your bot reacts to a data that simply no longer exists. So you (users) compensate: - Prompt or preset fatter slippage. Users pay it. - Prompt or preset higher pri fees. Users pay it. Two taxes. One root cause. A buffering RPC pretending it's a real-time. Most legacy RPCs buffer-then-flush. @FluxRPC streams decoded accounts as they're filtered. First byte in milliseconds. No 17 slot blackout. Real-time isn't a tagline. Its how it was built. It's whether your code is looking at the chain, or a screenshot. Stop paying the latency tax and stop making your users pay it. Run real-time, or get run over.
1
11
936
Flux RPC retweeted
Kind of crazy what you can build with @Rugcheckxyz API's, its a game changer. Combine that with agents, and it really opens the options and speed to market for new builders. Wouldn't be surprised to see a ton of @colosseum entrants using these and the new dexstream/data API's to get a big head start.
3
3
9
2,519
Can FluxRPC 10x your dApp too? @Rugcheckxyz likely the most relied on FREE public good on Solana needed a speed boost, and we delivered.
Big deployment live! Performance • 10x faster overall • Reports: 4s → ~100ms • Cold-starts: -90% • No more timeouts Features & fixes • Bulk reporting is back, up to 1k reports per batch • Near-realtime reports (cache drastically reduced) • Locker, Vaults & Holders display issues fixed Powered by @FluxRPC's improved gPA's & delta slots. True realtime reporting targeted within the month. Thanks for your patience.
1
2
10
979
Flux RPC retweeted
IBRL @FluxRPC is the future. Whats crazy is in some cases we return all the gPA data before other providers even respond (TTFB) Think about that for second, their TTFB lands after our TTLastByte. You're frontrunning yourself at this point.
1
6
1,602
Disclosure - this is not fair when comparing to legacy RPC's.
Forget the headline number for a (milli)sec. Yes, we beat the slowest, easy win, ignore it. Look at the rest: 6x, 6x, 9x faster. Not close. Fair comparison to legacy RPC? No. This is Lantern, local edge caching with @FluxRPC. Free add-on. Any plan. No upsell.
2
401
Flux RPC retweeted
Added in some QOL improvements into the usage dashboard for @FluxRPC Also noticed when setting up benchmarking, some RPC's limit the endpoints you can create on a free plan, we don't.
1
4
436
Flux RPC retweeted
Is this IBRL on @solana 4x faster on gPA, we didn't stop there. FluxRPC Lantern, caching at your edge, not theirs: getMultipleAccounts: 10-20x faster getAccountInfo: 10-20x faster getBalance: 10-20x faster And cheaper. Cached reads don't cost bandwidth. Faster. Cheaper. Yours. Proof 👇
3
3
11
884
Still a few days left to try the fastest RPC on @solana Yellowstone gRPC included in the $15 dev plan promotion. IBRL
1
8
1,099
Flux RPC retweeted
We have this cool add-on available with @FluxRPC its called Lantern. Its local edge caching, which improves latency & bandwidth of course. Whats also cool is we bill in bandwidth, not credits, so when you use Lantern, you save time and money. FluxRPC is already hyper fast, but when you add in Lantern, its next level.
3
2
12
2,668
Flux RPC retweeted
Ran the NYC benchmark yesterday — @FluxRPC smoked legacy Solana RPCs on getProgramAccounts. Natural question: "cool but what about EU?" Same benchmark from AMS3. Won every single run. Sometimes by 5x. Different continent. Same result. Proof 👇 (AMS3 server-side, no CDN, no averaging) Is this IBRL?
1
3
10
1,040
Flux RPC retweeted
FluxRPC just smoked legacy Solana RPCs on getProgramAccounts. 4× faster. Consistently. In many cases we return the full gPA response before competitors even hit TTFB. No distribution engine, no VC muscle... just a hackathon-winning team competing on raw performance, and winning. Proof attached. Server-side from NYC. No CDN. Same moment, same payload. @solana @fluxrpc
2
6
35
2,538