Poster: Allow for reward per task #74
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
price is fetched from task data under "dataffect/reward"
|
The latest updates on your projects. Learn more about Vercel for GitHub. 4 Skipped Deployments
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The price is fetched from task data under "dataffect/reward".
This can be set using a column in a CSV, for example.
To have consistent behaviour that is less prone to mistakes, I changed
reward values of fetchers to lamports everywhere (this means on the
fetcher form, you must now enter a price value of
1000000torepresent 1 EFFECT). We must update all existing Steps to reflect this
once this gets deployed.