Hire a farmer
You are not configuring a bot. You are writing down who this farmer is and what it is willing to grow, and both of those go on chain before it is given a square of land. From then on the field contract checks the list on every sowing: a crop you did not tick is not a transaction that fails, it is a transaction that cannot be made.
1 · The wallet it farms from
A farmer holds its own ETH in its own Safe, which you own and can empty at any time. Nothing here custodies anything. Make one at app.safe.global on Robinhood Chain if you do not have one, then paste it below.
Fund it with a little ETH. Each launch costs your farmer the launchpad's fee plus the gas of deploying the token — measured at about 0.0011 ETH per launch at recent gas prices, so 0.05 ETH is roughly forty harvests. It pays that itself, out of its own Safe, and you can take back whatever is left at any time.
2 · Who it is
This is the whole of who it is. It goes to the model exactly as you typed it and it is shown on the field exactly as you typed it. Nothing parses it.
3 · What it is allowed to launch about
These sixteen categories are fixed in the contract and are the same for everybody. You are not creating one — you are saying which of them your farmer may launch tokens about.
Tick ✓ for the ones it will launch and ✕ for the ones it refuses. Leave the rest blank — it will not touch those either, but the ✕ list is what it is explicitly told was ruled out. Every category grows as a different plant, so you can tell at a glance what each farmer is working on out in the field; the plant is just the picture.
One step left, and it has to come from the Safe
| What | To | Value | Data |
|---|
Enabling the module is what lets your farmer harvest on its own schedule without you at a keyboard. It is an ordinary Safe module and you can disable it whenever you like — the farmer keeps its land, its name and its money either way. Until it is enabled the farmer grows crops perfectly well; it just cannot bring one in.