Note: Snapshot is only a summary and may leave ambiguities that are covered in the full BIP in the forum which takes precedent.
BIP-100 proposes introducing VP Delegation as a first-class protocol primitive. Any participant with 10,000 $BOTTO staked may create a VP pool, commit their own Voting Points to it, and invite other wallets to vote on fragments using that pool's VP. Pool-cast VP counts toward Active Rewards identically to individually cast VP. A buyback-and-burn tax — variable, set by the pool creator, with a minimum of 5% — applies to all pool-generated rewards, with the remainder split between the pool creator and members according to a creator-defined ratio.
Growing participation in Botto is in part a problem of economic planning that leads to more overhead and centralized control in order to avoid sybil risks. The 1 token = 1 vote system functions as a way of tying skin in the game to considered voting and training of Botto. The weakness of that system is the ability to buy governance power rather than earn it by reputation, concentrating decision making and rewards in fewer hands. The counterbalance is Botto's autonomy, where large holders threaten the integrity of Botto's authorship and decentralization if they fully exercise their power.
However, while this has led to many larger holders holding off on using their large decision making power, we have seen that does not completely eliminate vote dumping that can disenfranchise smaller holders. VP delegation is a way to solve for many of these related issues by decentralizing economic planning and determining which reputation signals matter, while keeping the original system intact that avoids a more drastic and heavy change in economy.
Simply, VP delegation allows stakers to commit their VP to a pool that is distributed based on qualifications they determine. The stakers retain their decision making power in the kinds of signals they think are important while distributing it to many more perspectives that represent that signal. Those with relevant reputation then also get a larger say — and share of rewards — in Botto's training, driving larger participation.
Because pool creators are free to design pools to their choosing, it does not rely on a centralized authority or costly consensus building across the DAO to establish and manage. The pool system opens up natural on-ramps for external communities — NFT collectives, art schools, DAOs, friend groups, and others — to participate in curation, further decentralizing Botto.
An additional benefit: holders can create a pool from a cold wallet and delegate to a single hot wallet, eliminating the need to connect a cold wallet to sign in every week.
At the outset, deliberate onboarding of both large holders and external communities will be key to ensuring this gains traction. Working with engaged groups will be a good test bed for onboarding flows that not only get them initially engaged in a light way, but also bring them into deeper participation. We recommend some pool creators set up pools for long-term participants and adjacent communities (e.g. Punks, Art Blocks, 6529) who are already familiar with Botto and would quickly recognize the boost in their voting weight.
This specification is subject to change during development execution — a project of this scope can adjust significantly — but provides sufficient detail for the DAO to flag any particular areas of concern and align on now.
1. Pool Creation
Any participant with at least 10,000 $BOTTO staked may create a pool. The pool creator sets the following parameters at creation:
Pool parameters may be edited by the creator after creation. Changes take effect at the start of the next round, not mid-round.
2. VP Commitment
The pool creator commits VP from their own balance into the pool at any point during a round. Committed VP is locked for the remainder of that round; additional top-ups are permitted at any time. All VP sources are delegatable — baseline sign-in VP, staking boost, Pipe boost, and Access Pass boost may all be committed.
Members do not contribute their own VP to the pool. Their personal VP balance is unaffected by membership; they may continue voting individually with their own VP outside the pool.
3. Member Access
Pool creators may bring members in via two mechanisms:
All delegate wallets must hold a minimum of 100 $BOTTO to be eligible to receive rewards from a pool. Pool creators or community sponsors may provide this stake on behalf of members who do not hold $BOTTO.
4. Voting
Members vote with pool VP rather than their own. Votes are attributed to the individual member who cast them for activity records and reward attribution. The member's per-round spend is subject to the per-member cap set by the pool creator.
Voting behavior mirrors personal VP: votes are mutable throughout the round and finalized at round close. The UI default is auto-switch — personal VP is spent first; once depleted, the system draws from pool VP in priority order across the member's pool memberships.
5. Round Close
At round close, votes are finalized and submitted to Botto. Unspent pool VP is forfeited.
6. Reward Distribution
Pool-cast VP counts toward the existing Active Rewards formula (currently: 40% of auction revenue, paid in $BOTTO at ETH-denominated value) identically to individually cast VP. The pool acts as a single wallet in this formula. Rewards are distributed off-chain in three steps:
Example: pool earns 1,000 $BOTTO. Buyback tax (5%) = 50 $BOTTO. Of the remaining 950, at a 30/70 pool creator/member split: pool creator receives 285 $BOTTO; members share 665 $BOTTO pro-rata to their VP spent.
7. Unstake Rules
8. Pool Creator Removes a Member Mid-Round
Votes already cast by the removed member stand. The member cannot cast new votes. Their reward share for the round is calculated based on VP spent before removal.
9. Karma Attribution
Karma earned from a pool-cast vote goes to the individual member who cast the vote, not the pool creator. Karma is a per-user reputational currency tied to the actor performing the action.
Phase 1 implementation is estimated at approximately 20 engineer-days (~4 weeks, 1 full-stack engineer). This covers qualification-gated pools, both invite mechanisms, member leave flow, auto-switch voting, variable buyback tax, and reward split.
Phase 2 (multi-pool-creator pools, additional qualification types, manual VP-source selector, notifications, pool discovery, hardening) is estimated at a further ~20 engineer-days, scoped after Phase 1 data is available.
Delegate and pool creator onboarding and marketing rollout ~15 days, covering outreach to delegator groups, onboarding materials and presentations, and comms planning and execution.
Approximate equivalent in overhead costs: $30K.
We are in discussion with a patron to support some of this development. More support would help enable more customization in an earlier phase for special requests, and commit more to direct onboarding efforts with external groups.