25 lines
1.6 KiB
Markdown
25 lines
1.6 KiB
Markdown
# DeltaMesh MVP and Architecture
|
||
|
||
Overview
|
||
- DeltaMesh is a federated, privacy-preserving cross-venue options market-making engine.
|
||
- This repo contains an initial, production-oriented skeleton to bootstrap an MVP focused on the federation and privacy aspects, with a minimal, compilable C prototype for local markets, shared signals, and delta planning.
|
||
|
||
What you will find here
|
||
- Canonical primitives (LocalMarket, SharedSignals, PlanDelta) with tiny, well-scoped C implementations.
|
||
- A lightweight ADMM-like coordinator implemented as delta synchronization at the toy level (admm_lite).
|
||
- An adapter-stub that demonstrates how a data feed and a venue adapter could be wired in; for now it’s a toy example in demo_main.c.
|
||
- A small, self-contained test harness (test.sh) to compile and run the demo in a deterministic, repeatable way.
|
||
|
||
How to contribute
|
||
- Start with the delta_mesh/ directory; add adapters under delta_mesh/Adapters if needed.
|
||
- Keep interfaces minimal and stable; add new primitives only when they are durable enough for reuse across venues.
|
||
- Ensure tests compile and pass locally before proposing broader changes.
|
||
|
||
Development process
|
||
- Use the MVP plan: Phase 0 skeleton, Phase 1 governance and secure aggregation, Phase 2 cross-venue pilot, Phase 3 SDKs and conformance tests.
|
||
- For new features, add a small integration test that demonstrates the feature in a deterministic, isolated way.
|
||
|
||
Guidance for reviewers
|
||
- Prioritize safety, privacy, and auditor-ability aspects; ensure deterministic behavior on reconnects and partition handling.
|
||
- Avoid exposing real inventories or live quotes in tests; use toy values.
|