<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[bloXroute - Medium]]></title>
        <description><![CDATA[High-performance networking solutions to win DeFi trading. - Medium]]></description>
        <link>https://medium.com/bloxroute?source=rss----8592c799854e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>bloXroute - Medium</title>
            <link>https://medium.com/bloxroute?source=rss----8592c799854e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:43:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/bloxroute" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Base’s Azul Hard Fork Is Coming. Execution Data Is the Next Bottleneck]]></title>
            <link>https://medium.com/bloxroute/bases-azul-hard-fork-is-coming-execution-data-is-the-next-bottleneck-14572a304b9b?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/14572a304b9b</guid>
            <category><![CDATA[base]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[evm]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Tue, 12 May 2026 18:37:02 GMT</pubDate>
            <atom:updated>2026-05-12T18:37:02.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KN6H40qrrE8FAA5eTVa0Zg.png" /></figure><p>Base ships its Azul hard fork tomorrow (May 13th), bringing it closer to Ethereum mainnet equivalence.</p><p>The changes themselves are straightforward. Gas caps, precompile repricing, a new opcode, networking upgrades. Nothing here rewrites how Base works. But something else has already changed:</p><p><strong>The point in the block lifecycle where data is useful has moved earlier.</strong></p><p>Flashblocks introduced a ~200ms pre-confirmation cadence. That compresses the window in which systems can observe, decide, and act. In that environment, post-state snapshots are often too late.</p><p>To address this, we’re extending Flashblocks StateDiff to include <strong>execution logs, </strong>delivered in real time at Flashblock cadence.</p><h3>What Azul Actually Changes</h3><p>Azul is an equivalence upgrade. The relevant changes:</p><ul><li><strong>EIP-7825</strong> caps per-transaction gas at 16.7M, matching Ethereum’s per-tx gas ceiling</li><li><strong>EIP-7823 &amp; 7883</strong> adjust MODEXP limits, restricting input sizes and increasing gas costs for intensive operations</li><li><strong>EIP-7939</strong> introduces the CLZ opcode for cheaper bit-level computations in contracts</li><li><strong>EIP-7951 </strong>reprices the secp256r1 precompile to match Ethereum’s cost model</li><li>Networking moves to <strong>eth/69</strong> for improved compatibility and standardized peer communication</li></ul><p>For most applications, these are parameter updates, not behavioral shifts.</p><p>Where they <em>do</em> matter:</p><ul><li>Any system modeling gas costs needs to update assumptions</li><li>Contracts relying on MODEXP or precompiles will see execution differences</li><li>Simulation pipelines encoding constants will drift if not updated</li></ul><h3>Why State Alone Stopped Being Enough</h3><p>State diffs tell you what changed. They don’t always tell you:</p><ul><li>Which logs were emitted, and in what order</li><li>Which transaction produced a relevant event</li><li>How execution-result data maps to state changes</li><li>Whether your system needs to react before the full block is finalized</li></ul><p>That distinction used to be tolerable. With Flashblocks, it isn’t.</p><p>When your decision window is on the order of hundreds of milliseconds, the difference between “state updated” and “execution understood” is the difference between reacting in time and reacting after the opportunity is gone.</p><h3>What We’re Shipping</h3><p>We’re extending the existing Base Flashblocks StateDiff stream with a new optional include_logs parameter. When enabled, each relevant state diff update can include execution logs directly alongside the state changes.</p><p><strong>Execution logs</strong></p><ul><li>Topics</li><li>Data</li><li>block_position, representing the transaction’s actual index within the full block</li></ul><p><strong>Delivery</strong></p><ul><li>Aligned to Flashblock cadence</li><li>Available through the existing GetBdnFBTxnStateDiffStream</li><li>Compatible with existing StateDiff consumers unless they choose to enable include_logs</li><li>Supports existing address filters, so customers can scope updates to the contracts they care about</li></ul><p>This gives customers a practical way to continue accessing execution-result data after Azul without running their own node or building a separate tracing pipeline.</p><h3>Versus Running It Yourself</h3><p>You can build this stack yourself:</p><ul><li>Reth archive node with tracing</li><li>debug_traceBlock on every block</li><li>A pipeline to align traces with Flashblock updates</li><li>Enough hardware to keep latency within your decision window</li></ul><p>This gives you the data but it doesn’t necessarily give you the data at the right time.</p><p>Tracing a full block introduces delay. In practice, execution traces arrive <em>after </em>the block is built, often hundreds of milliseconds later depending on infra and load.</p><p>If your system needs to act inside the next Flashblock window, that latency is already too high.</p><p>bloXroute’s stream delivers execution logs alongside state diffs, pushed at Flashblock cadence.</p><h3>What This Unlocks</h3><p>We’re seeing teams move toward:</p><ul><li><strong>MEV / sandwich detection</strong> based on actual execution paths, not inferred state changes</li><li><strong>Simulation systems</strong> that replay real execution instead of approximating</li><li><strong>Real-time risk monitoring</strong> for lending and perps based on emitted events</li><li><strong>Routing analytics</strong> that evaluate how transactions actually traversed aggregators</li></ul><p>All of these depend on the same thing:</p><p><strong>Execution visibility inside the block, delivered fast enough to matter.</strong></p><h3>Get Access</h3><p>Start trading on Base today with a <a href="https://portal.bloxroute.com/registration">free Introductory account</a></p><p>Want to chat with a member of our team? <a href="https://bloxroute.com/book-a-meeting">https://bloxroute.com/book-a-meeting</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14572a304b9b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/bases-azul-hard-fork-is-coming-execution-data-is-the-next-bottleneck-14572a304b9b">Base’s Azul Hard Fork Is Coming. Execution Data Is the Next Bottleneck</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Shreds Premium Region]]></title>
            <link>https://medium.com/bloxroute/introducing-shreds-premium-region-8752fbd11852?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/8752fbd11852</guid>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[validator]]></category>
            <category><![CDATA[solana-network]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Thu, 16 Apr 2026 16:02:38 GMT</pubDate>
            <atom:updated>2026-04-16T16:02:38.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5i7ZvytKQeNWFwKIJAnYtw.png" /></figure><p>bloXroute is expanding its footprint on Solana by integrating with Figment’s validator infrastructure, one of the largest on the network. With this addition, bloXroute now supports validators representing over 10% of total staked SOL.</p><p>This integration strengthens bloXroute’s ability to deliver high-quality, low-latency data by connecting directly with a major source of block production.</p><p>With Figment’s validator infrastructure connected into bloXroute’s Optimized Feed Relay (OFR), customers gain faster and more reliable access to shred data as it propagates through the network.</p><h3>Shreds — Premium Region: faster, earlier access to Solana data</h3><p>bloXroute has just launched <strong>Shreds — Premium Region</strong>, designed for traders who need the earliest possible access to Solana data.</p><p>The first Shreds — Premium Region location is Toronto, powered by Figment’s validator infrastructure. This region provides direct access to high-stake shred data and some of the earliest real-time block data on the network.</p><p>Because Solana data propagates outward from validators, being closer to a major source like Figment means shreds can reach you sooner. By integrating directly with Figment and distributing data through the OFR, Shreds — Premium Region is designed to deliver earlier access compared to standard feeds.</p><h3>Built for latency-sensitive strategies</h3><p>Shreds — Premium Region is designed for:</p><ul><li>Trading bots operating in competitive environments</li><li>Searchers targeting backrun and arbitrage opportunities</li><li>Trading firms competing on execution speed</li><li>Market makers reconstructing order flow in real time</li></ul><p>For these participants, small differences in when data is received can translate directly into improved execution outcomes.</p><h3>What this unlocks</h3><p>With Shreds — Premium Region in Toronto, customers can expect:</p><ul><li>Earlier access to Figment-sourced shred data</li><li>Less delay between when shreds are produced and when you receive them</li><li>More consistent performance during periods of network congestion</li></ul><p>This is the first step in a broader rollout. bloXroute plans to expand Shreds — Premium Region to additional regions with concentrated validator presence over time.</p><h3>Get access</h3><p><a href="https://calendly.com/d/ckmt-64s-qd8/meeting-with-bloxroute">Meet with our team</a> to get set up with Shreds — Premium Region and start receiving shreds faster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8752fbd11852" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/introducing-shreds-premium-region-8752fbd11852">Introducing Shreds Premium Region</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing BSC Speed Boost]]></title>
            <link>https://medium.com/bloxroute/introducing-bsc-speed-boost-a361748c4aaf?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/a361748c4aaf</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[bsc]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Mon, 13 Apr 2026 16:56:14 GMT</pubDate>
            <atom:updated>2026-04-13T16:56:14.866Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4aUOkQxvCPbFCCwM8IHltw.png" /></figure><p><strong>BSC Speed Boost is the fastest way to reach all builders on BSC.</strong></p><p>It accelerates transaction and bundle propagation using bloXroute’s global BDN and private datacenter links, giving you a measurable edge in how quickly your flow reaches builders.</p><p>On BSC, that edge is increasingly important.</p><p>Block times are currently ~450 ms and expected to decrease further, shrinking the window to get transactions in front of builders.</p><p>And the impact is not theoretical. In our benchmarks, we see <strong>up to 40% faster delivery and ~94 ms saved</strong> on key routes.</p><h3>What BSC Speed Boost Does</h3><p>BSC Speed Boost optimizes the most overlooked part of execution:</p><p><strong>Propagation from you → to all relevant builders</strong></p><p>Instead of relying on public routing or stitching together multiple direct connections, bloXroute:</p><ul><li>Routes transactions through its global BDN</li><li>Uses private, low-latency datacenter links</li><li>Dynamically selects the fastest path per region</li></ul><p>This results in:</p><ul><li>Faster delivery to builders</li><li>Simultaneous delivery across major builder endpoints</li><li>Better relative ordering vs. competing flow</li></ul><p>In many cases, particularly across regions, this outperforms sending directly to builders yourself.</p><h3>Where Routing Optimization Delivers the Most Impact</h3><p>Methodology (simplified):</p><ul><li>Latency measured from cloud API entry points to bloXroute-hosted builder endpoints across multiple regions</li><li>“Direct” reflects standard routing from cloud infrastructure</li><li>“Via bloXroute” reflects optimized routing through the BDN and private network paths</li></ul><p>This benchmark focuses on routes where we can precisely measure end-to-end latency. While BSC Speed Boost distributes to a broader set of builders, these results use bloXroute-hosted endpoints as a consistent and verifiable baseline.</p><h3>Benchmark Results</h3><p>Here’s a simplified view of the benchmark data across major regions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*aafrS4P1Xpm5a-Py8zB_7w.png" /></figure><p>These examples highlight routes where routing optimization provides a clear advantage.</p><p>Not all paths benefit equally. If a route is already near-optimal via direct connectivity, improvements may be minimal or non-existent.</p><h3>Key Takeaways</h3><ul><li>Up to 94 ms saved (~40%) on long-distance routes</li><li>Consistent gains on cross-region routes, including intra-US and intra-Europe paths where routing is suboptimal</li><li>Largest improvements on Asia ↔ Europe and Asia ↔ US paths, where public internet routing is typically least efficient</li><li>In some cases, such as certain routes to Japan, direct paths are already optimal, and no meaningful improvement is observed</li><li>Meaningful edge even at low latency, where single-digit milliseconds matter</li></ul><h3>What This Means in Practice</h3><p>With BSC Speed Boost:</p><ul><li>Your transactions reach builders earlier in the block construction window, which is shrinking as block times decrease</li><li>Your bundles are more competitive in ordering</li><li>You reduce the risk of being outpaced on latency-sensitive routes</li></ul><p>In competitive environments, even tens of milliseconds can materially impact ordering and inclusion outcomes.</p><h3>Get Started</h3><p>⚡ <a href="https://portal.bloxroute.com/login"><strong>Enable BSC Speed Boost in the portal</strong></a></p><p>💬 <a href="https://calendly.com/d/ckmt-64s-qd8/meeting-with-bloxroute"><strong>Talk to our team to optimize your setup</strong></a></p><p>If you are already optimizing strategy and execution, this is the layer that ensures your transactions actually land first.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a361748c4aaf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/introducing-bsc-speed-boost-a361748c4aaf">Introducing BSC Speed Boost</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 ways top traders optimize transaction sending on Solana]]></title>
            <link>https://medium.com/bloxroute/5-ways-top-traders-optimize-transaction-sending-on-solana-84caaf5b7220?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/84caaf5b7220</guid>
            <category><![CDATA[crypto-trading]]></category>
            <category><![CDATA[solana-network]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[transactions]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 17:56:30 GMT</pubDate>
            <atom:updated>2026-04-07T17:56:30.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qsZYstZ88Sw2YOVfzbnZ0A.jpeg" /></figure><p>Getting transactions right on Solana is harder than it looks.</p><p>Most issues we see aren’t about strategy, they’re about <strong>execution details</strong>.</p><p>bloXroute’s Trader API is designed to help with that. But it works best when it’s treated as part of your execution pipeline, not just another endpoint.</p><p>Here are five patterns we often see:</p><h3>1) Not optimizing for physical location</h3><p>Latency on Solana is real.</p><p>If you’re trading from Frankfurt but hitting New York infra, you’re already behind.</p><p>Serious traders:</p><ul><li>Test across regions</li><li>Co-locate when possible</li><li>Optimize end-to-end latency (not just submission)</li></ul><p>Milliseconds matter <em>before </em>your transaction even enters the network.</p><h3>2) Thinking faster submission = guaranteed landing</h3><p>Speed helps, but landing depends on more than arrival time.</p><p>We regularly see fast transactions lose to slower, better-structured ones.</p><p>That means:</p><ul><li>Competitive priority fees</li><li>Strong propagation strategy</li><li>Proper compute budget configuration</li><li>Fresh blockhash timing</li></ul><p>These often beat transactions that were simply sent earlier.</p><h3>3) Duplicate submissions without safeguards (durable nonce)</h3><p>Many traders send the same transaction through multiple paths to increase landing probability.</p><p>That can work, but if you re-sign each submission (e.g. different blockhashes), you’re creating <em>different transactions</em>.</p><p>Different signatures = multiple executions → extra fees → slippage → unintended positions</p><p>One way to prevent this: use a shared durable nonce across submissions.</p><p>Only one transaction can consume the nonce. The rest automatically fail.</p><h3>4) Not tuning fees for the situation</h3><p>Two key levers:</p><ul><li><strong>bloXroute tip</strong>: influences propagation + bundle priority</li><li><strong>Priority fee</strong>: influences sequencing on-chain</li></ul><p>Priority fees matter most in contested scenarios (e.g. same-slot competition, sniping).</p><p>If these aren’t tuned based on conditions, landing probability drops.</p><h3>5) Execution issues vs infra issues</h3><p>Not every failed transaction is an infra problem.</p><p>Common causes:</p><ul><li>Program-specific errors</li><li>Parameter issues</li><li>Timing assumptions</li></ul><p>bloXroute can get your transaction to the leader faster but it doesn’t fix what happens after it arrives.</p><h3>The takeaway</h3><p>On Solana, execution quality matters as much as strategy.</p><p>Small details like fee configuration, submission paths, and latency can meaningfully impact outcomes.</p><p>Treat your transaction pipeline as something to design and test, not just something to plug in.</p><p>If you’re building or trading on Solana and want to improve landing consistency:</p><ul><li><a href="https://portal.bloxroute.com/registration">Try the Trader API</a> (free tier is live)</li><li>Or <a href="http://calendly.com/d/ckmt-64s-qd8/meeting-with-bloxroute">reach out</a> to talk strategy with a member of our team</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84caaf5b7220" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/5-ways-top-traders-optimize-transaction-sending-on-solana-84caaf5b7220">5 ways top traders optimize transaction sending on Solana</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Built to Scale: bloXroute’s New Pricing Model]]></title>
            <link>https://medium.com/bloxroute/built-to-scale-bloxroutes-new-pricing-model-d06f84d3600c?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/d06f84d3600c</guid>
            <category><![CDATA[solana-network]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[binance-smart-chain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Tue, 17 Mar 2026 15:50:50 GMT</pubDate>
            <atom:updated>2026-03-17T15:50:50.515Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gjWmC0F51c1B2dqqwaP0Q.png" /></figure><p>Pricing should adapt to teams, not the other way around.</p><p>As trading strategies evolve and activity becomes increasingly multi-chain, rigid subscription tiers stop making sense. Teams don’t scale in straight lines; they experiment and optimize with service credits and capabilities. Your cost structure should reflect that reality.</p><p>Today, we’re introducing a new pricing model designed around how teams actually operate: <strong>modular services, flexible configurations, </strong>and <strong>predictable savings.</strong></p><h3>The Vision: Flexible, Predictable, Scalable</h3><p>Over the years, we’ve worked with traders, searchers, validators, and high-performance teams operating across Ethereum, BSC, Base, Solana, and more. One pattern is clear:</p><blockquote><em>Teams do not scale by moving from one service tier to the next. They scale by adding modular capabilities.</em></blockquote><p>Rigid subscription tiers force customers into pre-packaged quantities that rarely match real usage. As teams become more sophisticated, fixed bundles begin to break:</p><ul><li>You need more mempool capacity, but not more gateways.</li><li>You need Solana data, but not expanded EVM tracing.</li><li>You want to experiment on Base without restructuring your entire plan.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EOn8Ynslhdk_U3gw8UpFbQ.png" /></figure><p><strong>What’s different</strong></p><ul><li>More flexibility. Select only the services you need, per chain.</li><li>More control. Add, remove, or modify services directly in the portal.</li><li>More predictability. Extend your contract term to lock in discounted pricing.</li></ul><p><strong>What stays the same</strong></p><ul><li>Ultra-low latency performance</li><li>Reliable propagation and data delivery</li><li>Access to the bloXroute BDN across supported chains</li></ul><p>This is not a change to performance or reliability. It’s a change to how you configure and pay for it.</p><h3>What’s Changing</h3><h4><strong>1. From Tiers to Services</strong></h4><p>We are shifting from subscription-based tiers to a modular services model.</p><p>Previously, customers selected a bundle (e.g., Enterprise, Elite, Ultra) that grouped multiple services together at fixed quantities. Now, you can configure your infrastructure stack directly:</p><ul><li>Add a Gateway for transaction propagation</li><li>Subscribe to Mempool, Blocks, or Receipts streams</li><li>Enable Base Flashblocks or state diff streams</li><li>Increase Solana Trader API capacity</li><li>Add tracing, simulations, or private regional routing</li></ul><p>You build the stack that fits your strategy, not the other way around.</p><p>For teams that prefer simplicity, our Enterprise, Elite, and Ultra bundles still exist. These curated packages combine high-demand services at significant cost savings compared to purchasing individually. If a bundled approach fits your needs, those options remain available.</p><p>You can view the available bundles and full service catalog here:</p><p><a href="https://bloxroute.com/pricing/"><strong>https://bloxroute.com/pricing/</strong></a></p><p><strong>2. Free Transactions on All Supported Chains</strong></p><p>All users can now send transactions on supported chains at no base cost.</p><ul><li>Standard network fees and validator tips still apply.</li><li>Solana Trader API rate limits still apply based on your plan and add-ons, with optional capacity upgrades available.</li></ul><p>This allows anyone to start building immediately, then layer in additional performance and data services as their needs grow.</p><p>At time of launch, bloXroute supports eight (8) chains: Solana, BSC, Base, Ethereum, Hyperliquid, Monad, TON, and X Layer.</p><p><strong>3. Term-Based Savings</strong></p><p>For teams that value cost savings and predictability, we’ve introduced commitment-based discounts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*1mr010i1tr8lzHVrQyH_Qw.png" /></figure><p>Extend your contract term to reduce your effective monthly cost, lock in pricing, and improve budget predictability.</p><p>Short-term flexibility remains available. Long-term commitment unlocks additional savings.</p><h3>What This Means for Existing Customers</h3><p>If you’re currently on an Enterprise, Elite, or Ultra subscription:</p><ul><li>Your subscription will be recreated as a service bundle.</li><li>There will be no price increase.</li><li>There will be no service disruption.</li></ul><p>Your access, performance, and capacity remain unchanged. You can now add or modify services directly within the portal. Existing subscriptions include special bundle pricing, so modifying core services may affect pricing.</p><p>For Professional tier customers, your services will be recreated in the portal. This bundle will not be offered in the future, but there are no immediate changes. At renewal, you can continue a-la-carte or modify your services as needed.</p><p>If you would like help optimizing your setup under the new model, our team is happy to assist.</p><h3>Why This Matters</h3><p>Modern blockchain infrastructure is multi-chain, latency-sensitive, and increasingly specialized.</p><p>Your cost structure should evolve with it.</p><p>This update gives you:</p><ul><li>Modular control</li><li>Transparent pricing</li><li>Commitment-based savings</li><li>The same performance and reliability you depend on</li></ul><p>A model built to scale with your strategy.</p><h3>Get Started</h3><p>Explore the new model and configure your services: <a href="https://portal.bloxroute.com/login"><strong>https://portal.bloxroute.com/login</strong></a></p><p>Want help designing the right setup? <a href="https://bloxroute.com/products/lets-chat/"><strong>Let our BD team assist you.</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d06f84d3600c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/built-to-scale-bloxroutes-new-pricing-model-d06f84d3600c">Built to Scale: bloXroute’s New Pricing Model</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Benchmarking BSC Block Discovery: bloXroute vs. BlockRazor (Frankfurt)]]></title>
            <link>https://medium.com/bloxroute/benchmarking-bsc-block-discovery-bloxroute-vs-blockrazor-frankfurt-66068ba78220?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/66068ba78220</guid>
            <category><![CDATA[mev]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[binance-smart-chain]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Fri, 27 Feb 2026 00:56:56 GMT</pubDate>
            <atom:updated>2026-02-27T00:56:56.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-GG07BWPMcAcOAemeYQaqw.jpeg" /></figure><p>Trading on BNB Smart Chain is brutally competitive. If your infrastructure lags even a few milliseconds, you lose edge.</p><p>Most teams obsess over mempool speed — but <strong>block discovery</strong> is just as important. New blocks are the canonical truth: state changes, newly confirmed opportunities, and the final outcome of everything that happened in the public mempool, along with all private transactions and bundles. If you see the next block late, you’re reacting late.</p><p>We benchmarked <strong>bloXroute’s bdnBlocks stream</strong> against <strong>BlockRazor’s NewBlocks stream</strong> in Frankfurt. The results show that bloXroute consistently outperforms on block discovery and propagation in Frankfurt. Below is our testing methodology and what we observed.</p><h3>Why block discovery speed matters for searchers</h3><p>On BSC, blocks arrive roughly every ~450ms. That’s fast enough that even “small” delays are meaningful.</p><p>Seeing a new block first helps you:</p><ul><li>Update internal state faster (balances, pool reserves, nonce expectations)</li><li>React sooner to newly confirmed arbitrage / liquidity conditions</li><li>Reduce stale assumptions in your simulation pipeline</li><li>Build and submit follow-up actions earlier in the next block window</li></ul><p>In practice: <strong>late block awareness becomes late decision-making</strong>, and late decision-making becomes lost edge.</p><h3>Benchmark setup</h3><p>We designed this benchmark to mirror what a real searcher cares about: <strong>which feed delivers the full block first</strong> to a consumer in-region.</p><p><strong>Streams compared in Frankfort region</strong></p><ul><li><strong>bloXroute:</strong> bdnBlocks</li><li><strong>BlockRazor:</strong> NewBlocks</li></ul><p><strong>Fairness controls</strong></p><ul><li>Both streams consumed from the <strong>same server / same machine</strong></li><li>Same region (Frankfurt)</li><li>Same timestamping and comparison logic</li><li>Same observation window: <strong>7 days</strong></li><li><strong>All blocks in the period</strong> included (no sampling)</li></ul><h3>Results: Overall win rate in Frankfurt</h3><p>Across the 7-day window between 2026–02–18 00:00:00 and 2026–02–25 00:00:00:</p><p><strong>bloXroute delivered 76.6% of blocks first.</strong></p><p>We measured the arrival-time difference between streams (in milliseconds) for blocks where one side won.</p><h3>When bloXroute wins (arrival-time advantage)</h3><ul><li><strong>P10:</strong> 0.73 ms</li><li><strong>P50:</strong> 4.01 ms</li><li><strong>P90:</strong> 11.50 ms</li></ul><p>Interpretation:</p><ul><li>In a typical win (median), bloXroute is ahead by ~<strong>4ms</strong></li><li>In the faster-tail wins, bloXroute is ahead by <strong>10ms+</strong></li><li>Those margins are large enough to change ordering and outcomes for time-sensitive strategies</li></ul><h3>When BlockRazor wins (arrival-time advantage)</h3><ul><li><strong>P10:</strong> 0.02 ms</li><li><strong>P50:</strong> 2.38 ms</li><li><strong>P90:</strong> 5.94 ms</li></ul><p>Interpretation:</p><ul><li>Even when BlockRazor wins, the margin is generally <strong>smaller</strong></li><li>bloXroute’s advantage is both <strong>more frequent</strong> and <strong>more decisive</strong></li></ul><h3>What this means in practice for BSC searchers</h3><p>This benchmark points to two practical implications:</p><h4>1) You see more blocks first</h4><p>Seeing <strong>~3 out of every 4 blocks first</strong> compounds quickly over a trading day. Even if your strategy only depends on “being earliest” some of the time, more frequent first delivery translates into more first-mover windows.</p><h4>2) When you win, you win by enough to matter</h4><p>A 1–2ms lead is nice. A 4–12ms lead is <strong>decisive</strong> — especially on BSC where downstream processing (decode → simulate → decide → submit) already consumes time. A consistent multi-millisecond head start gives your pipeline more room to operate before the next block cutoff.</p><h3>Upgrade your block discovery</h3><p>If your strategy depends on being first, your infrastructure should too.</p><p><a href="https://portal.bloxroute.com/registration">Upgrade your BSC block discovery</a> with bloXroute and give your simulation and submission pipeline the head start it needs.</p><p>To chat with our team, feel free to<a href="https://calendly.com/d/ckmt-64s-qd8/meeting-with-bloxroute"> book a meeting</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66068ba78220" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/benchmarking-bsc-block-discovery-bloxroute-vs-blockrazor-frankfurt-66068ba78220">Benchmarking BSC Block Discovery: bloXroute vs. BlockRazor (Frankfurt)</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monad, Hyperliquid, and X Layer Support Added]]></title>
            <link>https://medium.com/bloxroute/monad-hyperliquid-and-x-layer-support-added-d780b5945019?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/d780b5945019</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[hyperlink]]></category>
            <category><![CDATA[monads]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Mon, 22 Dec 2025 20:33:03 GMT</pubDate>
            <atom:updated>2025-12-22T20:33:02.110Z</atom:updated>
            <content:encoded><![CDATA[<p>Expanding Connectivity Across Eight Chains</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HcpMGBL_t5eJ4xcn5d9mw.png" /></figure><p>At bloXroute, our focus has always been on enabling <em>faster, more reliable transaction propagation and blockchain data. </em>Our low-latency BDN has become essential infra for teams, whether they’re running trading bots, optimizing MEV strategies, or sending transactions where milliseconds matter.</p><p>As new trading environments emerge, we move fast — delivering speed and reliability from day one.</p><p>We’re excited to announce support for <strong>Monad, Hyperliquid, and X Layer</strong>, bringing bloXroute’s total set of supported chains to eight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3y6sErodhXzOigfAa5jC6Q.png" /></figure><h3>Built for a Multi-Chain World</h3><p>Crypto is expanding into new execution environments, but each chain introduces its own challenges:</p><ul><li>Different propagation paths</li><li>Different mempool architectures</li><li>Different congestion patterns</li><li>Different execution models</li></ul><p>bloXroute addresses this with a unified, latency-optimized infrastructure that provides:</p><ul><li><strong>Ultra-low-latency transaction propagation</strong> through our high-performance BDN</li><li><strong>Reliable, real-time data streams</strong> designed for trading bots, wallets, and dApps</li><li><strong>Consistent landing performance</strong>, even during high-volatility or high-congestion conditions</li></ul><p>Adding Monad, Hyperliquid, and X Layer extends that same performance standard to more of the networks driving today’s onchain activity.</p><h3>Why These Chains Matter</h3><p><strong>Monad — High-Performance Parallel EVM<br></strong>Monad is built for speed and parallel execution. bloXroute helps ensure transaction delivery keeps up, giving execution-sensitive strategies a faster, more predictable path.</p><p><strong>Hyperliquid — Ultra-Fast Onchain Perpetuals<br></strong>Hyperliquid has raised the bar for onchain trading speed. bloXroute supports that environment with rapid transaction propagation, helping traders and automated systems stay competitive.</p><p><strong>X Layer — Scaling L2 Trading and DeFi<br></strong>As activity ramps on X Layer, bloXroute provides the infrastructure needed to support users. Faster propagation translates directly into better execution and UX.</p><h3>What’s Next</h3><p>Eight supported chains is another step toward connectivity and reliable performance in an increasingly fragmented environment. As these networks evolve, we’ll continue expanding services alongside them.</p><p>If you’re building a trading bot, running infrastructure, or looking for faster transaction delivery across chains, we’d love to talk.</p><p>📩 <a href="https://t.me/BaleyGabel_bloXroute">DM Baley Gabel on Telegram</a></p><p>📲 <a href="https://calendly.com/d/ckmt-64s-qd8/meeting-with-bloxroute">Book a call with our team</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d780b5945019" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/monad-hyperliquid-and-x-layer-support-added-d780b5945019">Monad, Hyperliquid, and X Layer Support Added</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A New Era of MEV on Solana]]></title>
            <link>https://medium.com/bloxroute/a-new-era-of-mev-on-solana-ae5cff390b71?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/ae5cff390b71</guid>
            <category><![CDATA[mev]]></category>
            <category><![CDATA[solana-network]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[solana-blockchain]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Wed, 22 Oct 2025 18:37:09 GMT</pubDate>
            <atom:updated>2025-10-22T18:37:05.266Z</atom:updated>
            <content:encoded><![CDATA[<p>By Daniel Tao @ bloXroute Labs</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*da35Uftx-yRWmq1ZJNp-OA.png" /></figure><p>Solana’s MEV landscape has entered a new phase — one where <strong>malicious validators</strong> rather than external bots have taken center stage. For over a year, MEV protection relied heavily on <strong>Jito bundles</strong>, which enforced “do-not-front-run” rules through trusted relays.</p><p>But recent data shows this approach is no longer enough. According to Ghost’s year-long analysis of Solana trades, <strong>wide (multi-slot) sandwiches</strong> — attacks where the frontrun and backrun occur across <em>different leader slots</em> — have exploded in prevalence, accounting for <strong>93% of all sandwiches</strong> and extracting over <strong>529,000 SOL</strong> in the past year.</p><p>These attacks evade traditional single-slot detectors and exploit validator-led control over transaction ordering. In other words, MEV has moved from the mempool to the validator set.</p><h3>What changed under the hood</h3><p>To meet this new threat model, bloXroute’s <strong>Solana Trader API</strong> introduces a <strong>multi-path, leader-aware submission system</strong> designed to adapt in real time to changing validator risk conditions</p><h4>🔹 Leader-aware MEV protection</h4><p>Our infrastructure now <strong>scores current and upcoming slot leaders in real time</strong>, identifying validators with an elevated risk of malicious ordering.</p><ul><li><strong>High-risk leaders</strong> (identified through sandwich correlations and validator behavior analytics) are delayed or skipped.</li><li><strong>Low-risk leaders</strong> receive accelerated submission through <strong>staked connections</strong>, improving both <em>protection</em> and <em>time-to-land</em>.</li></ul><p>This dynamic scheduling improves both <em>safety</em> (avoiding predatory slots) and <em>speed-to-land</em> during trustworthy leadership periods.</p><h4>🔹 Multi-path frontRunningProtection (FRP)</h4><p>Instead of depending solely on Jito relays, <em>frontRunningProtection=true</em> now routes transactions via <strong>Jito + Paladin + bloXroute’s propagation channels</strong>. This ensures redundancy and mitigates bundle-leak risk, especially against leaders suspected of colluding with attackers.</p><h4>🔹 Integrated submitProtection tiers</h4><p>FRP now defaults to <em>SP_MEDIUM</em> for balanced protection and speed, while <em>SP_HIGH</em> provides stricter ordering and landing safeguards.</p><h4>🔹 Optional revertProtection</h4><p>Enable <em>revertProtection=true</em> to prevent failed transactions from landing on-chain — useful for atomic or conditional strategies, though it introduces latency.</p><h3>The reason: validator-run sandwiching is the new frontier</h3><p>The shift to <strong>leader-controlled MEV extraction</strong> represents a structural change in Solana’s risk surface. The <em>Malicious Validator Sandwich Behaviors</em> research brief highlights several emerging tactics:</p><ul><li><strong>Cross-slot sandwiches</strong>, where attackers use multiple consecutive leadership slots to spread attack legs. This has quickly surged from a rare case to the most common sandwich attack pattern. Aligning with Ghost’s finding that 93% of current sandwiches are wide sandwiches.</li><li><strong>Authority-hop and passthrough attacks</strong>, where SPL token account ownership temporarily changes hands to obscure attacker identity.</li><li><strong>Bundle-leak exploitation</strong>, where pending transactions visible in relays are used to pre-position frontruns in the next slot.</li></ul><p>These behaviors exploit validator-level privileges that traditional relay-only systems (like Jito bundles) cannot fully mitigate.</p><h3>Why leader-aware routing matters</h3><p>Traditional MEV protection assumed all leaders were equal — but data shows that <strong>a handful of validators</strong> account for a disproportionate share of sandwich activity.</p><p>By integrating <strong>leader scoring</strong> directly into the transaction routing process, bloXroute ensures that orderflow dynamically avoids these high-risk slots, reducing the chance of being sandwiched by malicious leaders.</p><p>This approach strikes a new balance between:</p><ul><li><strong>Leakage risk reduction</strong> — Avoiding validators known to reorder or duplicate transactions.</li><li><strong>Time-to-finality optimization</strong> — Accelerating landing during low-risk leadership.</li></ul><h3>Deprecations and migration notes</h3><p>As part of this rollout (effective <strong>October 23, 2025, 14:00 ET</strong>):</p><ul><li><em>fastBestEffort </em>mode is deprecated; calls using it will default to <em>frontRunningProtection</em>.</li><li>Existing users should verify their <em>submitProtection</em> tier and enable <em>revertProtection</em> only when needed.</li></ul><p>Example payload:</p><blockquote>{</blockquote><blockquote>“frontRunningProtection”: true,</blockquote><blockquote>“submitProtection”: “SP_MEDIUM”,</blockquote><blockquote>“revertProtection”: false</blockquote><blockquote>}</blockquote><h3>Looking forward</h3><p>The rise of validator-run MEV extraction underscores a fundamental truth: <strong>attackers evolve with the protocol.</strong></p><p>bloXroute’s leader-aware and multi-path submission framework represents the next generation of MEV protection — one that no longer assumes trust in any single relay or validator set.</p><p>As the network continues to decentralize, our focus remains constant:<br> to deliver <strong>fair, efficient, and secure transaction landing</strong> for traders and protocols across Solana.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae5cff390b71" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/a-new-era-of-mev-on-solana-ae5cff390b71">A New Era of MEV on Solana</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Base Transaction Speed Benchmarks]]></title>
            <link>https://medium.com/bloxroute/base-transaction-speed-benchmarks-d39e4b20c584?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/d39e4b20c584</guid>
            <category><![CDATA[base]]></category>
            <category><![CDATA[mev]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Thu, 16 Oct 2025 22:29:17 GMT</pubDate>
            <atom:updated>2025-10-16T22:29:13.513Z</atom:updated>
            <content:encoded><![CDATA[<h3>bloXroute Global Endpoint vs Public Endpoints &amp; Cloud API</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8FU8S_TiHRXmMri60G7RyA.png" /></figure><p>Trading on Base happens in milliseconds and every millisecond counts.</p><p>With the Base sequencer currently centralized and traders operating from different regions around the world, network latency becomes a key performance differentiator.</p><p>To measure the real-world advantage of bloXroute’s optimized networking layer, we benchmarked the bloXroute Global Endpoint (premium endpoint with a per-tx cost) against:</p><ul><li>Base Public Endpoint</li><li>Base Preconf Endpoint</li><li>bloXroute Cloud API (regional endpoint, free to use)</li></ul><p>Our tests show that for regions far from the sequencer the Global Endpoint consistently outperforms all alternatives — achieving higher landing rates and better block positioning. This is especially important for regions like Tokyo that are closed to Binance exchange.</p><h3>Benchmark Setup</h3><p>All benchmarks were conducted from the same machine in <strong>Tokyo </strong>during <strong>October 2025</strong>, with sub-2 ms latency to both Base and bloXroute endpoints. All transactions in the tests were sent with the same gas prices.</p><p>Each test sent identical transactions simultaneously through two endpoints and compared:</p><ul><li><strong>Landing Rate</strong> (transactions included on-chain)</li><li><strong>Win Rate</strong> (which endpoint’s transaction landed first)</li><li><strong>Block Position Diffs</strong> (p50/p75/p90)</li></ul><p>All three tests were run independently but are presented in a single table. The number of transaction batches (i.e. “races”) per test and the setup pings are listed below:</p><ul><li><strong>Global Endpoint vs Cloud API:</strong> 2 ms ping to Global Endpoint, 1.8 ms to Cloud API</li><li><strong>Global Endpoint vs Base Preconf Endpoint:</strong> 1.7–1.8 ms to Global Endpoint, 1.6–2.5 ms to Base Preconf (0.25 ms delay added to Global Endpoint during the test to normalize for RTT differential)</li><li><strong>Global Endpoint vs Base Public Endpoint:</strong> 1.75 ms to Global Endpoint, 1.75 ms to Base Public</li></ul><h3>Results</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/767/1*PkmXSdxAmSG2SzXub0r3uA.png" /></figure><p>Across all benchmarks, the bloXroute Global Endpoint <strong>consistently outperformed</strong> every alternative, winning 100% of races against both the Cloud API and Base Preconf and ~99% against the Base Public endpoint.</p><p>Even with identical gas prices and near-identical latency, Global Endpoint transactions were included first in nearly every case, maintaining <strong>p50 and p75 block positions of 1 </strong>across all tests.</p><h3>Conclusion</h3><p>These benchmarks show a clear pattern: bloXroute’s Global Endpoint provides the fastest, most reliable path to the Base sequencer, consistently outperforming both public and regional endpoints.</p><p>For traders and searchers, this means:</p><ul><li><strong>Higher inclusion probability</strong> as latency to sequencer is optimized</li><li><strong>Earlier block positions</strong>, improving MEV and order execution outcomes</li><li><strong>Reduced latency variance</strong>, with predictable global performance</li></ul><p>As Base continues to attract high-frequency trading and MEV activity, every millisecond matters. bloXroute’s Global Endpoint minimizes latency across regions, giving users the lowest possible time-to-sequencer and a tangible performance edge.</p><p>To learn more about our Base offerings:</p><p>🌐 <a href="https://docs.bloxroute.com/base-network/submit-transactions/global-endpoint">Visit the docs</a></p><p>📅 <a href="https://calendly.com/d/ckmt-64s-qd8/meeting-with-bloxroute">Book a demo with the bloXroute team</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d39e4b20c584" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/base-transaction-speed-benchmarks-d39e4b20c584">Base Transaction Speed Benchmarks</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trade Faster on Base with bloXroute]]></title>
            <link>https://medium.com/bloxroute/trade-faster-on-base-with-bloxroute-9e5b869aaecb?source=rss----8592c799854e---4</link>
            <guid isPermaLink="false">https://medium.com/p/9e5b869aaecb</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[base]]></category>
            <dc:creator><![CDATA[bloXroute Team]]></dc:creator>
            <pubDate>Thu, 18 Sep 2025 19:03:30 GMT</pubDate>
            <atom:updated>2025-09-18T19:03:18.506Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yMIwFR9xiPYZksGjaviyFg.png" /></figure><p>Base is one of the fastest-growing ecosystems in crypto and is becoming increasingly competitive for traders, searchers, and builders. Whether you’re chasing MEV, arbitrage, liquidations, or simply need reliable inclusion, the edge comes down to two things:</p><p>🔍 Earlier visibility into blocks<br>⚡ Faster, more reliable transaction submission</p><p>bloXroute gives you both. We now support <strong>four real-time Base streams</strong> and <strong>two powerful submission endpoints</strong> to help you trade at the speed of the sequencer.</p><p>Here’s a quick overview of everything available on Base today:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ucz9pfdhABsEiB8ma89fnQ.png" /></figure><p>Now, let’s dive into the details 👇</p><h3>Streams: See Base Data in Real Time</h3><p>Our streams deliver low-latency access to Base block content, from finalized blocks to the earliest pre-confirmations.</p><h4>1. GetBdnFbTxnsStateDiff (NEW)</h4><p><em>Full state diffs + logs for all transactions in Flashblocks, streamed in real-time.</em></p><ul><li>Unlike standard tracing (available only after full block finalization ~2s), this stream delivers state diffs in ~200ms increments as Flashblocks are processed</li><li>Tracing-node level visibility without running costly infra</li><li>Perfect for MEV simulations, protocol monitoring, and analytics</li><li>Available via WebSocket + gRPC</li></ul><p>📃<strong> Docs:</strong> <a href="https://docs.bloxroute.com/base-network/base-streams/getbdnfbtxnstatediffstream">GetBdnFbTxnsStateDiff</a></p><p><strong>🎯 Availability:</strong> Enterprise Elite and Ultra users.</p><h4>2. GetBdnBlockStream</h4><p><em>Stream the latest Base blocks (headers + bodies) as they’re produced on the network.</em></p><ul><li>Real-time gRPC stream</li><li>Full block headers and bodies (including transactions)</li><li>Ideal for searchers, indexers, and latency-sensitive applications</li></ul><p>📃 <strong>Docs:</strong> <a href="https://docs.bloxroute.com/base-network/base-streams/getbdnblockstream">GetBdnBlockStream</a></p><p><strong>🎯 Availability:</strong> All user tiers.</p><h4>3. GetBdnFlashBlockStream</h4><p><em>Raw pre-confirmation blocks streamed directly by the Base sequencer every ~200ms.</em></p><ul><li>See block data before it’s finalized on-chain</li><li>Act earlier on MEV, arbs, and liquidations</li><li>Preload/index data to cut latency</li></ul><p>📃 <strong>Docs:</strong> <a href="https://docs.bloxroute.com/base-network/base-streams/getbdnflashblockstream">GetBdnFlashBlockStream</a></p><p><strong>🎯 Availability:</strong> Enterprise Elite and Ultra users.</p><h4>4. GetParsedBdnFlashBlockStream</h4><p><em>The same Flashblocks data, delivered parsed and ready-to-use.</em></p><ul><li>Available via WebSocket or gRPC</li><li>Saves time decoding raw data</li><li>Simplifies integration into trading stacks</li></ul><p><strong>📃 Docs: </strong><a href="https://docs.bloxroute.com/base-network/base-streams/getparsedbdnflashblockstream">GetParsedBdnFlashBlockStream</a></p><p><strong>🎯 Availability:</strong> Enterprise Elite and Ultra users.</p><h3>Submit Transactions: Land Faster on Base</h3><p>Seeing data early is only half the battle; you also need to get your transactions included faster and more reliably. bloXroute offers two ways to submit on Base.</p><h4>1. Standard Submission Endpoint</h4><p><em>Submit transactions via bloXroute’s Blockchain Distribution Network (BDN) for fast, redundant delivery.</em></p><ul><li>Supports WebSocket and HTTPS POST</li><li>Automatically enrolls transactions in Backrunme (earn shared backrunning rewards when you set a reward address)</li></ul><p>📃 <strong>Docs:</strong> <a href="https://docs.bloxroute.com/base-network/submit-transactions">Submit Transactions</a></p><p><strong>🎯 Availability:</strong> All user tiers.</p><h4>2. Global Submission Endpoint</h4><p><em>The fastest way to land transactions on Base.</em></p><ul><li>One endpoint for all regions; no need to manage routing</li><li>Aligns submissions with Flashblock’s ~200ms cadence</li><li>Uses bloXroute’s BDN for the fastest and most reliable path</li></ul><p>Requirement: Minimum tip of 0.00008 ETH per transaction (sent to 0x00D5c43e68FB37D3761A5688D3B705A2Bdc4BC9D).</p><p>📃 <strong>Docs:</strong> <a href="https://docs.bloxroute.com/base-network/submit-transactions/global-endpoint">Global Submission Endpoint</a></p><p><strong>🎯 Availability:</strong> All user tiers.</p><h3>Get Started Today</h3><p>bloXroute gives Base traders, builders, and validators the edge they need to win. Get started with a <a href="https://portal.bloxroute.com/registration">free Introductory account</a>.</p><p>📆 To learn more about Enterprise Elite and Ultra access, <a href="https://calendly.com/d/ckmt-64s-qd8/meeting-with-bloxroute">schedule a call</a> with the bloXroute team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e5b869aaecb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bloxroute/trade-faster-on-base-with-bloxroute-9e5b869aaecb">Trade Faster on Base with bloXroute</a> was originally published in <a href="https://medium.com/bloxroute">bloXroute</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>