Walrus Mainnet

Morse runs on Walrus Mainnet. This page covers what changes when you move from testnet: the deployment, the risks, setup, uploads and encrypted content.

Status

Morse has been live on Walrus Mainnet since 2026-09-09. The CLI and SDK ship with the mainnet addresses built in, so there are no addresses to supply. These are the current releases:

An app that uses morse-uploader 0.4.2 stays on morse-sdk 0.10.1, because the uploader does not accept morse-sdk 0.11. See React Uploader → Install.

The default storage-node read path for morse entry read and morse entry decrypt works from morse-cli 0.11.0 and morse-sdk 0.9.0. Upgrade if you are on an earlier release.

Public publications, collections, entries and files work on both networks. Encrypted content needs your own Seal credentials on mainnet. See Encrypted content.

The deployment

Mainnet runs version 1 of the Morse Move package. It has never been upgraded, so published-at and original-id are the same address.

You only need these ids for raw contract calls. Use published-at as the target of Move calls, and original-id for type-filtered queries. The source of truth is Published.toml. To build those calls yourself, see Quick Start: Smart Contracts.

Setting up

Fund the address you will use with SUI for gas and WAL for Walrus storage. There is no faucet on mainnet, so you have to acquire both.

Nothing carries over from testnet. Mainnet has its own package and its own PublicationRegistry, so you create your publications and collections again.

CLI

Keep mainnet in its own profile, so your testnet profile stays as it is. Create the profile, make it the default, import the key that pays on mainnet, and check the result:

morse config add mainnet --network mainnet
morse config use mainnet
morse account import
morse status

account import prompts for the key and a password. If the key is already in your keystore, run morse account use <address> instead.

Nothing selects mainnet for you. With no --network, MORSE_NETWORK or profile setting, the CLI targets testnet. Every command that spends gas prints the network it used, and --json output has a network field. To go back to the testnet profile from the quick start, run morse config use testnet.

SDK

morseConfig({ network: "mainnet" }) returns the full mainnet config, with the contract addresses built in. Use the same network for the gRPC client and the Walrus adapters. Start from the server setup and change every network literal to "mainnet":

const config = morseConfig({ network: "mainnet" });
const client = new SuiGrpcClient({
  network: "mainnet",
  baseUrl: config.rpcUrl,
});
const walrus = DefaultWalrusWriteAdapter.fromConfig(
  { network: "mainnet", suiClient: client },
  keypair,
);

Uploads and the upload relay

A direct upload sends slivers to every storage node in the Walrus committee at once: about 95 on mainnet. Many networks can't sustain that burst. The upload then fails with NotEnoughBlobConfirmationsError or "Unable to connect", even when the nodes are healthy. If uploads fail while reads work, this is almost certainly why. It is not a fault in your config.

Retry through the upload relay, which takes one connection instead of about 95. --upload-relay is a global option, so it goes before the subcommand:

morse --upload-relay auto entry add hello --file post.json

auto picks Mysten's canonical relay for the network. To use the relay for every upload, save it on the profile. Running config add on an existing profile updates it and keeps its other settings:

morse config add mainnet --network mainnet --upload-relay auto

Three things to know before you use it:

• It charges a small tip per upload, on top of WAL and gas.
• The tip is capped. --max-tip sets the cap in MIST and defaults to 10000000 (0.01 SUI). Over the cap, the upload is refused before anything is spent.
• The relay sees your bytes. Encrypt first if that matters.

The relay is opt-in. The direct path is free and trustless, and most networks handle it fine. In the SDK, pass uploadRelay with a host and a sendTip.max cap to DefaultWalrusWriteAdapter.fromConfig. For browser apps, see React Uploader → Walrus upload relay. The CLI README covers the relay in When uploads fail: the upload relay.

Storage is paid per epoch. A testnet epoch is roughly a day, and mainnet epochs are much longer, so the same --epochs value buys a very different duration.

Encrypted content

Encrypted commands need Seal key servers. Testnet pins an open set, so they work there with no setup. Walrus Mainnet pins none, because every Seal operator there is commercial. You bring your own credential. Without one, the CLI's encrypted commands exit with code 2 and an explanation.

In the CLI, set one of these environment variables:

They are environment variables, not flags, so the credential stays out of ps and shell history. Before it encrypts anything, the CLI checks the credential and refuses if the operator answers 401 or 403. Without that check, a bad credential would let encryption succeed and decryption fail, and you would pay to store content nobody can read.

In the SDK, DefaultSealAdapter.fromMorseConfig throws ConfigurationError on mainnet until you supply key servers. MAINNET_SEAL_COMMITTEE is Mysten's committee in the right shape. Add the apiKeyName and apiKey that Mysten issues you, and pass the result to morseConfig as sealKeyServers. For browser apps, see React Uploader → Encrypted files and Seal on Walrus Mainnet.

Encryption has not been verified end to end on Walrus Mainnet, because that needs a commercial credential. The CLI README covers the setup in Seal on mainnet.

Next steps