Find out nownot at deploy

Four read-only checks against a live wallet: gas, storage funds, the Warm Storage payment rail, and whether any approved provider is actually answering. A funded wallet is not a ready wallet.

Nothing is signed

Every call is a balance read, an allowance read, a registry read, or an HTTP ping. Ballast never creates a deal, approves an allowance, or moves funds — so it runs against any public address, with no private key.

The rail is the trap

Warm Storage needs an approved payment rail before it can create a data set. Balances tell you nothing about it, which is why the failure usually surfaces after the app is built.

Also a CLI

The same checks run in a terminal and exit non-zero when a wallet is not ready, so it works as a CI gate. ballast check --address 0x…