Skip to main content
Loading...

What does 'Decentralized by DIN' mean?

Does this article need to be translated?

Contribute to the Help Center

Submit translations, corrections, and suggestions on GitHub, or reach out on our Community forums.

By [Clemens Wan]

Overview​

Decentralized by DIN refers to Infura and MetaMask’s use of the Decentralized Infrastructure Network (DIN) to ensure greater reliability and redundancy for blockchain requests. DIN connects Web3 Gateway infrastructure with multiple third-party node providers, so if one provider fails or is congested, requests can seamlessly fail over to another. DIN also provides Web3 gateways connections with access to new networks without the heavy devops/engineering capacity overhead.

How it works​

  1. Multiple providers: DIN is a collaboration of 50+ independent service providers that specialize in hardware bare metal nodes all across the world.
  2. Failover: If your dapp or wallet makes an RPC call that fails on one provider, DIN automatically reroutes the request to another provider in the network.
  3. Infrastructure redundancy: DIN minimizes downtime and ensures your application or wallet remains operational, even if one infrastructure provider encounters issues.
  4. New networks: DIN works directly with foundations and protocols to increase the developer distribution of new blockchain networks across existing web3 gateway customers.

Benefits for Infura & MetaMask users​

  • Improved reliability: With requests spread across multiple providers, downtime is minimized.
  • Decentralized approach: No single point of failure, which aligns with core web3 principles.
  • Invisible to end users: End users typically won’t notice anything different - connections just work more often.

DIN’s roadmap and accomplishments​

DIN 2024 at a glance

In 2024, the Decentralized Infrastructure Network (DIN) evolved from a proof-of-concept into a production-ready ecosystem, powering failover and multi-provider capabilities across the Infura and MetaMask stacks. By onboarding new infrastructure partners, enhancing the underlying marketplace for node operators, and improving the developer experience through streamlined setup and dashboards, DIN laid the groundwork for next-generation, highly resilient dapp architectures and economic models we’ll be further expanding in 2025.

For more details, please review our successes: https://metamask.io/news/developers/din-2024-accomplishments/

FAQs​

  1. How do I enable DIN for my application?
    • DIN is automatically enabled from the backend and no configuration work is needed.
  2. Do end users need to do anything in MetaMask?
    • Nope. MetaMask automatically routes your requests through DIN when Infura is selected.
  3. What if I have a problem with the RPC endpoint?
    • Please direct all questions through the normal Infura and MetaMask Dev support channels.
  4. What if there are network issues and I’m a DIN Provider, Watcher, or Web3 Gateway using DIN services?
    • Please reach out to [email protected] through our existing slack and telegram channels to resolve any technical issues.
  5. Where can I learn more about DIN’s architecture?

Additional resources​

Last updated on by MetaMask Support Team