Interface VanaStorageConfig

Base URL of the vana-storage Worker. Defaults to https://storage.vana.org.

This selects the storage endpoint and is independent of network / chainId.

Named Vana protocol network that scopes blob paths. Prefer this for known Vana networks because it keeps callers on the SDK's typed network registry.

When set, uploads use chain-scoped routes derived from the network's chain ID (/v1/chains/1480/... for mainnet, /v1/chains/14800/... for Moksha).

Explicit numeric chain ID for custom or future networks not yet represented by ProtocolNetwork.

When set, uploads use chain-scoped routes (/v1/chains/{chainId}/blobs/...) so data for different chains under the same owner/scope/timestamp never collides. Reads and deletes must use the same chain-scoped namespace; legacy blobs should be migrated or re-collected rather than read through an ambiguous fallback. When omitted, the provider preserves the legacy /v1/blobs/... routes and behavior.

chainId and network are mutually consistent ways to select the namespace. If both are provided, they must resolve to the same chain ID. endpoint remains orthogonal: it picks the storage host, not the protocol namespace.

Wallet signer used to authenticate writes and reads.

Owner namespace under which blobs are stored. Defaults to the signer address.

Optional fetch implementation. Defaults to the global fetch. Useful for tests and for environments that need a custom HTTP client.