Check the status of the blob on Walrus before performing operations.

MystenLabs / walrus-sites

Walrus Sites: Decentralized Websites using Sui and Walrus.

https://docs.walrus.site/walrus-sites/intro.html

Apache License 2.0

11 stars 14 forks source link

Check the status of the blob on Walrus before performing operations. #35

Open giac-mysten opened 1 month ago

giac-mysten commented 1 month ago

The site builder currently only checks if the blob ID on chain matches the blob ID on disk.

However, if devnet was wiped, the two can be the same but the blob may be missing.

This is currently mitigated by the --force flag.

Tzal3x commented 1 week ago

if devnet was wiped, the two can be the same but the blob may be missing.

If devnet was wiped, how would one fetch the on-chain blobid in the first place?

giac-mysten commented 1 week ago

If I understand your question, the point here it that "devnet" is the Walrus devnet. The "on-chain blob ID" is on Sui testnet. So the Site and relative Resource objects on chain may still contain a blob ID, but the storage nodes do not have it stored.

mlegner commented 1 week ago

So the current behavior is the following:

Without --force, do not attempt to store files on Walrus if the corresponding Walrus Sites Resource already exists.
With --force, store all files on Walrus with the --force option (provided to the walrus binary).

What we would want to support the case that Walrus is redeployed is to attempt to store all files on Walrus but without using the --force option. This checks the blob status for all files and only stores those that are not yet certified.