Connecting a wallet.
HoodLock is non-custodial, so connecting is the only account there is. Nothing is stored on our side and no signature is needed just to look around.
Supported wallets#
Any wallet that supports Robinhood Chain works. The app discovers browser wallets automatically through EIP-6963, so anything installed shows up in the list without us maintaining one.
| Route | Notes |
|---|---|
| Browser extension | MetaMask, Rabby, Phantom, Trust and anything else that announces itself. Discovered automatically. |
| WalletConnect | For mobile wallets and anything not installed in this browser. Opens a QR or a deep link. |
| Wallet in-app browser | Opening hoodlock.tech inside your wallet's own browser is the most reliable route on mobile. |
Mobile wallet apps cannot inject into Safari or Chrome. On a phone you either use WalletConnect or open the site inside the wallet's own browser — a mobile wallet will never appear in the extension list, however many times you reload.
The network#
HoodLock runs only on Robinhood Chain, chain id 4663. The app asks your wallet to switch,
and to add the chain if it is missing, so you rarely need to do anything by hand. The parameters are on
the network page if you prefer to add it yourself.
Transactions are submitted through your wallet's RPC, not ours. If your wallet has chain 4663 configured with a broken endpoint, sending will fail no matter what the site does — remove the network and let the app re-add it.
What connecting does and does not do#
- It does not give us access to anything. Connecting shares your address. It grants no permission to move tokens.
- Browsing needs nothing. Proof pages, the explorer and these docs all work with no wallet at all.
- Approvals are per token, per amount. Locking asks the token contract to authorise a specific amount for the locker, not a blanket permission over your wallet.
When it fails#
The wallet does not appear in the list#
- On desktop: check the extension is unlocked, then reload. A locked wallet does not announce itself.
- On mobile: use WalletConnect or the wallet's in-app browser.
- If several wallets are installed, one can claim the injection slot. Disable the others temporarily or pick yours explicitly from the list.
Connected, but the network will not switch#
Some wallets refuse to add a chain they do not recognise. Add it manually with the parameters on the network page, then reconnect.
“HTTP request failed” or a transaction that will not send#
Usually the public RPC rate-limiting a read-heavy session. Reload and try again. If a lock transaction was submitted but the confirmation never arrived, check My locks before retrying. It very likely landed, and sending again would create a second lock and charge a second fee.
More cases in troubleshooting.
Approval succeeded but the lock did not#
These are two separate transactions. If the first went through and the second did not, nothing is lost — the approval simply sits unused. Start the lock again; you will not be asked to approve twice for the same amount.
Disconnecting#
Disconnect in the app clears the stored choice so the next visit does not reconnect silently. It does not revoke token approvals — those live in the token contract. Revoke them from your wallet's approvals screen or a revoke tool if you want them gone.