.env.example

# Copy to .env.local for development. Production values live in Vercel's
# environment variables, never in the repo.

# Signs the wallet sign-in session and nonce cookies.
#
# Required. Without it the auth endpoints fail closed - /api/auth/nonce returns
# "Sign-in is not configured on this deployment" - so sign-in is unavailable
# rather than insecure.
#
# Must be at least 32 characters. Generate one with:
#   node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"
#
# Rotating it invalidates every existing session, which signs all users out.
# That is the correct response if it is ever exposed.
SESSION_SECRET=

# Connects mobile wallets over WalletConnect: a QR code on desktop, a deep link
# into the wallet app on a phone. Trust, Rainbow, Rabby mobile and most others
# speak it; MetaMask has its own route and works without this.
#
# Optional, and free. Create a project at https://dashboard.reown.com and paste
# its Project ID here. Left blank, the WalletConnect option is simply not
# offered - a connector without an id fails the moment someone taps it, so it
# is left out rather than shipped broken.
#
# This one is public: it identifies the dapp to the relay and ships in the
# client bundle. It is not a secret, unlike SESSION_SECRET above.
VITE_WALLETCONNECT_PROJECT_ID=

# The chat's database. Three variables, and which of them is secret matters
# more than usual - two are public by design and one is the entire database.
#
# Create a free project at https://supabase.com, then run the migration in
# supabase/migrations/0001_chat.sql against it. Until all three exist the chat
# page says it is not configured on this deployment and offers nothing, rather
# than failing in the browser.

# The project's URL, e.g. https://abcdefgh.supabase.co
#
# Public. The browser needs it to read messages, and the api pairs it with the
# service role key below. Named with the VITE_ prefix because the browser half
# only receives variables spelled that way.
VITE_SUPABASE_URL=

# The anon key, from the project's API settings.
#
# Public, and safe to ship in the bundle - that is what it is for. It can only
# do what the row level security policies allow, which is to read messages and
# profiles and nothing else. It cannot post, edit or delete.
VITE_SUPABASE_ANON_KEY=

# The service role key, from the same page.
#
# SECRET. This one bypasses every row level security policy - it is unrestricted
# access to the database. It is what the api uses to write a message after
# checking the sign-in cookie.
#
# Never rename this with a VITE_ prefix. Vite inlines any variable spelled that
# way into the JavaScript every visitor downloads, which would hand the whole
# database to anyone who opened the network tab. If it is ever exposed, rotate
# it in the Supabase dashboard immediately.
SUPABASE_SERVICE_ROLE_KEY=

# Wallet addresses allowed to remove a chat message, separated by commas or
# spaces. Case does not matter.
#
# Optional. Left blank nobody can remove anything, which is the safe direction
# for a forgotten variable - the alternative reading, "no list means no
# restriction", would let any signed-in visitor moderate.
#
# This is a coarse tool: changing it takes a redeploy and there is no record of
# who removed what. It is here because a public chat with no way to remove
# anything is the worse problem.
ADMIN_ADDRESSES=