With Neckwork now operating Hydration's own archive node and infrastructure stack, could you clarify which production services currently depend specifically on Dwellir's public RPC, and whether there is a longer term plan to consolidate or deliberately maintain multiple RPC providers for redundancy?

Thanks for providing the usage statistics. Before voting, I would like to better understand how this service fits into Hydration's evolving infrastructure stack.
With Neckwork now operating an archive node and a growing part of Hydration's data infrastructure, could you clarify which production services currently depend specifically on Dwellir's public RPC?
I understand that an indexer/data layer and a public RPC serve different purposes, so I am not suggesting they are necessarily duplicate services. However, as Hydration is now funding several infrastructure providers, I think it would be useful to understand where the boundaries and overlaps are.
Is Dwellir currently one of several RPC providers used for redundancy, or are Hydration's main applications specifically dependent on Dwellir? If multiple providers are being maintained deliberately, what level of redundancy does Hydration actually need?
I am also curious about the dedicated DIA endpoint. Hydration separately funds DIA's oracle services, so could you clarify why the dedicated RPC endpoint needs to be funded by the Treasury separately, and whether DIA could use the general Hydration RPC infrastructure instead?
I think having a clearer picture of the overall infrastructure stack and its recurring costs would make these quarterly renewals much easier to evaluate.

[@12nQ...tdqM](12nQXR1v3RbKrMcHD9TRyjXGNEfP5RNLHrD6ov8BGQs2tdqM-hydradx) 

The Neckwork RPC isn't meant to replace any important part of the current RPC infrastructure and should be seen complementary <ins>for now</ins>. The load bearing RPC infrastructure still comes from Dwellir & IGL.

The most promising change in RPC infrastructure regards scaling might be a switch back from Polkadot-API (PAPI) to PolkadotJs for the clients to support stateless calls & caching via Subway.

Hydrated Dollar

Dwellir is currently serving the Hydration community with a public RPC endpoint service. We are serving on average 64,600,000 requests per day.

This proposal is to cover the costs for July, August and September 2026. It also includes a dedicated Hydration RPC service for Dia. We are requesting $3,459 for this period.

Read the [full proposal here](https://docs.google.com/document/d/1VWs02GcN25Orp4A6YRgSt7-f2YgMf73ZzaUHnCN8YIw/edit?tab=t.0#heading=h.gjdgxs).

/Team Dwellir

call

Deciding

Submitted

DecisionDepositPlaced

DecisionStarted

treasurer

Dwellir - Public RPC Endpoint Service Q3 2026

root

whitelisted_caller

referendum_canceller

referendum_killer

general_admin

spender

tipper

omnipool_admin

economic_parameters

Origin able to dispatch a whitelisted call.

 Origin for spending very high amounts of HDX(<= 50M HDX) from the treasury as well as generally administering it.

Origin able to spend up to 2,222,222 HDX from the treasury at once.

Origin able to spend up to 50K HDX from the treasury at once.

Origin able to perform specific Omnipool-related actions.