• © Goverland Inc. 2026
  • v1.0.5
  • Privacy Policy
  • Terms of Use
Beanstalk FarmsBeanstalk Farmsby0x6a93946254899A34FdcB7fBf92dfd2e4eC1399e70x6a93…99e7

BFP-44: Hire Lawne Bean

Voting ended almost 4 years agoSucceeded

Proposer: Dumpling

Proposal: Hire Lawne Bean as a Part-time Middleware Developer in the Engineering Department.

Resume: Lawne Bean is a full-stack software engineer and will be joining the Middleware team at Beanstalk Farms. They are currently working as a Product Manager, but they have spent a majority of their career working as a software engineer (mobile & backend) at various startups in both the micro mobility space and within web3.

Role Definition: Lawne Bean will work closely with funderberker on Middleware responsibilities including but not limited to:

  • Take on a major role in designing and developing the typescript SDK;
  • Efficiently gather and calculate state of Beanstalk Protocol and its users;
  • Significantly simplify UI development;
  • Enable third party developers to easily integrate with Beanstalk;
  • Simplify the internal technical process of expanding to new LPs and DeFi projects;
  • Coordinating with the subgraph developers to ensure availability of data through the SDK; -Designing a fallback system in TS for the subgraph event data; -Standardizing off-chain data calculations via implementations in ts; and
  • Standardize data typing throughout Beanstalk internal code via implementation in ts developing the frontend application. This will include re-architecting and implementing a new frontend codebase, optimizing page calls to speed up latency, and organizing the existing code. This is important for both scalability and for open-sourcing at the end of Q1.

Payment: 6066 Beans per month, paid twice per month, as of February 16th, 2022, though Q1 2022.

Commitment: Part-time (20+ hours/week). At will. To be potentially expanded with mutual agreement in Q2 2022.

Off-Chain Vote

Yes, hire Lawne Bean
1.29M 100%
No, do not hire Lawne Bean
0 0%
Download mobile app to vote

Timeline

Mar 03, 2022Proposal created
Mar 03, 2022Proposal vote started
Mar 09, 2022Proposal vote ended
Oct 26, 2023Proposal updated