network/kad: Increase memory store capacity for providers

[dmitry-markin]

Increase Kademlia memory store capacity for DHT content providers (used by parachain DHT-based bootnodes) and reduce provider republish interval & TTL. This is needed to support testnets with 1-minute fast runtime and up to 13 parachains.

Parameters set:

• 10000 provider keys per node
• 10h provider record TTL
• 3.5h provider republish interval

Closes paritytech/litep2p#405.

[dmitry-markin]

/cmd prdoc --audience node_dev --bump patch

[lexnv]

Nice 🙏

[bkchr]

Generally I don't like that we add these things here as random constants. IMO it would be better if this could be communicated better to the discovery subsystem.

[dmitry-markin]

Generally I don't like that we add these things here as random constants. IMO it would be better if this could be communicated better to the discovery subsystem.

I am going to move the constants to network/src/config.rs. From there we can either import them or pass to discovery initialization as parameters. EDIT: done.

Or do you mean it should be communicated at runtime from the runtime? This would be an ideal solution, but neither litep2p nor libp2p doesn't support updating these parameters at runtime.

[paritytech-workflow-stopper]

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/16522931493
Failed job name: fmt

[dmitry-markin]

/cmd fmt

[bkchr]

Or do you mean it should be communicated at runtime from the runtime? This would be an ideal solution, but neither litep2p nor libp2p doesn't support updating these parameters at runtime.

They could be exposed to the configuration to change them.

[dmitry-markin]

Or do you mean it should be communicated at runtime from the runtime? This would be an ideal solution, but neither litep2p nor libp2p doesn't support updating these parameters at runtime.

They could be exposed to the configuration to change them.

Do you think we need to expose this as CLI options, or just for custom node impls to put their own values?