Chainstack is supporting @base Batches 🔵 Every team in the program gets the Growth plan free until 30 Nov: 20M request units a month and 250 RPS to ship on Base. @buildonbase

Full announcement ⤵️ chainstack.com/chainstack-in…

X Layer is live on Chainstack Global Nodes 🛠️ The OP Stack L2 from the @okx team. Until now it ran on Dedicated Nodes only. Now there is a shared, geo-balanced option too: → Mainnet and Testnet → Archive data included → debug_* and trace_* on paid plans → Chain ID 196, 1-second blocks Start building on @XLayerOfficial ⤵️ chainstack.com/build-better-…

Both add-ons are available on Global Nodes on every plan, Developer included. Check both in our marketplace ⤵️ chainstack.com/marketplace/ Setup, code for each chain and the full breakdown by @arorautkarshini ⤵️ chainstack.com/what-is-mev-p…

Base, Arbitrum, Arc and Robinhood Chain have no public mempool. The focus shifts to getting your tx included fast. Optimized submission sends it through a private, optimized path designed for faster inclusion. If the path fails, it goes through the node's standard route, which still isn't public ⚡

On Ethereum and BNB Smart Chain, your tx waits in a public mempool first. Bots can see it and front-run it. MEV protection sends it only through a private route to block builders. If the route fails, you get a JSON-RPC error and the tx is not broadcast to the public mempool 🛡️ Active by default on new nodes ⤵️

Your swap can be profitable for someone else before it even executes 🥪 Whether you're exposed depends on the chain: → @ethereum, @BNBCHAIN: public mempool, searchers can see your tx → @base, @arbitrum, @arc, @RobinhoodCrypto: no public mempool, different problem Chainstack has an add-on for each 🧵

Heavy reads are faster. Agave v4.3.0 with @anza_xyz, a preloaded account index and new bare-metal servers. p95 in our rollout measurements: → getProgramAccounts: 25-60s to under 2s → getTokenAccountsByOwner: up to 2 min to about 1s

Heavy scans used to starve the rest of a node. getTokenAccountsByOwner averaged 18 s while basic methods on the same node answered in 20-40 ms. Scans now run in their own pool, so light calls stay fast, and getSupply went from 2 to 300 RPS.

Why latency dropped: Solana Mainnet Global Nodes now run fully on GEN 2.0 ✨ The old stack sent every request through an edge proxy before it reached the node. In Frankfurt that layer alone added about 17 ms. GEN 2.0 removes it and routes straight to the nearest healthy region.