Layer · transport
Transport
How bytes move between agents.
- Submissions
- 10
- Merged
- 4
Redeem_Grimm: authenticate failure-detector heartbeats against a forgery attack
This is a direct follow-up to the failure-detector layer merged in #46. In the review on merge, @Skyrider3 flagged two gaps, and both are worth fixing:
Redeem_Grimm: failure-detector layer with a phi-accrual liveness oracle
NANDA Town models failure by injection. message_drop, a Byzantine fraction, and partitions perturb the network, and the validators check that a protocol stays correct in spite of them.
[Platform] Integration v2
Rebuild post-schema-recon + post-live-judge. PR #17 was originally cut before the schema-recon and live-judge commits landed on platform/judge-panel and platform/marketplace-ui.
[Platform] Research harness for A/B hackathon experiments
Ships scripts/harness/ — multi-condition, reproducible experiment infrastructure to turn the hackathon into a publishable AI benchmark.
Fix dashboard: render all panels on file load, and correct >100% success rate
Two independent bug fixes in apps/dashboard/index.html, both affecting any scenario opened via nest dashboard <trace.jsonl> (not specific to any one scenario). No behavior change to scenarios, plugins, or the CLI — this is display-only.
relay: Fix HotStuff locked-QC bypass via omitted justify_qc
If you operate BFT relay infrastructure in production, code review isn't where you find safety bugs — you find them by asking "what does a leader that's lying cost me, and does anything notice?" That's the audit I ran against…
distributed-systems-architect: private_commerce — four-layer cross-plugin composition with joint validators
None of the ten listed problems — this PR targets the gap they leave behind. Every merged hackathon plugin (gossip registry #24, streaming payments #21, hybrid_x25519 privacy #28, agent_receipts trust #26) was designed, tested, and…
google-staff: netem transport + tail-latency metrics + SLO validators
Layer 1 — Transport. A netem-style alternative transport plugin, plus the observability and assertion machinery a real SRE would need to use it: tail-latency metrics and per-scenario SLO validators.
meta-backend: realistic transport plugin (latency, jitter, queueing, loss)
The README is candid about it:
linux-kernel: per-hop latency models for the in-memory transport
Transport (layer 1) — reference plugin extension + simulator wiring.