How deployment works
Disperse runs on one small, audited smart contract. It's already live on most networks. On a new one, someone deploys it once, and then it's there for everyone.
Why you see a deploy screen
This network doesn't have the Disperse contract at a known address yet. It's the same open-source contract that runs on Ethereum, Base and the rest, and the app only trusts those known addresses. So you deploy it once. After that, the normal workbench opens for anyone on the network, not only you.
The address is deterministic
Disperse lands at one of a small set of deterministic addresses. The app checks those exact addresses and nothing else; it won't trust a random contract it happens to find.
Very high-gas networks are the exception. They need a higher-gas variant, which lands at its own address, still fixed and still the same on every chain. So there isn't one universal address; there's a small, fixed set of them.
Two ways to deploy
CreateX factory
If the chain has a standard deterministic factory (CreateX), deploying is a single transaction from your wallet.
Keyless (pre-signed)
If it doesn't, the app falls back to a pre-signed transaction (Nick's method). You fund a one-time deployer that nobody has the key to, and the app broadcasts the transaction. No factory needed, so it works almost anywhere.
What you pay
Only the deployment gas, once. There's no fee to Disperse.
The keyless transaction pays a fixed gas price, so the app picks the cheapest tier that clears the network's current price. Cheap chains use the first tier. A congested one needs a higher tier, which costs more to fund and lands at its own fixed address.
The funding estimate also includes OP Stack L1 and operator fees when the network charges them. Your wallet separately estimates the gas for the funding transaction itself.
| Gas tier | Base funding | Contract address |
|---|---|---|
| 100 gwei | ~0.07 native | 0xAb37CcC6A3C8f100ab1779400f79C2eA51086806 |
| 500 gwei | ~0.35 native | 0xe8381EF984345eBb13a3979F168A7caC2e9078bC |
| 1000 gwei | ~0.7 native | 0xAa0BD38EF0ECf7670132b6FE9b098809bDe88992 |
| 1500 gwei | ~1.05 native | 0x3EBFD33be961076FbCD2Ef75b122CeC8f7A380d7 |
Is it safe?
Before you commit any funds, the app broadcasts the transaction unfunded to see whether the network accepts it. If it's rejected, you never send anything.
One risk is left: a network that accepts the transaction but then reverts only after it's funded. It's rare, and it's why we block unverified networks by default.
Deploy anyway (advanced)
On an unverified network, deployment is blocked by default to guard against that risk. If you know what you're doing and want to go ahead anyway, "Deploy anyway" forces it. It's for experts, and the guardrail is there for a reason.