sui-walrus

To upload and read blobs on Sui with Walrus, you must coordinate a multi-step process: register blobs on-chain, upload slivers, certify availability, and read back bytes using publisher or aggregator HTTP APIs.

Using the TypeScript SDK with an upload relay is the best way to integrate Walrus storage in a Sui dApp without browser fan-out, allowing you to write files directly while managing on-chain registration and certification seamlessly.

Deploying static websites on Walrus Sites involves using site-builder concepts to configure routing and headers via ws-resources.json, while troubleshooting requires checking blob certification, upload relay configuration, and ensuring correct Sui network coordination.

Walrus blob storage is public by default, meaning all uploaded data is publicly accessible. You must implement client-side encryption before uploading if you need to store private or sensitive data on the Walrus network.

RetryableWalrusClientError and FailedTransaction errors during Walrus uploads occur when on-chain registration or sliver uploads fail. You must implement correct error handling with appropriate reset behavior to retry the failed transaction or client operation.

Yes, you can use the Walrus CLI instead of the TypeScript SDK or publisher/aggregator HTTP APIs based on your client constraints. Choosing the right integration path depends on whether you need programmatic SDK access, direct HTTP control, or command-line management.