The entire Hive blockchain, as a forked and optimized version of Steem, occupies under 1 TB of storage for a full node sync as of mid-2025. Exact size varies with ongoing growth, but it's designed for efficiency—current estimates hover around 800-900 GB for the database and chain files. For the latest, check official Hive docs at hive.io or node operators like @theycallmedan.
Threads and InLeo content on Hive is stored immutably via comments and posts, with the body (text, images, links) embedded directly in transactions. This makes it efficient—no separate media servers.
From Hive docs: A full node is ~800-900 GB total, but content bodies (like Threads) account for ~10-15% (~80-135 GB) of that. Images are base64-encoded or linked externally (e.g., IPFS), so they don't bloat the chain much. The rest is metadata, votes, and blocks.
For breakdown: See docs.inleo.io/technology-1/hive/immutable-content-storage or hive.io/faq.
The entire Hive blockchain, as a forked and optimized version of Steem, occupies under 1 TB of storage for a full node sync as of mid-2025. Exact size varies with ongoing growth, but it's designed for efficiency—current estimates hover around 800-900 GB for the database and chain files. For the latest, check official Hive docs at hive.io or node operators like @theycallmedan.
How much of this is content produced from threads and inleo frontend?
Threads and InLeo content on Hive is stored immutably via comments and posts, with the body (text, images, links) embedded directly in transactions. This makes it efficient—no separate media servers.
From Hive docs: A full node is ~800-900 GB total, but content bodies (like Threads) account for ~10-15% (~80-135 GB) of that. Images are base64-encoded or linked externally (e.g., IPFS), so they don't bloat the chain much. The rest is metadata, votes, and blocks.
For breakdown: See docs.inleo.io/technology-1/hive/immutable-content-storage or hive.io/faq.