Before you begin, make sure you have:
- 10 USDC in your wallet (on the correct network)
- An RPC URL, for example:
https://eth-sepolia.g.alchemy.com/v2/A1bC23dEfG456hiJkLmnOpQRsTuvWxYz - Your wallet’s private key, like:
5f6a2b8790ac134d47fe28bcad6150eb7f426b8d60a743dc5b0940fbea29c6d1 - A NETWORK value that matches the network you're using (see below)
| Network | NETWORK Value |
|---|---|
| Base Mainnet | base |
| Base Sepolia | base-sepolia |
| Ethereum Sepolia | eth-sepolia |
Warning
Make sure your USDC, wallet, and RPC endpoint are all on the same network
If you don't know what any of this means, please read the Account Setup Guide first.
-
Go to QuickPod Templates
-
In the Docker Options edit the following
Warning
Replace the placeholder values below with your actual values from the prerequisites step:
| Placeholder | Replace With |
|---|---|
YOUR_PRIVATE_KEY_GOES_HERE |
Your actual wallet private key |
YOUR_RPC_URL_HERE |
Your actual RPC URL |
eth-sepolia |
Your chosen network value (see supported networks table above) |
Then hit Save.
- Launch a machine using your new template.
Note
You can skip this step if you’ve already staked from this wallet.
Once your pod is running:
You should see a message confirming the stake was successful.

You can verify your stake by visiting the appropriate explorer:
| Network Type | Explorer URL |
|---|---|
| Testnet | https://explorer.testnet.beboundless.xyz/balances |
| Mainnet | https://explorer.beboundless.xyz/balances |
Note
Skip this if services are already running from a previous stake.
After staking, restart the services:
supervisorctl restart allThis ensures the prover loads with the updated state.
Open your browser and go to:
You should see the Boundless broker UI showing your prover’s status.
-
Where is the
docker-compose.ymlfile? This setup does not use Docker ordocker-compose. Instead, services are managed using Supervisor. You can configure which services run by editing:/app/supervisord.confAfter making changes, restart all services with:
supervisorctl restart all
-
How do I restart a specific service (like the broker)? Use this command format:
supervisorctl restart <service-name>
For example, to restart the broker service:
supervisorctl restart broker
-
Where can I edit the
broker.tomlconfiguration? The file is located at:/app/broker.tomlYou can edit it using a text editor:
-
With nano (beginner-friendly):
nano /app/broker.toml
-
Or with vi (more advanced):
vi /app/broker.toml
-
-
How can I check logs? Logs for all services are in:
/app/logsYou can view them using:
-
To view the full log:
cat /app/logs/<filename>.log
-
To scroll through:
less /app/logs/<filename>.log
-
To follow logs in real time:
tail -f /app/logs/<filename>.log
-
-
How do I increase the number of
exec_agents? You can add the following option when starting the container:-e AGENTS=<number>
By default, it runs with 2 agents. For example, to run 4 agents:
-e AGENTS=4 ...
-
How do I update CPU or memory limits? Currently, there is no built-in way to limit resource usage. All processes will share the available CPU and memory of the container.
-
What settings should I use for my GPU? Update your docker options with the proper segement size based on the table below:
-e SEGMENT_SIZE=16
| GPU Memory | Recommended Segment Size | Memory Used | Cycles | Performance | Common GPU Models |
|---|---|---|---|---|---|
| 1-2GB | 16 | ~512MB | 65K | Basic | GTX 1050, RTX 3050 (4GB) |
| 2-4GB | 17 | ~1GB | 131K | Good | GTX 1060, RTX 3060 Ti |
| 4-6GB | 18 | ~2GB | 262K | Better | GTX 1070, RTX 3060 |
| 6-8GB | 19 | ~4GB | 524K | Great | GTX 1080, RTX 3070 |
| 8-12GB | 20 | ~6GB | 1M | Excellent | RTX 3080, RTX 4070 |
| 12GB+ | 21 (default) | ~7GB | 2M | Maximum | RTX 3080 Ti, RTX 3090, RTX 4080, RTX 4090 |
| 16GB+ | 22 | ~12GB | 4M | Overkill | RTX 3090, 4090, A100 |
| 24GB+ | 23 | ~20GB | 8M | Enterprise | RTX 6000, A100 |






