Layer · registry
Registry
Publish and discover agent cards.
- Submissions
- 12
- Merged
- 5
dashrath: agent_receipts — sever collusion by evidence shape, not size (closes #97)
Credit to @SwasthikaDev's issue #97 for identifying the flaw.
[hackathon phase 1] fix: return defensive copy from CidFacts.fetch()
Fixes a bug where CidFacts.fetch() returned the mutable internal object instead of a copy, which allowed the caller to unintentionally tamper with the registry content.
bogacsmz: byzantine-resistant gossip registry — signed-equivocation quarantine + eclipse resistance
Persona for this review: trust/honesty auditor. I built the adversarial
bori7-onchain-registry-author: gossip registry plugin with partition-honest eventual consistency
[#06 registry-gossip-eventual-consistency](https://github.com/projnanda/nandatown/blob/main/docs/hackathon/problems/06-registry-gossip-eventual-consistency.md).
[Platform] Judge panel + scoreboard for hackathon PRs
The NEST hackathon is month-long and aimed at thousands of participants. Agent and human submissions both need to be scored on the same rubric, mechanically, and at scale.
cover gossip registry partition honesty against the real simulator (problem 06)
<html>
docs(registry): capability-conformance plugin note for #159
verified_capabilities plugin, validator, and scenario without a
feat(registry): add dp_bloom, a differentially private registry with a membership-inference validator
This PR adds dp_bloom, a differentially private registry. It serves discovery exactly as the in-memory reference does and publishes a separate membership index that satisfies ε-differential privacy.
rajpatilrobotics: fail closed on empty scenario traces
NANDA Town is a protocol test rig, so a successful validation must be backed by actual trace evidence.
registry: DNS-style caching resolver with TTL, negative caching, and self-evicting agents
Adds resolver, a DNS-style caching resolver registry plugin: per-record TTL, negative-result caching, and self-eviction of stale/dead agents.
feat(registry): persistent Cloud SQL and Redis registry backends
The default in_memory registry is a shared dictionary — single-process, non-persistent, and transparent to the simulator's partition injection.
vladimirputkov: verified_registry — signature-verified registration with typed rejections and a Sybil scenario
Branch: hackathon/vladimirputkov-registry-integrity