libertaria
/
libertaria-stack
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
libertaria-stack/core/l0-transport/opq
History
Markus Maiwald 6f26b67d19
docs: add RFC-0140 Libertaria SSI Stack specification 
Complete Self-Sovereign Identity stack specification:

- Four Pillars: Communication, Contracts/Law, Economy, Decentralized Production
- L0-L4 Architecture: SoulKey + QVL / VC Layer / State Channels / Chapter Federation
- did:libertaria method spec with versioning (?versionId= fallback)
- Comparison table: Libertaria vs blockchain SSI systems
- Security & Privacy considerations
- Implementation status and roadmap

Key differentiators documented:
- No blockchain required
- Offline-first operation
- Exit as architectural primitive
- Kenya Rule compliant

Refs: IOP Morpheus lineage, W3C DID/VC compatibility
 		2026-02-06 13:06:45 +01:00
..
README.md refactor: restructure repository with tiered licensing 2026-02-05 20:12:32 +01:00
manager.zig docs: add RFC-0140 Libertaria SSI Stack specification 2026-02-06 13:06:45 +01:00
manifest.zig refactor: complete repository restructure with tiered licensing 2026-02-05 21:50:54 +01:00
merkle.zig refactor: restructure repository with tiered licensing 2026-02-05 20:12:32 +01:00
quota.zig refactor: restructure repository with tiered licensing 2026-02-05 20:12:32 +01:00
reorder_buffer.zig refactor: complete repository restructure with tiered licensing 2026-02-05 21:50:54 +01:00
sequencer.zig refactor: complete repository restructure with tiered licensing 2026-02-05 21:50:54 +01:00
store.zig docs: add RFC-0140 Libertaria SSI Stack specification 2026-02-06 13:06:45 +01:00
trust_resolver.zig refactor: complete repository restructure with tiered licensing 2026-02-05 21:50:54 +01:00

README.md

OPQ: Offline Packet Queue

Layer: L0 (Transport) RFC: RFC-0005

Purpose

OPQ allows Libertaria to function in disconnected environments by providing:

  • Persistent disk-backed storage for frames.
  • TTL-based pruning.
  • Quota-enforced storage limits (Policy vs Mechanism).
  • Queue manifest generation for peer synchronization.

Node Personas & Policy

The OPQ's behavior is dictated by the node's role:

  • Client: Outbox only. (Retention: <1hr, Buffer: <5MB).
  • Relay: Store-and-Forward. (Retention: 72-96hr, Buffer: Quota-driven).

Components

  • store.zig: Segmented WAL (Write-Ahead Log) for atomic persistence.
  • quota.zig: Hard-quota enforcement and eviction logic.
  • manager.zig: (Pending) Queue orchestration and manifest sync.