Gravity Alpha Mainnet: Completing the Transition to Gravity L1

Gravity Alpha Mainnet marked the first phase of bringing Galxe onchain, serving as a live environment to process production traffic and identify execution bottlenecks. Insights gained from Alpha Mainnet directly shaped Gravity L1, driving the development of Grevm (parallel EVM execution), sub-second finality, and a validator-attested Native Oracle. With Gravity L1 Mainnet now fully operational, Gravity Alpha Mainnet has fulfilled its role.

Gravity Alpha Mainnet’s network operations will officially conclude on November 1, 2026. Please note that October 25 is an earlier critical deadline for native bridge withdrawals and G unstaking, as both require a 7-day waiting period.

Critical Deadline:

October 25, 2026, at 8:00 PM Pacific Time (PDT, UTC−7): The Gravity Native Bridge and G Staking page on Galxe will be taken offline. You must initiate native bridge withdrawals and unstake your G before this deadline to allow time for the 7-day waiting period.
November 1, 2026: Gravity Alpha Mainnet will permanently cease operations. Assets remaining on the network after shutdown cannot be transferred.

Required Actions for Gravity Alpha Mainnet Users and G Stakers

Token holders on Gravity Alpha Mainnet and G stakers on Galxe must complete the following steps before affected date.

1. Bridge Assets Off Alpha Mainnet

For G Tokens: Use the official Gravity Bridge to move native G to Ethereum or Gravity L1 Mainnet beforeOctober 25, 2026, at 8:00 PM PDT.
For $USDT, $USDC, $ETH, and Other Tokens: Follow the Stargate Bridge Tutorial to route tokens off Alpha Mainnet before October 23, 2026.

2. Unstake G on Galxe before October 25, 2026, at 8:00 PM PDT.

G Staking on Galxe is sunsetting as part of this transition.

Navigate to the G Staking Portal and unstake tokens directly to the connected wallet.
Tokens will return to the chain where originally staked: BNB Chain, Ethereum, or Gravity Alpha Mainnet.
Important: If unstaked G returns to Gravity Alpha Mainnet, bridging it off the network before October 25, 2026 remains mandatory.

Rationale for Full Transition to Gravity L1

Maintaining two separate networks splits developer resources, liquidity pools, and tooling. Consolidating all activity onto Gravity L1 establishes a single environment engineered for high-throughput applications:

Parallel EVM Execution: 12,000+ TPS with sub-second finality powered by Grevm (Gravity's parallel EVM) and AptosBFT consensus.
Native Oracle Security: L1 validators attest to oracle messages directly, reducing reliance on external oracle networks or separate bridge signer sets.
Built for Autonomous Agents: A persistent execution layer designed for AI agents to read state, settle value, and execute smart contracts onchain.

Developer Setup for Gravity L1

To transition dApps, bots, or scripts running on Alpha Mainnet, update configurations to Gravity L1:

RPC Endpoint: https://mainnet-rpc.gravity.xyz
Chain ID: 127001
Block Explorer: https://mainnet-explorer.gravity.xyz
Agent Skill Integration: Load Gravity network parameters, precompiles, and contract maps directly into AI coding assistants:

npx skills add https://github.com/Galxe/gravity-skills