Origin Story

Hemi was born from the idea that Bitcoin and Ethereum shouldn’t exist in isolated silos. In 2024, Bitcoin core veteran Jeff Garzik and security expert Max Sanchez set out to create a network that converges the strengths of both. Unveiled at Bitcoin 2024 in Nashville, Hemi’s testnet quickly gained traction, processing millions of transactions and attracting a robust community through an incentivized program. By March 2025, Hemi launched its mainnet with over 50 projects on board, marking the first-ever Layer-2 that effectively treats Bitcoin and Ethereum as one combined ecosystem.

Tech Stack

Under the hood, Hemi is built on the OP Stack (Optimism’s modular rollup framework) but pushes beyond the standard formula. It runs on a Cosmos SDK-based infrastructure fused with a geth-derived Ethereum Virtual Machine. The twist? Hemi’s EVM, called hVM, is upgraded to include a full Bitcoin node. This means every Hemi node is aware of Bitcoin’s state (block headers, UTXOs, etc.) in addition to running the Ethereum consensus layer. Consensus is secured by Proof-of-Proof (PoP)– Hemi’s validators periodically commit snapshots of the chain to Bitcoin, leveraging Bitcoin’s proof-of-work for finality. Blocks on Hemi confirm in seconds, while PoP mining imbues them with Bitcoin-level security within a few hours. It’s a novel hybrid of an optimistic rollup (for scalability) and Bitcoin anchoring (for security).

Details on the Hemi Tech Stack are described in the following blog post: https://hemi.xyz/blog/inside-the-hemi-tech-stack/

Feature Spotlight

Hemi’s unique architecture unlocks features previously unattainable in a single network. For one, it enables trust-minimized crosschain bridges: Hemi’s native Tunnel contracts allow BTC to move onto Hemi and back to Bitcoin without centralized custodians. Developers can write smart contracts that directly verify Bitcoin transactions, opening the door to Bitcoin DeFi – think lending, derivatives, and stablecoins collateralized by real BTC, all enforced by code. Additionally, Hemi supports gasless transactions and advanced asset controls (like timelocks and password-protected transfers) at the protocol level. This improves UX, letting users move assets (even BTC) on Hemi without needing to hold a native gas token. In short, Hemi combines the programmability of Ethereum with the liquidity and security of Bitcoin in ways we’ve never seen before.

Ecosystem Overview

Since its mainnet debut, Hemi has been steadily growing as a crosschain DeFi hub. By late 2025, over 4.3 million transactions will have been secured via PoP checkpoints, and the network currently boasts $900M+ TVL across dozens of dApps. Notable projects include DEXes like SushiSwap and DODO, lending platforms like LayerBank, and infrastructure protocols like LayerZero and RedStone oracles launching on day one. Hemi’s DeFi scene has a strong focus on Bitcoin liquidity (e.g., wrapped BTC yield farms and even BTC restaking opportunities).

The network’s unique ability to handle both ERC-20 tokens and native BTC (via pegged representations) in one place has attracted over 50 launch partners ranging from AMMs to NFT marketplaces. With a $15M war chest from investors and a thriving community (Discord, Telegram, and quarterly hackathons), Hemi is positioning itself as the go-to chain for projects that need true Bitcoin-Ethereum interoperability.

Why DIN?

Hemi’s ambitious “supernetwork” approach demands equally resilient infrastructure. That’s where DIN comes in. From day one, Hemi’s public RPC endpoints are served through a federation of providers rather than a single service. This aligns with Hemi’s ethos of decentralization and reliability. For developers and users, DIN integration means:

• High uptime: If one provider has issues, others seamlessly take over, keeping Hemi’s API online 24/7.

• Low latency: DIN’s global network of nodes routes requests to the nearest/fastest provider, ensuring snappy responses even as Hemi’s usage scales.

• Censorship resistance: No single company or cloud hosts the RPC. Requests are distributed across independent providers meeting Infura’s strict quality criteria.

In practice, building on Hemi via Infura+DIN feels no different than using Infura for Ethereum or other chains, except you have an extra layer of assurance that the service won’t go down or become a bottleneck. This robust backend is critical as Hemi targets high-volume DeFi use cases and global users who expect consistent performance.

Roadmap & Governance

What’s next for Hemi? In the near term, the team is focused on fully decentralizing the network’s operations. Since the successful Hemi token (HEMI) launch, the team is focusing attention on transitioning governance to its community – enabling on-chain voting, stake-based validation, and economic incentives for PoP miners. On the technical front, Hemi’s roadmap includes enhancing its PoP protocol to allow external chains to leverage Bitcoin finality via Hemi. In other words, Hemi could become a security hub where other new blockchains plug in to get Bitcoin-grade security (a concept playfully dubbed “Bitcoin-security-as-a-service” in the community).

Moreover, being built on the OP Stack, Hemi is primed to participate in Optimism’s Superchain vision, meaning it could achieve seamless interoperability with other OP-based L2s. On governance, Hemi Labs currently guides upgrades and improvements, and is working on a more decentralized governance model with Hemi Improvement Proposals (HIPs) and community-elected validator sets. The ethos is similar to Ethereum’s path: start centralized for speed, then progressively decentralize as the network and community mature.

Community & Developer

Onboarding Hemi is making a concerted effort to welcome developers from both the Bitcoin and Ethereum worlds. For Ethereum devs, the experience is frictionless – all your usual tools (Remix, Hardhat, Ethers.js/Viem, MetaMask) work out-of-the-box on Hemi. Comprehensive docs are available, including quickstart guides and even examples of Solidity contracts using Hemi’s Bitcoin features (check out the Hemi Bitcoin Kit section in the docs).

For Bitcoin developers and enthusiasts, Hemi provides new toys to play with: you can write smart contracts that respond to Bitcoin events and even use Sats (via wrapped BTC) in DeFi strategies. The community runs active Discord and Telegram channels for support, and there’s a grants program to fund innovative dapps (recently, grants have targeted BTC yield protocols and crosschain wallet integrations).

Hemi’s incentivized testnet (with its Points leaderboard) successfully drew in thousands of testers, and similar incentive programs are planned for mainnet (like a potential airdrop for early users post-TGE, to be confirmed). In short, if you’re a developer interested in pushing the envelope of multi-chain dapps, Hemi’s community is ready to onboard you with documentation, support, and possibly funding for your idea.

Hemi + Infura

Available Now One of the best parts about Hemi’s launch is that it’s immediately accessible through familiar infrastructure. As of today, Hemi is live on the MetaMask Developer Dashboard (formerly Infura dashboard) – which means if you have an Infura API key, you already have access. Just select “Hemi” from the network list, and you can start querying the chain or deploying contracts.

Both Hemi’s testnet and mainnet endpoints are available, backed by Infura x DIN’s multi-provider network for reliability. No need to run your own node or worry about finding a third-party RPC. This ease of access lowers the barrier to entry for experimenting with Hemi. Have an existing Ethereum dapp that could benefit from Bitcoin integration? Point it at Hemi’s RPC and give it a try. The combination of Hemi’s tech and Infura’s infrastructure is enabling developers to build what was previously impractical: truly trust-minimized crosschain applications.

Resources

Interested in building on or learning more about Hemi? Here are some resources to get you started:

• Official Website: https://hemi.xyz – Learn about the Hemi vision and explore the ecosystem.

• Documentation: https://docs.hemi.xyz – Developer docs, tutorials, and references (everything from running a node to using the hVM).

• GitHub: https://github.com/HemiLabs – Hemi’s source code (feel free to inspect, contribute, or run your own nodes).

• Hemi on Twitter/X: https://x.com/hemi_xyz – Follow for the latest announcements and technical threads.

• Community Chat: https://discord.gg/hemixyz – Join Hemi’s Discord to ask questions or share ideas with fellow builders.

• Analytics: L2Beat – Hemi – See up-to-date metrics on Hemi’s Layer-2 (TVL, usage stats)

With Bitcoin and Ethereum finally coming together on Hemi, we’re witnessing the emergence of a new breed of dapps. If you’ve been waiting for a chain that gives you the best of both worlds — Bitcoin’s trust and Ethereum’s innovation — Hemi might just be the platform to build your next big idea. And with decentralized infrastructure support from day one, it’s never been easier to get started. Happy building! 🚀

About Simply Staking

Simply Staking started with professional validator operations and expanded methodically into staking infrastructure, node services, and developer tooling. Their approach is simple: pair seasoned operations with transparent, measurable reliability. The company’s portfolio now includes:

• Staking and yield primitives that secure networks and simplify participation for institutions.

• Custom infrastructure for networks and enterprises that need tailored deployments.

• DEPIN and AI infrastructure that pairs decentralized compute and data with emerging AI workloads.

• Consensus layer operations that emphasize resilient validator and node reliability.

• Execution layer services including RPC and higher level methods, delivered with strategic APIs, integrations, and observability.

This breadth lets the team meet projects at any point in the adoption curve, from early testnets to scaled mainnets.

Why DIN

Traditional RPC often relies on a single centralized operator, which creates downtime and censorship risk. Purely decentralized approaches can struggle with coordination, performance, and support. DIN bridges this gap by combining professional operators with EigenLayer-backed SLAs and slashing. Providers are held to verifiable, economic guarantees on uptime and responsiveness, while builders gain a permissionless way to access multiple providers through a single integration. For Simply Staking, that balance of performance, accountability, and openness is the right path to real decentralization.

Networks Live on DIN

Hemi is live today (in DIN testing), with additional networks on the way. Simply Staking prioritizes ecosystems where robust infrastructure and experienced operations have an outsized impact on developer experience. As demand grows, they will expand coverage to high-value networks that benefit from low-latency, high-uptime RPC backed by DIN’s performance expectations.

Spectrum Nodes and Developer Experience

Spectrum Nodes is Simply Staking’s production-grade API layer that processes 1B+ daily requests across 170+ networks. It was built to be predictable under load, observable in real time, and easy to integrate. That same philosophy informs their DIN deployments:

• Metrics and alerting map cleanly to DIN’s performance standards.

• Capacity planning is informed by live traffic profiles and error budgets.

• Operational playbooks keep recovery times short and regional redundancy high.

The result is an experience that feels enterprise-ready while remaining credibly neutral and decentralized.

Operational Impact and Revenue

DIN gives Simply Staking a new avenue to scale RPC alongside staking. Onboarding was clear, documentation was strong, and collaboration with other providers opened new opportunities to extend reach. Just as important, DIN’s verifiable standards encouraged deeper investment in monitoring, resiliency, and SRE processes. That lifts quality for all customers, not only DIN traffic, while diversifying revenue with transparent, performance-linked incentives.

Learnings and Early Wins

Two themes stand out:

• Speed of evolution. DIN moved quickly from concept to an EigenLayer-secured marketplace with active providers and testnet activity.

• Community alignment. The provider community is collaborative and solution-oriented. Open discussions around routing, observability, and SLAs have turned DIN into more than a gateway. It is an ecosystem of aligned operators improving reliability together.

Perspective on the Future

Simply Staking believes decentralized infrastructure is foundational for the next decade of Web3. Without it, the industry risks repeating Web2’s single-point-of-failure patterns. With DIN, infrastructure is not only about uptime. It is about economic guarantees, diversity of providers, and transparent performance. That combination unlocks better user experiences for dApps and a more resilient backbone for the entire ecosystem.

Looking Ahead

• Expand DIN coverage to additional high-value networks as adoption grows.

• Contribute operational feedback and tooling to strengthen DIN’s EigenLayer-backed SLAs and enforcement.

• Continue investing in Spectrum Nodes and related developer tooling so teams can scale from first deploy to global traffic with confidence.

Learn More

https://simplystaking.com/

Why Northwest Nodes Joined DIN

Northwest Nodes saw DIN as the most credible path to a decentralized and merit-based infrastructure layer. DIN’s AVS model with slashing ties rewards to measurable outcomes such as redundancy, uptime, and responsiveness. That alignment fits the team’s philosophy that performance should be earned and verifiable rather than promised.

Networks Live on DIN

Northwest Nodes currently supports:

• ZKsync

• Swell

Both ecosystems demand specific expertise and tight operational practices. By contributing these networks to DIN, Northwest Nodes helps developers reach performant endpoints through a single integration while keeping decentralization and reliability front and center.

Operational Impact

Joining DIN added a new income stream and encouraged deeper investment in internal processes. The team refined monitoring, alerting, and incident response as part of meeting DIN’s performance expectations, which now benefits all customers who rely on their infrastructure.

Learnings and Internal Tooling

A standout outcome has been the creation of a proprietary RPC tracking system. It measures availability and latency across multiple dimensions and is robust enough to serve many use cases. This system informs day-to-day tuning and longer-term capacity planning, improving service quality across the board.

The Role of Decentralized Infrastructure

Northwest Nodes believes decentralized infrastructure is essential for real uptime, security, and redundancy. Centralized services can be fast, but they create single points of failure and policy risk. DIN proves that a decentralized system can provide strong reliability when incentives are clear and performance is enforced.

Looking Ahead

Northwest Nodes plans to:

1. Expand coverage to additional high-demand networks as they mature.

2. Continue improving its RPC tracking system and share insights that strengthen the broader provider community.

3. Support DIN’s AVS roadmap so developers gain stronger guarantees without sacrificing usability.

Much appreciated note from the Northwest Team: “A big thank you from the team to DIN for professional guidance, thoughtful design, and ongoing support.”

Learn More

• Explore DIN → din.build

• Explore North West Nodes** → https://northwestnodes.com/ **

What EigenCloud Solves

Most dApps still rely on centralized infrastructure for heavy computation or data availability, losing the cryptographic guarantees that make blockchains valuable. EigenCloud fixes this by giving developers a “verifiable cloud” where every API call, data store, or off-chain workload inherits crypto-economic security from restaked ETH and EIGEN. AVSs plug into EigenCloud for slashing, rewards, and dispute resolution, making trust portable and programmable across Web3 and Web2 environments.

Why DIN Chose EigenCloud

DIN launched its decentralized RPC marketplace on EigenLayer to tap into the same slashing and reward mechanics that power EigenCloud. By anchoring service-level guarantees in restaked collateral, DIN can:

• Enforce uptime SLAs for critical RPC traffic

• Guarantee latency with economic backing

• Offer tiered service levels without manual policing

• Publish verifiable performance metrics that builders can audit

EigenCloud views DIN as a model AVS that showcases how restaking aligns incentives among permissionless providers and end users.

How the Technologies Complement Each Other

• EigenCloud supplies the crypto-economic backbone with staking, slashing, rewards, and on-chain proofs.

• DIN focuses on developer experience through smart routing, multi-provider fail-over, and a permissionless marketplace for RPC.

Together they create a full-stack solution where infra performance is both measurable and economically enforced.

To learn more about EigenLayer slashing, our very own Tom Hay (DIN Head of Product) talks with Matt Nelson (Head of Product in EigenCloud) in this EigenLayer, Infura, and LayerZero conversation:

Milestones So Far

• DIN is live on the EigenLayer testnet with slashing enabled, giving early node operators a sandbox to prove reliability before mainnet.

• Reward distribution begins soon, letting DIN providers earn directly from restaked incentives while builders gain trustless service guarantees.

• Community interest has surged after EigenLabs secured an additional $70 million token purchase from a16z to accelerate EigenCloud adoption.

What Comes Next

• Mainnet launch: DIN plans to migrate to EigenCloud mainnet with slashing and rewards fully active. Date is planned for Q4 2025 as we’re completing DIN AVS code review.

• Expanded primitives: Future AVSs on EigenCloud including verifiable compute, data feeds, AI agents plans to plug into DIN’s gateway, giving builders a single entry point for many trust-minimized services.

• Shared analytics: Both teams will explore real-time dashboards showing how restaked collateral backs RPC performance and other AVS workloads.

Final Thoughts

EigenCloud and DIN together demonstrate that decentralization can scale without sacrificing reliability or developer experience. By uniting crypto-economic security with a permissionless service marketplace, they set a new standard for how Web3 infrastructure should work.

Explore More

• DIN Whitepaper and Gateway Program → din.build

• EigenCloud launch details → blog.eigencloud.xyz

• EigenCloud documentation → docs.eigencloud.xyz

Why Nodies Joined DIN

Traditional RPC platforms often deliver speed at the cost of sovereignty, while fully decentralized solutions can struggle with observability and predictable uptime. Nodies saw DIN as the balance point. DIN’s curated marketplace enforces service-level standards through transparent metrics, yet still distributes control across independent providers. That model fit perfectly with Nodies’ mission to make Web3 infrastructure both reliable and credibly neutral.

Networks Live on DIN

Nodies currently serves:

• Blast – mainnet and testnet

• Scroll – mainnet and testnet

• Sei – mainnet and testnet

Each chain sits at the frontier of performance or novel architecture, attracting active developer communities that demand responsive, decentralized RPC. By bringing these endpoints to DIN, Nodies gives builders a single integration path to emerging ecosystems without sacrificing latency or uptime.

Operational Impact

DIN introduced a fresh revenue stream that complements Nodies’ direct customer channels. The network’s performance weighting pushed Nodies to elevate internal monitoring and fail-over logic, investments that now benefit all of their clients. Diversifying traffic through DIN also reduced exposure to cyclical demand from any one chain or user segment.

Collaboration Highlights

While there have been no major surprises, Nodies cites DIN’s hands-on approach as a standout experience. Fast feedback loops, clear documentation, and open dialogue around upcoming AVS features helped the team optimize deployments quickly. The partnership affirmed that large gateway operators and independent node teams can move in lockstep toward shared decentralization goals.

View on Web3 Infrastructure

Nodies believes the next generation of dApps will only thrive on a foundation that is verifiably decentralized. Centralized gateways expose users to single-point outages and content filtering, risks that contradict the ethos of permissionless systems. By pooling independent providers under a common performance framework, DIN proves that decentralization and enterprise-grade reliability can coexist.

Looking Ahead

Nodies plans to:

1. Expand DIN coverage to additional high-demand L1s and L2s as they reach mainnet.

2. Contribute feedback and tooling for DIN’s forthcoming AVS roll-out.

3. Continue open collaboration to raise the bar on monitoring, alerting, and node hardening across the provider community.

The team thanks DIN for the opportunity to build together and looks forward to a long-term partnership that strengthens the entire Web3 ecosystem.

Explore More

• Nodies infrastructure services → nodies.network

• din.build

DIN’s co-founder, EG Galano, recently presented at CODE NYC Coinbase Hackathon in Brooklyn on Aug 9 talking about our implementation of x402 for DIN endpoints. For those who need a refresher, x402 is an internet-native payment protocol that was developed by Coinbase for fast, cheap, and AI-friendly payments. Our code calling this implementation is available for review:

https://github.com/DIN-center/din-x402-examples

Setting the Stage

EG’s talk during the 1-hour workshop covers our narrative of why we built a demo with x402 in order to enable AI Agents access to web3 networks paid with micro-transactions.

Through this digital era, technology has been a driving force that has made our lives easier and lowered the barrier of entry with conveniences.

The disruption we see with major tech like cryptocurrency and AIs have some key features.

• Cryptocurrency has an infrastructure that provides a transparent database with a store of value of assets traded on different exchanges

• Blockchain as the underlying technology has this shared storage mechanism driven by the economics of certain cryptocurrencies

• Large Language Models created with generative AI has made all of the internet a conversational place where we no longer have to do the searching and creating ourselves

• Agentic AI is connected to different apps so they can complete tasks like a personal assistant. Maybe you want to make a reservation to a restaurant and your personalized AI will call a restaurant’s AI to negotiate the best times and then share the log of the conversation.

• And lastly the digital twin AI is the next step we’ve seen where your phone can have a local digital representation of your data and your interface with this AI will be the training that has it learn more and more about you.

From these technologies, we’ve seen a few interesting use cases that intersect with the fintech world.

• Cryptocurrency in itself has a global emerging market with a huge shift towards stablecoin regulation and staking infrastructure

• Blockchains are accessed through wallets that can be created without unified SaaS platforms. These wallets can access multiple databases and aggregate cryptocurrency and other functions.

• Generative AI now gives you full director control of content creation. Some people will use it to create AI slop, while others will actually build useful novel ideas and pursue their startups

• Agentic AI interactions is what’s coming next where we may see a personalized AI decide on how to trade and balance a portfolio

• The digital twin AI will likely lead to more data aggregation and algorithms for making personalized decisions. Maybe this could include sending funds to a friend after splitting a lunch and then asking for some authentication for the payment.

In a future where we might see more actions coming from AI agents (like bots in a social media platform), there will be a service that can easily connect and aggregate with authentication from different financial institutions. The AI Agent may want access to capital.

We think this connected AIs will need blockchains and for its citizenship across identity, communities, and agreements. A network layer can support this by having a separately verifiable source of services for interacting with these AIs.

Enter DIN… we’re not just looking at decentralized RPC< but we’re building out a marketplace for infrastructure providers to complete on price and quality of service.

If you think of the next phase in the Web3, the AI Agents will start to take over for individuals. The new Web + AI will be an age of personalized digital twin Training where you may enjoy private training of your algorithms rather than the public publishing of your blogs.

The dirty little secret with Web3 infrastructure is that we still use traditional financial rails for paying our infrastructure bills and ever-so-important devops team members.

Where we want to get to is a better on-chain payment system that covers Agentic AI integration, but also can be used by B2B providers to better manage their web3 treasury.

The way DIN works is by allowing for any customer to access the API Marketplace and route to our DIN API Providers. The Payments piece creates a streaming of payments, but also a netting mechanism to keep tokens within the ecosystem to subsidize the costs for running more network bandwidth and accessing a larger breadth of networks.

What we’ve built to showcase this is a x402 example in Go:

https://github.com/DIN-center/din-x402-examples

This constructs the x402-buyer to call the DIN request and pay directly to the DIN Treasury (x402-seller) for Ethereum, Base, and Blast networks.

If this were extended to an AI Agent workflow, the AI Agent itself could host its own Eliza OS or other wallet to manage and sign transactions connected to DIN as an MCP. This MCP tooling would allow for the AI Agent Orchestrator to make the best choice of collecting and managing data.

The “headless gateway” concept we’ve created here allows for AI Interaction and the following use cases:

• As an AI Agent, I can call a DIN endpoint (for Ethereum, Base, and Blast), pay with a token (USDC), and receive relevant JSON RPC information for my response.

• As an AI Agent, I can receive additional information on my DIN usage (e.g. receipts of TXs, calls with the endpoint). This can be a redirect of user to a DIN Web App for monitoring.

• As an AI Agent, I can share additional information (e.g. website, code, docs). This can be a terminal-like response function.

This could effectively be a terminal interface with your AI Agent conducting additional memory context for completing your tasks.

We’ve got a whole list of additional features we can add to this. From Breadth to Depth, we can see:

• Addition of more endpoints

• Connecting DIN with different workflows and agentic tools

• Adding gateway integration with Infura and generic for other DIN Providers

• Adding this payment as an option for B2B payments with Node Providers

• More token types for payment of access

• Usage of DIN for AI Networks, Marketplace, AVS, and Treasury

To round out this idea, we’ve found that Business to AI integration will be a new line of business as AI Agents become more mature. In order to connect AI to more APIs and tools, we’ll need to consider the discovery, rate limiting, specifications, workflows, documentation, and structured outputs within the web3 ecosystem.

DIN continues our journey of progressive decentralization by partnering with the right players for GTM on our ideas. We’re opening to more community contributions and finding new ways to approach the deployment of DIN itself without reinventing the wheel with another dedicated blockchain network or just launching a simple utility token. We are deliberate in our methodology of building to cover the needs of the many web3 infrastructure providers powering your cryptocurrency access and fintech experimentation.

Learn more about DIN at @DINBuild and https://din.build . Follow EG’s talks on YouTube:

https://www.youtube.com/playlist?list=PL3HvrmRiIDCVt75Rt0egH8xX8ypUQfi4c

Login and try it now: https://developer.metamask.io

Origin Story

Sei Network originally launched as a high-speed Cosmos-based chain focused on DeFi. But with most developers building in Solidity, Sei's team evolved the protocol to speak the language of the EVM. The result is Sei v2, an upgraded Layer-1 that embeds a fully-integrated Ethereum Virtual Machine inside the Sei core, all while preserving blazing-fast performance (~390ms finality). It marks the first EVM chain to support true parallel execution natively.

Tech Stack

Sei combines the Cosmos SDK with a Geth-based EVM, making it fully Ethereum-compatible. Core components include:

• Parallel execution engine: Optimistically runs transactions in parallel, falling back to sequential execution on conflict.

• Twin Turbo consensus: Optimized Tendermint variant tuned for sub-second block times.

• SeiDB: A new storage model splitting state into a compact consensus-critical commitment and a full, fast-access store.

• Integrated EVM: Solidity contracts deploy out-of-the-box using Ethereum tooling like Hardhat and MetaMask.

Feature Spotlight

• First Parallelized EVM: No need for developers to annotate transactions—the network handles conflict detection and scheduling.

• EVM + CosmWasm: Supports both Solidity and Rust contracts; enables cross-VM calls.

• MEV-aware plugins: Validators can run customizable MEV strategies; extraction is transparent and auditable.

• SeiDB: Nodes use 20x less storage and sync 10x faster than legacy Cosmos chains.

• Native restaking integrations: Designed for AVS participation via EigenLayer and Symbiotic.

Ecosystem Overview

As of mid-2025:

• Over 2 billion transactions processed.

• $200M+ TVL across DeFi, NFT, and gaming dApps.

• dApps like Vortex DEX, NFT marketplaces, and on-chain games live.

• Sei's L2-compatible bridge supports USDC, swETH, and other cross-chain assets.

• Builders have deployed via Gitcoin grants and the $50M Sei Ecosystem Fund.

Why DIN?

Sei v2's performance makes RPC a mission-critical component. DIN integration ensures:

• High uptime via a federated network of providers.

• Low latency thanks to geo-routed access.

• Load balancing for 28K+ TPS workloads. This gives developers a resilient backend to match Sei's frontend speed.

Roadmap & Governance

• Sei Giga upgrade will boost TPS to 250K with a new "Autobahn" consensus layer and fully parallelized VM.

• Governance remains on-chain via SEI stakers, with grants, fee tuning, and upgrade approvals managed by community proposal.

• The Sei Foundation and Labs support core dev, but validators and users shape long-term direction.

Community & Developer Onboarding

• Sei supports all standard EVM tooling.

• Devs can deploy with Hardhat, test with Foundry, or use Keplr for CosmWasm.

• Grants available via Gitcoin and ecosystem fund.

• Educational campaigns and "Accelathon" events foster new ideas and cross-chain collaborations.

-→ Sei is live today on MetaMask Developer Dashboard Check out Sei v2 endpoints on MetaMask Developer Dashboard - https://developer.metamask.io/

Deploy, restake, and scale on Sei. Whether you’re building DeFi, games, or restaking infra, Sei offers:

• Ethereum-level compatibility

• Solana-level performance

• DIN-level reliability.

Spin up a node, publish a dApp, or join the community to shape the next generation of high-performance EVM blockchains.

Additional Resources

• https://www.sei.io

• https://docs.sei.io

• https://twitter.com/SeiNetwork

• https://github.com/sei-protocol

• https://l2beat.com/scaling/projects/sei

• https://app.artemis.xyz/project/sei

From Pocket Network to Grove: Seven Years of Infra R&D

Pocket Network began as a relay marketplace serving billions of JSON-RPC calls. As the ecosystem matured, the founders of Pocket Network formed Grove to reflect a broader mission: coordinate any service (blockchain or otherwise) through a protocol-first design.

• Shannon migrates Pocket from Tendermint Classic to the Cosmos SDK, introducing on-chain fee markets, permissionless gateways, and light-client suppliers that lower node costs.

• PATH, Grove’s open-source SDK, lets developers spin up sovereign gateways with smart QoS rules, load balancing, and enterprise-grade SLAs on top of the new chain.

Shannon and PATH set the stage for Grove to support hundreds of services, not just blockchain RPC. This is exactly the type of modular future DIN envisions.

Why DIN Fits Grove’s Long-Term Arc

Web3 infra choices often feel binary: centralized SaaS that sacrifices sovereignty or rough-edged decentralized networks that struggle with UX. DIN blends both worlds by turning decentralization into a product with structured onboarding, performance-based routing, and transparent incentives. Grove sees DIN as validation that large providers like Infura are ready to integrate third-party protocol networks rather than build closed silos. For a team obsessed with coordination layers, that alignment is impossible to ignore.

Network Footprint on DIN

Grove has given its full catalogue of 53 services to DIN, but not all of them are live and serving traffic. They are focusing first on high-demand chains:

• Ethereum for mainstream DeFi and NFT traffic

• Polygon for low-fee consumer apps

• Solana for high-throughput use cases

As Shannon goes live and PATH gateways mature, Grove will light up additional chains (from Bitcoin and Base to emerging modular L2s) to mirror both DIN’s roadmap and Pocket’s expanding supplier ecosystem.

Operational Impact and New Economics

DIN’s marketplace funnels traffic to the lowest-latency endpoints. Grove’s globally distributed suppliers routinely top latency charts, so the network quickly became a meaningful demand source. More important than the revenue bump is proof that protocol-aligned participation can be profitable when linked to open demand channels. Metrics such as uptime, proof submission, and relay success map neatly onto DIN’s staking and slashing logic, reinforcing Grove’s internal performance goals.

Early Lessons and Wins

• Aligned incentives: DIN’s decision to open its gateway stack created fast feedback loops and shared observability dashboards, fostering rapid trust.

• Marketplace effect: New chains like Mantle, Blast, and Scroll saw immediate traffic spikes once listed, demonstrating how neutral discovery accelerates adoption.

• Supplier interest: Grove reports increased inbound interest from node operators who want to serve both Shannon and DIN, citing smoother monetization than traditional white-label models.

Practical Decentralization for Web3’s Next Wave

Grove argues we are shifting from ideological decentralization to practical decentralization. Builders need verifiable guarantees that their access will not be throttled, censored, or surveilled—while still scaling to millions of users and autonomous agents. DIN plus Grove delivers that promise by combining protocol-level coordination with enterprise-grade performance.

What’s Next

1. Shannon mainnet on 3 June 2025 has already unlocked permissionless gateways and new fee markets.

2. PATH 1.0 will streamline gateway deployment for DIN operators seeking multichain coverage.

3. Cross-network experiments will explore relay settlement between DIN’s AVS contracts and Pocket light-client suppliers, aiming for deeper liquidity and redundancy across both ecosystems.

Grove believes decentralization thrives through collaboration. By pairing Infura’s reach with Pocket’s protocol DNA, DIN and Grove can push the frontier of resilient, inclusive infrastructure.

Explore More

• DIN Gateway Program → din.build

• Grove roadmap and Shannon details → https://grove.city

• PATH SDK docs → https://path.grove.city

Why Benchmarking Matters in a Decentralized Marketplace

Web3 developers often choose infrastructure blindly, trusting marketing claims or small test scripts that miss real-world variability. CompareNodes solves that problem with RPC Node Benchmarking as a Service. Teams can submit any two endpoints—public or premium—and receive side-by-side results in seconds. Long-running charts track hundreds of providers over time, revealing performance trends and outliers.

Key stats today

• 200+ providers indexed

• 560+ protocols covered

• 2,200+ endpoints benchmarked

• 27 global probe sites spanning North America, Europe, and Asia

Because CompareNodes does not sell RPC or data services, its results remain impartial, allowing everyone (from solo devs to enterprise teams) to compare infrastructure on a level playing field.

Why CompareNodes Became DIN’s First Watcher

Most DIN partners deliver traffic; CompareNodes delivers measurement. By onboarding as the network’s first Official Watcher in May 2024, CompareNodes adds a native layer of monitoring that is both independent and verifiable. Their role is to

1. Onboard nodes into DIN’s registry with baseline performance checks

2. Monitor health continuously from multiple regions

3. Publish results so routing and staking rewards align with real performance

This collaboration ensures DIN’s marketplace remains transparent, rewarding providers that meet strict latency and reliability targets.

How CompareNodes Strengthens DIN

DIN already routes calls to the fastest endpoints within each network. CompareNodes’ granular data makes that routing smarter, adding region-specific insights that help operators fine-tune deployments. Builders can:

• Discover the best endpoint for their user base in Frankfurt, N. Virginia, or Singapore

• Validate that premium plans outperform free tiers before committing budget

• Compare their own self-hosted nodes against top DIN providers

This feedback loop accelerates decentralization by letting performance, not marketing, determine traffic flow.

Early Wins and Milestones

A standout milestone came when CompareNodes launched three-region Ethereum benchmarking (Frankfurt, N. Virginia, Singapore) just weeks after joining DIN. Providers quickly used the metrics to optimize load balancers, and several DIN nodes saw measurable drops in p95 latency. The community responded with tooling proposals that feed CompareNodes data into dashboards and auto-scaling scripts, illustrating the power of open metrics.

What Comes Next

1. Deeper dashboard integration: Surface live CompareNodes charts directly inside DIN tools so builders see performance at a glance.

2. Routing hooks: Let DIN’s AVS reference real-time benchmarks when selecting fallbacks or triggering slashing conditions.

3. More chains and regions: Expand probes to South America, Africa, and emerging L2 ecosystems.

4. Custom APIs: Offer teams programmatic access to benchmarking data for CI pipelines and automated failover logic.

Together, DIN and CompareNodes will make performance transparency a native feature of decentralized infrastructure—turning raw data into better routing, fairer incentives, and a smoother developer experience.

Explore More

• DIN Gateway Program → din.build

• CompareNodes Inspector → comparenodes.com

Highlights from Q2 2025 (First Half Recap)

The first half of 2025 was packed with progress. Here are some of the key milestones we hit in Q2 and earlier this year:

• MetaMask Solana Integration - DIN’s infrastructure helped power MetaMask’s new Solana wallet support, which went live in MetaMask Extension in Q2. By leveraging DIN’s decentralized RPC network for Solana, MetaMask could offer multi-chain functionality (“one home, many chains”) to its users. This was a proud moment for us, showcasing how DIN can plug in to enable non-EVM networks on a mainstream wallet.

• AVS Testnet v0.1 Completed - We successfully ran DIN AVS ephemeral testnet v0.1 with nine node providers staking via EigenLayer. This multi-stakeholder effort (with partners like AltLayer, BuildBear, and Txtx) proved that autonomous slashing and rewards can be integrated into our decentralized RPC infrastructure. It’s a huge validation of our Autonomous Verifiable Service (AVS) approach to enforce reliability and security in a decentralized way.

• Community Spotlights - We featured 8+ DIN providers and tech partners in our weekly highlight series (e.g. Web3 Wednesdays), showcasing the diverse contributors powering DIN’s ecosystem. From bare-metal infrastructure specialists to new tooling partners, these spotlights shined a light on our growing community of collaborators.

• AIDIN Launch - We introduced AIDIN, DIN’s AI persona, to make our advanced tech more accessible and engaging. AIDIN isn’t just a chatbot. It’s a friendly voice that answers questions about DIN in clear, simple terms and even joins our “Ask AIDIN” discussions to educate the community.

• Marketing Push - Alongside AIDIN, we kicked off a broader DIN marketing strategy. This included launching regular blog posts on Mirror, ramping up our social media presence (@DINBuild on X, YouTube, etc.), and sharing educational content. The goal: to raise DIN’s visibility and welcome more Web3 developers into our community.

• Bitcoin Support Testing - We began internal testing of Bitcoin integration within DIN. As MetaMask’s team works to expand into non-EVM networks like Bitcoin, we’ve been prepping our infrastructure to handle Bitcoin RPC traffic in a decentralized manner. Early results are promising, bringing us closer to including Bitcoin in DIN’s multi-chain roster.

• Scaling Milestone - DIN’s network scaled massively! We’re now handling 300+ million daily RPC requests, a 2× increase from the start of the year. This surging usage reflects both organic developer growth and new integrations like MetaMask’s. It’s amazing to see over 300 million JSON-RPC calls per day flowing through DIN’s decentralized providers, reinforcing the need for the reliable network we’re building.

• Watcher Upgrades - We completed a major Watcher overhaul, upgrading our health checks and monitoring. Watchers (our independent performance monitors) now catch issues faster and with greater accuracy, improving overall network reliability. These upgraded health checks mean node providers are immediately alerted to anomalies, and end-users enjoy more consistent service thanks to quicker failovers.

Looking Ahead: The Rest of 2025

DIN’s AVS is the on-chain “watchtower” that connects node providers and watchers, enforcing SLA rules through staking and slashing. This autonomous approach is a cornerstone for scaling DIN’s decentralized infrastructure with trust and transparency. With testnet v0.1 behind us, the next AVS iterations – and a host of other initiatives – are paving the way to mainnet. Here’s what’s on the roadmap for the rest of 2025:

• AVS v0.2 and v0.3 - Building on the success of v0.1, we’re already hard at work on AVS v0.2. This next version will roll out to more providers, integrating the lessons from testnet and refining our slashing, jailing, and reward parameters. In parallel, we’ve started planning v0.3, which will incorporate additional feedback, launch on a perpetual testnet (“Vector Testnet”), and prep the AVS for production. Each iteration brings us closer to a robust, battle-tested AVS for mainnet.

• DIN App Admin Modules - We’re launching new admin modules in the DIN App to improve user experience for all participants. Providers will get richer dashboards to manage their nodes and track rewards; Watchers will have tools to monitor network health and respond to incidents; and an AVS admin console will facilitate on-chain governance (like proposing parameter tweaks or reviewing slashing events). This will give our providers and watchers more control and insight as we decentralize those roles.

• din.build Ecosystem Hub - To improve transparency and accessibility, we are migrating our public materials to din.build. This means documentation, explorer views, and marketing content will live on din.build (moving away from infura.io pages). By centralizing resources on din.build, anyone can easily find information about DIN’s architecture, nodes, and how to get involved in one place. Expect a more comprehensive ecosystem hub that showcases everything from our whitepapers to real-time network stats.

• Economics & Tokenomics Paper - A deep dive into DIN’s economics is on the way. We’re finalizing a paper that details AVS economics, the DIN payment model, and $DIN mechanism design. This report will explain how fees flow through the system, how providers/watchers earn rewards, how slashing penalties are allocated, and how the $DIN token underpins network incentives and governance. Our aim is to share a transparent model with the community, articulating how value and rewards are distributed in a fully decentralized DIN.

• Network Expansions - More networks are coming! Solana was just the start – additional blockchains (both EVM and non-EVM) are on our integration roadmap for H2. As MetaMask and the Web3 community embrace new chains, DIN will be ready to provide decentralized RPC for them. We’re researching support for Layer 2s and non-EVM chains that are rising in demand. Each new network integration means developers can rely on DIN for a one-stop, multi-chain infrastructure solution.

• AVS Operator Resources - In preparation for mainnet, we’ll be releasing comprehensive AVS operator documentation and tooling. Node providers and watchers can look forward to setup guides, test suites, and monitoring tools to help them onboard smoothly. We’re also planning workshops and tutorial content so that by the time DIN AVS is live, a broad set of community operators will feel confident running nodes or watcher agents. Decentralization isn’t just about code, it’s about empowering people with knowledge and tools.

• Streaming Payments - Another big focus is payments and settlement within DIN. We’ve been prototyping DIN streaming payments by leveraging state channels so that value flows in real-time as RPC calls are served. Our payment system will likely ride on EigenLayer’s restaking or similar rails for security. These efforts will enable usage-based billing (think pay-per-call API access) that’s seamless and trust-minimized.

• DIN Association - Decentralizing infrastructure also means decentralizing governance. We plan to establish the DIN Association in the coming months. It’s a community-led foundation to oversee the network’s growth and integrity. The DIN Association will help manage aspects like multi-signature treasury funds, grants for ecosystem development, and stewardship of DIN’s open-source code. This structure, common in many decentralized projects, will formalize how contributors and stakeholders can shape DIN’s future in a transparent, accountable way.

• AVS Mainnet Launch - Everything is converging towards the DIN AVS mainnet launch targeted for late 2025. This will be the moment DIN graduates from the testnet phase to a fully decentralized production network. Mainnet AVS will bring decentralized staking, slashing, and rewards to all providers, with watchers safeguarding performance on-chain. Stay tuned for testnet v0.2/v0.3 updates as we march toward this huge milestone!

• $DIN Token Launch Prep: Last but not least, we’re finalizing plans for the $DIN token as we approach network launch. This includes publishing token materials (distribution, utility, and governance details) and ensuring alignment with the broader Consensys ecosystem. For example, we’re coordinating with Linea on potential synergies with a future $LINEA token. Our goal is to make $DIN a rewarding asset for DIN’s participants, while complementing initiatives and not conflicting with them. Expect more info on $DIN’s release and how it will integrate with things like MetaMask and Linea as those programs unfold.

Thank you to our community, providers, and partners for your support. Q2 2025 has affirmed our vision for a decentralized infrastructure network, and we’re beyond excited for what’s coming next. With these milestones achieved and ambitious goals ahead, DIN is more ready than ever to continue decentralizing Web3 with all the networks and AI agents out there. Stay tuned for more updates as we build towards an open, resilient future for blockchain infrastructure!

Web3 RPC & API infrastructure companies serve as the backbone of the Dapp industry, servicing data and write access to blockchains to the large majority of the industry. However, with the evolution and maturation of the industry, the business model supporting this backbone faces a challenge.  Termed by DIN as the “RPC trilemma,” web3 RPC & API providers are confronted with the difficulty to simultaneously achieve three competing priorities:

1. High Reliability: Consistent uptime, low latency, and quality of service

2. Breadth of Services: Support for the multitude of idiosyncratic Layer-1 and Layer-2 networks and the many features and diverse APIs required

3. Economic Sustainability: The ability to maintain a margin positive offering in the face of diverse competition

In the post-2022 landscape, this trilemma has become more pronounced. The Web3 industry has matured, with meaningful financial activity on-chain that requires 100% uptime. DeFi and AI agents demand faster and more performant blockchain access to execute advanced strategies. As Dapps go multi-chain, the elevated performance requirement is expanding across a swiftly growing number of new blockchains. As these blockchains become more complex with higher throughput and idiosyncratic features, infrastructure costs spiral with limited economies of scale to be realized.

This blog post examines how these priorities are in tension and the practical challenges faced by API providers. Finally, it examines how Infura, the industry's leading RPC company, is solving this challenge by leveraging the superpowers of web3, permissionless innovation and community empowerment, via its evolution into DIN.

The RPC Trilemma: Reliability vs. Coverage vs. Cost

The RPC trilemma can be summarized as the need for Remote Procedure Call (RPC) services to be reliable, performant, and cost-efficient – often a “pick two of three” situation.

Pick any two, traditional providers can’t deliver all three:

| Picked dimensions | Hidden downside

| Reliability + Coverage | Run-rate costs explode, forcing price hikes.

| Coverage + Cost | One-off nodes per chain lead to throttling and outages.

| Cost + Reliability | Narrow chain menu; developers go elsewhere.

In practice, an ideal RPC provider would have maximal uptime and responsiveness, support all the networks and features a developer needs, and remain affordable and easy to use. In reality, maximizing one dimension often undermines another. For example:

• High Reliability & Performance: This requires robust infrastructure with globally distributed nodes, rapid scalability, failover mechanisms, and heavy monitoring, which can drive up costs.

• Breadth of Services (Multi-Chain Support): After L2s became popular, the number of prominent blockchains exploded. Dapps have evolved to need access to these networks to create a seamless cross-chain UX for users. Supporting many L1s/L2s means running more nodes and adapting to different protocols, from Ethereum’s account model to UTXO or novel consensus designs. This divergence adds to R&D costs and complicates maintenance.

• Cost Efficiency: Developers are highly sensitive to infrastructure costs and a competitive market exists among the large number of companies that can offer node services. In the effort to be competitive on cost, RPC companies have to consider focusing on an area of specialization, forgo investments in performance improvement or cut other operational overhead costs.

Rising Demands: Dapps and AI Agents Need High Reliability & Performance

Modern Dapps (DeFi protocols, NFT marketplaces, etc) and emerging AI agents increasingly require fast and reliable on-chain data in real time. Automated trading bots, on-chain games, and AI-driven DeFi managers can make split-second decisions and thus depend on low-latency, high-throughput RPC access.

For example, AI agents in DeFi rely on “real-time, high fidelity data” with updates in milliseconds to act on fast-moving markets. Any downtime or lag in accessing blockchain state can lead to lost opportunities or even financial loss.

Uptime is critical. Speed is a must.

In response, Dapp developers increasingly build in their own redundancy. It’s now a best practice to use multiple RPC endpoints with automatic failover and parallel processing. For example, OpenZeppelin’s tooling recommends configuring at least three endpoints and rotating to ensure high availability. If one returns errors (e.g. HTTP 429 rate limits), the client library can seamlessly switch to another. This multi-endpoint strategy significantly improves resiliency, as no single point of failure will take the Dapp offline.

However, maintaining such redundancy comes with cost and complexity. A project may need subscriptions to Infura, Alchemy, QuickNode, etc., concurrently, paying each for sufficient capacity.  Dapps must also implement logic to route requests and handle inconsistent data between providers. Most Interesting; however, these clunky solutions organically, unintentionally, aim to solve the problem inherent to centralization. The opportunity exists, then, for a more elegant solution that leverages crypto-native solutions to deliver the never down, decentralized promise of blockchains.

OmniChain Complexity and Fragmented Services

Since 2022, the Ethereum ecosystem has become unequivocally multi-chain. A quick look at Dapp Radar and you will find 100s of L1/L2s and user activity and liquidity spread across Ethereum mainnet and an array of L2 networks (Optimism, Arbitrum, Polygon’s chains, zk-rollups), as well as alternative L1s (Avalanche, BNB Chain, Fantom, etc.).

Many Dapps have followed suit, deploying their contracts on several chains to reach a broader user base. This brings clear benefits like access to more users and lower fees on L2s, but it magnifies infrastructure challenges.

It becomes difficult for a single RPC provider to scale their chain coverage at the accelerating growth of the L1/L2 ecosystem. RPC companies take on financial risk when launching a new chain and trade-off other roadmap potential. For modern, high-throughput blockchain designs, the time teams need to devote to truly understand the intricacies of running and optimizing nodes adds to the R&D cost and time. In an informal DIN survey of 15 of the leading RPC providers, two-thirds indicated they prefer to not split focus on greater than 10-15 blockchains at one time.

When a Dapps primary provider doesn’t have sufficient coverage for access to its necessary blockchains, they rely on multiple third-party RPC providers to get the coverage required; often looking for specialists in a certain ecosystem (e.g. EVM, SVM, Cosmos). This means managing multiple provider accounts, introducing integration friction. Each provider may have different pricing, rate limits, dashboards, and sometimes require using different authentication tokens or even paying in different currencies.

Yes, some providers do advertise coverage for 60+ or even 100+ chains. However, the dirty-little-secret of the RPC industry is that in order to support that breadth of networks, teams either have insufficient infrastructure running, maybe one single node, that comes with a performance cost. Or, more common, the RPC provider white-labels and up-charges another RPC provider’s service to give its customer access.

Our industry deserves better.

Costs and Friction in a Multi-Provider World

The third side of the trilemma, cost control, has grown in importance as the market has evolved since 2021. The exuberance of the 2021 boom faded and projects became more cost-conscious. Dapps were competing more fervently over user acquisition and shifted-focus toward value-added layers; while looking for ways to cut at the non-differentiating API/RPC plumbing layers.

The number and diversity of chains exploded and Dapps sought early entry in search of ecosystem growth. Not too long ago, it was headline news when a Dapp added support for a new chain; now every Dapp is beginning to launch its own chain, and an omnichain, frictionless Dapp experience is the new expectation. With the growth in new L1s and L2s, these chains started to get more complex and idiosyncratic in search of differentiation from one another. This resulted in running node infrastructure getting more complex and expensive to run.

For a web3 infrastructure team, as you add new chains you split your team’s attention and resources. Each chain has its own requirements, nuances, and infrastructure. Even among opStack chains, which are fairly uniform, you have instances like Hemi and BOB which run a parallel BTC chain and Unichain which has adopted a unique TEE scheme. These differences result in real challenges for professional infrastructure companies; particularly at the rate with which chains are expanding and being demanded by customers.

Another trend is the growth in ZK-chains or high-throughput blockchains as our industry chases more real-world use cases. These types of chains require large server instances with disc sizes exceeding 20, 30, even 40 TBs to run nodes. This drives up the fixed cost requirements to run nodes profitably; often leaving teams to build less redundant, lower quality, setups to cut costs. This trade-off has resulted in decreased industry performance

With this evolution of the market, running RPC infrastructure has become economically challenging. All of this makes clear why the RPC trilemma is a real and practical challenge: it’s hard to simultaneously maximize uptime/quality, connect to everything, and keep costs low. However, the ecosystem is actively seeking solutions to ease these trade-offs.

DIN: A Unified, Elegant Solution to the Trilemma

Blockchains have the expectation that they are never-down; and so too should the infrastructure API gateways through which the ecosystem connects to them. The industry deserves a solution that breaks through the RPC Trilemma.

We should embrace the superpowers of web3. The industry should no longer stitch together clunky solutions that aggregate a multitude of web2-style API SaaS companies. Instead a permissionless, incentivized protocol should represent the dial-tone the industry taps into  to access the redundancy, chain breadth, and specialized performance needs.

Infura introduced the DIN in late 2022. DIN tackles the RPC trilemma by building a unified Web3 API Marketplace and services layer. Instead of Dapps connecting to a single provider’s server cluster, they connect to the  DIN protocol, which routes their requests to a pool of 50+ independent providers in the network. These providers include both large infrastructure firms and smaller node operators around the world.

DIN acts as an intelligent gateway: if one provider fails or is overloaded, the request seamlessly fails over to another, without the Dapp needing to do anything.

Finally, DIN is building a marketplace. If you disagree with DIN’s intelligent gateway; you can tap into the marketplace, optimizing API requests across the community of over 50+ independent web3 API providers.

Stay tuned for more by following @DINBuild across socials.

From Institutional Staking to DIN Participation

Founded to bring enterprise rigor to Web3 infrastructure, Validation Cloud operates SOC 2 Type II-certified clusters and recently raised a $15 million Series A to accelerate global expansion of its AI and staking services. The team joined DIN in 2024 to extend that reliability to a decentralized, performance-routed marketplace. For Validation Cloud, DIN’s cryptoeconomic incentives and transparent monitoring offered the perfect venue to showcase low-latency endpoints while contributing to a trust-minimized ecosystem.

How DIN Improves on Existing Models

Traditional RPC hosts often limit top-tier performance to one or two regions, and many “decentralized” offerings trade visibility for convenience. DIN routes traffic to the fastest, most reliable nodes across all providers and enforces SLAs through staking and slashing. This model aligns with Validation Cloud’s focus on measurable uptime, latency, and institutional-grade observability, creating an environment where performance is the primary driver of rewards.

Networks Live on DIN Today

Validation Cloud currently serves

• BNB Smart Chain mainnet

• BNB Smart Chain testnet

• opBNB mainnet

• opBNB testnet

These chains attract high-growth applications that demand sub-second responses, a metric where Validation Cloud consistently leads in global benchmarks. The company plans to add more of the 50-plus networks it already supports (among them Bitcoin, Ethereum, Solana, Base, and Monad) as DIN expands.

Business Impact and Technical Alignment

DIN introduces a new revenue lane that rewards verifiable performance rather than simple participation. Because Validation Cloud’s monitoring, alerting, and automated scaling were built for institutional clients, absorbing DIN traffic required minimal overhead. The network’s transparent metrics also feed back into internal performance dashboards, helping the team refine latency targets across all regions.

Collaboration Highlights

DIN’s engineering group provided rapid feedback loops, joint incident reviews, and inclusive workshops that accelerated Validation Cloud’s shift from testnet to mainnet across multiple L1 and L2 environments. This hands-on collaboration has been cited by the Validation Cloud team as a key reason for the partnership’s early success.

Vision for Decentralized Infrastructure

Validation Cloud views decentralized RPC as essential for a scalable, permissionless Web3. As traditional finance and large enterprises integrate blockchain solutions, demand for verifiable, low-latency endpoints will only grow. DIN’s marketplace model ensures that no single provider becomes a bottleneck, while Validation Cloud’s AI-driven insights help institutions make sense of an expanding data universe. Looking ahead, the company sees opportunities for DIN to move beyond RPC into additional data and compute services. These are areas where Mavrik’s natural-language analytics could add significant value.

What Comes Next

• Expanded network support across high-value chains

• Shared analytics dashboards that surface real-time performance insights for DIN operators

• AI-powered tooling from Mavrik to help builders query, visualize, and automate on-chain data

Validation Cloud is committed to advancing DIN’s mission of combining enterprise-grade performance with trustless infrastructure, creating a stronger foundation for the next wave of institutional and consumer Web3 applications.

Explore More

• DIN Gateway Program → din.build

• Validation Cloud → validationcloud.io

• Mavrik Data × AI → validationcloud.io/ai

Reliability by Design

Chainstack operates full and archive nodes across the United States and Europe, serving more than 10 billion relays per month for customers such as 1kx, Story Protocol, DRPC, PASG Network, Pokt.Network, ARKEO, Lava Network, and Elliptic. Their multi-cloud setup automatically scales and monitors nodes, delivering low-latency access while avoiding single-region bottlenecks. Public tooling like the Compare Dashboard offers real-time success-rate and latency benchmarks that anyone can audit, reinforcing their transparency ethos.

Why DIN Fit the Mission

Many “decentralized” RPC services still depend on a single hidden operator or require builders to stitch together several vendors. DIN replaces that patchwork with a unified, on-chain marketplace that routes traffic to the fastest, most reliable endpoints. Chainstack views this model as the missing link between ease of use and true decentralization. Joining DIN allowed the team to plug its high-availability clusters into a network where performance is continuously verified and fairly rewarded.

Network Coverage on DIN

Chainstack currently delivers endpoints for

• Ethereum

• Arbitrum and Arbitrum Sepolia

• Base

• BNB Smart Chain (BSC)

• Scroll

• Solana

• Starknet

• ZKsync

These eight ecosystems align with Chainstack’s existing full and archive node fleet, ensuring instant, globally distributed capacity for builders who need production-grade throughput.

Business Impact

DIN’s performance-weighted routing naturally directs heavy traffic toward well-maintained infrastructure. Chainstack’s clusters absorb that demand without extra overhead because monitoring, alerting, and billing pipelines were already in place. The result is a healthy boost to enterprise revenue, achieved through reliability alone rather than aggressive sales tactics.

Unexpected Insights

The team predicted Ethereum-centric usage but quickly saw developers overwhelming Mantle and Blast endpoints the moment those networks went live. This rapid adoption confirmed that a neutral marketplace can accelerate new-chain growth simply by making high-quality RPC instantly discoverable.

Building a Stronger Web3 Backbone

Chainstack believes decentralized infrastructure is indispensable for user-friendly, resilient dApps. Their open-source tools, such as the Compare Dashboard and load-balancer templates, let projects build multi-cloud, geographically balanced RPC stacks in minutes. They also foresee pricing moving from per-request billing to predictable RPS tiers, similar to the Unlimited Node add-on that offers flat-fee, capacity-capped clusters for demanding workloads.

Looking Ahead

The Chainstack team is eager to

• contribute analytics and benchmarking utilities for DIN,

• deploy and configure new networks on demand, and

• continue refining flat-rate capacity models that simplify budgeting for high-traffic applications.

Their long-term commitment to performance and openness makes Chainstack a cornerstone of DIN’s growing provider ecosystem.

Explore More

• DIN Gateway Program → din.build

• Chainstack Unlimited Node → docs.chainstack.com/unlimited-node

• Chainstack Compare Dashboard → compare.chainstack.com

From POKT to NodeFleet: A Journey Toward Independent Scale

NodeFleet was founded by the former Head of Infrastructure at POKT.network. After leaving in 2022, the founder set out to build a more agile and independent infrastructure operation, capable of supporting the growing diversity of blockchain networks and applications.

Today, NodeFleet operates bare-metal and virtualized infrastructure across the United States and Europe. They provide data services to top blockchain companies including 1kx, Story Protocol, DRPC, PASG Network, Pokt.Network, ARKEO, Lava Network, and Elliptic. With billions of monthly relays under management, NodeFleet has become a foundational partner for Web3 teams looking for performance, reliability, and scale.

Joining DIN was a strategic next step. The team saw DIN as an opportunity to participate in a permissionless infrastructure layer designed for verified performance and high-impact application traffic.

A Different Approach to Decentralized Infrastructure

NodeFleet has been part of many infrastructure networks. What makes DIN different, according to the team, is its focus on structured onboarding, application-grade reliability, and transparent incentives.

DIN introduces a progressive framework for adding new blockchains and managing RPC traffic through a verifiable system. While some processes feel slower compared to other platforms, NodeFleet appreciates the long-term value that DIN provides. The protocol’s measured approach helps ensure service consistency and operational readiness before scale is introduced.

Network Support and Contributions

NodeFleet currently supports the following networks on DIN:

• Sei

• Sei Testnet

• Arbitrum

• Arbitrum Sepolia

These networks reflect a combination of production usage and testnet readiness, giving NodeFleet opportunities to serve both mature ecosystems and early-stage deployments. While the team missed an opportunity to support BSC during testing, they remain eager to onboard additional networks and grow their footprint within DIN.

Revenue Impact and Long-Term Commitment

Participating in DIN has added a valuable revenue stream for NodeFleet. While it is not yet a major portion of their balance sheet, the team sees DIN as a strategic long-term partner. They value the reliability and professionalism of the DIN team, as well as the opportunity to contribute to a growing network built on transparent values and shared performance goals.

NodeFleet has committed to supporting DIN as both a provider and a collaborator. They see their participation not just as a business opportunity, but as a way to help shape the future of decentralized infrastructure.

A Culture of Collaboration

One of the most rewarding aspects of working with DIN, according to NodeFleet, is the collaborative culture. As an independent provider, they have felt welcomed and respected. DIN’s open engagement and clear technical alignment have helped establish trust and foster a shared sense of purpose.

NodeFleet values this relationship and is ready to contribute further, not only as a node operator, but as a partner in infrastructure development.

The Role of Decentralized Infrastructure in Web3’s Future

NodeFleet believes that decentralized infrastructure is essential for the long-term growth of Web3. With new networks launching regularly and user demand increasing, scalable, reliable, and geographically diverse infrastructure is no longer optional—it is critical.

Decentralization also brings greater service diversity, enhanced fault tolerance, and higher levels of transparency. NodeFleet sees this as especially important as applications begin to touch real-world assets, cross-chain systems, and compliance-sensitive use cases.

Looking Ahead

NodeFleet is actively exploring new contributions to DIN, including:

• Development of analytics and benchmarking systems

• On-demand deployment and configuration support for emerging blockchain networks

Their goal is to support DIN not only as a provider, but as an innovation partner. As DIN expands its reach, NodeFleet plans to grow with it, helping deliver the infrastructure foundation for a more open and scalable Web3.

Learn More

Discover how DIN and NodeFleet are building the future of decentralized RPC:
🔗 din.build

AltLayer is not just an infrastructure enabler. Their contributions have helped bring DIN’s decentralized RPC and verifiable compute model into production-ready territory, positioning DIN as a secure, scalable, and aligned component of the EigenLayer ecosystem.

Rollups, AVS, and Modular Infrastructure at Scale

AltLayer is an infrastructure platform focused on modular blockchain deployment. Through their Rollups-as-a-Service (RaaS) framework, AltLayer enables developers to launch custom rollups quickly using a no-code dashboard or developer SDK. Their platform supports multiple leading rollup frameworks, including OP Stack, Arbitrum Orbit, Polygon CDK, and ZKsync ZKStack, as well as integrations with Celestia, EigenDA, and Avail for modular data availability.

Their innovation around ephemeral rollups allows for short-lived, purpose-built rollup environments; ideal for events like NFT mints or gaming tournaments, where throughput and scalability are required temporarily. This model significantly reduces cost, complexity, and risk for developers looking to scale on-demand without managing long-term infrastructure.

With billions in total value secured across restaked rollups and applications, AltLayer has quickly become one of the most trusted platforms for secure, flexible rollup deployment across the Web3 landscape.

Strengthening DIN's AVS Layer from the Ground Up

AltLayer has been deeply involved in building DIN’s AVS infrastructure. As the core development partner for DIN’s AVS modules, AltLayer helped implement key components responsible for enforcing service-level agreements, staking logic, and slashing conditions using EigenLayer’s middleware.

Working side-by-side with the DIN team and the engineers at EigenLayer, AltLayer continues to ensure that DIN’s AVS remains compatible with upstream protocol changes and middleware improvements. Their work allows DIN to maintain forward compatibility, reduce fragmentation, and keep pace with the evolving EigenLayer ecosystem.

In addition to building core AVS logic, AltLayer helped design the onboarding flow for AVS operators and Watchers, ensuring a smooth developer experience while supporting decentralized participation.

A Key Milestone: DIN AVS Ephemeral Testnets

Earlier this year, AltLayer supported DIN’s ephemeral testnet v0.1, v0.2, and v0.3. These were all milestone releases that successfully integrated EigenLayer’s new slashing mechanism. The testnet was used to onboard DIN Providers and Watchers, test key AVS interactions, and validate staking and penalty conditions in a live environment.

The success of this testnet demonstrated the real-world viability of DIN’s model: a decentralized RPC layer backed by performance-based economics and automated enforcement. AltLayer’s technical guidance was instrumental in enabling this result, and their support helped ensure a smooth rollout across multiple AVS participants.

What Comes Next: Scaling DIN Across the Rollup Ecosystem

Looking forward, AltLayer plans to offer DIN as a native RPC option for clients launching rollups through its RaaS platform. This integration would give developers direct access to DIN’s decentralized and crypto-economically secure RPC endpoints, while also helping distribute demand across DIN’s Provider network.

As DIN approaches its mainnet launch, AltLayer remains a critical partner in operational support, AVS refinement, and rollout strategy. Their continued collaboration helps ensure that DIN’s infrastructure remains aligned with the latest security standards, governance frameworks, and network incentives.

AltLayer’s long-term commitment to decentralization, verifiability, and high-performance infrastructure makes them an ideal tech partner for DIN’s mission.

Final Thoughts

AltLayer’s role in DIN extends far beyond integration. As a builder, collaborator, and strategic advisor, AltLayer has helped lay the foundation for DIN’s decentralized infrastructure to scale responsibly and securely. Together, we are building a future where RPC access, rollup deployment, and verifiable compute are modular, programmable, and economically aligned with the needs of developers and users alike.

Learn More

Explore how AltLayer and DIN are working together to advance the future of permissionless infrastructure:🔗 din.build🔗 altlayer.io

Infrastructure First: The Origin of Liquify

Liquify was founded on the belief that decentralization must begin at the infrastructure layer. The team operates bare-metal servers across geographically distributed regions to maximize uptime, reduce latency, and eliminate reliance on centralized cloud providers.

With experience spanning validator operations, protocol advisory, and data infrastructure across major ecosystems such as Ethereum, Cosmos, and Solana, Liquify has long focused on critical system reliability. When they discovered DIN’s approach to decentralized data delivery and oracle systems, the synergy was immediate. Joining DIN allowed them to apply their infrastructure principles to a new, trust-minimized data layer that removes opaque intermediaries and replaces them with transparent, verifiable compute.

Rethinking the Oracle Model

Most existing oracle solutions rely on centralized aggregators, permissioned validators, or off-chain gatekeepers. Liquify saw DIN as a new paradigm. By enabling a permissionless Feeder model, DIN allows any operator to contribute data directly, with every step verifiable on-chain or through cryptographic evidence.

In this model, data sourcing, submission, and computation become open, observable, and modular. Operators can build custom feeds, developers can audit them in real time, and users can choose sources based on transparent performance. This creates a foundation for true data sovereignty—one that aligns closely with Liquify’s values and technical strengths.

Networks Supported and Performance Milestones

Liquify currently supports a broad range of production and test networks on DIN, including:

• Arbitrum

• Avalanche

• Binance Chain

• Binance Chain Testnet

• Ethereum Mainnet

• Ethereum Hoodi Testnet

• ZKsync

• ZKsync Sepolia

These networks reflect both maturity and emerging potential. By contributing to testnets and mainnets alike, Liquify supports the full lifecycle of Web3 development—from early experimentation to production-grade data delivery.

Liquify’s high reliability as a Feeder node has made them a go-to provider for many of these integrations. Their consistent uptime and responsiveness continue to help strengthen DIN’s multi-network coverage.

Operational Impact and Revenue Model

Joining DIN has introduced a new compute category that rewards performance at the infrastructure level. Unlike traditional validator economics that depend on staking and delegation, DIN rewards are earned directly through uptime, accuracy, and data consistency.

This model is well suited to operators like Liquify, who run purpose-built infrastructure designed for durability. It also introduces a more active and performance-based revenue stream that does not require reliance on user delegation. As DIN expands, Liquify sees this as a path to greater financial sustainability for independent node operators.

Learnings and Technical Adaptability

From a technical perspective, Liquify was impressed by how quickly they could deploy within the DIN system. Their Feeder node reached 100 percent uptime from day one, and the modular nature of DIN’s architecture allowed them to customize their operations.

One particularly useful insight has been the ability to create internal tooling to visualize and validate data workflows. These tools improve client communication, enhance internal transparency, and allow Liquify to continuously optimize its service quality.

The Role of Infrastructure in Web3’s Next Chapter

Liquify sees decentralized infrastructure as essential to the long-term credibility of Web3. As DeFi protocols and real-world asset platforms scale, the need for trust-minimized backend systems will only grow.

Many protocols today still rely on centralized infrastructure for oracles, RPC endpoints, or data storage. These dependencies weaken the security guarantees of otherwise decentralized applications. Solutions like DIN are a step toward correcting that imbalance. Liquify believes that resilience at the infrastructure layer is not only a technical requirement—it is a philosophical one.

Looking Forward

As part of DIN’s founding provider cohort, Liquify is committed to scaling the network. They plan to support additional chains, new data types, and emerging use cases that rely on trust-minimized infrastructure.

Their goal is to empower builders with full control and visibility over the data that powers their applications. In partnership with DIN, they are helping redefine what is possible when infrastructure is open, verifiable, and fully aligned with the principles of Web3.

Learn More

Explore how DIN and providers like Liquify are building the next generation of decentralized infrastructure:🔗 din.build

Solving Web3’s Centralization Bottleneck

Rivet was built to solve a foundational problem in Web3. Despite the proliferation of decentralized networks and applications, most developers still depend on centralized services for access to blockchain data. This creates a critical trust gap.

Rivet’s infrastructure addresses that directly. It provides high-throughput, reliable access to blockchain networks using software built with open source principles. The goal is to make node infrastructure as seamless and dependable as possible for developers, while removing the need to trust a single provider.

This pursuit of trustless, performant infrastructure is exactly where Rivet and DIN converge. Both aim to make access to on-chain data more secure, more scalable, and more aligned with the principles that define Web3.

Why DIN

For Rivet, partnering with DIN was a strategic decision grounded in technical alignment. DIN is not just a node network. It is a coordinated, incentive-aligned protocol where infrastructure providers can deliver access with measurable performance and cryptoeconomic accountability.

Rivet joined DIN at the protocol design level. Their goal was to help build a system that addressed the very challenges they had been solving independently for years: how to create a sustainable, decentralized infrastructure layer that delivers real performance and reliability at scale.

Technical Contributions to DIN

Rivet’s involvement with DIN runs deep. One of their key contributions is the DIN Router, the component responsible for distributing RPC traffic across multiple nodes in a way that balances latency, redundancy, and trust minimization.

In addition to the Router, Rivet is building out the Node Kit, a toolkit that enables independent operators to onboard to DIN quickly. This tool will simplify node registration and make it easy for new infrastructure providers to become part of the DIN ecosystem.

Rivet is also helping shape the upcoming payments system using NFTs, which will allow usage-based revenue to flow seamlessly from consumers to node operators. This system will support both stability and decentralization, creating a true utility layer for infrastructure.

A Vision in Motion

Rivet sees every milestone on the DIN roadmap as part of a larger arc—one where centralized infrastructure becomes obsolete. With each passing week, what once felt like a long-term vision is becoming reality.

Among the many technical achievements, Rivet points to DIN’s use of EigenLayer’s Actively Validated Service (AVS) as a major differentiator. By enforcing service-level agreements through staking and slashing, DIN introduces real accountability to infrastructure provision. This turns uptime and reliability into enforceable conditions, not just expectations.

Looking Ahead

Rivet is most excited about expanding access. As the Node Kit matures and AVS integration deepens, DIN will be able to support a broader range of providers. Smaller teams and independent node operators will gain the ability to earn revenue directly from their infrastructure, without intermediaries.

Over time, Rivet expects DIN to become the default backend for dApps across Layer 1s, Layer 2s, and emerging networks. They see a future where developers no longer have to choose between decentralization and performance. In this vision, decentralized infrastructure is not only viable—it is the superior option.

Ultimately, Rivet believes infrastructure will be run by unstoppable code, supported by open networks like DIN, and aligned by design with the values Web3 was built on.

Final Thoughts

Rivet’s role in DIN is foundational. As both a contributor and a visionary partner, they have helped shape what DIN is and what it will become. Through technical leadership and a long-term commitment to decentralization, Rivet continues to push the boundaries of what infrastructure can be.

Explore more about how DIN is redefining blockchain access:🌐 din.build

A Decade of Infrastructure Experience, Formalized

0xFury was founded by three co-founders who each have nearly ten years of experience running Web3 infrastructure. Their journey began independently, operating PoW and PoS nodes, supporting early networks, and building custom tooling. Over time, they began collaborating across networks, offering mutual support on node deployments, validator operations, and RPC architecture.

In 2023, they decided to formalize their efforts. Launching 0xFury allowed them to unify their infrastructure expertise and scale their impact under a shared brand. Their objective was clear: deliver enterprise-grade infrastructure without compromising on decentralization.

When the team learned about DIN, it aligned immediately with their mission. They had already been working closely with decentralized RPC providers, so participating in a decentralized RPC protocol backed by Infura felt like a natural next step.

Why DIN Stood Out

For the 0xFury team, DIN addressed a long-standing gap in Web3 infrastructure. Most decentralized RPC projects tend to struggle with either developer experience, service reliability, or coordination among providers. On the other hand, traditional providers often offer great UX but centralize risk.

DIN offered a different model. It retained the standards and developer experience Infura is known for, while decentralizing the backend across independent node operators. Through EigenLayer integration, DIN also introduced cryptoeconomic accountability via staking and slashing. This balance of decentralization and reliability made DIN unique among existing infrastructure solutions.

According to the team, DIN makes it possible to contribute to a more resilient ecosystem while participating in a professionally operated, standards-aligned protocol.

Supporting Mantle and Unichain on DIN

0xFury first joined DIN to support Mantle, an emerging Layer 2 focused on performance and scalability. Shortly after, they were onboarded to help launch RPC infrastructure for Unichain, another new network looking to provide decentralized access from the outset.

Both networks represented strong technical foundations and growth potential. The team saw an opportunity to deliver stable, performant RPC endpoints while helping bootstrapping ecosystems avoid centralized infrastructure dependencies. Their work with DIN positioned them as early contributors to each chain’s decentralized foundation.

Operational Impact and Scale

Joining DIN has allowed 0xFury to expand their infrastructure footprint. To meet network requirements and growing demand, they spun up new servers in an additional geographic region, improving latency and fault tolerance across users and applications.

DIN also brought a more structured and predictable revenue model compared to typical node operations. With clear expectations, high-quality documentation, and real network demand, 0xFury was able to confidently invest in infrastructure and capacity expansion.

Lessons from Production

Since joining DIN, 0xFury has remained deeply engaged in real-time network operations. As early RPC providers for Mantle and Unichain, they had to respond to chain upgrades, node stability issues, and urgent infrastructure changes.

These experiences highlighted the importance of proactive participation. DIN Providers are not passive node operators. They play an active role in keeping RPC access stable and aligned with the underlying network state. This operational engagement has helped build trust with both the DIN team and the protocols they support.

A Vision for the Future of Web3 Infrastructure

For 0xFury, decentralized infrastructure is essential to Web3’s long-term integrity. Applications may be permissionless at the protocol level, but if backend services like RPC are centralized, the system remains vulnerable.

This is why they see DIN as a critical evolution. It provides the performance and usability developers expect, but with an architecture designed for trustless-ness and resilience.

In their words, the future of Web3 will only be as decentralized as the infrastructure that powers it. Supporting DIN is their way of helping ensure that infrastructure keeps pace with the values and demands of the next generation of decentralized applications.

Closing Thoughts

As DIN prepares for mainnet and expands its AVS implementation, partners like 0xFury are helping set the standard for professional, mission-aligned infrastructure provision. Their work reinforces the idea that decentralization and high performance are not mutually exclusive, but essential to each other.

🛰️ Learn more about DIN and how to get involved at din.build

Everstake is one of our standout node providers on DIN, known for operating high-performance infrastructure across dozens of chains. With a track record of reliability and an unwavering commitment to decentralization, Everstake is helping define what it means to be a next-gen infrastructure partner in the Web3 ecosystem. Let’s dive into their story.

A Legacy of Performance, a Vision for Decentralization

Everstake isn’t new to Web3. With over six years in the game and experience running infrastructure for 85+ blockchain networks, they’ve earned a reputation as one of the largest PoS/dPoS validators and node operators in the space. Operating more than 40,000 nodes across networks, bridges, and infrastructure layers, Everstake brings unmatched scale and technical depth to DIN.

Their DIN journey began in 2023, during our early testnet phases. Drawn by our shared mission (making Web3 more accessible, reliable, and decentralized), Everstake joined as an early provider to help bootstrap a truly trustless RPC infrastructure layer. “We’ve always believed resilient, decentralized RPC infrastructure is key to Web3’s future,” the team shared. “Becoming a DIN Provider aligns with that vision.”

Bridging Traditional and Decentralized Infrastructure

What sets DIN apart? For Everstake, it's the fusion of reliability and decentralization. Traditional RPC providers often face bottlenecks from centralized control, while many decentralized models lack the operational coordination to scale. DIN bridges this divide by integrating with EigenLayer, introducing economic guarantees and cryptoeconomic accountability through slashing, staking, and service-level enforcement.

This model creates a permissionless RPC marketplace where performance isn’t just expected; it’s enforced. “DIN is not only scalable, it’s trustworthy. That’s the critical innovation.”

Supporting Scroll with High-Availability RPC

Today, Everstake provides RPC infrastructure for Scroll, a fast-growing zkEVM-based Layer 2 that demands high throughput and low latency. Everstake’s DIN-hosted Scroll RPC endpoint delivers on both fronts, offering fast, stable access for dApp developers building the next wave of zk-powered applications.

“Scroll is one of the most exciting L2s out there. Reliable RPC access is mission-critical for the ecosystem’s success,” Everstake noted. “DIN helps us ensure that access is not only performant but trustless.”

Operational Impact and Early Wins

DIN’s collaborative onboarding and standardized documentation stood out to Everstake early on. “The onboarding flow was smooth and well-structured. It helped us align quickly and set clear expectations,” the team shared. That operational clarity has made it easier to scale their participation, all while preparing for deeper integration as DIN progresses toward mainnet.

Along the way, Everstake has discovered new collaboration opportunities, especially as DIN evolves into a hub for both emerging networks and infrastructure operators. Their early involvement has positioned them at the center of a growing, economically-aligned ecosystem.

The Path Forward: Mainnet and AVS

Looking ahead, Everstake is actively participating in the DIN AVS testnet, helping validate slashing enforcement, service guarantees, and Watcher coordination mechanisms. With DIN set to launch its AVS on mainnet later this year, providers like Everstake will soon operate in a fully decentralized, permissionless framework—backed by restaked ETH and cryptoeconomic incentives.

“DIN shows that decentralization and performance don’t have to be a tradeoff. We’re proud to be helping build the infrastructure that will carry Web3 into the next decade.”

As DIN expands into more networks and rolls out its full slashing-enabled architecture, partners like Everstake are setting the benchmark for what decentralized infrastructure should look like: fast, resilient, and economically accountable.

How to Get Involved

Stay tuned for more exciting updates, and don’t forget to follow us on our new social channels (DINBuild on X, Mirror.xyz, and YouTube) to stay informed. Learn more about DIN on din.build.

AIDIN is more than a chatbot. It's a voice designed to make complex topics like Autonomous Verifiable Services (AVS), decentralized RPC, EigenLayer integration, new chains and protocols, and blockchain infrastructure approachable for everyone. AIDIN helps answer questions clearly, assist with educational initiatives, and offer real-time engagement with the DIN community.

One of the most exciting early projects with AIDIN is the "Ask AIDIN" series. In this live conversation format, Clemens Wan (Lead Architect at DIN) and AIDIN engage in recorded discussions, demystifying critical topics about decentralization, infrastructure, and the future of Web3.

https://youtube.com/shorts/ivS26JLvdO8?feature=share

Some example questions from the "Ask AIDIN" series include:

• "What is DIN and why is decentralizing RPC infrastructure so important?"

• "How does EigenLayer integration enhance the security of DIN?"

• "What are Autonomous Verifiable Services (AVS) and why do they matter for Web3 developers?"

• "How does DIN support node providers in a decentralized network?"

Right now, AIDIN draws on a rich static dataset compiled from DIN's whitepapers, roadmaps, and documentation. This ensures that AIDIN's answers stay consistent with DIN's values and vision. As we grow, AIDIN will evolve too, incorporating dynamic public data, internal insights, and continuous feedback loops from the community.

Looking ahead, we'll share more posts to dive deeper into AIDIN's journey:

• How AIDIN Was Built: A look under the hood at our tech stack, trained data, and Slack integrations.

• AIDIN's Roadmap: Our vision for how AIDIN will support DIN, the community, and node providers.

• AIDIN Usage Retrospective: Challenges we've encountered and solutions we've implemented.

• AIDIN’s Role in Decentralization: How AIDIN strengthens community knowledge sharing in a decentralized future.

AIDIN is just getting started. Stay tuned and follow AIDIN at @DINBuild as we continue building AIDIN as a cornerstone of decentralized infrastructure communication and a trusted voice for the DIN community.