Resolving the Quadratic issues in Lock2Earn

This discussion stems from the previous Discourse thread regarding VeDelegate’s fund flow.

I am creating this thread following Favo’s invitation to discuss VeDelegate’s L2E design in a dedicated thread.

For context, it is important to understand why this discussion is needed:

  1. VeDelegate is the main beneficiary of L2E term voting (source)
  2. L2E’s multi-TBA structure creates an artificial quadratic boost for multi-term users (source)

When multiple TBAs vote under Quadratic Voting:

  • It artificially inflates VD’s weekly allocation;
  • It directly increases the baseline for the weekly 30% withdrawals;
  • It dilutes the fair share of weekly allocations going to other ecosystem apps;
  • It compromises governance integrity by allowing to vote with multiple accounts.

Here is @favo’s response from the previous thread:

Thanks for digging into this, Morb. We’ve brought the Lock2Earn limit back down to three terms per user. I understand your concern is about how those terms vote, not just how many a user can open.
Using one voting wallet per owner is an interesting idea. In our setup, it would mean reworking how rewards are tracked and distributed for each term, including terms that are already active. It’s not a straightforward upgrade, and we’re not planning to make that change at this point.
I’ll leave the product discussion here. I don’t think comparing figures accumulated over two years with today’s market cap is a helpful starting point for discussing product changes. We’ll keep listening to feedback, and I’d like to hear from more people across the community before deciding what to prioritize. I’m happy to continue that conversation in a separate thread focused on the design.

While lowering the cap from 10 to 3 was an initial step, it does not resolve the issue. Even with 3 TBAs, splitting a position creates an artificial ~73% quadratic boost. At the same time, capping users at 3 terms restricts user flexibility for those who want multiple terms.

The core issue is the multi-TBA voting footprint, regardless of which app receives the vote. It is not the frontend user experience that creates this problem - it is the underlying smart contract design.

The cleanest solution is allowing users to open as many L2E terms as they want on the frontend, while mapping all of a user’s term NFTs to 1 dedicated voting TBA under the hood using internal accounting.

To address the concern about development burden and active positions: nobody is asking VeDelegate to disrupt active terms or change how current rewards are distributed. Existing active terms can simply run until their natural maturity. The 1 TBA architecture would only apply to newly created and renewed terms.

User experience is protected, risks of fund migration avoided, and governance issues resolved.

@favo Lowering the limit from 10 to 3 shows we’re already on the same page about the effect multi TBAs have on governance. Since this sunset approach lets your existing terms mature safely without touching active rewards, is this an upgrade you’d be willing to plan for new terms?