|
2 | 2 |
|
3 | 3 | ### 0.4.9 - 2017-04-30
|
4 | 4 |
|
| 5 | +Ipfs 0.4.9 is a maintenance release that contains several useful bugfixes and |
| 6 | +improvements. Notably, `ipfs add` has gained the ability to select which CID |
| 7 | +version will be output. The common ipfs hash that looks like this: |
| 8 | +`QmRjNgF2mRLDT8AzCPsQbw1EYF2hDTFgfUmJokJPhCApYP` is a multihash. Multihashes |
| 9 | +allow us to specify the hashing algorithm that was used to verify the data, but |
| 10 | +it doesn't give us any indication of what format that data might be. To address |
| 11 | +that issue, we are adding another couple of bytes to the prefix that will allow us |
| 12 | +to indicate the format of the data referenced by the hash. This new format is |
| 13 | +called a Content ID, or CID for short. The previous bare multihashes will still |
| 14 | +be fully supported throughout the entire application as CID version 0. The new |
| 15 | +format with the type information will be CID version 1. To give an example, |
| 16 | +the content referenced by the hash above is "Hello Ipfs!". That same content, |
| 17 | +in the same format (dag-protobuf) using CIDv1 is |
| 18 | +`zb2rhkgXZVkT2xvDiuUsJENPSbWJy7fdYnsboLBzzEjjZMRoG`. |
| 19 | + |
| 20 | +CIDv1 hashes are supported in ipfs versions back to 0.4.5. Nodes running 0.4.4 |
| 21 | +and older will not be able to load content via CIDv1 and we recommend that they |
| 22 | +update to a newer version. |
| 23 | + |
| 24 | +There are many other use cases for CIDs. Plugins can be written to |
| 25 | +allow ipfs to natively address content from any other merkletree based system, |
| 26 | +such as git, bitcoin, zcash and ethereum -- a few systems we've already started work on. |
| 27 | + |
| 28 | +Aside from the CID flag, there were many other changes as noted below: |
| 29 | + |
5 | 30 | - Features
|
6 | 31 | - Add support for using CidV1 in 'ipfs add' ([ipfs/go-ipfs#3743](https://github.com/ipfs/go-ipfs/pull/3743))
|
7 | 32 | - Improvements
|
|
0 commit comments