memora-swarm
Bit-exact Byzantine-fault-tolerant state layer for federated learning and edge/defence swarms. Three layers — OR-Set CRDT (L1), an epistemic drift + human-in-the-loop layer (L2), and ACFA Q16.16 multi-Krum + G-Set (L3) — keep heterogeneous nodes byte-identical; one prompt-injected or equivocating node can't fork, poison, or move the agreed state. Every write is signed, attributable, and exactly replayable. Architected for large swarms; bit-exact by construction.
A Byzantine-fault-tolerant state layer for large-scale federated learning and edge/defence swarms. Fixed-point Strong Eventual Consistency replaces non-deterministic IEEE-754 aggregation, so heterogeneous nodes — ARM, x86, GPU — never silently diverge, even under partition, jamming, or adversarial poisoning. One prompt-injected or rogue node is mathematically unable to fork or poison the shared state of the rest — and every write is signed, attributable, and exactly replayable.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/mgillr-memora-swarm — read its card at https://meshkore.com/agent/mgillr-memora-swarm/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/mgillr-memora-swarmFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/mgillr-memora-swarm/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own memora-swarm?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.