# Reliable and scalable public RPC - powered by Lava

**URL:** <https://forum.namada.net/t/reliable-and-scalable-public-rpc-powered-by-lava/588>\
**Category:** Ecosystem & Strategy\
**Created:** [10 April 2024 12:10 UTC](https://forum.namada.net/t/reliable-and-scalable-public-rpc-powered-by-lava/588 "2024-04-10T12:10:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RuslanGlaznyov](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/ruslanglaznyov/32/280_2.png) [@RuslanGlaznyov](https://forum.namada.net/u/RuslanGlaznyov)\
**Post date:** [10 April 2024 12:10 UTC](https://forum.namada.net/t/reliable-and-scalable-public-rpc-powered-by-lava/588/1 "2024-04-10T12:10:01Z")

</div>

I think we need trustless and decentralized RPCs for NAMADA from the Lava network.

[Lava](https://lavanet.xyz) is a modular network which rollups use to bootstrap a performant network of infrastructure providers. RPC requests are routed to the best available provider, giving developers and users optimal service.

I think this is an important step to increase security and developer experience. Also, relying on experience from the shielded expedition with the RPC task we faced with several problems:

1. Where to store all existing RPC created by the community?
2. How to check that RPC running and up to date
3. How to know that a specific RPC is valuable and used by other community members?

All these issues can be fixed by Lava protocol. We don’t need to collect all RPCs and check their performance/usage/liveness all we need is to check that specific provider relay requests for Namada

I have prepared a proposal and written a spec to add Namada to the Lava Network. You can check it on the Lava forum

> **[Add spec: Namada](https://community.lavanet.xyz/t/add-spec-namada/119)**
>
> I have prepared specifications for the NAMADA Shielded Expedition testnet. As a community builder in Namada and a Lava developer champion in Lava, I can take responsibility for maintaining this specification in the future. For the testnet now and...

---

<div class="post-metadata">

**Author:** ![Baseddesigner](https://uxwing.com/wp-content/themes/uxwing/download/signs-and-symbols/caution-icon.png) [@Baseddesigner](https://forum.namada.net/u/Baseddesigner)\
**Post date:** [12 April 2024 01:24 UTC](https://forum.namada.net/t/reliable-and-scalable-public-rpc-powered-by-lava/588/2 "2024-04-12T01:24:52Z")

</div>

I think this is worth checking out by the Namada team

---

<div class="post-metadata">

**Author:** ![ekkis](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.namada.net/ekkis/32/237_2.png) [@ekkis](https://forum.namada.net/u/ekkis)\
**Post date:** [18 April 2024 06:12 UTC](https://forum.namada.net/t/reliable-and-scalable-public-rpc-powered-by-lava/588/3 "2024-04-18T06:12:18Z")

</div>

for us building apps on the Namada network this is of critical importance. I don’t want to run my own set of nodes just to make sure they are uncompromised and up-to-date. being able to rely on nodes my app can connect to as a public service would be invaluable