Botto

This BIP is posted on behalf of Sync, the author of the proposal.

Note: Snapshot is only a summary and may leave ambiguities that are covered in the full BIP in the forum which takes precedent. Please refer to the BIP-80 forum post for full details and the Discord thread for discussion.

Summary

This BIP proposes launching a new liquidity pool — BOTTO + BOLD stablecoin — on the Base network, seeded in collaboration with The DeFi Collective (TDC).

The pool is designed to serve as a powerful companion to the DAO’s mainnet POL, enabling more cross-chain strategy and real-time interactions with a wider stablecoin userbase thanks to Coinbase’s recent integration of trades for tokens on Base directly via the Coinbase app.

• Objective: Expand Botto’s economic architecture with a new on-chain venue tailored to active usage and experimental integrations such as via the Coinbase app’s recent incorporation of trading on Base.
• Strategic Benefits: Establishes liquidity on a cheaper, faster chain; complements Botto’s mainnet POL in collaboration with TDC as an aligned and committed crypto native partner to help further advance Botto’s outreach.

Proposal Specification

Botto DAO donates $25K in BOTTO to TDC as funded from a portion of mainnet POL being repurposed.

TDC commits $25K in BOLD to launch the BOTTO + BOLD pool on Aerodrome under their oversight as a basic volatile pool with a 0.3% trading fee.

TDC commits 100K veAERO voting power to support the BOTTO + BOLD pool with votes weekly.

TDC commits 20% of the BOLD it apportions for Aerodrome bribes weekly to veAERO voters for the BOTTO + BOLD pool, as allocated from its Liquity V2 PIL initiative.

Timeline

• Pool deployment by TDC within two weeks of BIP passing.
• Outreach initiatives coordinated in collaboration with TDC after deployment.

Criteria of Success

• Pool remains liquid and usable for DAO tools and partner integrations.
• Trading activity occurs regularly and with low fees.

Disadvantages/Risks

• Base network may introduce new risks or require unexpected maintenance.
• Risk of low usage if not integrated with real use cases.