dRPC // AI-powered RPC Infrastructure

Product launch alarm 🚨 After a succesfull beta, the final NodeCore OSS package is out 🚀 What's NodeCore? dRPC’s open-source, self-hosted RPC infrastructure stack. Built for teams that want to run their own RPC layer with more control over routing, reliability, and access. GitHub: github.com/drpcorg/nodeco…

👉🏼 Check the tool: drpc.org/agent-skills 👉🏼 Read the full tutorial: drpc.org/blog/how-to-us…

You can use it for: > wallet analysis > transaction tracking > cross-chain comparisons > gas insights No need to understand RPC methods.

How do you actually use AI agents to query blockchain data? No RPC setup. No SDKs. No manual requests. Tutorial steps on the thread 👇

In dRPC you can run a quorum of data providers, including internal nodes, with custom rules for quorum. We made it in 2023: #why-use-verification" target="_blank" rel="nofollow noopener">drpc.org/docs/gettingst…. For a mission-critical application like a bridge or oracle, there's no excuse not to set it up. But they didn’t. The framing of the recent KelpDAO and LayerZero incidents as some novel attack vector, or the work of meaningfully smarter attackers, is mostly wrong. The actual failure mode - applications trusting a single RPC endpoint to return honest data - has been discussed openly for years, by @VitalikButerin, @lomashuk, @MicahZoltu, @wagmiAlexander, @ChainLinkGod, @banteg, and many others. It is neither new nor subtle. A closely related failure happened in 2022 with the Ankr DNS hijack on Polygon and Fantom: x.com/Mudit__Gupta/s… The point here isn't ideological. In a 24/7 market where automated systems act on RPC responses in real time, assuming one provider will always return correct data is a system-level risk. There is no T+2 window in which a human notices the error and reverses it. When we launched dRPC, cross-verification across a permissioned set of RPC providers was the core idea. The original repo and docs are still up (although outdated since then): -#why-use-verification" target="_blank" rel="nofollow noopener">drpc.org/docs/gettingst… - github.com/drpcorg/drpc-s… We used a simple quorum rather than zk-based verification, partly to test real demand before overbuilding. Two observations from that period: 1. The demand was not there. In public, everyone agreed with the thesis. In private, the responses were "we are not ready to pay more for quorum," or "yes, we could apply it to sensitive paths only, but it's not a priority." 2. The risk was real. The market is now discovering this at a cost of roughly $250M. Because full cross-verification on every request is overkill for most workloads, we eventually shifted toward shadow checks — randomized background comparisons across providers that detect and eject unhealthy nodes before they serve meaningful traffic. This is a reasonable compromise for general workloads. It is not a substitute for quorum on sensitive paths. So the practical rule, for anyone building infrastructure whose failure mode is user funds: 1. Use at least 3–5 independent, reliable RPC providers. 2. Do not build your load balancer on training wheels. Something like drpc.org/nodecore-open-… is open source, free, and almost certainly better than what you would build in-house. Contributing to it is a better use of time than reinventing it. You cannot defend against every possible attack. But this particular class is avoidable at low cost, if you are willing to treat RPC as a system-level dependency rather than a commodity input. That is a reasonable bar for anything meant to serve more than a narrow circle of users. We will update the dRPC NodeCore (drpc.org/nodecore-open-…) with strict rules for quorum on your side in the near future, stay tuned. If you have more sophisticated requirements for security, we are fully open for your requests - feel free to each me our via DM here or by email kz@drpc.org

@armsves @ETHWarsaw Gone!

@dRPCorg @ETHWarsaw Official swag

EthWarsaw, aka EthSilesia, is on 🔥and team dRPC arrived in the house with a bag full of hackathon survival gear. Rich out to Armando, the 100 hackathon Jedi, to get to know dRPC infrastructure and grab yours. Good luck to all participants 🍀

@ArcadiaFi Good luck, team! You are going to rock it 🚀

@dRPCorg Happy to be working with you guys 👍

dRPC × Arcadia Finance We’re now the primary RPC infrastructure provider for @ArcadiaFi We are excited to support a new wave of capital-efficient DeFi where execution, reliability, and performance directly impact user outcomes.

If you’re allocating capital on-chain and care about efficiency, risk, and execution quality Arcadia Finance is worth your attention → arcadia.finance

For Arcadia, this means: → Stable execution for complex strategies → Reliable collateral management flows → Infrastructure that holds under pressure Because in DeFi, performance is part of the product.

Try it 👇  github.com/drpcorg/drpc-a… Get your questions answered 👇👉🏼drpc.org/blog/agent-ski…

Same coverage. Same reliability. 100+ chains. 200+ networks. Just a completely new interface to access them.

Why are you still writing RPC calls in 2026? What if your AI agent could just ask for blockchain data and get it instantly? Learn like a PRO on the thread 👇