Constantine | dRPC.ORG

CEO at @dRPCorg - The most performant & reliable Web3 infrastructure

[Constantine | dRPC.ORG @constantine_rm]

In dRPC you can run a quorum of data providers, including internal nodes, with custom rules for quorum. We made it in 2023: https://t.co/5K8YgG6z3K. 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: https://t.co/MYUn9vdXui

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):
-https://t.co/5K8YgG6z3K
- https://t.co/rMMaul9HJW

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 https://t.co/pJDU21rKi4 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 (https://t.co/pJDU21rKi4) 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 [email protected]

[LayerZero @LayerZero_Core]

https://t.co/3vIHs3Xgs4

[Constantine | dRPC.ORG @constantine_rm]

@solana ‘s probably biggest update so far

[P2P.org @P2Pvalidator]

Alpenglow is live on Solana mainnet.

Finality now targets ~150 ms, and validators pay 0.8 SOL per epoch to vote.

Here’s what it means for institutions staking SOL. https://t.co/1PSmviqRqu

[Constantine | dRPC.ORG @constantine_rm]

@aeroxyz @aero_agent @aero_agent extra leg space please

[Constantine | dRPC.ORG @constantine_rm]

Only up and forward 🚀

[Aero @aeroxyz]

Aero is here. Get on board.

[Constantine | dRPC.ORG @constantine_rm]

@DIMIDJ @Cointelegraph @googlecloud Gratz Dmitry, huge achievement 💪

[Constantine | dRPC.ORG @constantine_rm]

@nabutovsky @Quicknode Gratz, great job 👏

[Constantine | dRPC.ORG @constantine_rm]

@wagmiAlexander @aeroxyz Let’s gooo 🚀💪

[Constantine | dRPC.ORG @constantine_rm]

@wagmiAlexander @Stonks_Exchange @aeroxyz Great move guys! 👏🚀

[Constantine | dRPC.ORG @constantine_rm]

@OpenZeppelin Gratz!

[Constantine | dRPC.ORG @constantine_rm]

From Day 1 as usual!
If you want to always be prepared for new launches, add dRPC to your pool of RPC providers. If you are still working without a pool and just use one RPC provider, check NodeCore (https://t.co/xtdCHQSVlU)

[dRPC // AI-powered RPC Infrastructure @dRPCorg]

Arc 🤝 dRPC

dRPC is live on Arc from day one.

What it unlocks:

→ Instant RPC access to Arc Mainnet through NodeCloud, or self-hosted access through NodeCore

→ Reliable infra for payments, FX, and agentic economic activity on Arc, built on stablecoins as gas, starting with USDC

→ One more dependable access point for the builders and institutions already running on Arc

Build on Arc: https://t.co/m9JEUTLwSY
dRPC Chainlist: https://t.co/Dw8QWphDjI

@Arc

[cyber•Fund @cyberfund]

Applications for Batch II are now open.

12 weeks of single-minded focus and intensity.

What would you build with $2M and zero distractions?

[Constantine | dRPC.ORG @constantine_rm]

I feel that people shipping more than enough, problem that they mostly ship that don’t really needed and that they will not ship without AI, because it’s unnecessary.

It’s not issue of workflows or agents, it’s issue in people, because for decades people prefer to do a lot of work and create perception of high output for themselves and for others, instead of pursuing real outcome. AI just accelerated this “shit conveyor”

[Constantine | dRPC.ORG @constantine_rm]

If you are looking for enterprise-grade crypto infra, no matter staking, blockchain-indexed data, or RPC -> https://t.co/hzAKsxaiGb is the #1 choice.

[P2P.org @P2Pvalidator]

Institutions do not take security claims at face value.

https://t.co/YjE3JpL8As has achieved ISO/IEC 27001:2022 certification from BSI, adding a fourth independently verified credential alongside SOC 2 Type II, BSSC membership, and SumSub Sentinel.

⟡ Covers security, engineering, operations, and every client-facing function

⟡ Spans https://t.co/YjE3JpL8As's global entities

⟡ Four frameworks, one diligence process

Full breakdown at the link 👇

🔗 https://t.co/SZDkLqwofV

[Constantine | dRPC.ORG @constantine_rm]

@bandosei Because it was not for revenue, never was.
Venture didn’t put money into majority of crypto projects with expectations of revenue, only with expectations to sell it to less informed VCs later.
And when they seen projects with revenue - they rejected to invest by the same reason.

[Aero @aeroxyz]

Aero is on the horizon 🛫

Read on for the latest update on audit progress, launch timeline, and more 👇

https://t.co/gX7Yt6ll7b

[P2P.org @P2Pvalidator]

🎁 Giveaway: 2x Ledger Nano Gen5 up for grabs

Your keys. Your rewards.

Now, with a chance to upgrade your setup.

To enter:

→ Follow @P2Pvalidator and @Ledger
→ Retweet this post

Winners announced 22/07/2026. Good luck.

[Constantine | dRPC.ORG @constantine_rm]

As always from day 1 at dRPC -> https://t.co/kExLlEHWs5

Feel free to build on Robinhood with performant and reliable RPC🚀

[Robinhood Crypto @RobinhoodCrypto]

Yesterday at Robinhood Presents: The World is Flat, we went deep on crypto infrastructure. Here's what we announced. 🧵

[Constantine | dRPC.ORG @constantine_rm]

The most convenient way to get wallet data across more than 30 EVM chains via 1 request! What if you need Solana? We also have it! Try it, and you will love it 🫰

[dRPC // AI-powered RPC Infrastructure @dRPCorg]

Building crypto finance apps takes months of infrastructure work. Not anymore.

Today, dRPC is launching the Data and Wallet API.
Balances, DeFi positions, and historical PnL across 8,000+ protocols, 35 EVMs, and Solana, all in a single API call.

https://t.co/CqyJFcXh6s

[Constantine | dRPC.ORG @constantine_rm]

Happy to help @GoKiteAI to be a much more robust solution than the majority of the current crypto market. I am personally happy that more and more people implement several levels of fallbacks in their infrastructure.

[KITE AI @GoKiteAI]

Bridge security isn't a single safeguard. It's independent layers, and breaking through means breaking all of them at once.

At Kite, security sets the bar for who runs our infrastructure. We renewed our SOC 2 Type II this year, and we hold every RPC provider behind our bridge to that same standard. That is why we've expanded our independent RPC set with @ankr, @dRPCorg, and @DwellirOfficial. Why independence matters:

▷ A DVN is only as trustworthy as its RPC data. Independent providers, across separate infrastructure and regions, mean a DVN has to reach quorum before it attests. An attacker would have to compromise several at once.

▷ Layered under our multi-DVN setup on @LayerZero_Core, that means two independent security layers reinforcing each other.

Chosen for reliability, not convenience. The rails for the agent economy have to be secure before they're fast. 🪁

[cyber•Fund @cyberfund]

Introducing the Monastery for AI-native founders.

A single builder can now outperform a publicly traded company.

$2 million. 12 weeks. Do the impossible.

[Aero @aeroxyz]

Today: We're the #1 DEX on the #1 chain.

Soon: We're the #1 DEX across all EVM. 🛫