Guides

Walrus mainnet

TuskPoint defaults to Walrus mainnet. Reads are public and free; writes cost gas and need a publisher. Here is exactly what to set.

Reads — public and free

Any mainnet aggregator serves a content-addressed blob to anyone. The default aggregator is below; the engine falls back to community aggregators if it is unreachable.

env

WALRUS_AGGREGATOR_URL=https://aggregator.walrus-mainnet.walrus.space

Writes — need a publisher

Storing a blob on mainnet costs SUI (gas) plus WAL (storage), so there is no public, unauthenticated publisher. You have three options:

1. Community publisher — quickest to try; may rate-limit or require an allowlist. This is the default in .env.example:

env

WALRUS_PUBLISHER_URL=https://walrus-mainnet-publisher-1.staketab.org:443

2. Run your own publisher — recommended for production. Run the Walrus publisher with a funded Sui wallet and point WALRUS_PUBLISHER_URL at it.

terminal

walrus publisher --sui-wallet <path-to-wallet> ...

3. Use the upload relay — the mainnet relay at https://upload-relay.mainnet.walrus.space with a funded key.

Everything is env-overridable

WALRUS_PUBLISHER_URL and WALRUS_AGGREGATOR_URL always take precedence over the built-in defaults. Reads work without any of the above — only writes (checkpoint_save, checkpoint_fork) need a publisher.

Falling back to testnet

To experiment without spending mainnet tokens, point both URLs at the public testnet endpoints:

env (testnet)

WALRUS_AGGREGATOR_URL=https://aggregator.walrus-testnet.walrus.space
WALRUS_PUBLISHER_URL=https://publisher.walrus-testnet.walrus.space