Skip to main content
If the KUEST_* credentials are missing or invalid, users can browse markets but trading auth and proxy wallet flows will fail.

Required for production

VariableWhy it mattersHow to obtain it
KUEST_ADDRESS
KUEST_API_KEY
KUEST_API_SECRET
KUEST_PASSPHRASE
Powers proxy wallet setup and authenticated trading requests.Generate credentials at auth.kuest.com by connecting your Polygon wallet.
ADMIN_WALLETSGrants access to the admin dashboard.Use a comma-separated list of wallet addresses for trusted operators.
REOWN_APPKIT_PROJECT_IDEnables wallet logins through Reown (WalletConnect).Copy it from the Reown dashboard.
BETTER_AUTH_SECRETProtects Better Auth sessions and encrypted trading credentials.Generate a 32-character value using the Better Auth installation guide.
CRON_SECRETSecures scheduled jobs.Create any random string with at least 16 characters.
Optional in .env.example means the variable is not always filled manually. Some deployment targets still require one database connection and one storage profile.

Optional variables from .env.example

VariableWhere it is usedWhen to use itFormat or example
DISABLE_IMAGE_OPTIMIZATIONAffects image rendering across market cards, event covers, category icons, and uploaded brand assets.Set it to true if your host, reverse proxy, or CDN breaks Next.js image optimization, or if you already optimize images upstream.true or false
POSTGRES_URLMain runtime database connection for users, admin settings, categories, events, markets, and migrations.Required for manual installs unless your platform injects the database URL for you.postgresql://user:password@db.example.com:5432/kuest?sslmode=require
SUPABASE_URLServer-side connection used for asset storage when the site uploads images to Supabase Storage.Use it only if your deployment target runs in Supabase storage mode. It must be paired with SUPABASE_SERVICE_ROLE_KEY.https://project-ref.supabase.co
SUPABASE_SERVICE_ROLE_KEYServer-only credential for uploads, signed URLs, and asset management in Supabase mode.Fill it only together with SUPABASE_URL. Do not expose it in client-side tools.eyJhbGciOi...
S3_BUCKETBucket name used to store logos, event images, market covers, and other uploaded assets in S3 mode.Use it when you choose S3-compatible storage instead of Supabase.kuest-assets
S3_ENDPOINTStorage endpoint the app calls when uploading or reading files from S3-compatible storage.Add it for providers such as Cloudflare R2, DigitalOcean Spaces, MinIO, or any non-default S3 endpoint.https://nyc3.digitaloceanspaces.com
S3_REGIONRegion metadata used by the storage client when signing S3 requests.Fill it when your provider requires an explicit region or signature region.us-east-1
S3_ACCESS_KEY_IDServer credential used to authenticate uploads and file operations in S3 mode.Required whenever you use S3-compatible storage.DO00ABC123EXAMPLE
S3_SECRET_ACCESS_KEYSecret paired with S3_ACCESS_KEY_ID for server-side storage access.Required whenever you use S3-compatible storage. Keep it server-side only.wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
S3_PUBLIC_URLPublic asset base shown to users when the site renders uploaded files.Use it when your images should load from a CDN or custom files domain instead of the raw bucket endpoint.https://cdn.example.com/assets
S3_FORCE_PATH_STYLEChanges how the storage client builds S3 URLs and signed requests.Keep true when your provider needs path-style requests. Switch to false if your provider expects virtual-host style URLs.true or false
SENTRY_DSNRuntime error reporting for both the app server and the user-facing site.Add it if you want crashes and production errors sent to Sentry.https://abc123@o12345.ingest.us.sentry.io/67890
SENTRY_ORGBuild or release integration with Sentry, not the core app runtime.Use it only if your deployment pipeline also uploads source maps or creates releases in Sentry.kuest
SENTRY_PROJECTIdentifies which Sentry project should receive build-time release artifacts.Use it together with SENTRY_ORG when your build integrates with Sentry releases.prediction-market
SENTRY_AUTH_TOKENServer-side token for build tooling that pushes releases or source maps to Sentry.Needed only for build-time Sentry integration. It is not required for basic runtime error capture with SENTRY_DSN.sntrys_...
EVENT_CREATION_SIGNER_PRIVATE_KEYSUsed by recurring or scheduled market creation flows in the admin calendar. The server loads these keys to sign automated event creation.Needed only if you plan to use recurring events or server-driven scheduled creation. It accepts comma-separated keys or a JSON array.0xabc...,0xdef... or ["0xabc...","0xdef..."]
Choose one storage profile only. Use SUPABASE_URL + SUPABASE_SERVICE_ROLE_KEY, or use S3_BUCKET + S3_ACCESS_KEY_ID + S3_SECRET_ACCESS_KEY.