Skip to content

Releases: ipfs/kubo

v0.21.0-rc1

12 Jun 16:17
@hacdias hacdias
v0.21.0-rc1
This tag was signed with the committer’s verified signature.
hacdias Henrique Dias
SSH Key Fingerprint: WRIzu7ytwJKPlb20tQzDeIxZdzLjcU+sRlPlmlr9rkg
Verified
Learn about vigilant mode.
85c53ab
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.21.0-rc1 Pre-release
Pre-release

Changelog: docs/changelogs/v0.21.md

Loading

v0.20.0

09 May 11:11
@hacdias hacdias
v0.20.0
This tag was signed with the committer’s verified signature.
galargh Piotr Galar
GPG key ID: 2ACC6C98453FCE44
Verified
Learn about vigilant mode.
b8c4725
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.20.0

Overview

🔦 Highlights

Boxo under the covers

We have consolidated many IPFS repos into Boxo, and this release switches Kubo over to use Boxo instead of those repos, resulting in the removal of 27 dependencies from Kubo:

  • github.com/ipfs/go-bitswap
  • github.com/ipfs/go-ipfs-files
  • github.com/ipfs/tar-utils
  • gihtub.com/ipfs/go-block-format
  • github.com/ipfs/interface-go-ipfs-core
  • github.com/ipfs/go-unixfs
  • github.com/ipfs/go-pinning-service-http-client
  • github.com/ipfs/go-path
  • github.com/ipfs/go-namesys
  • github.com/ipfs/go-mfs
  • github.com/ipfs/go-ipfs-provider
  • github.com/ipfs/go-ipfs-pinner
  • github.com/ipfs/go-ipfs-keystore
  • github.com/ipfs/go-filestore
  • github.com/ipfs/go-ipns
  • github.com/ipfs/go-blockservice
  • github.com/ipfs/go-ipfs-chunker
  • github.com/ipfs/go-fetcher
  • github.com/ipfs/go-ipfs-blockstore
  • github.com/ipfs/go-ipfs-posinfo
  • github.com/ipfs/go-ipfs-util
  • github.com/ipfs/go-ipfs-ds-help
  • github.com/ipfs/go-verifcid
  • github.com/ipfs/go-ipfs-exchange-offline
  • github.com/ipfs/go-ipfs-routing
  • github.com/ipfs/go-ipfs-exchange-interface
  • github.com/ipfs/go-libipfs

Note: if you consume these in your own code, we recommend migrating to Boxo. To ease this process, there's a tool which will help migrate your code to Boxo.

You can learn more about the Boxo 0.8 release that Kubo now depends and the general effort to get Boxo to be a stable foundation here.

HTTP Gateway

Switch to boxo/gateway library

Gateway code was extracted and refactored into a standalone library that now
lives in boxo/gateway. This
enabled us to clean up some legacy code and remove dependency on Kubo
internals.

The GO API is still being refined, but now operates on higher level abstraction
defined by gateway.IPFSBackend interface. It is now possible to embed
gateway functionality without the rest of Kubo.

See the car
and proxy
examples, or more advanced
bifrost-gateway.

Improved testing

We are also in the progress of moving away from gateway testing being based on
Kubo sharness tests, and are working on
ipfs/gateway-conformance test
suite that is vendor agnostic and can be run against arbitrary HTTP endpoint to
test specific subset of HTTP Gateways specifications.

Trace Context support

We've introduced initial support for traceparent header from W3C's Trace
Context spec.

If traceparent header is
present in the gateway request, one can use its trace-id part to inspect
trace spans via selected exporter such as Jaeger UI
(docs,
demo).

To learn more, see tracing docs.

Removed legacy features
  • Some Kubo-specific prometheus metrics are no longer available.
  • The legacy opt-in Gateway.Writable is no longer available as of Kubo 0.20.
    • We are working on developing a modern replacement.
      To support our efforts, please leave a comment describing your use case in
      ipfs/specs#375.

--empty-repo is now the default

When creating a repository with ipfs init, --empty-repo=true is now the default. This means
that your repository will be empty by default instead of containing the introduction files.
You can read more about the rationale behind this decision on the tracking issue.

Reminder: ipfs pubsub commands and matching HTTP endpoints are deprecated and will be removed

ipfs pubsub commands and all /api/v0/pubsub/ RPC endpoints and will be removed in the next release. For more information and rational see #9717.

📝 Changelog

Full Changelog
Read more
Loading

v0.19.2

03 May 09:48
@hacdias hacdias
v0.19.2
This tag was signed with the committer’s verified signature.
hacdias Henrique Dias
SSH Key Fingerprint: WRIzu7ytwJKPlb20tQzDeIxZdzLjcU+sRlPlmlr9rkg
Verified
Learn about vigilant mode.
afb27ca
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.19.2

Highlights

FullRT DHT HTTP Routers

The default HTTP routers are now used when the FullRT DHT client is used. This fixes
the issue where cid.contact is not being queried by default when the accelerated
DHT client was enabled. Read more in (ipfs/kubo#9841).

Changelog

Full Changelog
  • github.com/ipfs/kubo:
    • fix: use default HTTP routers when FullRT DHT client is used (#9841) (ipfs/kubo#9841)
    • chore: update version

Contributors

Contributor Commits Lines ± Files Changed
Gus Eggert 1 +65/-53 4
Henrique Dias 1 +1/-1 1
Loading

v0.20.0-rc2

25 Apr 13:49
@hacdias hacdias
v0.20.0-rc2
This tag was signed with the committer’s verified signature.
galargh Piotr Galar
GPG key ID: 2ACC6C98453FCE44
Verified
Learn about vigilant mode.
8418b08
Compare
Choose a tag to compare
v0.20.0-rc2 Pre-release
Pre-release

Changelog: docs/changelogs/v0.20.md

Loading

v0.20.0-rc1

07 Apr 10:29
@galargh galargh
v0.20.0-rc1
This tag was signed with the committer’s verified signature.
galargh Piotr Galar
GPG key ID: 2ACC6C98453FCE44
Verified
Learn about vigilant mode.
ff409cc
Compare
Choose a tag to compare
v0.20.0-rc1 Pre-release
Pre-release

Changelog: docs/changelogs/v0.20.md

Loading

v0.19.1

05 Apr 20:00
@galargh galargh
v0.19.1
This tag was signed with the committer’s verified signature.
galargh Piotr Galar
GPG key ID: 2ACC6C98453FCE44
Verified
Learn about vigilant mode.
958e586
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.19.1

🔦 Highlights

DHT Timeouts

In v0.16.0, Kubo added the ability to configure custom content routers and DHTs with the custom router type, and as part of this added a default 5 minute timeout to all DHT operations. In some cases with large repos (example), this can cause provide and reprovide operations to fail because the timeout is reached. This release removes these timeouts on DHT operations. If users desire these timeouts, they can be added back using the custom router type.

Changelog

Full Changelog
  • github.com/ipfs/kubo:
    • chore: update version
    • fix: remove timeout on default DHT operations (#9783) (ipfs/kubo#9783)
    • chore: update version
  • github.com/ipfs/go-blockservice (v0.5.0 -> v0.5.1):
    • chore: release v0.5.1
    • fix: remove busyloop in getBlocks by removing batching
  • github.com/libp2p/go-libp2p (v0.26.3 -> v0.26.4):
  • github.com/libp2p/go-libp2p-routing-helpers (v0.6.1 -> v0.6.2):

Contributors

Contributor Commits Lines ± Files Changed
Marco Munizaga 1 +347/-46 5
Gus Eggert 3 +119/-93 8
Jorropo 2 +20/-32 2
galargh 2 +2/-2 2
Marten Seemann 1 +2/-2 1
Loading

v0.19.0

20 Mar 13:55
@galargh galargh
v0.19.0
This tag was signed with the committer’s verified signature.
galargh Piotr Galar
GPG key ID: 2ACC6C98453FCE44
Verified
Learn about vigilant mode.
1963219
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.19.0

Overview

🔦 Highlights

Improving the libp2p resource management integration

There are further followups up on libp2p resource manager improvements in Kubo 0.18.0
and 0.18.1:

  1. ipfs swarm limits and ipfs swarm stats have been replaced by ipfs swarm resources to provide a single/combined view for limits and their current usage in a more intuitive ordering.
  2. Removal of Swarm.ResourceMgr.Limits config. Instead the power user can specify limits in a .json file that are fed directly to go-libp2p. This allows the power user to take advantage of the new resource manager types introduced in go-libp2p 0.25 including "use default", "unlimited", "block all".
    • Note: we don't expect most users to need these capablities, but they are there if so.
  3. Doc updates.

Gateways

Signed IPNS Record response format

This release implements IPIP-351 and
adds Gateway support for returning signed (verifiable) ipns-record (0x0300)
when /ipns/{libp2p-key} is requested with either
Accept: application/vnd.ipfs.ipns-record HTTP header
or ?format=ipns-record URL query parameter.

The Gateway in Kubo already supported trustless, verifiable retrieval of immutable /ipfs/ namespace.
With ?format=ipns-record, light HTTP clients are now able to get the same level of verifiability for IPNS websites.

Tooling is limited at the moment, but we are working on go-libipfs examples that illustrate the verifiable HTTP client pattern.

Example: fetch IPNS record over HTTP and inspect it with ipfs name inspect --verify
$ FILE_CID=$(echo "Hello IPFS" | ipfs add --cid-version 1 -q)
$ IPNS_KEY=$(ipfs key gen test)
$ ipfs name publish /ipfs/$FILE_CID --key=test --ttl=30m
Published to k51q..dvf1: /ipfs/bafk..z244
$ curl "http://127.0.0.1:8080/ipns/$IPNS_KEY?format=ipns-record" > signed.ipns-record
$ ipfs name inspect --verify $IPNS_KEY < signed.ipns-record
Value:         "/ipfs/bafk..."
Validity Type: "EOL"
Validity:      2023-03-09T23:13:34.032977468Z
Sequence:      0
TTL:           1800000000000
PublicKey:     ""
Signature V1:  "m..."
Signature V2:  "m..."
Data:          {...}

Validation results:
 Valid:     true
 PublicKey: 12D3...

Addition of "autoclient" router type

A new routing type "autoclient" has been added. This mode is similar to "auto", in that it is a hybrid of content routers (including Kademlia and HTTP routers), but it does not run a DHT server. This is similar to the difference between "dhtclient" and "dht" router types.

See the Routing.Type documentation for more information.

Deprecation of the ipfs pubsub commands and matching HTTP endpoints

We are deprecating ipfs pubsub and all /api/v0/pubsub/ RPC endpoints and will remove them in the next release.

For more information and rational see #9717.

📝 Changelog

Full Changelog
  • github.com/ipfs/kubo:
    • chore: update version
    • docs: 0.19 changelog (ipfs/kubo#9707)
    • fix: canonicalize user defined headers
    • fix: apply API.HTTPHeaders to /webui redirect
    • feat: add heap allocs to 'ipfs diag profile'
    • fix: future proof with > rcmgr.DefaultLimit for new enum rcmgr values
    • test: add test for presarvation of unlimited configs for inbound systems
    • fix: preserve Unlimited StreamsInbound in connmgr reconciliation
    • test: fix flaky rcmgr test
    • chore: deprecate the pubsub api
    • test: port peering test from sharness to Go
    • test: use T.TempDir to create temporary test directory
    • fix: --verify forgets the verified key
    • test: name --verify forgets the verified key
    • feat: add "autoclient" routing type
    • test: parallelize more of rcmgr Go tests
    • test: port legacy DHT tests to Go
    • fix: t0116-gateway-cache.sh (ipfs/kubo#9696)
    • docs: add bifrost to early testers (ipfs/kubo#9699)
    • fix: typo in documentation for install path
    • chore: update version
    • feat: Reduce RM code footprint
    • Doc updates/additions
    • ci: replace junit html generation with gh action
    • test: port rcmgr sharness tests to Go
    • test(gateway): use deterministic CAR fixtures (ipfs/kubo#9657)
    • feat(gateway): error handling improvements (500, 502, 504) (#9660) (ipfs/kubo#9660)
    • docs: be clear about swarm.addrfilters (#9661) (ipfs/kubo#9661)
    • chore: update go-libp2p to v0.26 (#9656) (ipfs/kubo#9656)
    • feat(pinning): connect some missing go context (#9557) (ipfs/kubo#9557)
    • fix(gateway): return HTTP 500 on ErrResolveFailed (#9589) (ipfs/kubo#9589)
    • docs: bulk spelling edits (#9544) (ipfs/kubo#9544)
    • docs: "remote" errors from resource manager (#9653) (ipfs/kubo#9653)
    • test: remove gateway tests migrated to go-libipfs
    • fix: update rcmgr for go-libp2p v0.25
    • chore: update go-libp2p to v0.25.1
    • docs(0.18.1): guide users to clean up limits (#9644) (ipfs/kubo#9644)
    • feat: add NewOptionalInteger function
    • fix: dereference int64 pointer in OptionalInteger.String() (#9640) (ipfs/kubo#9640)
    • fix: restore wire format for /api/v0/routing/get|put (#9639) (ipfs/kubo#9639)
    • refactor(gw): move Host (DNSLink and subdomain) handling to go-libipfs (#9624) (ipfs/kubo#9624)
    • refactor: new go-libipfs/gateway API, deprecate Gateway.Writable (#9616) (ipfs/kubo#9616)
    • Create Changelog: v0.19 (ipfs/kubo#9617)
    • refactor: use gateway from go-libipfs (#9588) (ipfs/kubo#9588)
    • Merge Release: v0.18.1 (ipfs/kubo#9613)
    • Add overview section
    • Adjust inbound connection limits depending on memory.
    • feat: ipfs-webui 2.22.0
    • chore: bump go-libipfs remove go-bitswap
    • docs: DefaultResourceMgrMinInboundConns
    • feat(gateway): IPNS record response format (IPIP-351) (#9399) (ipfs/kubo#9399)
    • fix(ipns): honour --ttl flag in 'ipfs name publish' (#9471) (ipfs/kubo#9471)
    • feat: Pubsub.SeenMessagesStrategy (#9543) (ipfs/kubo#9543)
    • chore: bump go-libipfs to replace go-block-format
    • Merge Kubo: v0.18 (ipfs/kubo#9581)
    • fix: clarity: no user supplied rcmgr limits of 0 (#9563) (ipfs/kubo#9563)
    • fix(gateway): undesired conversions to dag-json and friends (#9566) (ipfs/kubo#9566)
    • fix: ensure connmgr is smaller then autoscalled ressource limits
    • fix: typo in ensureConnMgrMakeSenseVsResourcesMgr
    • docs: clarify browser descriptions for webtransport
    • fix: update saxon download path
    • fix: refuse to start if connmgr is smaller than ressource limits and not using none connmgr
    • fix: User-Agent sent to HTTP routers
    • test: port gateway sharness tests to Go tests
    • fix: do not download saxon in parallel
    • docs: improve docs/README (#9539) (ipfs/kubo#9539)
    • test: port CircleCI to GH Actions and improve sharness reporting (#9355) (ipfs/kubo#9355)
    • chore: migrate from go-ipfs-files to go-libipfs/files (#9535) (ipfs/kubo#9535)
    • fix: stats dht command when Routing.Type=auto (#9538) (ipfs/kubo#9538)
    • fix: hint people to changing from RSA peer ids
    • fix(gateway): JSON when Accept is a list
    • fix(test): retry flaky t0125-twonode.sh
    • docs: fix Router config Godoc (#9528) (ipfs/kubo#9528)
    • fix(ci): flaky sharness test
    • docs(config): Provi...
Read more
Loading

v0.19.0-rc1

06 Mar 14:56
@galargh galargh
v0.19.0-rc1
This tag was signed with the committer’s verified signature.
galargh Piotr Galar
GPG key ID: 2ACC6C98453FCE44
Verified
Learn about vigilant mode.
0f1181d
Compare
Choose a tag to compare
v0.19.0-rc1 Pre-release
Pre-release

Changelog: docs/changelogs/v0.19.md

Loading

v0.18.1

30 Jan 15:21
@galargh galargh
v0.18.1
This tag was signed with the committer’s verified signature.
galargh Piotr Galar
GPG key ID: 2ACC6C98453FCE44
Verified
Learn about vigilant mode.
675f8bd
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.18.1

🔦 Highlights

New default Pubsub.SeenMessagesStrategy

A new optional Pubsub.SeenMessagesStrategy configuration option has been added.

This option allows you to choose between two different strategies for
deduplicating messages: first-seen and last-seen.

When unset, the default strategy is last-seen, which calculates the
time-to-live (TTL) countdown based on the last time a message is seen. This
means that if a message is received and then seen again within the specified
TTL window based on the last time it was seen, it won't be emitted.

If you prefer the old behavior, which calculates the TTL countdown based on the
first time a message is seen, you can set Pubsub.SeenMessagesStrategy to
first-seen.

Improving libp2p resource management integration

This builds on the default protection nodes get against DoS (resource exhaustion) and eclipse attacks
with the go-libp2p Network Resource Manager/Accountant
that was fine-tuned in Kubo 0.18.

Adding default hard-limits from the Resource Manager/Accountant after the fact is tricky,
and some additional improvements have been made to improve the computed defaults.
As much as possible, the aim is for a user to only think about how much memory they want to bound libp2p to,
and not need to think about translating that to hard numbers for connections, streams, etc.
More updates are likely in future Kubo releases, but with this release:

  1. System.StreamsInbound is no longer bounded directly
  2. System.ConnsInbound, Transient.Memory, Transiet.ConnsInbound have higher default computed values.

Changelog

Full Changelog
  • github.com/ipfs/kubo:
    • Add overview section
    • Adjust inbound connection limits depending on memory.
    • feat: Pubsub.SeenMessagesStrategy (#9543) (ipfs/kubo#9543)
    • chore: update version
  • github.com/libp2p/go-libp2p-pubsub (v0.8.2 -> v0.8.3):

Contributors

Contributor Commits Lines ± Files Changed
Mohsin Zaidi 2 +511/-55 12
Antonio Navarro Perez 2 +57/-57 5
galargh 1 +1/-1 1
Loading

v0.18.0

23 Jan 17:00
@galargh galargh
v0.18.0
This tag was signed with the committer’s verified signature.
galargh Piotr Galar
GPG key ID: 2ACC6C98453FCE44
Verified
Learn about vigilant mode.
6750377
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.18.0

🔦 Highlights

Content routing

Default InterPlanetary Network Indexer

Content routing is the process of discovering which peers provide a piece of content. Kubo has traditionally only supported libp2p's implementation of Kademlia DHT for content routing.

Kubo can now bridge networks by including support for the delegated routing HTTP API. Users can compose content routers using the Routing.Routers config to pick content routers with different tradeoffs than a Kademlia DHT (e.g., high-performance and high-capacity centralized endpoints, dedicated Kademlia DHT nodes, routers with unique provider records, privacy-focused content routers).

One example is InterPlanetary Network Indexers, which are HTTP endpoints that cache records from both the IPFS network and other sources such as web3.storage and Filecoin. This improves not only content availability by enabling Kubo to transparently fetch content directly from Filecoin storage providers, but also improves IPFS content routing latency by an order of magnitude and decreases resource consumption.

Note: it's possible to retrieve content stored by Filecoin Storage Providers (SPs) from Kubo if the SPs service Bitswap requests. As of this release, some SPs are advertising Bitswap. You can follow the roadmap progress for IPNIs and Bitswap in SPs here.

In this release, the default content router is changed from dht to auto. The auto router includes the IPFS DHT in addition to the cid.contact IPNI instance. In future releases, we plan to expand the functionality of auto to encompass automatic discovery of content routers, which will improve performance and content availability (for example, see IPIP-342).

Previous behavior can be restored by setting Routing.Type to dht.

Alternative routing rules, including alternative IPNI endpoints, can be configured in Routing.Routers after setting Routing.Type to custom.

Learn more in the Routing docs.

Increase provider record republish interval and expiration

Default Reprovider.Interval changed from 12h to 22h to match new defaults for the Provider Record Expiration (48h) in go-libp2p-kad-dht v0.20.0.

The rationale for increasing this can be found in
RFM 17: Provider Record Livenes Report,
kubo#9326,
and the upstream DHT specifications at libp2p/specs#451.

Learn more in the Reprovider config.

Gateways

(DAG-)JSON and (DAG-)CBOR response formats

The IPFS project has reserved the corresponding media types at IANA:

This release implements them as part of IPIP-328
and adds Gateway support for CIDs with json (0x0200), cbor (0x51),
dag-json (0x0129)
and dag-cbor (0x71) codecs.

To specify the response Content-Type explicitly, the HTTP client can override
the codec present in the CID by using the format parameter
or setting the Accept HTTP header:

  • Plain JSON: ?format=json or Accept: application/json
  • Plain CBOR: ?format=cbor or Accept: application/cbor
  • DAG-JSON: ?format=dag-json or Accept: application/vnd.ipld.dag-json
  • DAG-CBOR: ?format=dag-cbor or Accept: application/vnd.ipld.dag-cbor

In addition, when DAG-JSON or DAG-CBOR is requested with the Accept header
set to text/html, the Gateway will return a basic HTML page with download
options, improving the user experience in web browsers.

Example 1: DAG-CBOR and DAG-JSON Conversion on Gateway

The Gateway supports conversion between DAG-CBOR and DAG-JSON for efficient
end-to-end data structure management: author in CBOR or JSON, store as binary
CBOR and retrieve as JSON via HTTP:

$ echo '{"test": "json"}' | ipfs dag put # implicit --input-codec dag-json --store-codec dag-cbor
bafyreico7mjtqtqhvawro3yud5uqn6sc33nzqb7b5j2d7pdmzer5nab4t4

$ ipfs block get bafyreico7mjtqtqhvawro3yud5uqn6sc33nzqb7b5j2d7pdmzer5nab4t4 | xxd
00000000: a164 7465 7374 646a 736f 6e              .dtestdjson

$ ipfs dag get bafyreico7mjtqtqhvawro3yud5uqn6sc33nzqb7b5j2d7pdmzer5nab4t4 # implicit --output-codec dag-json
{"test":"json"}

$ curl "http://127.0.0.1:8080/ipfs/bafyreico7mjtqtqhvawro3yud5uqn6sc33nzqb7b5j2d7pdmzer5nab4t4?format=dag-json"
{"test":"json"}
Example 2: Traversing CBOR DAGs

Placing a CID in CBOR Tag 42 enables the
creation of arbitrary DAGs. The equivalent DAG-JSON notation for linking
to different blocks is represented by { "/": "cid" }.

The Gateway supports traversing these links, enabling access to data
referenced by structures other than regular UnixFS directories:

$ echo '{"test.jpg": {"/": "bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi"}}' | ipfs dag put
bafyreihspwy3zlkzgphmec5d3xb5g5njrqwotd46lyubnelbzktnmsxkq4 # dag-cbor document linking to unixfs file

$ ipfs resolve /ipfs/bafyreihspwy3zlkzgphmec5d3xb5g5njrqwotd46lyubnelbzktnmsxkq4/test.jpg
/ipfs/bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi

$ ipfs dag stat bafyreihspwy3zlkzgphmec5d3xb5g5njrqwotd46lyubnelbzktnmsxkq4
Size: 119827, NumBlocks: 2

$ curl "http://127.0.0.1:8080/ipfs/bafyreihspwy3zlkzgphmec5d3xb5g5njrqwotd46lyubnelbzktnmsxkq4/test.jpg" > test.jpg
Example 3: UnixFS directory listing as JSON

Finally, Gateway now supports the same logical format projection from
DAG-PB to DAG-JSON as the ipfs dag get command, enabling the retrieval of directory listings as JSON instead of HTML:

$ export DIR_CID=bafybeigccimv3zqm5g4jt363faybagywkvqbrismoquogimy7kvz2sj7sq
$ curl -H "Accept: application/vnd.ipld.dag-json" "http://127.0.0.1:8080/ipfs/$DIR_CID" | jq
$ curl "http://127.0.0.1:8080/ipfs/$DIR_CID?format=dag-json" | jq
{
  "Data": {
    "/": {
      "bytes": "CAE"
    }
  },
  "Links": [
    {
      "Hash": {
        "/": "Qmc3zqKcwzbbvw3MQm3hXdg8BQoFjGdZiGdAfXAyAGGdLi"
      },
      "Name": "1 - Barrel - Part 1 - alt.txt",
      "Tsize": 21
    },
    {
      "Hash": {
        "/": "QmdMxMx29KVYhHnaCc1icWYxQqXwUNCae6t1wS2NqruiHd"
      },
      "Name": "1 - Barrel - Part 1 - transcript.txt",
      "Tsize": 195
    },
    {
      "Hash": {
        "/": "QmawceGscqN4o8Y8Fv26UUmB454kn2bnkXV5tEQYc4jBd6"
      },
      "Name": "1 - Barrel - Part 1.png",
      "Tsize": 24862
    }
  ]
}
$ ipfs dag get $DIR_CID
{"Data":{"/":{"bytes":"CAE"}},"Links":[{"Hash":{"/":"Qmc3zqKcwzbbvw3MQm3hXdg8BQoFjGdZiGdAfXAyAGGdLi"},"Name":"1 - Barrel - Part 1 - alt.txt","Tsize":21},{"Hash":{"/":"QmdMxMx29KVYhHnaCc1icWYxQqXwUNCae6t1wS2NqruiHd"},"Name":"1 - Barrel - Part 1 - transcript.txt","Tsize":195},{"Hash":{"/":"QmawceGscqN4o8Y8Fv26UUmB454kn2bnkXV5tEQYc4jBd6"},"Name":"1 - Barrel - Part 1.png","Tsize":24862}]}
🐎 Fast directory listings with DAG sizes

Fast listings are now enabled for all UnixFS directories: big and small.
There is no linear slowdown caused by reading size metadata from child nodes,
and the size of DAG representing child items is always present.

As an example, the CID
bafybeiggvykl7skb2ndlmacg2k5modvudocffxjesexlod2pfvg5yhwrqm represents a UnixFS
directory with over 10k files. Listing big directories was fast
since Kubo 0.13, but in this release it will also include the size column.

QUIC and WebTransport

WebTransport enabled by default

WebTransport is a new libp2p transport that was introduced in v0.16 that is based on top of QUIC and HTTP3.

This allows browser-based nodes to contact Kub...

Read more
Loading