2

According to this, an IPFS hash can be represented with 32 bytes.

  1. Would these hashes need to be stored in RAM?
  2. If so, is it limited to 1 file stored per hash?
  3. Would it be ~$0.20/hash to store in RAM if we assume:


enter image description here


enter image description here

Slide from Dan's presentation on "Scaling Blockchain Computation and Storage"

  • 1
    For 1., that depends on your use case. What is this. You could also browse the history to find a transaction with your hash. See eosproof.io for example. – friedger Jul 6 '18 at 11:38
  • 1
    For 2., you could also store the hash of a directory – friedger Jul 6 '18 at 11:40
2
  1. Yes, if your contract needs to access hashes. In other word, if you store hashes in multi-index table rows, it needs RAM.

  2. From the view of IPFS, a hash represents a file. Whatever the content it has.

  3. Your math is correct. But the RAM price you gave is 0.0228/32*1000 = 0.7125 EOS/KB, pretty much on the recent spike. The RAM has gone crazy lately and thus gives you the answer $0.20/hash. Now the market calms down a little. By the time I'm answering this question, the price is 0.47 EOS/KB. https://eos.feexplorer.io/

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.