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…

Neither replaces your contract checks. Private routing doesn't fix a loose slippage setting. Before you ship: → Set amountOutMinimum and a deadline on every swap → Check that the Add-ons tab shows Active on the node you send through → A node without the add-on uses the standard route

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 🧵

Try the upgrades on your own workload. Growth plan 50% off for 3 months with code GROWTH50 ⤵️ chainstack.com/build-better-… сс: @solana_devs

The rest: → Scans stop at 60 s or the memory limit with error -32012 instead of hanging → A scan is cancelled when your client disconnects → Shred feed gaps cut to about a third, e.g. Frankfurt 1: 16.65% to 5.36% → getMultipleAccounts fetches in a single batch All 7 upgrades with the numbers ⤵️ chainstack.com/solana-rpc-ch…

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

getProgramAccounts limits now depend on program size. With filters: → Under 10K accounts: 20 RPS, was 1 → 10K to 30K: 15 RPS, was 1 → 1M+ accounts: 3 requests per 20 s A cache now picks up popular programs on its own. Large programs are limited tighter than before.

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.

We rebuilt Solana RPC on Chainstack and shipped big upgrades for @solana builders: → getSupply: 2 to 300 RPS → getProgramAccounts p95: 25-60 s to under 2 s → Median getLatestBlockhash: ~17 ms to ~2 ms → and 4 more upgrades Details in the thread below 🧵

thanks for taking the time on this one. S tier feels great 💙

@CoinStats can we help? 🙂

Run your own node on any protocol with Chainstack Self-Hosted. @RobinhoodCrypto node on AWS example ⤵️ chainstack.com/how-to-run-a-… AWS announcement ⤵️ aws.amazon.com/about-aws/wha…

This week @awscloud launched @ethereum and @solana snapshots ⚡ But when self-hosting, there are more protocols to support, plus deployment, failover, and monitoring. Chainstack Self-Hosted brings together everything needed for your nodes to work flawlessly. On AWS, too 👀

35 of our 100 largest customers by recurring revenue work in financial verticals. Five build gaming, NFT or social products. Our founder @easeev on where blockchains actually work ⤵️

One mainnet run: 1,999 unique payments printed, 86,333 repeats filtered. In our own measurement, the edge over a WebSocket subscription was tens of milliseconds. It's a protocol demo, not production infra. Full walkthrough ⤵️ chainstack.com/how-to-read-x… cc @RippleXDev