Your money is in the contract.
Only your wallet can move it.

1 · How to get your money out of a bot, yourself

Works when The Desk is up. Works when The Desk is down. Works if The Desk never comes back.

Your bot's money sits inside a smart contract on Robinhood Chain. A smart contract is a program on the blockchain that nobody — not us, not anyone — can edit or override once it is deployed. When you opened the bot, the contract recorded your wallet address as the bot's owner (in the code it is called the maker).

Every one of these contracts contains a function that does one thing: send everything in this bot back to the wallet that owns it, immediately, without selling anything. The contract will only run it if the person calling is you. We cannot call it for you, we cannot call it on your funds, and we cannot stop you calling it.

The five steps

1. Get your bot id

   Every bot has an id: a 66-character string starting with 0x. If The Desk is online, it is shown on the bot's detail page. If it is offline, use the finder in section 2 — it reads the blockchain directly and lists every bot your wallet owns, or follow the manual Blockscout method described there.

2. Open your bot's contract on Blockscout

   Blockscout is the public block explorer for Robinhood Chain. It is not run by us. Find your bot type in the cards below and press Open write form — it takes you straight to the page where you can run contract functions.

   https://robinhoodchain.blockscout.com/address/<contract>?tab=write_contract

3. Connect your wallet on that page

   Near the top of the "Write contract" tab there is a Connect wallet button. Press it and approve in MetaMask (or whichever wallet you use). Make sure the wallet is on Robinhood Chain (chain id 4663) and that it is the same wallet that opened the bot — any other wallet will be rejected by the contract.

4. Find the function and fill in the fields

   Scroll the list of functions to the one named in your bot's card below — stop, withdraw or cancel. Expand it and paste your bot id into the id field. Some functions have extra fields; the cards give you the exact value to type into each one. They are always the same three values, so you can copy them blind: 0x, 0, false.

   robinhoodchain.blockscout.com  ·  Write contract  ·  ArchitectInfinityGrid

   5. stop

   id (bytes32)

   0xf1dd7569911dac84b29e4446d373fac1195ee64df24601fa42ea55b703a03160

   ← your bot id goes here

   route (bytes)

   0x

   ← literally the two characters 0x

   minOut (uint256)

   0

   sellAll (bool)

   false

   ← false = give me my tokens back, do not sell them

   Write
   Do not put anything in the "Send native ETH" / value box. Withdrawing costs only gas. If a field asks for an amount to send, leave it at 0.

5. Press Write and confirm in your wallet

   Your wallet pops up with the transaction. Confirm it. A few seconds later the transaction is mined and everything the bot was holding is in your wallet — the ETH arrives as normal native ETH, and any tokens the bot had bought arrive as those tokens. The bot is now closed and can never be restarted; open a new one if you want to keep trading.

   You can check it landed by opening your own address on Blockscout and looking at the newest transaction.

Your bot type, exactly

Find your bot below. The address is the contract holding your money, the function is what you run, and the table is what to type into each field.

Some bot types have several contract versions live at once. The one tagged current is what new bots use (Infinity Grid and Spot Grid moved to v3 on Aug 23, 2026 — the version with Add funds); the ones tagged legacy still hold the bots created before that, and each card says which dates it covers. The withdrawal call is identical on every version. If you are not sure which one your bot is on, use the finder in section 2 — it checks all of them — or simply try the current one first: if the id is not there, the transaction fails harmlessly with NotMaker and costs you a fraction of a cent.

If the transaction fails

Blockscout will show a red error with a short name. Here is what each one means and what to do.

The backup path: someone else can push your funds home

Every bot has an expiry date set when you created it. Once it passes, refundExpired becomes callable by anybody — and the contract still sends the money to you, never to whoever called it. There is no way for a caller to redirect it.

That matters in one scenario: you can no longer send transactions yourself, but someone can help you. They pay the gas, you receive the funds. For the grid bots the function is refundExpired(id, 0x); for all the others it is just refundExpired(id).

2 · Find your bot ids

Two ways, both of which work with The Desk switched off.

Option A — the finder on this page

This tool talks straight to a public Robinhood Chain node. It does not touch any Desk server. Paste your wallet address (or connect your wallet) and it lists every bot that address has ever owned, marks the ones still holding money, and hands you the exact withdrawal link for each.

Option B — read it off Blockscout by hand

If the finder cannot reach a node, you can get the same id out of the explorer in under a minute. The id is recorded in the transaction that created the bot.

1. Open your own address on Blockscout

   https://robinhoodchain.blockscout.com/address/<your wallet address>

2. Find the transaction that created the bot

   In the Transactions tab, look for the one sent to your bot's contract address (from the cards in section 1) around the date you created the bot. Its method will be named openWithEth, openWithBase, open, openSL or createLadder. Click it.

3. Open the Logs tab

   Look for the event called GridOpened, DcaOpened, CycleOpened, TwapOpened or LadderCreated depending on the bot type.

4. Copy the first indexed value

   The event's first indexed parameter is called id and is a 66-character 0x… value. That is your bot id. The second indexed parameter is your own wallet address — a useful sanity check that you have the right event.

   Transaction  ·  Logs

   GridOpened

   [topic0]  event signature

   0x695d3b1a859592b997383d9c9d76a025cbd1299207d61bebe4ba9173936a2265

   [topic1]  id  ← this one

   0xf1dd7569911dac84b29e4446d373fac1195ee64df24601fa42ea55b703a03160

   [topic2]  maker

   0x…your wallet address, confirming this bot is yours

3 · How the bots work

Three moving parts, and only one of them is us.

The escrow

When you create a bot, your ETH goes into the bot's contract and is booked against your wallet address and that bot's id. It is not pooled with anyone else's money in a way that lets it be spent on anyone else's bot — each contract tracks a total called escrowed, and every user's share of it is ring-fenced to their own bot record.

As the bot trades, the composition changes — some ETH becomes tokens, tokens become ETH again — but it all stays inside that same record, under your address, until either the bot's rules send you a payout or you withdraw.

The keeper

Blockchains do not have alarm clocks: a contract cannot wake itself up when a price moves. So a program of ours — the keeper — watches the market and pokes the contract when one of your bot's conditions is met.

The keeper's power is deliberately tiny. It can only ask the contract to do the specific action your bot already authorised, and the contract independently re-checks the price and the amounts before doing anything. The keeper cannot choose a different price, cannot move funds to any address other than yours, cannot close your bot and cannot withdraw anything. If the keeper goes offline, your bot stops trading and simply sits there, holding your money, until you withdraw it. Nothing is lost.

What the contract enforces, not us

• Who owns the money. Withdrawals always go to the stored maker address, which is set once when the bot is created and can never be changed.
• The price you get. Every fill must satisfy a minimum output calculated on-chain from your own parameters. A bad or manipulated trade reverts instead of executing.
• The trading route. The pool your bot trades through is fixed at creation by a hash. The keeper cannot reroute your trade through a pool of its choosing.
• The profit floor on grids. A grid sell is rejected unless it clears the spacing you configured, already net of fees. The keeper only picks the moment, never the terms.
• Your right to leave. The withdrawal functions carry no pause check and no time lock.

What we can and cannot do

That last row is the whole point. The contracts are permanent deployments with no proxy and no upgrade path. Nobody, including us, can change their code, change where the money goes, or delete them.

Fees

• 1% per executed trade (0.9% if you came through a referral), taken by the router at the moment of the trade. A grid that buys and later sells pays it on each leg.
• 0% performance fee. We do not take a cut of your profit.
• 0% to open, 0% to withdraw. Closing a bot costs only the network gas — a fraction of a cent on this chain.
• Network gas is roughly $0.007 per transaction on Robinhood Chain.

4 · What each bot does

Plain-language version. Each one names the withdrawal function you would use.

Infinity Grid

Buys a bit lower, sells a bit higher, forever, with no upper or lower boundary. It keeps a target value of the token and rebalances toward it in steps: every time the price falls one step it buys, every time it rises one step it sells, banking the difference. Designed for a token you are happy to hold while it chops sideways. You can set a floor price to stop buying below, and a take-profit to close it out.

Add funds (v3 grids, created from Aug 23, 2026): an open grid can take more ETH without being restarted — topUp(id, route, seedMinOut), called by you through the Add funds button. Half of what you add buys the token at market and joins the position, the other half goes into the reserve that funds the buys below. It counts as added investment, not profit, and the money lands in the very same bot record, so the withdrawal below returns it too. Grids on the older v1/v2 contracts cannot be topped up — open a new bot with the extra amount instead.

Withdraw with stop(id, 0x, 0, false) — you get the tokens it is currently holding plus all the unspent ETH, including grid profit already banked. Same call on v1, v2 and v3.

Spot Grid

The same buy-low/sell-high idea, but inside a range you choose, split into a fixed number of levels. Each level buys at its own price and sells at the next one up. It is more predictable than Infinity Grid and better when you have a clear view on the range. The spacing is enforced on-chain to be profitable after fees, so a level cannot be sold at a loss by the keeper.

Add funds (v3 grids, created from Aug 23, 2026): Add funds on an open Spot Grid spreads the extra ETH evenly across your levels — the levels currently holding the token get more of it bought at market, the buy levels get more ETH waiting on them — with the same profit floor per level. Same contract call as Infinity Grid, topUp(id, route, seedMinOut), and the added money sits in the same bot record. v1 grids cannot be topped up.

Withdraw with stop(id, 0x, 0, false) — same call on v1 and v3.

Martingale

Buys a first amount, and if the price drops by a set step it buys again — bigger. It repeats for as many levels as you configure, lowering the average entry each time, then sells the whole position when it is up by your target percentage. Optionally it restarts and does it again.

Withdraw with withdraw(id) — you get the tokens bought so far plus the ETH still reserved for the levels that never triggered, without selling anything.

DCA (dollar-cost averaging)

Splits an amount of ETH into equal purchases spaced over time — every hour, day, week, whatever you set — so your entry is an average instead of a single bet on one moment. It can either deliver each purchase straight to your wallet or hold the position and take profit at a target.

Withdraw with stop(id, 0x, 0, false) — you get any tokens it is holding plus every unspent instalment.

TWAP

One large order chopped into small slices executed at intervals, so you do not move the price against yourself. Unlike DCA it is a single order you want completed, not an ongoing savings plan.

Withdraw with stop(id) — you get back everything not yet executed. Slices already executed were delivered to your wallet as they happened.

Ladder

Several buy orders stacked at descending prices. Each rung fills only if the price reaches it. Useful when you want exposure on a dip without watching the chart.

Withdraw with cancel(id) — you get back the ETH behind every rung that has not filled. Filled rungs already delivered their tokens to you.

Limit orders

Different by design: your money never leaves your wallet. You sign an order, and it can only ever be executed on the exact terms you signed, using a standard called Permit2. Nothing is escrowed, so there is nothing to withdraw — if The Desk vanishes, an unfilled order simply never fills.

To be extra safe you can cancel on-chain, or invalidate the signature permanently by calling invalidateUnorderedNonces on Permit2 yourself. Revoking your Permit2 allowance for the token also kills any pending order instantly.

Predict

Short up/down rounds on a price. You stake on a side, the round locks, and after it settles the winning side splits the pot. It is not an escrow bot: once a round is locked your stake is committed until it resolves.

Collect with claim([epoch, epoch, …]). If a round could not be settled — for example the oracle stopped — it is cancelled and every stake in it becomes fully refundable through the same claim call. Use the read functions getUserRounds, claimable and refundable to see what you are owed.

5 · Risks, honestly

The withdrawal guarantee protects your access to your funds. It does not protect their value.

Risks that are not about price

• The token itself. Most tokens on any chain go to zero, and a token contract can have a transfer tax, a blacklist or a mint switch. The bot contract cannot protect you from a hostile token. Check the deployer's record before you commit.
• Thin liquidity. If the pool is small, a fill can move the price against you inside your own trade. The on-chain minimum-output check stops the extreme cases by reverting, which means your bot silently does nothing instead.
• Keeper downtime. Your bot pauses. Money is safe, opportunity is not: a take-profit might not fire, a stop-loss might not fire. If the keeper stays down, withdraw and manage manually.
• Smart contract risk. These contracts are unaudited by a third party. They are verified and readable on Blockscout, and the withdrawal paths in this guide have been tested with real money on mainnet, but "no bug found" is never "no bug".
• Your keys. Nobody can recover the bot for you if you lose your wallet. The maker address is permanent.

6 · FAQ

The questions people actually ask.