Skip to content

fix(kad): prove buddy callback parity - #213

Merged
itlezy merged 7 commits into
mainfrom
feature/lowid-buddy-callback-evidence
Nov 2, 2026
Merged

itlezy merged 7 commits into
mainfrom
feature/lowid-buddy-callback-evidence

Conversation

@itlezy

@itlezy itlezy commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a diagnostics-only buddy-relay eligibility control and causally joined FINDBUDDY, held-socket, callback-request, relay-decision, and relay-packet evidence
  • canonicalize Kad buddy hashes and diagnostic identities at the wire/display boundaries
  • separate server and Kad reachability authorities, retain stock contact liveness, and match stock peer-HELLO identity precedence

Evidence

  • deterministic Rust/MFC buddy-callback campaign passed with byte-identical callback requests and OP_CALLBACK relays
  • immutable receipt: rust-mfc-transfer-20261102t084332z
  • artifact SHA-256: 38d4e6fa88ed0de399ec7e9866552edf485bd760359fc7e2517d9b5681294e66
  • Rust callback request, relay decision, and relay packet: sequences 26/27/29

Validation

  • python tools/rust_quality_gate.py ci
  • full workspace tests and strict Clippy passed
  • canonical diagnostics and WebUI gates passed
  • three observed-egress VPN leak tests passed

Coordinated with the MFC diagnostics, build-tests, and tooling PRs for RUST-CI-031.

Threepwood-7 added 7 commits November 2, 2026 08:28
Track stock CemuleApp::GetID precedence across Kad contact, Kad firewall state, and server assignment so held buddy sockets receive the same HELLO identity as the MFC oracle. Reuse the resolver for listener and Kad firewall-check HELLO paths.\n\nRUST-CI-031
Carry Kad buddy IDs as NodeId values through diagnostic emitters and serialize stock CUInt128 display order. Add asymmetric vectors so raw wire-order regressions are detected.\n\nRUST-CI-031
@itlezy
itlezy merged commit 45c3cc9 into main Nov 2, 2026
15 checks passed
@itlezy
itlezy deleted the feature/lowid-buddy-callback-evidence branch November 2, 2026 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant