Split from #76 / PR feat/108-no-fallback-rpc.
--no-fallback-rpc makes the runtime provably Glif-free (head=gossipsub, cold blocks=gateway+bitswap). But the one-time boot anchor (#54, fetchVerifiedTrustedHead) still gathers from gateway + Glif and requires ≥2 agreeing independent sources.
So a --no-fallback-rpc node is Glif-free at runtime but still contacts Glif once at boot for the multi-source trusted-root agreement. For a maximally honest 'zero-Glif' claim (and the answer to reviewers poking at Lantern's dependency surface), the boot anchor should be able to satisfy its ≥2-source agreement without Glif when --no-fallback-rpc is set.
Options
- Use the
init --bootstrap-quorum peer set (Lantern beacons) as anchor agreement sources.
- Allow an operator's own Forest RPC as the 2nd anchor source (
--vm-bridge-rpc reuse).
- A 2nd independent gateway.
Acceptance
- With
--no-fallback-rpc, boot anchor reaches ≥2-source F3-checked agreement with zero Glif contact; --insecure-anchor still the single-source escape hatch.
Not a v1.9.0 blocker; the runtime bridge-off claim stands today via the fetch counters (#104 Phase 2).
Split from #76 / PR feat/108-no-fallback-rpc.
--no-fallback-rpcmakes the runtime provably Glif-free (head=gossipsub, cold blocks=gateway+bitswap). But the one-time boot anchor (#54,fetchVerifiedTrustedHead) still gathers from gateway + Glif and requires ≥2 agreeing independent sources.So a
--no-fallback-rpcnode is Glif-free at runtime but still contacts Glif once at boot for the multi-source trusted-root agreement. For a maximally honest 'zero-Glif' claim (and the answer to reviewers poking at Lantern's dependency surface), the boot anchor should be able to satisfy its ≥2-source agreement without Glif when--no-fallback-rpcis set.Options
init --bootstrap-quorumpeer set (Lantern beacons) as anchor agreement sources.--vm-bridge-rpcreuse).Acceptance
--no-fallback-rpc, boot anchor reaches ≥2-source F3-checked agreement with zero Glif contact;--insecure-anchorstill the single-source escape hatch.Not a v1.9.0 blocker; the runtime bridge-off claim stands today via the fetch counters (#104 Phase 2).