Skip to content

Latest commit

 

History

History
55 lines (36 loc) · 3.38 KB

bfcp-b-08-remove-guy.md

File metadata and controls

55 lines (36 loc) · 3.38 KB

BFCP-B-8: Remove "guy" (fka "austin") from BFC (Again 2x)

Proposed: December 1, 2023

Status: Failed

Link: Snapshot, Arweave


The farm needs a more transparent group of BFC members to keep the community engaged. Currently, all timelines and project updates are discussed behind closed doors.

In addition, several bot operators (some of whom are in direct contact and affiliated with current BFC members) have direct knowledge of development timelines and product development that help maximize their current stakes while keeping this information hidden from the broader farmer community to react and operate on the same playing field.

image

"When a government betrays the people by amassing too much power and becoming tyrannical, the people have no choice but to exercise their original right of self-defense – to fight the government.” — Alexander Hamilton

Proposer

Beanstalk Farmer (not a troll or proposal based on frustration as noted by BFC minions to delegitimize the proposal)

Summary

Remove "guy" (fka "austin") from BFC. We proposed the removal of "guy" via BFCP-B-1, BFCP-B-4 and BFCP-B-6 but the current BFC members failed to announce the proposal on Discord to notify farmers (how convenient they only announce proposals they agree with). In addition, they had their minions delegitimize the proposal to reduce voter turnout. We hope the BFC makes the proper announcements for this proposal (we will keep proposing until BFC presents it to the farmers via Discord announcements).

Quorum Note

Quorum is 35% of total outstanding Stalk participating in the vote.

Voting Choices

  • Keep "guy" (fka "austin") as BFC member
  • Remove "guy" (fka "austin") from BFC

Background

According to Beanstalk Farms governance, at least 3 BFC members will control Beanstalk Farms. Accordingly, BFCP-C-3 extended the terms of guy, mod323, sweetredbeans until end of H2 2023.

Proposal

Considering the current BFC team members are not actively engaged with the Beanstalk community, this BFCP is proposed to remove the current BFC member "guy" by rescinding BFCP-C-3.

Immediately following the successful removal of the current BFC members, we will hold an emergency BIP to elect 3 new BFC members into the BFC that will engage more with the community and provide substantive updates and timelines.

image

Rationale

Need a more transparent group of BFC members to keep the community engaged. Currently, all timelines and project updates are discussed behind closed doors.

New BFC Members

Going forward BFC members should be able to effectively communicate development and audit plans and timelines. Several Farmers have effectively done this type of work in other communities (some of which are currently working on protocols that would benefit Beanstalk). We will propose a list of names as we progress with the removal of the current BFC members.