- Fix "order of preference" phrasing for peer discovery mechanisms
- Replace "zcashd reference implementation" with "zcashd implementation"
  throughout and document Zebra's corresponding values
- Remove integer type table (belongs in protocol spec)
- Add note that CompactSize is not formally defined in protocol spec
- Add RFC 4291 reference for IPv4-mapped IPv6 addresses
- Spell out "little-endian" instead of abbreviating "LE"
- Add Protocol Version Negotiation section to clarify ambiguous
  "the protocol version" usage
- Spell out bit numbering convention for service flags
- Add reference to zcashd PR #7039 for alert removal
- Note ZIP 155 for addrv2 deployment version assignment status

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Replace undefined ``bool`` with ``uint8``; 0 for false, 1 for true
  in the version message relay field
- Change "Unix epoch time" / "Unix timestamp" to "Unix-epoch UTC time
  in seconds" for all timestamp fields

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Revise DNS seeding to describe both zcashd and Zebra behavior
- Remove zcashd-specific SeedSpec6 reference from hardcoded seeds
- Clarify command string validation: "ignored" not "rejected"; enumerate
  all currently used command strings
- Use $k$ inline math syntax instead of :math: for service flags
- Rewrap pong timeout line with "a corresponding pong"
- Fix getblocks/getheaders descriptions: "up to and including hash_stop"
  and explicit MUST NOT limits
- Soften misbehavior penalties from MUST to SHOULD (overspecification)
- Note that zcashd does not use headers-first sync (refs zcashd#6292)
- Make MSG_TX MUST for v4 transactions (bidirectional requirement)
- "To impede" instead of "To prevent" for trickling rationale
- "halved rounding down" instead of "halved via integer right-shift"
- "its view of the current chain tip" for transaction expiry
- Remove orphan expiration check interval (overspecification)
- Simplify shielded eligibility to "fully transparent transactions"
- Document relay fee complexity with zcashd source reference
- Use "zcashd-specific rate-limiting" and "token-bucket algorithm"
- Reorder references per ZIP convention (BCP14, RFCs, protocol spec,
  ZIPs, BIPs, external)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

- Capitalize "Bloom" filter throughout (named after Burton Howard Bloom)
- Capitalize "Testnet" and "Mainnet" in protocol version note
- Add version validation disconnect summary to Protocol Version
  Negotiation section
- relay field: no text change needed (informational links noted)
- MSG_TX MUST for v4: already addressed in prior commit
- MIN_TESTNET_PEER_PROTO_VERSION: confirmed 170040 matches zcashd

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Zebra strictly validates that the relay field is 0 or 1; zcashd
accepts any non-zero value as true via implicit C++ bool conversion.
Use SHOULD to recommend validation without making zcashd non-conformant.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>