Skip to content

Connect a wallet

user

What wallet connect is for — receipt ownership and Base-side x402 flows. Not a Robinhood connection.

What connecting a wallet does

HISS is a wallet-connected workbench. Connecting an EVM wallet and signing one login message does two things: it attaches the receipts, command packs, and instruction packs you compile to your wallet address (so you can list them later under /api/me/receipts), and it identifies you for Base-side flows — the HISS x402 services settle in USDC on Base.

How sign-in works

  1. Click Connect wallet in the nav and pick a wallet (injected/EIP-6963 and Coinbase Wallet work out of the box; WalletConnect appears when configured).
  2. HISS issues a one-time nonce and your wallet signs a plain-text EIP-4361 login message. The statement in the message says exactly what it is for.
  3. The signature is verified server-side and an HttpOnly session cookie is set for seven days. When the production database is configured, your user row and session are persisted.

The primary chain is Base (chain ID 8453). If your wallet is on another network you'll see a switch prompt — nothing breaks, but x402 flows expect Base.

What gets saved

Your normalized wallet address, chain ID, and session timestamps — nothing else. Receipts compiled while signed in carry your user ID; anonymous compiles stay anonymous. See Wallet security for the full model and Database for what each table holds.

Disconnecting

Disconnect from the nav at any time: the server session is revoked, the cookie is cleared, and the wallet connection is dropped. Receipts already attached to your address stay yours.

$HISS is independent research software in paper mode — not investment advice, and not affiliated with Robinhood, Bankr, or Chainlink.