Viewing a response to: @elbiasto/pks7spzvx
<p>I am not a steem witness or proficient in the steem blockchain. But this is what I understand from the underlying data from the blockchain.</p> <p>The current consensus max size per block is <strong>64KB</strong>, created every 3 seconds. 64KB is actually a big enough size. Here we can store 64,000 characters. A block will store information on post, comment, votes, custom json, and transactions. Posts and comments will likely take up most of the storage here. But it is hard to imagine a 64000 characters posts/comments being created every 3 seconds. </p> <p>Next is custom json. As more and more dapps start to use the custom json for storing information, this part of the block will get more and more usage in the future. But again, it is still quite impossible to fill up that space.</p> <p>Currently, there are around 25,727,000 blocks already created. If we multiply that with 64KB, we get around <strong>1.65 Terabytes</strong> of storage used. This is assuming every single block is fully utilized with 64KB. We know that is not happening. Hypothetically assuming so, the total steem blockchain is at maximum 1.65 TB. I say the realistic usage is probably just 10-20% of that. </p> <p>1.65TB of SSD is actually not too big. We are now seeing 2TB SSD disk at really cheap price. So that is not much of an issue. Top witnesses earn much more than just a few SSD disk. Let them worry about it. </p> <p>I don't think it will be a problem in the near future. Disk technology grows faster than the rate of our steem blockchain usage. What I am concern is the image storage. When I go back and browse some of my steemit earlier posts, I find that many images were not displaying. Not sure if steemit does archiving and remove older images, but that is a real and serious problem. Storage needed for image for exceeds the storage needed for steem blockchain. This is why many dapps are shifting to IPFS. IPFS will be the ones facing serious serious size problem. For us, at steem, don't worry, we are safe.</p> <p><em>image source: https://steemdb.com/</em></p> <figure><img src="https://cdn.steemitimages.com/DQmP5KiULv8XW6KgVPya6k33tZ2dcBjqRBawDqYhK2AE1pU/image.png"/></figure> <p><br></p>
author | jrvacation |
---|---|
permlink | pkc7ylyt5 |
category | musing-threads |
json_metadata | "{"app":"Musing","appTags":["Steem","Blockchain","Steemit","Cryptocurrency"],"appCategory":"Steem","appBody":"<p>I am not a steem witness or proficient in the steem blockchain. But this is what I understand from the underlying data from the blockchain.</p>\n<p>The current consensus max size per block is <strong>64KB</strong>, created every 3 seconds. 64KB is actually a big enough size. Here we can store 64,000 characters. A block will store information on post, comment, votes, custom json, and transactions. Posts and comments will likely take up most of the storage here. But it is hard to imagine a 64000 characters posts/comments being created every 3 seconds. </p>\n<p>Next is custom json. As more and more dapps start to use the custom json for storing information, this part of the block will get more and more usage in the future. But again, it is still quite impossible to fill up that space.</p>\n<p>Currently, there are around 25,727,000 blocks already created. If we multiply that with 64KB, we get around <strong>1.65 Terabytes</strong> of storage used. This is assuming every single block is fully utilized with 64KB. We know that is not happening. Hypothetically assuming so, the total steem blockchain is at maximum 1.65 TB. I say the realistic usage is probably just 10-20% of that. </p>\n<p>1.65TB of SSD is actually not too big. We are now seeing 2TB SSD disk at really cheap price. So that is not much of an issue. Top witnesses earn much more than just a few SSD disk. Let them worry about it. </p>\n<p>I don't think it will be a problem in the near future. Disk technology grows faster than the rate of our steem blockchain usage. What I am concern is the image storage. When I go back and browse some of my steemit earlier posts, I find that many images were not displaying. Not sure if steemit does archiving and remove older images, but that is a real and serious problem. Storage needed for image for exceeds the storage needed for steem blockchain. This is why many dapps are shifting to IPFS. IPFS will be the ones facing serious serious size problem. For us, at steem, don't worry, we are safe.</p>\n<p><em>image source: https://steemdb.com/</em></p>\n<figure><img src=\"https://cdn.steemitimages.com/DQmP5KiULv8XW6KgVPya6k33tZ2dcBjqRBawDqYhK2AE1pU/image.png\"/></figure>\n<p><br></p>","appDepth":2,"appParentPermlink":"pks7spzvx","appParentAuthor":"elbiasto","musingAppId":"aU2p3C3a8N","musingAppVersion":"1.1","musingPostType":"answer"}" |
created | 2018-09-06 17:25:57 |
last_update | 2018-09-06 17:25:57 |
depth | 2 |
children | 0 |
last_payout | 2018-09-13 17:25:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 2,218 |
author_reputation | 98,808,821,433,006 |
root_title | "Musing Posts" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 70,525,607 |
net_rshares | 1,878,117,115 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
pixelfan | 0 | 1,878,117,115 | 0.55% |