• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
BeefyBeefyby0x650C0Ed459d82335AfdaD70794b9a61b7795AA6Aalltradesz.eth

AllTrades into the Beefy Core

Voting ended about 4 years agoSucceeded

** AllTrades' Associated Statement

  • Will continue to lead localization, including a Beefy-controlled tie-in of the CrowdIn SaaS to automate it. Actually, this effort has already been funded, so I will fulfill this over and above the rest of the work about to be described.

  • I seek a role as a fix-it or improve-it resource who takes on valuable initiatives for Beefy, addressing discrete pain points. That involvement can be in a development or project-management capacity or both. In that vein, Cowllector and analogous backend automation tooling seem good first targets.

  • In collaboration especially with @Moonster, will take the on stabilizing and extending Cowllector as Beefy's secondary keeper process. To fill in gaps alongside the Gelato solution being rolled out. After stabilization, this will include automated triggering of end-of-lifing (EOLing) vaults when it's detected that farm emissions have dried up. With respect to the initial "stabilization" of Cowllector, aspects to receive attention include

    • Development of a mechanism to harvest only strats not managed by Gelato.
    • Fix existing bugs, like failure to follow the current schedule and proper detection of the presence of harvestable rewards in some cases.
    • Document the technical system which consists of multiple interrelated scripts whose interoperation is not outlined anywhere. Also for any areas adjusted, provide in-line documentation of what's intended by the code.
    • Rationalize the reporting. Current logging is wastefully verbose and does not yet provide clear reporting of obvious items needing attention.

With respect to auto-EOL, architectural decisions will consider - use of Tenderly tooling to monitor strats as an event listener and send rules-based triggers, and/or - using the cronned Cowllector to do related or similar instead or alongside - if desired, calling panic() on identified vaults where rewards have stopped - if desired, posting alerts of an EOL having been carried out or as being needed on identified vaults - if desired, automated edition and PRing of the vault descriptors the app uses to surface status in the UI/UX

  • Because some learning curve in automating blockchain interaction remains for me, I'll accept a reduced rate of compensation through Q2. Indeed over the last months I have done much independent learning to put myself in position to reasonably offer this. My aim continues to be to become ever more useful within Beefy.

  • More medium term, I look to grow into helping Beefy streamline on its development and backend-maintenance fronts. This will involve learning those ropes from Moonster and the rest of the backend dev team. Example initiatives would include fostering TypeScript in the v2 app and collaboratively establishing coding standards and coding-pattern best practices, and implementation of a framework and culture by which to have such honored on-going.

  • Lead an effort to document and rationalize backend areas that would benefit from it. For instance, tightening up of safety-scoring in vaults. Collaboratively proselytize the application of such guidelines by devs.

  • Help with marketing at conferences and, if desired, on podcasts.

Compensation ask through Q2: $4.5K/month, $2.25K for the last half of Februrary

Off-Chain Vote

Yes
9.91K 98.7%
No, not yet
133.5 1.3%
Download mobile app to vote

Timeline

Feb 27, 2022Proposal created
Feb 28, 2022Proposal vote started
Mar 03, 2022Proposal vote ended
Oct 26, 2023Proposal updated