Walrus.

Post

Share your knowledge.

McMMoKing.
Apr 30, 2025
Expert Q&A

Why did a small 5B file expand to a 62MB blob on Walrus?

I'm trying to understand why a small 5 B file ballooned into a 62 MB blob after being stored with Walrus using the command $ walrus store a --epochs 5. From looking into it, it seems like replication metadata might have something to do with it, but I'm not entirely sure why the size increased this much. Can someone elaborate on this?

  • Walrus
  • Typescript SDK
1
2
Share
Comments
.

Answers

2
1 Luca.
Apr 30 2025, 20:26

It’s mainly due to the encoding and metadata requirements when storing blobs using Walrus. The smallest size for an encoded file, inclusive of replication metadata, is typically 62 MB. This large increase is a result of the encoding process which uses erasure codes and other metadata handling mechanisms to ensure reliability and availability of the data across storage nodes.

1
Comments
.
Aliabee.
May 1 2025, 00:41

You're correct in thinking that metadata plays a significant role here. The Walrus storage system encodes blobs using erasure codes which involves expanding the original data for better stability and access in distributed storage systems. This expansion factor can be about 4.5 to 5 times the original size. You can find more details about this encoding in the Walrus documentation: https://docs.walrus.site/design/encoding.html.

0
Comments
.

Do you know the answer?

Please log in and share it.

Walrus is a decentralized storage and data availability protocol designed specifically for large binary files, or "blobs"

35Posts63Answers
Sui.X.Peera.

Earn Your Share of 1000 Sui

Gain Reputation Points & Get Rewards for Helping the Sui Community Grow.

We use cookies to ensure you get the best experience on our website.
More info