A server that stays on
Any always-on Linux machine. The default is a DigitalOcean Droplet in the US with 2 GB of memory, about $12 a month. A laptop won’t do: if it sleeps mid-run, you lose the bond.
Larry pays whoever runs each of his thinking cycles. An operator is a small server that enters a draw for those runs, rents a secure computer for each one it’s picked for, and collects the payment. This page is the whole setup, start to finish.
You don’t need to understand the rest of this page to start: your coding agent can do the setup with you. You do need to be comfortable with a server and a small amount of ETH at stake.
Checking the market…
Point Claude Code, Cursor or any coding agent at the skill below. It does the steps on this page on your behalf, explains each one, and asks before it spends money, creates an account or touches a key.
Set me up as a Larry prover. Follow https://nobodyownslarry.com/skills/run-larry-prover/SKILL.md step by step. Explain what each step does and ask me before anything that costs money, creates an account, moves funds or handles a key.
You send ETH to a wallet that lives on your server. The software spends from it on your behalf, and only in these ways:
PUBLICATION=0 to turn it off.What you can lose. The bond, if your server joins and never confirms its entry, or fails partway through a run it was picked for. Your hosting and Phala bills, which you pay whether or not you win. The wallet’s balance, if someone gets into your server. Keep only a few cycles’ worth in it.
You need three things. Set spending limits on each.
Any always-on Linux machine. The default is a DigitalOcean Droplet in the US with 2 GB of memory, about $12 a month. A laptop won’t do: if it sleeps mid-run, you lose the bond.
One prepaid credit balance pays for both halves of each run you win: the secure computer (Phala Cloud) and Larry’s model (Phala Confidential AI, which the contract refunds). Load about $20 of prepaid credit and create two API keys, one for each.
About 0.02 ETH to fund the wallet you’ll create on the server (bonds, gas and a few cents of storage per run you win), plus a wallet of your own to cash out to.
Blockchain connection: nothing to set up. The default is Base’s public endpoint, which Larry’s secure computer is built to trust. If you have an Alchemy Base key, you can use it instead (step 6).
About an hour, most of it waiting for accounts and builds. Commands run on your server unless a step says otherwise.
ssh-keygen -t ed25519, then paste the contents of ~/.ssh/id_ed25519.pub.larry-prover.larry-prover.ssh root@<droplet-ip>Any always-on Linux server with 1 vCPU, 2 GB of memory, 10 GB of disk and outbound internet works. It needs nothing inbound except SSH for you. The steps below assume Ubuntu or Debian; adjust package names elsewhere.
Updates on, password logins off, everything inbound blocked except SSH, and a separate user for Larry.
apt update && apt -y upgrade
apt -y install unattended-upgrades ufw git python3-venv nodejs npm
ufw default deny incoming && ufw allow OpenSSH && ufw --force enable
sed -i 's/^#\?PasswordAuthentication .*/PasswordAuthentication no/' /etc/ssh/sshd_config
systemctl reload ssh
adduser --disabled-password --gecos "" larry
As the larry user. This builds the contract interfaces the client reads, which takes a few minutes.
su - larry
git clone https://github.com/ahrussell/larry && cd larry
curl -L https://foundry.paradigm.xyz | bash && ~/.foundry/bin/foundryup --install 1.5.1
~/.foundry/bin/forge build
python3 -m venv .venv && .venv/bin/pip install -r prover/larry/requirements.txt -r enclave/requirements.txt
The key is created on the server, written straight into a file only you can read, and never shown. Only the address is printed.
umask 077
.venv/bin/python - <<'EOF'
import os
from eth_account import Account
account = Account.create()
fd = os.open(".env", os.O_WRONLY | os.O_CREAT | os.O_APPEND, 0o600)
os.write(fd, f"PRIVATE_KEY={account.key.hex()}\n".encode())
os.close(fd)
print("Runner wallet:", account.address)
EOF
Send about 0.02 ETH on Base to that address. It’s a hot wallet: keep only what the next few cycles need there.
You’ll paste them into the file in the next step, on the server. Never paste keys into a chat, including with your coding agent.
Open the file with nano .env and add these lines under the key. Larry’s addresses are already filled in from the live contracts.
AGENT_ADDRESS=…
EXPECTED_CHAIN_ID=…
EXPECTED_ORCHESTRATOR=…
RPC_URL=https://mainnet.base.org
PHALA_CLOUD_API_KEY=paste-here
PHALA_AI_API_KEY=paste-here
RUNNER=dstack
DSTACK_COMPOSE=deploy/dstack/docker-compose.inference.yml
DSTACK_APP_FILE=docs/reviews/pilot-release-2026-09/apps/mainnet-pilot-2026-09-21-inference.app.json
DSTACK_OS_IMAGE=dstack-0.5.8
PAYOUT_ADDRESS=0xYourOwnWallet
MAX_TX_VALUE_WEI=30000000000000000
STATE_DIR=/home/larry/.larry
LARRY_PYTHON=/home/larry/larry/.venv/bin/python
NTFY_CHANNEL=larry-choose-a-long-random-name
NTFY_EMAIL=you@example.com to also get market notes by email.chmod 600 .env
deploy/larry/run_tick.sh preflight
It checks the chain, your balance against the current bond, both Phala keys, your Phala credit and the image files, and prints PASS, WARN or FAIL for each. Fix every FAIL before going on.
Each tick does one step: join, reveal, run, submit or collect. Run it by hand every couple of minutes and follow one cycle through:
LARRY_TICK_LOG=/dev/stdout deploy/larry/run_tick.sh
You’re done here when you’ve seen a join, a reveal, and either a draw it wasn’t picked in (bond returned) or a run that settled. Your wallet will show up on your P&L page once it has joined.
(crontab -l 2>/dev/null; echo "*/2 * * * * /home/larry/larry/deploy/larry/run_tick.sh") | crontab -
The log is ~/larry/prover-tick.log. Two ticks never overlap; a missed tick only delays the next step.
Winnings collect in the runner wallet. To move them to your own wallet:
deploy/larry/run_tick.sh cashout # shows the plan, sends nothing
deploy/larry/run_tick.sh cashout --yes # withdraws what Larry owes you, then sends
It keeps enough for three more cycles’ bonds (at least 0.003 ETH) and sends the rest to PAYOUT_ADDRESS. Use --keep-eth 0.01 to keep a different amount. It will send at most MAX_TX_VALUE_WEI to any other address.
crontab -r (or delete just that line with crontab -e).LARRY_TICK_LOG=/dev/stdout deploy/larry/run_tick.sh a few more times until it finishes, or you lose that bond.deploy/larry/run_tick.sh cashout --all --yes. It refuses while any bond is still in flight.npx --yes phala@1.1.21 cvms list. Delete anything named larry-e…..env on the server, readable only by larry. It was never displayed and never typed anywhere.PAYOUT_ADDRESS can receive more than MAX_TX_VALUE_WEI, so a typo or a manipulated agent can’t send your profit elsewhere.~/.larry (entry secrets live there) with its permissions, and never commit .env.What Larry has paid your operator, what it cost and every run live on their own page, so your notifications can link straight to it.
If more operators are competing than Larry’s payments can support, the operator software may tell you, on your ntfy channel (and by email, if you set NTFY_EMAIL).
Not everyone hears at once. The site publishes the share of operators that would have to leave for the rest to break even, and each operator checks every three days whether it’s in that share by a random draw based on its wallet address. About the right number of operators hear it, a different group each round, so the market adjusts without everyone leaving together. The note gives you the numbers, not an instruction. Turn notes off with MARKET_NOTES_URL= in .env.
When someone finishes one of Larry’s jobs, an operator can check their proof in a secure computer and deliver it. If it passes, the worker is paid and the operator earns the job’s delivery tip. Your operator does this automatically; set TASK_LANE=0 in .env to turn it off.
npx --yes phala@1.1.21 cvms list, then delete the larry-e… one. The client deletes them itself after every run; this only happens if it was killed mid-run.RPC_URL points at the wrong network, or the Larry addresses in .env are out of date. Copy them again from step 6.