js-IPFS 0.46.0 released with new faster bitswap and go-IPFS 0.5 compat
by Alex Potsides on 2020-06-08
Bitswap 1.2.0, transfer speed improvements & go-IPFS 0.5.x compatibility
Blink and you’ll miss it,
js-IPFS@0.46.0 has been released; goodies include Bitswap 1.2.0, much faster file transfers, and go-IPFS 0.5.x compatibility!
↔️ Bitswap 1.2.0
Version 1.2.0 of the Bitswap protocol has landed in
js-IPFS and brings a host of performance improvements around coordinating the supply of blocks to peers across the network. For example, peers can now respond to WANTs with messages saying they have the block but not sending it, in order to later send multiple blocks in one message instead of many small messages resulting in less chatty network operations and faster overall transfer times.
See ipfs/js-ipfs-bitswap#204 for more!
💨 Faster file transfers
The Bitswap module has had a bit of an overhaul and is now much faster at pulling blocks from other nodes across the network. Before, we waited a little while before sending our wantlist to newly connected peers—we’ve reduced that window and seen a massive speedup (smaller bars are better):
As you can see, the new js-IPFS is about 3x faster at pulling large files from other nodes on the network than the previous release, and that increases to about 5x as the files get smaller.
We’re not stopping there though, there are plenty more performance improvements on the way!
See ipfs/js-ipfs-bitswap#224 for all the details.
🤝 go-IPFS v0.5.x compatibility
The new version of go-IPFS brought a whole slew of changes with it—check out our blog post for more details.
The good news is js-IPFS has taken on a whole heap of these features and the
ipfs-http-client is now 100% compatible with
js-IPFS nodes will now happily chat away to
go-IPFS nodes over the network via Bitswap and gossipsub too.
See ipfs/js-ipfs#3013 for the full rundown.
- Using an AbortSignal to cancel a request to get a block (via
ipfs.catfor example) will now cause those blocks to be removed from your wantlist (ipfs/js-ipfs-bitswap#214)
ipfs.dht.get(key, [options])accepts a string or a buffer as
🦟 Bugs fixed
- Decrease wantlist sending debounce time (ipfs/js-ipfs-bitswap#224)
- Fix bitswap race conditions when requesting the same block twice (ipfs/js-ipfs-bitswap#214)
- libp2p pubsub now creates two unidirectional streams to topic peers making message delivery more reliable (ipfs/go-ipfs-pubsub#331)
keyis optional again (#3069) (d043138)
- extra mode bits passed to unixfs constructor are now ignored (ipfs/js-ipfs-unixfs#53) (65a040d)
🏗 API Changes
ipfs.lsno longer supports a
sortoption (#3013) (0900bb9)
ipfs.key.gendefaults to 2048 bit RSA keys (#3013) (0900bb9)
HTTP API Client
🗺️ What’s next?
Check out the js-IPFS Project Roadmap which contains headline features organised in the order we hope them to land.
Only large features are called out in the roadmap, expect lots of small bugfix releases between the roadmapped items!
😍 Huge thank you to everyone that made this release possible
- @0xflotus (1 commit, 1 PR)
- @5310 (1 comment)
- @achingbrain (30 commits, 12 PRs, 1 issue, 55 comments)
- @aphelionz (1 PR, 1 comment)
- @AquiGorka (1 comment)
- @Artod (1 comment)
- @autonome (11 comments)
- @bluelovers (1 commit)
- @bmann (1 comment)
- @carsonfarmer (1 issue, 4 comments)
- @chelneru (1 comment)
- @codecov-commenter (9 comments)
- @danielrempe-ut (1 issue, 1 comment)
- @dapplion (2 comments)
- @daviddahl (1 issue, 5 comments)
- @dirkmc (1 comment)
- @domwoe (1 comment)
- @DougAnderson444 (4 comments)
- @Gozala (2 PRs, 7 issues, 25 comments)
- @hacdias (2 comments)
- @hugomrdias (4 commits, 5 PRs, 1 issue, 26 comments)
- @jacobheun (4 commits, 3 PRs, 2 issues, 18 comments)
- @jakehemmerle (2 comments)
- @johnnymatthews (1 commit, 1 PR)
- @justinmchase (1 comment)
- @kumavis (2 comments)
- @lazyweirdo (2 comments)
- @lidel (1 PR, 2 comments)
- @matrushka (1 PR)
- @mburns (1 comment)
- @mdtanrikulu (1 issue)
- @mikeal (1 comment)
- @mitra42 (1 comment)
- @momack2 (1 commit, 1 comment)
- @mpetrunic (1 comment)
- @obo20 (1 comment)
- @oed (10 comments)
- @RenatoPerotti (1 issue)
- @revolunet (1 commit, 1 PR)
- @ribasushi (1 comment)
- @robert-cronin (1 issue, 1 comment)
- @rohail411 (2 issues, 2 comments)
- @rumkin (1 issue)
- @rvagg (4 comments)
- @SignpostMarv (1 comment)
- @stasbar (1 issue, 1 comment)
- @Stebalien (7 comments)
- @stensonb (11 commits)
- @tabcat (1 issue)
- @tarunbatra (1 PR, 3 comments)
- @thattommyhall (1 commit)
- @tymmesyde (1 comment)
- @typhu-xyz (2 comments)
- @vasco-santos (56 commits, 13 PRs, 8 issues, 66 comments)
- @vmx (2 commits, 5 comments)
- @welcome (5 comments)
- @wemeetagain (38 commits, 9 PRs, 3 issues, 8 comments)
- @witten (1 comment)
- @xinfushe-dev (1 comment)
- @xmaysonnave (1 comment)
🙌🏽 Want to contribute?
Would you like to contribute to the IPFS project and don’t know how? Well, there are a few places you can get started:
- Check the issues with the
help wantedlabel in the js-IPFS repo
- Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute: https://github.com/ipfs/team-mgmt/#weekly-ipfs-all-hands
- Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
- Join the discussion at https://discuss.ipfs.io/ and help users finding their answers.
- Join the 🚀 IPFS Core Implementations Weekly Sync 🛰 and be part of the action!
⁉️ Do you have questions?
The best place to ask your questions about IPFS, how it works, and what you can do with it is at discuss.ipfs.io. We are also available at the
#ipfs channel on Freenode.