KEEP EXCHANGE KEYS LOCAL
Exchange → Ethereum ETH → Robinhood ETH.
The website creates a public-address plan. The local companion talks directly to your exchange, so withdrawal credentials stay off HOODLABS.
Fund one wallet first
- Create and restore-verify the node backup in HOODLABS.
- Enter the source withdrawal amount in ETH. It is separate from the desired Robinhood balance.
- Download the plan labelled Ethereum funding plan. It contains public addresses and amounts, never wallet keys.
- Inspect and review one exchange withdrawal in the local companion.
- After Ethereum ETH arrives, use the node’s Relay panel. Keep source gas, bridge once, verify completion, then check Robinhood ETH.
Exchange support
| Exchange | Supported connection | Check before use |
|---|---|---|
| Binance | Read-only account and network checks. Withdraw manually. | Ethereum enabled, key permissions, whitelist, minimum, fees and Travel Rule. Binance.US is separate. |
| Kraken | Read checks and one reviewed withdrawal per destination when local live execution is enabled. | Approved address key, Ethereum method, amount semantics and fee. |
| OKX | Read-only account, network and balance checks. Withdraw manually. | Region/API host, permissions, destination, ETH-Ethereum network and fee. |
Published APIs do not guarantee access for each country or account. Never assume direct Robinhood withdrawals are supported.
Official API references
Run the companion privately
- Use Node 24 in Linux or WSL. Native Windows is currently unsupported.
- Keep the journal in a private Linux home directory.
- Set credentials only in the local process environment.
- Follow the reviewed local setup guide.
- Inspect with
node companion/cli.cjs inspect kraken funding-plan.json 1. Usebinanceorokxfor their read-only connectors.
The companion has no web server. Local live withdrawals remain disabled until explicitly enabled after review.
Controls that prevent a duplicate send
- Use a dedicated API key, restricted IP and approved destinations where available. Grant only required permissions.
- Never paste credentials into this website, support chat or a funding-plan file.
- A timeout can happen after acceptance. The journal marks it unresolved and the companion does not resend automatically.
- Reconcile an unresolved request at the exchange. Do not delete the journal to bypass protection.
- Automatic funding allows one attempt per destination, including successful attempts. Make later top-ups manually.
Where connection status appears
The website has no exchange credentials and cannot report your account as connected. The local companion shows capability, fee and withdrawal results.
Mock tests cover request construction and failure handling. Your permissions, regional rules and any real withdrawal still need account-specific validation.