src/libp2p/config.rs (2)

41-44: QUIC v1 default listen address looks good; consider updating the field doc

The added "/ip4/0.0.0.0/udp/0/quic-v1" entry cleanly achieves “listen on QUIC by default” while preserving the existing TCP default. One minor follow‑up: the listening_multiaddrs doc comment above still says “TCP and WebSocket with DNS are supported”, which is now slightly misleading—might be worth mentioning QUIC there to keep code docs in sync with behavior.

---

53-60: Strengthen config_default test to assert the actual defaults

Right now the test only checks that Libp2pConfig::default() doesn’t panic. It would be more useful to assert that the default actually exposes both TCP and QUIC listen addrs (and possibly other key defaults), so future changes don’t silently regress the behavior this PR is introducing.

For example:

 #[test]
 fn config_default() {
-    let _ = Libp2pConfig::default();
+    let cfg = Libp2pConfig::default();
+
+    assert_eq!(
+        cfg.listening_multiaddrs,
+        vec![
+            "/ip4/0.0.0.0/tcp/0".parse().expect("Infallible"),
+            "/ip4/0.0.0.0/udp/0/quic-v1".parse().expect("Infallible"),
+        ]
+    );
 }

This keeps the test small but makes it actually guard the new default. Based on learnings, this matches your preference for fail‑fast, explicit defaults.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Learnt from: hanabi1224
Repo: ChainSafe/forest PR: 5930
File: build.rs:64-77
Timestamp: 2025-08-13T09:43:20.301Z
Learning: hanabi1224 prefers hard compile-time errors in build scripts rather than runtime safeguards or collision detection, believing it's better to fail fast and fix root causes of issues like malformed snapshot names.

Learnt from: hanabi1224
Repo: ChainSafe/forest PR: 6057
File: src/cli/subcommands/f3_cmd.rs:0-0
Timestamp: 2025-09-09T10:37:17.947Z
Learning: hanabi1224 prefers having default timeouts (like 10m for --no-progress-timeout) to prevent commands from hanging indefinitely, even when the timeout flag isn't explicitly provided by users. This fail-fast approach is preferred over requiring explicit flag usage.