Peer Seed Default
This commit is contained in:
@@ -28,7 +28,7 @@ The **booter** owns the **consumer** side: it looks up peers on the same topic,
|
||||
|
||||
You almost always run them as **two separate processes** (two terminal tabs or windows). The booter needs a live seeder (or an already-replicated drive) to make progress within its boot timeout.
|
||||
|
||||
**Resilience — peer system seeding:** After a node has booted, you can set **`BARE_OS_PEER_SYSTEM_SEED=1`** on the **host** so it also serves **MBR block 0** and mirrors the publisher’s early **`bare_os.*`** RPC hints to other cold booters (same Hyperswarm topic). This does not remove the need for at least one trusted publisher for the first tip, but it spreads block and RPC load across up-to-date peers. Optional **`BARE_OS_SEED_IMAGE_TIP_ID`** on the seeder and **`BARE_OS_PEER_SEED_IMAGE_TIP_ID`** on helpers pin the advertised image tip; see the [environment appendix](../docs/reference/environment-and-posix-appendix.md).
|
||||
**Resilience — peer system seeding:** By default, after a node has booted it **may** serve **MBR block 0** and mirror the publisher’s early **`bare_os.*`** RPC hints to other cold booters (same Hyperswarm topic) when eligibility passes. Set **`BARE_OS_PEER_SYSTEM_SEED=0`** (or **`false`** / **`no`** / **`off`**) on the **host** to turn this off. This does not remove the need for at least one trusted publisher for the first tip, but it spreads block and RPC load across up-to-date peers. Optional **`BARE_OS_SEED_IMAGE_TIP_ID`** on the seeder and **`BARE_OS_PEER_SEED_IMAGE_TIP_ID`** on helpers pin the advertised image tip; see the [environment appendix](../docs/reference/environment-and-posix-appendix.md).
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
|
||||
Reference in New Issue
Block a user