How RedStone keeps price feeds reliable across 51 chains with Alchemy

When a lending market has to liquidate a position, the price feed underneath it cannot be late, wrong, or down. RedStone is the data layer behind institutional DeFi and onchain capital markets: custom oracle price feeds for complex assets like LSTs, LRTs, Bitcoin LSTs, stablecoins, FX pairs, and tokenized real-world assets, across 110+ chains, and provides the onchain price feed for BlackRock's BUIDL, Apollo's ACRED, and Hamilton Lane's SCOPE.

Since using Alchemy as its RPC provider, RedStone has pushed 26.8 million pricing transactions onchain with a 99.999% success rate.

Products used: Node RPC API

The setup: an oracle with no room for error

Oracle infrastructure has zero tolerance for degraded performance. A stalled node delays a price update that lending markets and perpetuals rely on to liquidate safely. For RedStone, that bar applies on every one of the 100+ chains it operates on, from established EVM networks to newer, non-EVM chains where institutional clients are now deploying tokenized funds.

That reliability bar is also why institutions choose RedStone in the first place. Asset managers, banks, and tokenization platforms come to it for accurate NAV calculations on off-chain assets, delivered onchain, with account balances reconciled in time and bespoke integrations built around how each institution actually operates.

Besides price feeds, RedStone delivers instant settlement for tokenized RWAs through Settle, off-hours pricing through Live, proof of reserve, and independent risk ratings through Credora. Each turns tokenized assets into usable, liquid collateral rather than static holdings.

The challenge: a separate decision for every chain

Operating across 100+ chains meant RedStone had to source, integrate, and vet an RPC provider separately for every deployment. This caused a few challenges:

• Fragmented coverage slowed incident response. Every chain-specific issue meant rebuilding context with a different vendor, on a system where response time matters as much as uptime.
• Chain launches also compress timelines. A new chain's oracle needs to be live from day one, which leaves no room for a multi-week provider evaluation each time RedStone expands.
• Before working with Alchemy, RedStone ran ad hoc RPC selection per chain launch, picking whoever had coverage at the time.

The evaluation: performance under load, not headline uptime

RedStone tested Alchemy's nodes against its own feed requirements: latency and behavior under load. They also evaluated Alchemy's chain roadmap, since keeping pace with new chain launches was central to the problem RedStone needed solved.

A shared culture around reliability and customer experience made choosing Alchemy a straightforward decision. Both teams treat those as fundamental to how they operate.

"If a price update is late, a liquidation is late too…or it just doesn't happen. Reliability and performance are paramount to us. When we tested Alchemy's nodes under the same load we tested our own feeds against, they held up. When we needed urgent answers, their founder picked up the phone. That's what convinced us that this is a partnership to grow together over the long term."

— Marcin Kaźmierczak, Co-Founder, RedStone

The solution: one RPC provider, one escalation path, every chain

Alchemy is now RedStone's preferred RPC provider for new chain launches, allowing it to skip the evaluation step that used to come with every deployment. RedStone gets the same reliability profile and support standard on every chain, rather than a different one depending on which provider happened to cover that network.

Escalation is single-threaded. RedStone gets one channel and one team that is familiar with its architecture, ensuring a faster resolution when something needs attention, instead of rebuilding context with a new vendor each time an issue is chain-specific.

That reliability can be seen directly in RedStone's own numbers while delivering price feeds through Alchemy nodes: a 99.999% success rate across 26.8 million onchain price-push transactions, with 12B+ total requests served since RedStone made Alchemy its preferred RPC provider in February 2025.

By the numbers, on Alchemy:

• 99.999% success rate on price-push transactions — 26.8M eth_sendRawTransaction calls submitted onchain, lifetime
• 12 billion+ requests served since RedStone made Alchemy its preferred RPC provider in February 2025
• 51 chains actively serving RedStone traffic on Alchemy nodes today, including BNB Chain, Solana, Base, and Arbitrum
• 27x monthly growth, from 47.5M requests/month at launch (Feb 2025) to a sustained 1.2B+ requests/month pace since October 2025

The data shows how far the infrastructure scales. RedStone went from 47.5 million requests a month to over a billion, and added dozens of chains, while the success rate stayed at 99.999%.

With a single reliable RPC layer in place, RedStone can bring price data to a new chain without re-running a provider evaluation. Since Alchemy can see how it performs under production load, RedStone becomes a natural data-layer recommendation for Alchemy's enterprise clients building products that need reliable price data.

What's next

RedStone and Alchemy are building joint products aimed at the largest financial institutions entering onchain markets, pairing Alchemy infrastructure with RedStone price feeds and Credora risk ratings. As RedStone expands to new institutional-focused chains, Alchemy nodes are part of the plan from genesis rather than a later addition.

If your protocol needs price feeds, risk data, or node infrastructure that holds up under institutional-grade reliability requirements, get started with Alchemy nodes, talk to us, or explore RedStone's price feeds.