Upgrade Iroh native backend foundation
This commit is contained in:
parent
b042149173
commit
9d46dd4d0d
11 changed files with 1588 additions and 712 deletions
13
README.md
13
README.md
|
|
@ -198,13 +198,12 @@ has `cas.fetch` on `resource:cas:local`, and the caller verifies that the bytes
|
|||
hash to the requested BLAKE3 CAS hash before storing them locally. Successful
|
||||
fetches record the serving peer as a local provider, visible with
|
||||
`geth cas providers <hash>`. This is the bootstrap transfer path; future work
|
||||
will move provider/fetch behavior to `iroh-blobs`. `geth status` currently
|
||||
reports the native backend blocker for CAS, KV, and pubsub: the daemon endpoint
|
||||
is pinned to `iroh 0.90.0`, while the Rust-1.85-compatible backend crates
|
||||
resolved from crates.io are `iroh-blobs 0.97.0`, `iroh-docs 0.95.0`, and
|
||||
`iroh-gossip 0.95.0`, all of which require `iroh 0.95`. These cannot be wired
|
||||
to the daemon-owned endpoint until the endpoint wrapper is upgraded in one
|
||||
coordinated step.
|
||||
will move provider/fetch behavior to `iroh-blobs`. `geth-iroh` is now pinned to
|
||||
`iroh 0.95.1` and compiles the native backend libraries `iroh-blobs 0.97.0`,
|
||||
`iroh-docs 0.95.0`, and `iroh-gossip 0.95.0` against the same daemon-owned
|
||||
endpoint generation. `geth status` reports those backends as ready to wire; the
|
||||
module implementations still use the explicit bootstrap control path until the
|
||||
module-specific migrations replace it.
|
||||
Remote resource commands that accept `--bearer-secret` can also authorize with a
|
||||
resource-scoped bearer proof generated from the private bearer token returned at
|
||||
creation time. The persisted auth log stores a public bearer id and token
|
||||
|
|
|
|||
Loading…
Reference in a new issue