Walrus

Start with the Testnet guide: install the CLI, configure the network and Sui account, obtain test tokens, then store and read a file. Keep both the blob ID for reading and the Sui object ID for storage updates. For production, choose the SDK, an upload relay, or a private authenticated Mainnet publisher.

Direct Mainnet storage uses WAL for storage payments and SUI for transaction fees. Testnet uses valueless test tokens and may wipe data. Console is currently available without charge, with up to 5 GB per space, five folders, and 100 MiB per upload; its free access and limits can change. Console has no guaranteed permanent free tier.

Anyone with a blob ID can read the underlying blob bytes. Encrypt sensitive content before storing it. Console encrypts uploaded file content on your device with Seal, but limited metadata such as file names, types, and sizes remains unencrypted.

Storage lasts for the epochs purchased. Mainnet epochs are two weeks; Testnet epochs are one day. Extend storage before it expires. Console currently renews active accounts on a reasonable-efforts basis, which can be changed or discontinued. Expired data can be permanently lost; keep independent copies.

Verification establishes that retrieved bytes match the stored content and that storage is available. It does not establish that a dataset, claim, or AI output is factually correct.

No. Deleting a Console item removes it from your account, but underlying protocol data may remain until its storage term ends. The protocol cannot guarantee removal of caches, old storage-node pieces, or copies made by other users.

Walrus supplies storage. Walrus Memory is a separate layer built on it for persistent agent context. Console can display connected memory metadata, while memory management remains in the Walrus Memory dashboard. Neither storage verification nor the connection itself guarantees an agent’s output quality.