Content pfp
Content
@
0 reply
0 recast
0 reaction

Oppai γŠγ£γ±γ„ πŸ“ pfp
Oppai γŠγ£γ±γ„ πŸ“
@oppai
WAGMI DAO proposal Background The $BERRY token has been managed in collaboration with the WAGMI team. To align with our evolving strategic priorities, we propose sending the $BERRY LP 0x718dd3FE2Eb211F0679B5dF550Cc7c29C05E1Fc2 to the burn wallet address below 0x000000000000000000000000000000000000dEaD thereby severing ties with the WAGMI team. Objective Seek DAO approval to burn the $BERRY LP to achieve independence and enable focused strategic initiatives. Rationale Autonomy: Gain complete control over $BERRY’s future direction. Resource Allocation: Reallocate resources to better serve community interests and pursue new partnerships aligned with our goals. Plan of Action Community Approval: Secure majority DAO vote. Transparency: Provide detailed process updates. Execution: Send $BERRY LP to burn wallet upon approval. Potential Risks Market Reaction: Manage potential volatility through clear communication. Liquidity Impact: Plan new liquidity pools to counter
4 replies
2 recasts
10 reactions

Oppai γŠγ£γ±γ„ πŸ“ pfp
Oppai γŠγ£γ±γ„ πŸ“
@oppai
@wagmi1337.eth
1 reply
0 recast
0 reaction

WAGMI πŸŽ©πŸ˜‡ pfp
WAGMI πŸŽ©πŸ˜‡
@wagmi1337.eth
Looks great! As we write you to dm previously, please provide detailed tech summary of proposal: witch transactions we should execute (contract, calldata, value)
2 replies
0 recast
2 reactions

Oppai γŠγ£γ±γ„ πŸ“ pfp
Oppai γŠγ£γ±γ„ πŸ“
@oppai
Trying to format this correctly to meet guidelines Is this what you are referring to? **$BERRY Token Smart Contract Address** 0xe0FA2782080a3669F76EBBA92Ec2A9Cdaf39C765 **$BERRY Smart Contract ---- Code, Read, & Write URLs** CODE = https://basescan.org/address/0xe0fa2782080a3669f76ebba92ec2a9cdaf39c765#code READ = https://basescan.org/address/0xe0fa2782080a3669f76ebba92ec2a9cdaf39c765#readContract WRITE = https://basescan.org/address/0xe0fa2782080a3669f76ebba92ec2a9cdaf39c765#writeContract πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ **$BERRY Liquidity Pool Contract Address** 0x718dd3FE2Eb211F0679B5dF550Cc7c29C05E1Fc2 πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“ - πŸ“
1 reply
0 recast
0 reaction

WAGMI πŸŽ©πŸ˜‡ pfp
WAGMI πŸŽ©πŸ˜‡
@wagmi1337.eth
Which function we should call? With which params? Please, provide all details for it, thanks
1 reply
0 recast
0 reaction

eggman πŸ”΅ pfp
eggman πŸ”΅
@eggman.eth
gm, just assisting @oppai - pls confirm the below fren :) LP contract: 0x718dd3FE2Eb211F0679B5dF550Cc7c29C05E1Fc2 This is the uniswap v3 pair representing berry/weth. The initial LP creator is the contract at 0xff747d4cea4ed9c24334a77b0e4824e8ec9a6808. What @oppai is requesting is that the uniswap v3 NFT representing the LP pair above is transferred to the dead address :) However, from looking at the contract at 6808 - it looks like the LP is effectively "locked" in there, as I'm not seeing any functions on there that allow you to interact with it? Which in essence, would mean it's technically already burned/cannot be broken or transferred by wagmi? Please correct me if I'm wrong on this - just getting this from a cursory glance against the contract/fairlaunch routine :)
0 reply
0 recast
0 reaction