Live sync KV stores over Iroh
This commit is contained in:
parent
68153be5d5
commit
f85039367c
9 changed files with 473 additions and 13 deletions
|
|
@ -141,8 +141,14 @@ are future work.
|
|||
through `kv create/set/get`. `kv set --subject <principal>` evaluates local auth
|
||||
ops for `kv.write_key:<key>` so prefix grants can be tested before networked
|
||||
callers exist. The local node/agent retains owner access for administration.
|
||||
Iroh Documents namespaces, remote caller identity, and replication are future
|
||||
work.
|
||||
Iroh Documents namespaces remain the target backend, but the bootstrap can sync
|
||||
named KV stores over the protected Iroh control ALPN. `geth kv sync <node-id>
|
||||
<name>` requires `kv.read` on the remote `resource:kv:<name>`, transfers entries
|
||||
at or beyond a per-peer/per-KV high-water cursor, and imports only values that
|
||||
are at least as new as the local entry timestamp. The daemon background
|
||||
live-sync loop runs the same KV sync for local KV stores and known peers.
|
||||
Private value encryption should use resource secret epochs before payloads are
|
||||
exposed to remote peers.
|
||||
|
||||
`geth-document` currently registers local document resources and stores
|
||||
validated JSON state in the local SQLite metadata store through
|
||||
|
|
|
|||
Loading…
Reference in a new issue