Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

⚡️ v0.34.0 RELEASE 🚀 #1721

Closed
47 of 49 tasks
alanshaw opened this issue Nov 19, 2018 · 9 comments
Closed
47 of 49 tasks

⚡️ v0.34.0 RELEASE 🚀 #1721

alanshaw opened this issue Nov 19, 2018 · 9 comments
Assignees
@alanshaw
Labels
topic/release Topic release

Comments

@alanshaw
Copy link
Member

alanshaw commented Nov 19, 2018 •
edited
Loading

Ahh yeah, it got fast

🗺 What's left for release?

🔦 Highlights

🏎 Reading Protobuf DAG nodes is super fast

Reading Protobuf DAG nodes just got a serious speed boost as well as a memory reduction. Previously Protobuf DAG nodes (dag-pb nodes for short) carried a multihash property (a CIDv0) with them. This used up loads of CPU time calculating the hash for a given node as it was retrieved from storage and with the advent of CIDv1 there was no guarantee the hashing algorithm and length were correct.

So, we removed it! 🦖

Ok so that had the unfortunate consequence of making the object API a whole lot less useful when writing data - the DAG nodes you got back were basically the data you put in. Hence the object API was refactored to return CIDs instead of DAG nodes for write operations...and we all lived happily ever after.

🚤 Adding content is blazingly fast

We found a big bottleneck (or should I say small bottleneck?) that meant the bigger the file you added to IPFS, the longer it would take - oh no 😭! Good news folks, we've seen the speed of adding large files increase by 50% or more in some cases! 💥

Read all about it in the pull request notes.

🎄 HAMT support added to MFS

We're putting the whole of npm on IPFS! These days npm is like 5.3 terabytes of data and it's all going in MFS. This is super rad, but we needed a good sharding strategy because 5TB is a lorra lorra files.

If you're curious about npm on IPFS, check out the project here.

📣 IPNS over pubsub and DHT

Get informed of IPNS record updates and read and publish your IPNS records to the DHT. It's all there and it's all awesome. For those of you new to IPNS, let me give you the lowdown - IPNS puts the mutable in immutable 🤣 It's an age old problem, content addressing is rad and all that, but if I change something the hash changes - 👎 boo...but wait, IPNS solves this, you get a permenant address for changeable content - hooray \o/.

IPNS over pubsub gets the word out quicker to peers that are interested when an IPNS record changes. IPNS over DHT allows peers to find and resolve your IPNS address to some content in the first place! In the next JS IPFS release (0.35) the DHT will be enabled by default and it's going to be epic.

⚾️ CID handling improvements

Smoosh your CIDs into whatever version you like - you can now add data under a version 0 CID and get it back using a version 1 CID and vice versa. Now that you have this freedom you can encode them with whatever multibase encoding you like. Version 0 CIDs are all base58btc but if you convert to a version 1 CID you can encode it with base2, base32, base64url or whatever:

# base2
010111000000010010001000000100011011010100010010000001010010111001110001011010111100010100000111000011101010101010101101111100000001011101110001011110100001000100111010101101010111111001000111110001001010000101100010110000001000011110101110100100010101110110100010110100110000001110
# base32
bafybeicg2rebjoofv4kbyovkw7af3rpiitvnl6i7ckcywaq6xjcxnc2mby
# base58btc
QmT78zSuBmuS4z925WZfrqQ1qHaJ56DQaTfyMUF7F8ff5o
# base64url
uAXASIEbUSBS5xa8UHDqqt8BdxehE6tX5HxKFiwIeukV2i0wO

This is all work to smooth out the eventual transition to base32 CIDv1 by default - a move to allow CIDs to be used as valid URL origins. Have a read of this for more.

To help you craft your artisanal CIDs we've introduced a --cid-base option to a bunch of CLI commands (and ?cid-base option to a bunch of HTTP API endpoints). Check it out:

jsipfs add file.txt --cid-base=base32
added bafybeibns4lrebrxaymvyshgmki5biwh6cd53idxfpen6ysomzrywtsm44 file.txt

💪 Deps got upgrades!

We got you covered with WebUI 2.3 (quic support, responsive navbar, and a language selector), libp2p 0.24 and many other upgrades giving you a faster and smaller JS IPFS.

🏓 DHT bumped to next release

The Distributed Hash Table(tennis) is finally here! This is the biggest leap forwards for JS IPFS since sliced bread. It allows your IPFS node to find peers and content way more easily and it has full interop with Go IPFS nodes so y'all have the full IPFS network at your fingertips 💥 I know, you're welcome - send flowers to @vasco-santos.

🏗 API Changes

  • Object API methods that write DAG nodes now return a CID instead of a DAG node. Affected methods:
    • ipfs.object.new
    • ipfs.object.patch.addLink
    • ipfs.object.patch.appendData
    • ipfs.object.patch.rmLink
    • ipfs.object.patch.setData
    • ipfs.object.put
    • More info
  • DAGNode instances, which are part of the IPLD dag-pb format have been refactored. These instances no longer have multihash, cid or serialized properties. This effects the following API methods that return these types of objects:
  • Files API methods add*, cat*, get* have moved from files to the root namespace. Specifically, the following changes have been made:
    • ipfs.files.add => ipfs.add
    • ipfs.files.addPullStream => ipfs.addPullStream
    • ipfs.files.addReadableStream => ipfs.addReadableStream
    • ipfs.files.cat => ipfs.cat
    • ipfs.files.catPullStream => ipfs.catPullStream
    • ipfs.files.catReadableStream => ipfs.catReadableStream
    • ipfs.files.get => ipfs.get
    • ipfs.files.getPullStream => ipfs.getPullStream
    • ipfs.files.getReadableStream => ipfs.getReadableStream
  • New core files API methods added:
  • DHT API methods renamed and return types changed
    • ipfs.dht.findprovs renamed to ipfs.dht.findProvs and returns an array of PeerInfo
    • ipfs.dht.findpeer renamed to ipfs.dht.findPeer and returns a PeerInfo
    • ipfs.dht.query now returns an array of PeerInfo
    • More info
  • A new option is available in the CLI, HTTP API and core that will allow the multibase encoding to be specified for any CIDs that are returned as strings.
    • A --cid-base option has been added to the following CLI commands:
      • jsipfs bitswap stat
      • jsipfs bitswap unwant
      • jsipfs bitswap wantlist
      • jsipfs block put
      • jsipfs block stat
      • jsipfs add
      • jsipfs ls
      • jsipfs object get
      • jsipfs object links
      • jsipfs object new
      • jsipfs object patch add-link
      • jsipfs object patch append-data
      • jsipfs object patch rm-link
      • jsipfs object patch set-data
      • jsipfs object put
      • jsipfs object stat
      • jsipfs pin add
      • jsipfs pin ls
      • jsipfs pin rm
      • jsipfs resolve
      • Note: these two MFS commands already implement the --cid-base option:
      • jsipfs files ls
      • jsipfs files stat
    • A ?cid-base= query option has been added to the following HTTP endpoints:
      • /api/v0/bitswap/wantlist
      • /api/v0/bitswap/stat
      • /api/v0/bitswap/unwant
      • /api/v0/block/put
      • /api/v0/block/stat
      • /api/v0/add
      • /api/v0/ls
      • /api/v0/object/new
      • /api/v0/object/get
      • /api/v0/object/put
      • /api/v0/object/stat
      • /api/v0/object/links
      • /api/v0/object/patch/append-data
      • /api/v0/object/patch/set-data
      • /api/v0/object/patch/add-link
      • /api/v0/object/patch/rm-link
      • /api/v0/pin/ls
      • /api/v0/pin/add
      • /api/v0/pin/rm
      • /api/v0/resolve
    • A cidBase option has been added to the following core functions:
      • resolve
    • NOTE Using the CID base option in bitswap, dag and object APIs WILL NOT auto upgrade your CID to v1 if it is a v0 CID and WILL NOT apply the encoding you specified. This is because these APIs return IPLD objects with links and changing the version of the links would result in a different hash for the node if you were to re-add it. Also, the CID you used to retrieve the node wouldn't actually refer to the node you got back any longer. Read this for further context.
  • All API methods that returned big.js instances now return bignumber.js instances.

✅ Release Checklist

❤️ Huge thank you to everyone that made this release possible

By alphabetical order, here are all the humans that contributed to the release:

🙌🏽 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:

⁉️ 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.
@alanshaw alanshaw added the status/in-progress In progress label Nov 19, 2018
@alanshaw alanshaw self-assigned this Nov 19, 2018
@alanshaw alanshaw mentioned this issue Nov 21, 2018
Merged
@vasco-santos vasco-santos mentioned this issue Nov 22, 2018
Merged
2 tasks
@alanshaw alanshaw mentioned this issue Dec 4, 2018
Closed
@vasco-santos vasco-santos mentioned this issue Dec 6, 2018
Closed
@alanshaw alanshaw mentioned this issue Dec 7, 2018
Closed
@daviddias
Copy link
Member

This release is going to be HUUUUGEEEE!!

This was referenced Dec 9, 2018
Closed
Closed
@olizilla olizilla mentioned this issue Dec 10, 2018
Closed
@alanshaw alanshaw mentioned this issue Dec 11, 2018
Closed
@fsdiogo fsdiogo mentioned this issue Dec 11, 2018
Closed
@alanshaw alanshaw pinned this issue Dec 17, 2018
@jennwrites jennwrites mentioned this issue Dec 18, 2018
Closed
This was referenced Dec 19, 2018
Closed
Closed
Closed
This was referenced Jan 3, 2019
Open
Closed
Closed
@daviddias
Copy link
Member

@alanshaw with this release, can js-ipfs move to base32 by default?

@mkg20001
Copy link
Contributor

@alanshaw Possibly want to make this release even bigger than it is? I'm currently working on stardust, a replacement for ws-star that actually works. I could ship it behind a flag with some help on this pr #1812 which requires this one to be finished libp2p/js-libp2p-crypto#125

@daviddias
Copy link
Member

@mkg20001 additional transports can be added through adding a custom libp2p bundle -- https://github.com/ipfs/js-ipfs#optionslibp2p. No need for special flags :)

@mkg20001
Copy link
Contributor

@daviddias I'm talking about replacing ws-star with stardust upstream in js-ipfs. So that EXPERIMENTAL.stardust would switch ws-star for stardust. See libp2p/js-libp2p-websocket-star#70

@alanshaw
Copy link
Member Author

alanshaw commented Jan 14, 2019 •
edited
Loading

@alanshaw with this release, can js-ipfs move to base32 by default?

I'd love it to but there's no PRs implementing it yet. Possibly in 0.35 or more likely in 0.36.

0.34 will bring js-ipfs up to speed with go-ipfs in terms of CID version agnostic get and be ahead of it with the --cid-base option.

Essentially the rough plan now is:

  • 0.35 - DHT
  • 0.36 - base32 CID v1

@alanshaw Possibly want to make this release even bigger than it is?

Absolutely not! This release needs to leave the building asap. 🤣

@alanshaw alanshaw mentioned this issue Jan 15, 2019
Closed
@aphelionz
Copy link
Contributor

Great work everybody! Exciting stuff.

@kyledrake kyledrake mentioned this issue Jan 16, 2019
Closed
@alanshaw alanshaw mentioned this issue Jan 16, 2019
Closed
@ghost ghost removed the status/in-progress In progress label Jan 17, 2019
@alanshaw alanshaw unpinned this issue Jan 17, 2019
@ntninja ntninja mentioned this issue Jan 27, 2019
Closed
@alanshaw alanshaw added the topic/release Topic release label Aug 5, 2019
@younasm
Copy link

younasm commented Mar 13, 2022 •
edited
Loading

Error: /api/v0/object has been removed, use /api/v0/dag instead

I am using ipfs for image uploading it was working fine but now I am getting the above error. how should I change my code to make it work again. i am new to Ethereum please help.

uploaddoc: function(){
    const reader = new FileReader();
    reader.onloadend = function() {
      const ipfs = window.IpfsApi('ipfs.infura.io', 5001, {protocol: 'https'}) // Connect to IPFS
      console.log('ipfs-connection', ipfs);
      const buf = buffer.Buffer(reader.result) // Convert data into buffer
      ipfs.files.add(buf, (err, result) => { // Upload buffer to IPFS
        if(err) {
          console.error(err)
          swal("Error", "Something went wrong!", "error");
          return
        }
        let url = `https://ipfs.io/ipfs/${result[0].hash}`
        console.log(`Url --> ${url}`)
        $(".js-uploaded-hash").attr("data-hash", result[0].hash);
        swal("Document Uploaded!", "Thanks for choosing us!", "success");
      })
    }
    const photo = document.getElementById("memories");
    reader.readAsArrayBuffer(photo.files[0]); // Read Provided File

  },

@younasm
Copy link

younasm commented Mar 28, 2022

Error: /api/v0/object has been removed, use /api/v0/dag instead

I am using ipfs for image uploading it was working fine but now I am getting the above error. how should I change my code to make it work again. i am new to Ethereum please help.

uploaddoc: function(){
    const reader = new FileReader();
    reader.onloadend = function() {
      const ipfs = window.IpfsApi('ipfs.infura.io', 5001, {protocol: 'https'}) // Connect to IPFS
      console.log('ipfs-connection', ipfs);
      const buf = buffer.Buffer(reader.result) // Convert data into buffer
      ipfs.files.add(buf, (err, result) => { // Upload buffer to IPFS
        if(err) {
          console.error(err)
          swal("Error", "Something went wrong!", "error");
          return
        }
        let url = `https://ipfs.io/ipfs/${result[0].hash}`
        console.log(`Url --> ${url}`)
        $(".js-uploaded-hash").attr("data-hash", result[0].hash);
        swal("Document Uploaded!", "Thanks for choosing us!", "success");
      })
    }
    const photo = document.getElementById("memories");
    reader.readAsArrayBuffer(photo.files[0]); // Read Provided File

  },

Hello Please anyone expert here I am waiting for help.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@alanshaw alanshaw

Labels
topic/release Topic release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@aphelionz @alanshaw @daviddias @mkg20001 @younasm