Robinhood Chain
Robinhood Chain (“Hood”) is Candle’s EVM chain. The Candle Harness trades on it as it does on Solana: the same cards, limits, kill switch and Journal. Every position, fill, card and trigger keeps the chain it was made on.
A Solana-only account sees no change. Every Candle account has an empty embedded wallet on Hood, and that alone changes nothing on screen. Hood shows once the account uses it: a Hood TEE wallet (stopped or not), a balance, or a token there. An embedded wallet Candle couldn’t read doesn’t count. Once the core has seen Hood in use, a failed read keeps Hood on screen, with the wallet’s balance marked unread.
Your wallets on Hood
Section titled “Your wallets on Hood”| Wallet | What it is | Plan |
|---|---|---|
| The embedded wallet on Hood | Your account’s own EVM wallet. Every agent you allow pays from it, as on Solana. | Any |
| A Hood TEE wallet | A wallet of its own for one agent’s key, signed through your own candle CLI. | Pro or Max |
from embedded always means the embedded wallet on the trade’s chain. A trade pays only from a wallet on its own chain: a Solana wallet named for a Hood token is refused before anything is sent (Which wallet pays). Each agent can have a default on each chain: [agents.<name>.wallet] with solana = … and hood = … in config.toml (Configuration).
A Hood TEE wallet for an agent
Section titled “A Hood TEE wallet for an agent”Click add a Hood wallet on the agent (its picker or the palette), or in the Wallets pane once the account uses Hood. It shows for an agent with no Hood TEE wallet, on Pro or Max. Each step runs in the prompt pane as you, with your vault’s factor first:
candle vault new-key --chain evm, where your vault has no EVM key yet;candle vault promotefrom that key to the agent’s key, which makes the wallet and pins it to that vault key, its way home.
The first Hood TEE wallet moves the vault file to version 4, which an older candle CLI can’t open. The card says so before you approve it: keep candle at 0.13.20 or later on every machine that uses the vault. Hood and Solana TEE wallets share your plan’s count of linked wallets.
ETH first. A Hood TEE wallet pays gas in ETH on every trade, a USDG buy included, and Candle keeps a little ETH back as a reserve so the wallet can always be swept home. A new one starts empty, so the pane offers three ways to fund it:
bridge ETH: a bridge card from the same key’s Solana TEE wallet (below);fund from vault key:candle vault fund <address> --asset ETHfrom its EVM vault key, which you fund first;⧉ address: send ETH to it from anywhere.
A Hood TEE wallet that holds tokens and no ETH says needs ETH to trade on its Wallets row. A trade from it without enough ETH is refused before anything is bought, with the shortfall and the reserve in ETH.
One trade at a time. Candle runs one operation at a time on a Hood TEE wallet. A second trade you approve waits in the core, its card saying “waits for the wallet’s last trade”, and goes once Candle lets the wallet go: the first’s job has ended, a bridge’s deposit has landed, or 30 minutes have passed since the first was sent. One still waiting when its card’s 60 seconds run out is refused, with nothing sent: ask for it again. The kill switch withdraws a waiting buy. A Hood trade runs in one to four steps (approve, Permit2, the trade, the fee), each sent once the one before has landed; trades took about 7 to 9 seconds when we measured. One that outlasts the CLI’s wait is followed by its id, never sent again. One Candle ends as failed after its trade step was sent may still have filled: its card says so, and that what the wallet holds says which, and it isn’t read again.
Stopping and sweeping one
Section titled “Stopping and sweeping one”Each step takes the wallet’s 0x address, as on Solana: candle tee disable stops it for good (in the prompt pane, with the vault’s passphrase), then candle tee sweep sends its tokens home to its vault key and its ETH last. A sweep needs ETH for gas, and is refused while a bridge from or to the wallet is open. candle tee status shows where it stands. A stopped Hood wallet’s ETH is read over the Hood RPC; its tokens aren’t listed once Candle drops the wallet, so the pane says they weren’t read. candle tee check is Solana’s only.
Trading on Hood
Section titled “Trading on Hood”A Hood token is named by its 0x… address, or by a name a pane or the agent has shown. Typed trades work as on Solana:
buy 0.01 eth 0x…buy 5 usdg 0x…buy $5 of 0x…sell 50% 0x…- A Hood token trades against its own quote asset, ETH or USDG, as Candle sets it. A dollar buy pays in ETH. A buy in the other asset is refused by Candle, naming the one the token settles in, and nothing is sent.
- ETH and USDG are what trades spend, so neither can be a buy’s or sell’s token, nor can WETH. Converting one is a swap.
- A name seen on both chains isn’t traded by name. The message line lists each one as a chip (its name, its chain and a short address), and a click puts that token’s address on the line. Nothing is sent until you send the line.
- A card on Hood says
· on Hoodon its first line.
Limits. An ETH or USDG buy counts at its dollar value against the agent’s limits and the wallet’s figures. Candle values USDG at a fixed $1, and so does the Candle Harness. The approvals menu lists embedded on Hood once the account uses Hood, so it can trade inside limits on its own figures. A Hood amount the core can’t price is always a card, and says why.
The chain filter
Section titled “The chain filter”When the account uses both chains, an all chains ▾ chip sits beside the agent chip in the status bar: all chains, Solana, or Hood. Every listing pane follows it: Feed, Trending, Signals, Positions, Wallets, P&L, Activity and the Journal. The agent’s pane and its cards never do. It’s one choice for every view, kept across a restart, and the palette has the same rows. Every account starts on all chains; a Signals pane’s own chain stays that pane’s. P&L’s totals stay Candle’s, for the whole account.
While a view mixes chains, each row carries a dim sol or hood tag. The Wallets and Positions panes put Solana’s and Hood’s wallets under their own headings instead, with the embedded wallet under each, its own balance and its ⧉.
Trending on Hood. Candle’s New, Graduated and On Fire lists are read on Hood too. With all chains showing, Hood’s lists are read at half the pace, and only while one is on screen, to stay inside Free’s request budget; with Hood picked, they take Solana’s pace and Solana’s stop. Final Stretch is pump.fun’s, on Solana only, and says so.
Hacc’s token check on Hood
Section titled “Hacc’s token check on Hood”Candle’s own safety check doesn’t read Hood tokens yet. On Pro and Max, the token pane shows Hacc’s check for a Hood token instead, said as Hacc’s: Hacc: no honeypot, 0% buy and sell tax, LP locked 92%. It’s read while you follow the token, and kept for a minute.
- Amber only where a field warrants a look before buying: a honeypot, a token that can’t all be sold, a sell tax over 10%, or an owner who can pause trading.
- A field Hacc leaves blank is “not said by Hacc”, never “no”. A fresh token often has none filled in, and the pane says Hacc has no check for it yet: not checked, not clean.
- On Free, the pane says Hacc’s check needs Pro or Max.
The agent’s hacc_token read gives it the same fields.
The bridge
Section titled “The bridge”A bridge moves funds between two of the account’s own wallets, one on each chain: SOL or USDC on Solana to ETH or USDG on Hood, or back. It isn’t sending funds out.
- TEE to TEE: from an agent’s TEE wallet to the same key’s TEE wallet on the other chain, through your
candleCLI and Relay. With several on the far side, name the one it lands in: typed, addinto <wallet>(bridge 0.5 sol to eth from bot-1 into bot-1-h); the agent names it too. Without it, a bridge with several on the far side is refused, naming them. - Embedded to embedded: between the account’s two embedded wallets, through Candle’s own route.
The agent proposes it, or you type it: bridge 0.5 sol to eth, with from <wallet>, into <wallet> and as <agent>. A bridge written as a sentence goes to the agent. A bridge is always a card, live only, even on a wallet that trades inside limits. Its four lines say what moves, the route, the cost, and the chips. Its figure is a price conversion before Relay’s fee, so the card says “less Relay’s fee”: Candle charges no fee, but Relay takes its own, which weighs most on a small bridge. ctrl-o shows each step once it’s sent.
In flight, the card reads sent on Solana · arriving on Hood…. A TEE bridge is followed by its id (candle swap status). Candle answers an embedded bridge once the deposit has landed, usually before Relay fills it, so the core follows that one by the landing embedded wallet’s balance, read once before the bridge is sent: it says arrived once that balance has risen by what the quote said, less 1%. Either is read every 10 seconds for ten minutes, then each minute, and a restart picks it up again, never sending it twice. If Relay can’t fill it after the deposit landed, Relay refunds it to the wallet it came from, and the card says so. With no result after two hours, or a result Relay couldn’t tie to one fill, the card and Activity say so and name the wallet to check, and it’s no longer followed. So does an embedded bridge whose landing balance couldn’t be read before it went, or that Candle hasn’t answered in ten minutes.
While a bridge is open (up to two hours), a sweep of either wallet is refused. The kill switch withdraws a bridge card still waiting, and can’t stop one already sent; it says so. A bridge counts as a move between your own wallets: it’s in Activity when it arrives, and isn’t spend, a trade, or P&L. Candle’s own caps on the sending asset still apply.
Bots and triggers on Hood
Section titled “Bots and triggers on Hood”- Rules bots take
chain = "hood"in their definition, with a wallet on Hood. Its buys spend ETH, and are checked against the ETH its wallet holds. A wallet on the other chain is refused when the bot is made. A bot set to both chains with a wallet on one skips the other chain’s signals, saying its wallet’s on the other chain. A live Hood bot’s exits sell from whichever Hood wallet holds the position. - Code bots buy on Hood with the token’s
0xaddress;chainmay be given, and must match. A buy on a chain the bot’s wallet isn’t on is refused before anything is recorded. - Triggers watch a Hood token’s price or market cap, read from Candle’s market data on Hood, and Hacc’s tape with
chain hood. Each keeps its chain from when you approved it.
What isn’t on Hood yet
Section titled “What isn’t on Hood yet”Candle doesn’t offer these on Hood yet, so neither does the Candle Harness:
- Candle’s safety check and forensics (Hacc’s check stands in, above);
- launches and liquidity pools;
- price history through Candle’s tools: the chart uses Hacc’s history, as it does on Solana;
- Candle’s analytics: insiders, smart money, research and Final Stretch;
candle tee checkandcandle swap --dry-run, which check Solana wallets only.
Linked EVM wallets of your own (such as a browser wallet) aren’t supported yet either.