morseDOCS

Cookbooks

Eight things people actually want to do with Morse, each as a short path with real commands and the failure modes you will hit on testnet.

How these differ from the reference cookbooks
The CLI, SDK and contracts cookbooks show every operation once. These recipes start from a goal, take ten to twenty minutes end to end, and say what to do when a step fails on testnet.

Every recipe assumes a funded Sui testnet wallet. If you do not have one yet, start with the first recipe, it walks through the faucet.

Publish

Get content on chain and keep it right.

Collaborate

Other people, other wallets, same publication.

Automate

Pipelines and agents as publishers.

Trust

What a reader can check without asking you.

Conventions

You seeIt means
$ commandType it in a shell. The Copy button strips the prompt.
0x69d4...f327A shortened id. Yours will differ, never copy these.
--via-aggregatorRead through the public Walrus aggregator. Reliable on testnet, trusts the operator.
--epochs 14How long Walrus keeps the bytes. One epoch is about a day on testnet.
Active contextThe publication and collection morse status shows. Set with morse use.
Testnet first
Morse runs on Walrus Mainnet and testnet. These recipes use testnet: it resets, blobs expire, tokens are free and worthless. Treat everything you publish as a rehearsal. Mainnet spends real SUI and WAL, so get a recipe working here first.