walrus-sdk-js

Create a Sui client such as SuiGrpcClient, then call .$extend(walrus()) to add Walrus functionality. Install @mysten/walrus with @mysten/sui, and do not pass a network option to walrus() since it is inferred from the Sui client.

Use client.walrus.writeFilesFlow to split the upload into explicit user-triggered steps, since browsers block wallet popups not tied to user gestures. Call flow.encode(), then flow.register(), sign the transaction, and continue with upload and certify steps.

Yes, but the SDK includes WASM paths, so verify the current docs for loading the WASM module in Vite. The packages are ESM-only, requiring "type": "module" in package.json and a compatible TypeScript moduleResolution like NodeNext or Bundler.

Pass an onStep callback to writeBlob or writeFiles and persist each step. On restart, pass the saved step as the resume option; the flow skips completed steps, validates the blob ID, and uploads only missing slivers.

Direct storage-node writes require roughly 2200 requests per blob, so an upload relay reduces client-side write complexity. Configure it via walrus({ uploadRelay: { host, sendTip } }) and validate the relay host, tip policy, and trust model before production use.

Replace new WalrusClient({ suiRpcUrl, network }) with a Sui client plus $extend(walrus()), and remove the network option from walrus(). WalrusClient.experimental_asClientExtension() was removed, and method calls move from walrusClient.* to client.walrus.*.