3.2 KiB
Kubo changelog v0.21
v0.21.0
Overview
🔦 Highlights
Saving previously seen nodes for later bootstrapping
Kubo now stores a subset of connected peers as backup bootstrap nodes (kubo#8856).
These nodes are used in addition to the explicitly defined bootstrappers in the
Bootstrap configuration.
This enhancement improves the resiliency of the system, as it eliminates the necessity of relying solely on the default bootstrappers operated by Protocol Labs for joining the public IPFS swarm. Previously, this level of robustness was only available in LAN contexts with mDNS peer discovery enabled.
With this update, the same level of robustness is applied to peers that lack mDNS peers and solely rely on the public DHT.
Gateway.DeserializedResponses config flag
This release introduces the
Gateway.DeserializedResponses
configuration flag.
With this flag, one can explicitly configure whether the gateway responds to deserialized requests or not. By default, this flag is enabled.
Disabling deserialized responses allows the gateway to operate as a Trustless Gateway limited to three verifiable response types: application/vnd.ipld.raw, application/vnd.ipld.car, and application/vnd.ipfs.ipns-record.
With deserialized responses disabled, the Kubo gateway can serve as a block backend for other software (like bifrost-gateway, IPFS in Chromium etc) without the usual risks associated with hosting deserialized data behind third-party CIDs.
client/rpc migration of go-ipfs-http-client
The go-ipfs-http-client RPC has
been migrated into client/rpc.
With this change the two will be kept in sync, in some previous releases we updated the CoreAPI with new Kubo features but forgot to port thoses to the http-client, making it impossible to use them together with the same coreapi version.
TODO(@Jorropo): add link to boxo-migrate once support for rewriting this import path has been added