Wallet connection issues

Browser may have blocked the popup. Click the MetaMask extension icon in your toolbar manually — the pending request usually appears there. If not, refresh the Botely page and try again.

Some browsers (especially Brave with strict shields) block the connection request. Lower shields on botely.trade or temporarily switch to Chrome / Firefox for the wizard.

MetaMask's currently-selected network doesn't matter for the `approveAgent` action — Hyperliquid's signing is EIP-712 typed-data over HTTP, not an on-chain transaction. You can be on Ethereum mainnet, Arbitrum, anything.

If the wizard insists on a specific network, that's a bug — flag it via support@botely.trade. The action is venue-agnostic at the EIP-712 level.

If you have MetaMask + Rabby + Coinbase Wallet all installed, the browser may route the connection to the wrong one. In MetaMask Settings → Experimental, toggle on "Use MetaMask as default for window.ethereum" — or disable the other extensions before running the wizard.

Rabby specifically intercepts MetaMask by default. If you want to use Rabby, that's fine — the wizard works with any EIP-712-capable EVM wallet. If you want MetaMask, disable Rabby in `chrome://extensions` first.

Hardware wallets sometimes show the EIP-712 payload as raw hex rather than parsed fields. If the device says "Blind signing required", enable it in the device's app settings (Ledger: Ethereum app → Settings → Blind signing → Enable).

After enabling, retry the wizard. The device will now display the message — verify the agent address shown on the device screen matches the wizard before pressing confirm.