Skip to content

fix(frontend): default new visitors to mainnet#64

Merged
keanji-x merged 1 commit into
mainfrom
fix/frontend-mainnet-default
Jun 5, 2026
Merged

fix(frontend): default new visitors to mainnet#64
keanji-x merged 1 commit into
mainfrom
fix/frontend-mainnet-default

Conversation

@keanji-x

@keanji-x keanji-x commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Reorder NETWORK_FILES in next.config.mjs so mainnet is the first entry. The NetworkPicker defaults to NETWORKS[0], so new visitors now land on mainnet on first visit.
  • Testnet is still selectable from the picker; users who previously chose testnet keep their localStorage selection on the next page load.

Why

The main repo was deployed to k8s with APP_CONFIG=gravity (testnet) as the default network. After the mainnet contract upgrade today, prd should default to mainnet so visitors see real on-chain state without having to click the network selector.

Test plan

  • Build the image locally (or via GHA frontend-image) and verify NEXT_PUBLIC_NETWORKS puts mainnet first.
  • Load the UI fresh (no localStorage entry under gt:network) and confirm the NetworkPicker shows Mainnet as active and the engine hits https://mainnet-rpc.gravity.xyz.
  • Switch to Testnet, reload — confirm the choice persists.

🤖 Generated with Claude Code

Reorder NETWORK_FILES so mainnet is the first entry, making it the
default network on first visit. Testnet remains selectable in the
NetworkPicker and existing localStorage choices are preserved.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
gravity-town Ready Ready Preview, Comment Jun 5, 2026 3:02am

Request Review

@keanji-x keanji-x merged commit 05709da into main Jun 5, 2026
6 checks passed
@keanji-x keanji-x deleted the fix/frontend-mainnet-default branch June 5, 2026 03:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant