Bootstrap Operations
resource: bootstrap — 3 operations managing the daemon's bootstrap peer list
What bootstrap peers are: the well-known peers a Kubo daemon dials on startup to join
the wider IPFS network before it has discovered anyone else. This list is persistent daemon config, not
a live connection state — compare with Swarm Operations, which
reports actual current connections.
add
| Field | Type | Required | Description |
|---|---|---|---|
peerAddress | text | ✓ Yes | Peer multiaddr to add to the persistent bootstrap list. |
Missing → CFG_MISSING_PEER_ADDRESS.
list
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
expandAuto | bool | No | false | Resolve "auto"-flavored bootstrap entries to their concrete addresses before returning. |
List-shaped response: array of { peer } entries plus count.
remove
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
peerAddress | text | Conditional | — | Peer multiaddr to remove — required unless all=true. |
all | bool | No | false | Remove every configured bootstrap peer. Destructive. |
confirmDestructive | bool | Conditional | false | Must be true before an all=true removal is executed. |
Safety guard on
all=true: if all is true and
confirmDestructive is not also true, the call fails before any network
request with CFG_CONFIRM_DESTRUCTIVE_REQUIRED ("Removing all bootstrap peers requires
confirmDestructive=true."). Removing a single named peer (all=false, a specific
peerAddress) needs no confirmation — only clearing the entire list is treated as
destructive. A missing peerAddress without all=true fails with
CFG_MISSING_PEER_ADDRESS.