Author: coderdan (1484) Quorum Requirement: 20% (9M) Vote Duration: 14 days

Proposal Summary

Pixelcraft Studios proposes that Aavegotchi perform a full, “all-in, no-looking-back” migration to Base. Existing assets on Polygon would remain onchain, but their smart contracts would be upgraded to prevent transfers and state adjustments. Then, we would clone deploy all Aavegotchi assets 1:1 and mint them on Base, including Aavegotchis, wearables, badges, REALM Parcels, Forge assets, and FAKE Gotchis.

Post-migration, end users would have very little work to do, besides re-connecting to the Aavegotchi dapp using Base instead of Polygon network.

Much of the migration work has already been done for Geist, including prepping the dapp to be multichain, and prepping the full Aavegotchi diamond to be deployed on a new chain.

Pixelcraft estimates that all of the required migration and testing can be completed by the time this prop has passed CoreProp (4-6 weeks).

Some of the benefits of this move include:

• Frictionless onboarding. Base is the most used EVM chain (besides BNB and Tron), with easy onboarding from Coinbase or any other chain. Base is also expanding its funnel via deep integrations with Farcaster and Coinbase Wallet. GHST is also listed on Coinbase, has liquidity pools on Aerodrome and Uniswap, and recently had deposits and withdrawals to Coinbase enabled.
• Increased accessibility on major NFT marketplaces. As part of this migration, we’ll introduce a “wrapper” contract to protect your Aavegotchis and wearables when you list them on popular NFT marketplaces like MagicEden and OpenSea. This prevents last-minute item removals that can lead to scam listings.
• Better end user experience. Transacting on Base is fast and smooth, while still maintaining the inherent security of Ethereum.

Rationale + FAQ

For full rationale and FAQ, please refer to this X article posted by the author: https://x.com/coderdannn/status/1890021821459935706

Failure Case

If this proposal is not successful, due to lack of quorum or other reasons, then Aavegotchi will continue using its existing deployment on Polygon.

Options

• Yes, Make Aavegotchi Based Again
• No, stay on Polygon