chore: key Bitcoin testnet4 DNS seeds

[daixiheguu]

Description

Use keyed chaincfg.DNSSeed literals for the Bitcoin testnet4 seeds. This removes the unkeyed-field vet warning and makes it clear that each value sets Host and HasFiltering.

There is no behavior change.

How Has This Been Tested?

• Tested CCTX in localnet
• Tested in development environment
• Go unit tests
• Go integration tests
• Tested via GitHub Actions

---

Note

Low Risk
Cosmetic struct literal change in testnet4 chain params; no logic, security, or data-path impact.

Overview
Updates TestNet4Params.DNSSeeds in bitcoin_testnet4.go to use explicit Host and HasFiltering fields on each chaincfg.DNSSeed entry instead of positional struct literals.

This is a readability and static-analysis fix only—the same two seeds and filtering flag as before, with no runtime or networking behavior change.

^{Reviewed by Cursor Bugbot for commit 0194e6c. Configure here.}

Greptile Summary

The PR replaces positional Bitcoin testnet4 DNS seed literals with equivalent keyed Host and HasFiltering fields, improving clarity and eliminating the unkeyed-field vet warning without changing configured values.

• Preserves both existing testnet4 DNS seed hosts.
• Preserves DNS filtering as enabled for each seed.

Confidence Score: 5/5

The PR appears safe to merge because it preserves the existing DNS seed values and behavior.

The only changes replace positional struct initialization with explicit field names while retaining identical host strings and filtering values, and no actionable defect was identified.

Important Files Changed

Filename	Overview
pkg/chains/bitcoin_testnet4.go	Converts two chaincfg.DNSSeed values to keyed literals while preserving their hosts and filtering settings.

_{Reviews (1): Last reviewed commit: "chore: key Bitcoin testnet4 DNS seeds" | Re-trigger Greptile}

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.