What ship does

You send bytecode. We deploy on Monad testnet, open the session, and print an app address plus a node URL.

The commands live on First hour. This page is only what happens after you run ship.

What we do

ship POSTs bytecode to https://control.interludelayer.xyz. Interlude deploys on Monad testnet, calls delegateAll(), starts a node, and prints two values: an app address and a node URL. No faucet, no wallet key, no invite. A rate limit is what stops a loop from draining the faucet wallet.

Pass a region (us, ny, eu, asia, sa, tokyo, mumbai, africa) to sit the node next to the people who tap. Omit it and control picks from the request. One writer, so one region. The first node can 502 for a few minutes: that is the image building, not a broken deploy.

What you keep

The source, the frontend and the users. The on-chain owner of a shipped app is Interlude. v1 is permissioned: you trust us to run the validator, not to keep the state. A slash unwinds a lie.

The one URL that is never yours

https://rpc.interludelayer.xyz serves the Paris demo floor. status() on that node names the demo address, not yours, and does not throw. Point the SDK at the URL ship printed.

Laptop

interlude dev stands up anvil, a hub, a validator and a node on loopback. The published CLI does not ship the Rust binary. Set INTERLUDE_NODE_BIN or run from this checkout. The public path is ship.

Hard cases: a constant mapping key, an inherited write with no guard, a contract you cannot redeploy. Those are on What will not work.