> For the complete documentation index, see [llms.txt](https://docs.gage.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gage.cash/start-here/wallet.md).

# Connect a wallet

Browser wallets with Robinhood Wallet first, WalletConnect, and a hand-off to a wallet app on a phone. What you need in the wallet before a deal.

gage runs on **Robinhood Chain** (chain id 4663). RPC `https://rpc.mainnet.chain.robinhood.com`; explorer [robinhoodchain.blockscout.com](https://robinhoodchain.blockscout.com). Gas is paid in ETH.

## Wallets

Choose **Connect wallet** in the header, or at the end of an action form. The sheet lists, in this order:

1. **Browser wallets** the page discovers, each as its own row, with **Robinhood Wallet** at the top when it is present. Robinhood Wallet is how Stock Tokens reach people, and it holds USDG and ETH on the chain. When no wallet announces itself, one generic **Browser wallet** row stands in.
2. **WalletConnect**: on a phone, pick your wallet app and approve there, and you come back connected; on a desktop, scan with another device. On a phone its list leads with the wallets gage's visitors use: MetaMask, Rabby, Binance Wallet, OKX Wallet, Trust Wallet and Bitget Wallet.
3. On a phone without a wallet, or inside another app's browser, a hand-off: **Open in MetaMask**, **Trust Wallet** or **Coinbase Wallet** reopens this page in that wallet's browser, or copy the link and paste it there yourself. On a phone, closing WalletConnect's list without connecting opens these links at once; *Open this page in a wallet app instead* opens them too.

Nothing moves until you confirm in your wallet. A wallet on another network is asked to switch to Robinhood Chain.

## What you need

| To                | You need in the wallet                                                                                                         |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Borrow            | The collateral (Stock Tokens, a meme, an RH ECO token or WETH), and ETH for gas                                                |
| Earn              | The asset the partner vault lends, USDG, GLD, NVDA or HIMS, one whole unit or more, and ETH for gas                            |
| Reclaim           | The full cap in USDG, or use Cash out: the collateral is sold through a supported route, the cap repaid, and the rest is yours |
| Provide liquidity | ETH, USDG, GAGE or sGAGE, or GAGE and sGAGE together                                                                           |

## Before your first deal

On first connect, the app shows three things to know and asks you to confirm you have read them. They are in [Before your first deal](/start-here/before-your-first-deal.md).

## Balances you withdraw

Anything the contracts owe you, USDG or collateral, is credited to a Gage balance and withdrawn by you. On Portfolio, **Now** lists everything ready to collect and one **Collect all** takes it: one signature where your wallet can send a batch, else one step per contract. Nothing is pushed to your wallet. This is what lets a frozen or paused token delay only its own holder and never a counterparty's settlement.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gage.cash/start-here/wallet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.