Report native backend blockers
This commit is contained in:
parent
ee80ff780c
commit
d9150024dd
7 changed files with 103 additions and 13 deletions
|
|
@ -30,6 +30,17 @@ uses Iroh's default relay policy; local-only/offline development can set
|
|||
`relay_map = "<name>"`, validated at config load, and reported in status as
|
||||
`custom:<name>` without exposing relay URLs.
|
||||
|
||||
The native module-backend crates currently available for the intended CAS, KV,
|
||||
and pubsub replacements are not wired in yet because they require a coordinated
|
||||
endpoint upgrade. Crates.io metadata checked during this prototype pass resolved
|
||||
`iroh-blobs 0.97.0`, `iroh-docs 0.95.0`, and `iroh-gossip 0.95.0` as
|
||||
Rust-1.85-compatible candidates; those crates depend on `iroh 0.95` and cannot
|
||||
share the daemon-owned `iroh 0.90.0` endpoint. Pulling them in beside the
|
||||
current endpoint would create parallel Iroh stacks and violate the one-endpoint
|
||||
daemon invariant. Until the endpoint wrapper upgrades as a unit, `geth status`
|
||||
reports CAS, KV, and pubsub native backends as blocked and the bootstrap
|
||||
control-ALPN paths remain explicit.
|
||||
|
||||
Module ALPNs are registered through `geth-iroh`'s protocol router scaffold. The
|
||||
router owns the default protocol descriptors, rejects duplicate ALPN
|
||||
registrations, and returns explicit unknown-ALPN errors. It does not yet accept
|
||||
|
|
|
|||
Loading…
Reference in a new issue