chore(frontend): point gravity.json at Gravity mainnet#63
Merged
Conversation
Switch the `gravity` frontend config from testnet to Gravity mainnet: - rpc_url → https://mainnet-rpc.gravity.xyz - chain_id → 127001 - router → 0x4c2F6C0BAd768A75a67949b35feb094BAC4De03a - explorer → https://mainnet-explorer.gravity.xyz The frontend resolves all other contract addresses on-chain via the Router, so only the router needs to change. Verified against the live mainnet Router (getAddressesV3) — all nine addresses resolve exactly, including the freshly-upgraded GTreasury / CardLedger / ArenaEngine. Values match the committed gravity-mainnet.example.json.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Point
frontend/config/gravity.jsonat Gravity mainnet (was Gravity testnet).rpc_urlhttps://rpc-testnet.gravity.xyzhttps://mainnet-rpc.gravity.xyzchain_id7771625127001router_address0x5cAD…112C30x4c2F6C0BAd768A75a67949b35feb094BAC4De03aexplorer_urlhttps://explorer-sepolia.gravity.xyzhttps://mainnet-explorer.gravity.xyzwss_urlwss://rpc-testnet.gravity.xyz""The frontend discovers every other contract address on-chain via the Router, so only the router address needs to change.
Verified against the live mainnet Router
Router.getAddressesV3()at0x4c2F…De03aresolves all nine addresses exactly as deployed (incl. the freshly-upgraded GTreasury / CardLedger / ArenaEngine):0x906Dd69FCe1Ac822d683db7b4bA202b4bCB1c98b0x08e6f61987b16165b9976DD9A96576C6b848F85d0xA336F5263f5164984F582e58242aCAA0E3DCD5780x05f7900B2B4d94a981AD52E783f37d2731C9618a0xF1A15Ebbb23EC1b3AA5c2BE2f5758d6cBD111d870xDD2555CF9F99a191fD6dF77bE7B24fC737Ae25790x48d038d02188568ce24f92852e594e52561a7e860xF45F145D9e36224d03EE9f18C41b97070554DA910xF7C71901654EF9945e024683DC258AD58BD93319Values also match the committed
gravity-mainnet.example.json.Notes
wss_urlset to""to matchgravity-mainnet.example.json(testnet had a wss endpoint). If mainnet exposes a websocket endpoint, tell me and I'll add it so the frontend gets live push updates instead of polling.Test plan
chain_idis a number (127001), not a string.https://mainnet-rpc.gravity.xyz(chainId0x1f019= 127001).gravityconfig from testnet → mainnet (the runtime network picker still offers both via the*.example.jsonfiles).