Docs / Layers

Members and sign-in

Live, one walletRuns on near-connect

A member is an account named <name>.<site>, created through the relayer with no NEAR. The page makes the member's key in the browser and never sends it anywhere. A NEAR wallet can sign in instead, by signing a NEP-413 message that the page checks.

Commands

quay members list
quay members open
quay members close

How Harbour Board uses it

1. On 2026-11-11 there were nine members. Six were seeded, one joined from the live /new/ page in a headless browser, and two came from Telegram tests.
2. Wallet sign-in worked with one connector, NEAR CLI. It signed a NEP-413 message for walletchk-he8kli.harbour-board.testnet, the Board accepted it, and a changed message or a wrong site was refused.
3. Intear's testnet index was empty and Meteor blocks headless browsers, so neither is proven. Ledger and Nightly were not tried.
4. For Telegram, a telegram-auth function on OutLayer checked test init data signed with a made-up bot token, then joined two members. No real bot has run yet.

Proof on testnet

Check it without a key: view list_members '{"from_index":0,"limit":50}'. The view helper is in the repository README, and scripts/judge.sh runs these checks.

What you trust

The page loads @hot-labs/near-connect from esm.sh and the wallets it lists. A member key lives in that browser only. Pass your own connector, or sign with an explicit key in Node.

Limits

Every flag is in the command reference, generated from quay members --help.