# $BEND Token Burn, Lender Rewards, and Buyback Strategy

- Space: [BendDAO](https://snapshot.box/s:benddao.eth.md)
- Author: 0xF40Fd88ac59A206D009A07F8c09828a01e2ACC0d
- State: Passed
- Voting type: Basic
- Start: 2025-07-31 19:00 UTC
- End: 2025-08-10 19:00 UTC
- Votes: 9
- Quorum: 1 voting power
- Discussion: https://governance.benddao.xyz/t/bend-token-burn-lender-rewards-and-buyback-strategy/778
- Open in Snapshot: https://snapshot.box/#/s:benddao.eth/proposal/0x14a3bf874b526bb8c51cfa2c13c4149e6bb3f30631bb06e14e54af8ac640461c

## Results

- For: 113,158,801.7 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

I’m proposing a three-part strategy to stabilize the $BEND token, boost lender activity, and rebuild confidence post-Azuki crash. This leverages the community’s input and aims to address our current challenges with bad debt and low engagement. Below is the detailed plan: Treasury BEND Token Burn (30-50%) Action:

**Burn 50% of the $BEND tokens held in the treasury over 5 months (e.g., 10% monthly burns):**
* Execution: Announce the burn schedule publicly via Twitter, Discord, and a blog post. Execute burns transparently, sharing transaction hashes to verify.,
* Purpose: Reduce circulating supply to support token value and create a marketing event to restore community trust.

**Reintroduce Lender Rewards:**

* Action: Offer $BEND rewards to lenders for a 3-month trial period to drive lending activity.
* Structure: Fund via protocol fees like before.
* Execution: Promote heavily across socials and NFT communities to attract new and returning lenders.
* Purpose: Incentivize lending to increase platform liquidity and engagement.,

**Buyback and Burn Program:**

 *Action: Allocate 20% of protocol revenue (e.g., lending fees) to monthly $BEND token buybacks, with immediate burns of purchased tokens.,
* Execution: Conduct buybacks on open markets, announce each event, and share burn proofs to maintain transparency.,
* Purpose: Create consistent demand for $BEND, further reduce supply, and tie token value to protocol performance.,

**Implementation Notes:**

* Timeline: Start the treasury burn and lender rewards within 1 month of approval, with buybacks beginning once revenue stabilizes (est. 2-3 months).,
* Transparency: Regular updates (e.g., monthly reports) on burns, rewards distributed, and buyback progress via Discord and Twitter.,
* Monitoring: Track lending volume, token price, and user growth to assess impact and adjust (e.g., tweak reward rates or burn pace).,

**Impact Assessment:**

* Potential BenefitsIncreased Lender Activity: Rewards can attract new and returning lenders, boosting platform liquidity. A 10-20% increase in lending volume is possible if marketed effectively.,
* Token Value Support: Burning 50% of treasury tokens and ongoing buybacks could reduce circulating supply by 20-35% over 6 months, potentially increasing BEND’s price if demand holds.,
* Community Confidence: Transparent burns and rewards signal proactive governance, likely improving sentiment among token holders and users.,
Marketing Buzz: Public (twitter & discord) messages of burns and buybacks can draw attention from NFT and DeFi communities, potentially onboarding new users.,

**Potential Risks:**

* Treasury Depletion: Burning 50% of BEND tokens reduces flexibility for future needs (e.g., partnerships). Mitigated by spreading burns over months.,
* Reward Costs: High reward rates could strain finances if lending revenue doesn’t grow. Mitigated by a 3-month trial and fee-based funding.,
* Market Volatility: Buybacks may not lift token price if broader market sentiment remains bearish (e.g., ongoing NFT market weakness). Mitigated by tying buybacks to revenue.,
* Execution Risk: Poor communication or delays could dampen community support. Mitigated by clear timelines and regular updates.

**Voting:**
Voting Quorum: Approximately 40M veBEND (10% of the total supply).
Pass Rate: Over 70% approval.
The voting will last for 10 days.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

