Wire KV sync through iroh-docs
This commit is contained in:
parent
72f28224ce
commit
59c463eb40
9 changed files with 406 additions and 47 deletions
|
|
@ -486,7 +486,7 @@ authorization and durable-state boundaries clear.
|
|||
rejection.
|
||||
- `[x]` Docs explicitly avoid claiming forward secrecy or PCS.
|
||||
|
||||
- `[~]` Iroh-docs KV integration.
|
||||
- `[x]` Iroh-docs KV integration.
|
||||
Acceptance criteria:
|
||||
- `[x]` `geth kv create/set/get` works against a named local KV resource.
|
||||
- `[x]` KV metadata and entries are durable in the local SQLite store.
|
||||
|
|
@ -500,7 +500,10 @@ authorization and durable-state boundaries clear.
|
|||
- `[x]` Remote KV sync requires `kv.read` on `resource:kv:<name>`.
|
||||
- `[x]` Background live-sync refreshes local KV stores from known peers using
|
||||
per-peer/per-KV high-water cursors.
|
||||
- `[ ]` KV metadata is replicated through Iroh Documents.
|
||||
- `[x]` KV metadata is replicated through Iroh Documents.
|
||||
- `[x]` Authorized peers receive read-only Iroh Documents tickets, not write
|
||||
capabilities, after geth control authorization succeeds.
|
||||
- `[x]` Tests cover imported KV docs state after authorized remote sync.
|
||||
|
||||
- `[~]` Iroh-gossip pubsub integration.
|
||||
Acceptance criteria:
|
||||
|
|
|
|||
Loading…
Reference in a new issue