FAQ
Please open an issue if you'd like something addressed here
- 👩👧 What is the relationship of Helia to js-IPFS?
- 🤝 How does Helia guarantee compatibility with Kubo and other IPFS implementations?
- 🏎️ How does it perform compared to other implementations including js-IPFS?
- 🙃 Why consider using Helia over js-IPFS
- 🤷 Why use Helia over the kubo-rpc-client
- 🧭 What mechanisms does Helia have for content and peer routing?
- 🚌 What data transports does Helia have
IPFS is a suite of specifications and tools that concern data addressing and transfer. Historically it's also been the name of two applications that implement those protocols in Go (Kubo) and JavaScript (js-IPFS).
With Filecoin development, Protocol Labs found that progress towards the goal of "one protocol multiple implementations" was smoother when implementations did not contain the word "Filecoin" as by including that term, people consciously or unconsciously assume that one project is somehow "blessed", favoured or otherwise more important than another.
So in late 2021 a plan was enacted to remove the word "IPFS" from go-IPFS and js-IPFS and free up the space for multiple alternative implementations, which would be free to innovate on their own terms and perhaps specialize for certain tasks or environments.
go-ipfs was renamed Kubo and carried on as usual, but for js-IPFS we wanted to take the opportunity to have another look at what an implementation of IPFS in JS could look like and to apply learnings from the previous years of development.
The result of this is Helia - a new implementation of IPFS in JavaScript that is designed to be more modular and lightweight than js-IPFS which focusses on the most important use cases of IPFS in JavaScript.
It shares some internal components with js-IPFS - libp2p, bitswap etc but has a redesigned API that will enable the next generation of distributed applications.
js-IPFS is being retired in favour of Helia. Read more about the thought processes that informed Helia's design, check out the examples and start porting your application today!
Each Helia component has an interop suite that tests compatibility with other IPFS implementations. These tests run during CI as part of each PR and before a release.
Initially they test compatibility with Kubo but if you maintain another IPFS implementation please open an issue or a PR to get added to the test matrix.
See:
Other modules should implement an interop suite which can be linked to from here.
For the areas that have been benchmarked, very favourably.
There is a benchmarking suite in this repository which will be extended to cover most functional areas such as data transfer.
Helia uses reference counting for garbage collection. This has proven to be much more scalable than the approaches taken by js-IPFS or Kubo.
Please see #36 for graphs and discussion of the results.
Helia is a fresh look at what a fully-featured IPFS implementation written in JavaScript could look like.
From it's inception js-IPFS was intended to be an API-compatible clone of what was go-IPFS and has since been renamed Kubo. Over time this began to make less sense as more and more features were added to Kubo, js-IPFS struggled to keep pace and even then not all of the added features made sense in a JS context.
Although compatible on the wire with Kubo and other interfaces, Helia is not constrained by the Kubo API and is free to innovate in ways that empower JS use cases. For example there's no need to follow the kitchen-sink approach of the Kubo/js-IPFS, instead users can keep their applications lightweight but just pulling in the features they use.
js-IPFS is deprecated and will receive no further updates outside of emergency security fixes.
Helia and the kubo-rpc-client are fundamentally different beasts.
When running the kubo-rpc-client you also must run an accompanying Kubo daemon which means managing a separate go runtime which is opaque to familiar JS monitoring and inspection tools and you must also protect an HTTP RPC API with very little in the way of built in security.
Running Helia allows you to embed an IPFS node into your application giving you the lowest latency and best possible performance. For server applications this reduces the amount of moving parts and deployment tasks and for browser applications it's the only way to run a full IPFS node for every user.
It also means the user can use their JS expertise to tune and monitor their node using the same skillset and tools they'd use to inspect their application.
Helia supports all of the existing libp2p content and peer routing mechanisms.
These include but are not limited to:
- @libp2p/kad-dht
- @libp2p/ipni-content-routing
- @libp2p/reframe-content-routing
- @libp2p/delegated-content-routing
- @libp2p/delegated-peer-routing
Helia supports all of the existing libp2p transports.
These include but are not limited to:
- @libp2p/webtransport
- @libp2p/webrtc
- @libp2p/websockets
- @libp2p/tcp
