Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[MCH-318-157] feat: add a way for automated tokemak claims #157

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

charlesndalton
Copy link

@charlesndalton charlesndalton commented Apr 21, 2022

Description

For our tokemak strats, we need to call a special function to claim TOKE (this one). Ideally, we'd automate this, which isn't possible through the existing keep3r jobs. This is one idea on how to allow for this.

Essentially, we'd have a new type of job called a CalldataV2Keep3rJob where Yearn would be able to specify an approved function selector for a strategy. A keep3r would call function work(address _strategy, bytes calldata _callData), passing in the required calldata. In our case, the approved function selector would be the bytes4 equivalent of claimRewards, and keep3rs would be able to call claimRewards by passing in this information.

Since there is additional information required by the keep3r, we'd also need to add some docs on how they can get this calldata.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Text update
  • Other

Change details

Detail the changes that occur if necessary.

Resources

Any screenshots, links or relevant resources to explain better the changes.

@yearn-linear-gh-sync yearn-linear-gh-sync bot changed the title feat: add a way for automated tokemak claims [MCH-318-157] feat: add a way for automated tokemak claims Apr 21, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant