# Gnars Base Jump


## Migration Plan

Overview:

- Tech requirements and deployment plans
- Mobilising relevant groups (community pod etc)
- Builder DAO marketing activation

### Tech Migration

Proposed migration plan:

1. Deploy fully onchain metadata renderer to L2 (same as L1)** - [Seeder and descriptor contracts deployed on Base Sepolia by Mulf](https://discord.com/channels/928811922244137020/1026553205393477642/1208195441204920391)
2. Gnars L1 proposal (1) to pause auctions, fund migration gas costs and associated marketing efforts
3. Gnars L1 proposal (2) to call [L2 Migration Deployer](https://hackmd.io/peXISQ2CSQOwRGmvpUpK9A#L2-Migration-Deployer), deploy a DAO with given parameters on Base (including an [Alternate Metadata Renderer](https://hackmd.io/peXISQ2CSQOwRGmvpUpK9A#Custom-Metadata-Renderers)), and set [Merkle Reserve Minter](https://hackmd.io/peXISQ2CSQOwRGmvpUpK9A#Merkle-Reserve-Minter) to allow L1 holders to claim
4. Gnars L1 proposal (3) to call L2 Migration Deployer and use `depositToTreasury` to transfer test amount (ETH and USDC) from L1 treasury to newly deployed L2 treasury
5. Gnars L1 proposal (4) to call L2 Migration Deployer and use `depositToTreasury` to transfer remaining ETH and USDC from L1 treasury to newly deployed L2 treasury
6. Gnars L2 proposal (5) to renounce `L2MigrationDeployer.sol`'s ownership once setup is complete and unpause auctions to commence L2 operations

Important links:

- Tech details: [Migration to Base via Builder](https://hackmd.io/mhKFWt2oRJ2sA5Hjk9Mu2Q)

*Meeting 14 Feb 2024*

**Considerations:**

- Frontend changes that need to be made to ensure no incorrect contract calls or transactions made on Base L2 etc. Bagel raised and Mulf has brought up some foundational solutions such as which wallet connection library we are using etc
- Frontend update to gnars.wtf to disable functionality, we can make use of the nouns.build frontend for the time being, make it read only for historical purposes as the DAO will actually live on forever on Ethereum L1
- Capture all the data and statically render it out (archive) for people to always have that reference to L1 onchain and Snapshot proposals
- DAO configurations: we should maintain our current settings, minus the founder reward for athletes,
- Treasury clean up, need to ensure we migrate what we can, and move out what we can't etc. For example, we have Nouns Vision glasses and Gnars in our multisig at shred.gnars.eth
- We gonna ask folks to vote 3 times on L1 so we should mention in the proposals, at the top, that's voting will be subsidised and all voters will be refunded their gas once we are on L2
- Can we stack the proposals as we believe so, or do we need to be mindful of one proposal needing to execute before another? (shouldn't need to)
- Remove option to submit proposals in frontend, so no props can change the treasury values while we are migrating, we can vote down or even veto if we need to
- Can we migrate USDC in our call to L2 Migration Deployer using `depositToTreasury` or is it ETH only? May need to consider things such as the decimal places etc
- If we need to we can use the crosschain capabilities in USDC contract's native functions ([cross chain transfer protocol](https://developers.circle.com/stablecoins/docs/cctp-getting-started
))
- We need to communicate repeatedly, and reach out to holders directly, about any Gnars that might be stored in addresses that don't map directly (eg. some Gnosis Safe multigs maybe)
- Gnosis Safe migration, can we map directly or do we move them out

## Social Party

Task list:

## Media Party

Task list:

## PM - Source of Truth

https://app.clarity.so/gnars/project/2