# What is the mapping between block hashes and storage in .ipfs/blocks/?

**URL:** <https://discuss.ipfs.tech/t/what-is-the-mapping-between-block-hashes-and-storage-in-ipfs-blocks/409>\
**Category:** Help\
**Created:** [May 23, 2017, 12:07am UTC](https://discuss.ipfs.tech/t/what-is-the-mapping-between-block-hashes-and-storage-in-ipfs-blocks/409 "2017-05-23T00:07:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![flyingzumwalt](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/flyingzumwalt/32/12_2.png) [@flyingzumwalt](https://discuss.ipfs.tech/u/flyingzumwalt)\
**Post date:** [May 23, 2017, 12:07am UTC](https://discuss.ipfs.tech/t/what-is-the-mapping-between-block-hashes-and-storage-in-ipfs-blocks/409/1 "2017-05-23T00:07:56Z")

</div>

_From @JustinDrake on Thu Dec 22 2016 12:43:53 GMT+0000 (UTC)_  
  
Answer: `base32encode-nopad(base58-decode(HASH))`, but this will change soon (see [Default 5 digit prefix for flatfs is no longer sufficient for CidV1 · Issue #3463 · ipfs/kubo · GitHub](https://github.com/ipfs/go-ipfs/issues/3463))  
  
_Copied from original issue: [What is the mapping between block hashes and storage in .ipfs/blocks/? · Issue #213 · ipfs-inactive/faq · GitHub](https://github.com/ipfs/faq/issues/213)_
